Ship It Live — $1,999 flat
Design + build + deploy · kickoff in 24h · limited slots
Ship It Live · design sprint
Every screen designed, handed over in 14 days.
For teams with developers and no designer. Every screen, every state, a component library and a prototype real enough to test — handed over in a fortnight.
Quick answer
A product can be fully designed in 14 days for a fixed $1,999: every screen including empty states and errors, a component library your developers build against, and a clickable prototype. No code ships — this is for teams who already have developers and need the design decided.
The plan
Day one to day 14, written down.
You get this schedule before you commit, not after. If a phase slips, that is mine to absorb — the price and the date were agreed before anything started.
- 1
Days 1–2
Flows
The journeys that matter, mapped before anything is drawn. What the product does, in what order, and which screens actually exist.
- 2
Days 3–8
Screens
Every screen designed against real content. You see the core flow first, so anything I have misread surfaces while it is still cheap to change.
- 3
Days 9–11
States and system
The parts nobody designs — empty, loading, error, partial — plus the component library the build will be made of.
- 4
Days 12–14
Prototype and handover
Wired into a clickable prototype, the file organised and documented, and a call with the people who have to build it.
What $1,999 gets you
Everything needed to launch — nothing padding the invoice.
Who books this
Built for
Teams with engineers who are being asked to invent the UI as they go
Founders who need something convincing in front of investors or users
Agencies who have the client and the developers but no design capacity
Real situations
Five ways this shows up, and what actually fixes it.
Not hypothetical — the shape of the problem before someone books this sprint, and the specific part of the build that resolves it.
Situation 1
Engineers designing by default
A capable engineering team is shipping features while inventing the interface as they build, so the product works but feels like five different products depending on the screen.
Every screen is designed up front against one component set, so the team builds from a decided design rather than deciding it at four in the afternoon.
Situation 2
A demo that has to hold up in a room
A founder has a pitch in a fortnight and a product that is either half-built or entirely hypothetical, and screenshots of a real-looking interface will decide how the conversation goes.
A clickable prototype lands inside the window — real enough to walk through on a screen share, without anyone having to build the backend first.
Situation 3
The happy path is the only path
A product has been designed for the demo — the version where data exists and nothing fails — and every empty, loading and error state is being improvised in code.
The states nobody designs are part of the scope here: first run, empty, loading, partial, failed and offline, all decided before they become bug reports.
Situation 4
An agency with the client but no designer
An agency has won work they can build but not design, and subcontracting the design usually means losing control of the timeline.
Fixed scope, fixed fortnight, fixed fee, with a Figma handover their developers can work from — and I stay invisible to their client if that is how they want it.
Situation 5
Figma that nobody can build from
A team has a design file from a previous freelancer that is a scatter of loose frames with no components, no naming and no record of why anything was decided.
The handover here is organised and built on components, with the decisions written down next to the screens, so it survives the person who made it leaving.
The honest part
When 14 days is the wrong answer.
A fixed deadline only works when the scope genuinely fits inside it. These are the cases where I will tell you so rather than take the booking.
Design with nobody to build it. If you do not have developers, you want a build sprint — a Figma file is not a product, and I would rather say that than sell you one.
Design systems for an existing large product. Retrofitting a system across a mature product is its own project and does not fit a fortnight.
Pixel-matching a competitor. I will take the reference happily; I will not take it as the brief.
Inside the 14 days
- Every screen designed — flows, empty states, errors, loading, not just the happy path
- A component library your developers can build against
- A clickable prototype, real enough to test and to show investors
- Mobile and desktop where the product needs both
- A handover call with whoever is building it
- The decisions written down beside the screens, not just the screens
- The Figma file is yours, organised, at handover
- Two rounds of revisions inside the fortnight
Quoted as one number before day one. A week running long is mine to absorb.
Outside the line
- Design with nobody to build it. If you do not have developers, you want a build sprint — a Figma file is not a product, and I would rather say that than sell you one.
- Design systems for an existing large product. Retrofitting a system across a mature product is its own project and does not fit a fortnight.
- Pixel-matching a competitor. I will take the reference happily; I will not take it as the brief.
Real work, sized and priced separately. You hear it before you book, not at handover.
Questions
Before you book
No. This is design only, which is the point — it is priced for teams who already have engineers. If you need it built too, the build sprints include design.
Other sprints
14 days from now, this could be live.
A 30-minute call decides whether the scope fits. If it doesn't, I'll tell you what would.