DreamBiz generates projects and pitch decks from a single prompt.
Four surfaces rebuilt in a month, and partners stopped asking if it was a prototype
One month. Four platforms. Zero previous designers. I rebuilt the entire product — from broken flows to something developers could build from and partners could demo.
Project, Pitch Deck, Chat, and Mobile — all redesigned with a unified design system underneath.
Users who previously dropped off at the empty chat now completed their first project or pitch deck.
Fewer dev questions and QA regressions. A proper design system and annotated specs meant developers built it right the first time. Less back-and-forth after QA review.
Building what was missing, from the structure up
When I joined, the product had been designed by the PM and built by engineering wherever screens were missing. The result: patterns without a system, screens without flows. My job was to get it to a state where the business could demo it, developers could build from it, and users could actually finish something.
- Contribution
- Product design, Design system, UX audit, Motion
- Duration
- 1 month
Nothing was shared between the four surfaces, so each one had broken in its own direction.
DreamBiz had no shared component library. Each developer and each screen used independently built components — unlinked in Figma, drifting in production. There was no way to change one thing and have it propagate.
The platform's core value is creating projects and pitch decks through a chat. But when a new user lands, the chat is empty — and there was nothing guiding them toward the first action.
The product could generate complete projects and pitch decks from a single prompt — but new users faced a blank input with no examples, no guidance, and no entry point. The path from arrival to first creation didn't exist visually.
The most visually inconsistent surface. Built section by section by engineering without design input — each block had its own visual logic, typeface choices, and spacing. No shared typographic scale, no spatial rhythm, no brand identity.
The pitch deck editor was the surface partners would see first in a demo. It needed to read as a real product — polished enough that no one would ask “is this a prototype?”
The shared system first. After that every surface got cheaper to fix.
Built a component library from scratch: master components with auto-layout, semantic naming, and design tokens. File restructured by surface with a dedicated system page. One change now propagates everywhere.
Designed a contextual empty state: example prompts tailored to the platform, clear entry points to start a project or pitch deck, and visual cues that reduced blank-page friction.
Applied a unified design language across all project sections — single typographic scale, one spacing system, consistent card and section patterns. The page now reads as one coherent surface.
Redesigned the slide editor with consistent layout templates, a defined grid, and a refined output view. Partners could be demoed the full pitch deck flow without caveats or qualifications.
Four surfaces. One month. After the first partner demo, no one asked whether this was a prototype.
Happy to walk through the parts that did not fit here. Let's get on a call.
