How we work
Five steps from a blank page to a product in use.
Every project runs on the same order: discover, design, build, ship, scale. Short weeks, a working demo at the end of each, and one team that owns the product from the first call to the second year.
The work, in order.
The numbers here are a sequence, not a slogan. Each step ends with something you can open, click, or ship, and a clear decision about what comes next.
Discover
We map the problem before we open a design tool. Working sessions with you, and where it helps your customers, to pin down who the product is for, what it has to do first, and where AI removes real work instead of decorating a screen.
What you get
A written product brief: scope for the first version, the risky assumptions, and a build plan with a fixed sequence.
Rough timing
About one week.
Design
We design the core flows as real, clickable screens, not static pictures. Interface, copy, and edge states are decided together, so engineering builds from something the whole team has already used and agreed on.
What you get
A clickable prototype of the main flows, plus the design tokens and components the build will reuse.
Rough timing
One to two weeks, overlapping with Discover.
Build
Design and engineering work as one team, in weekly cycles. We build the product for real: the data model, the interface, and the AI or automation where it earns its place. You see a working build at the end of each week, not a status deck.
What you get
A working product that grows every week, a demo link that always reflects the latest state, and weekly notes on what shipped and what is next.
Rough timing
Usually three to five weeks for a first version.
Ship
We put the product in front of real users: production setup, analytics, and the last mile of polish that decides whether people come back. Launch is a checklist we have run before, not an event we improvise on the day.
What you get
A live product on your domain, wired for analytics and error tracking, with a short runbook for your team.
Rough timing
Launch week, once the build is signed off.
Scale
We stay on as your product team. We watch how the product is actually used, fix what breaks, and build the next version against real usage instead of a spec that has aged. This is the part most agencies skip; it is the part we were built for.
What you get
A roadmap driven by usage, ongoing engineering and design, and a partner accountable for the product working in the world, not a repo handed over at launch.
Rough timing
Ongoing, month to month.
What holds across every step.
The order changes what we do each week. These four do not change at all.
- Weekly demos. Every step ends with something you can open and try, so progress is visible and never a surprise at the end.
- One team, no handoff. The same people design, build, and ship, so intent survives from the first sketch to production.
- AI where it pays. Models go where they cut work or unlock a feature, measured in hours saved, not slides filled.
- Owners, not vendors. We run our own products, SellEzzy and EzzyBooks among them, on this exact process, so we plan for cost, scale, and the second year.
Questions about the process.
Most first versions ship in six to eight weeks. Discover and Design take one to two weeks together, Build runs three to five weeks, and Ship happens in launch week. Larger products take longer, but the weekly cadence stays the same.
A working build you can open, a demo link that reflects the latest state, and a short note on what shipped and what is planned next. Nothing is hidden until a big reveal.
Yes. If Discover is already done, we review your brief, adjust scope where needed, and start at Design or Build. The steps are an order, not a fixed contract.
We stay on in the Scale step as your product team: engineering, design, and a roadmap driven by how the product is actually used. It is month to month, not a fixed retainer you cannot leave.
Both. A first version is usually scoped as a fixed sequence with a target window. After launch, most teams keep us on month to month for the next versions.

