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.
Schedule a callQuick 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.
By Shaheer Malik · Updated
The plan
Product design in 14 days: the day-by-day 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
What's included in product design for $1,999
Everything needed to launch — nothing padding the invoice.
Who books this
Who product design in 14 days is for
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
Why teams book product design
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 product design in 14 days is the wrong choice
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.
What it costs
How much does product design cost?
On this sprint, product design costs a fixed $1,999 for 14 days of work. The price and the schedule are agreed in writing before anything starts, and the price does not move if the work takes me longer than planned. It covers all 8 items listed under what's included.
In the price
- Everything in the list of what's included
- The 14-day schedule, written down before you commit
- Changes inside the agreed scope
Paid separately, directly by you
- New scope added after the plan is agreed, priced in writing before work on it starts
Fixed price, hourly or a monthly retainer
| Compare | This sprint | Hourly | Monthly retainer |
|---|---|---|---|
| When you know the total | Before work starts | When the work is done | Month by month |
| If it takes longer than planned | I absorb it | You pay for the extra hours | You pay for the extra months |
| A change of scope | Priced in writing first | More hours on the invoice | Added to the queue |
Why I price this way, and when it is the wrong model, is on no hourly rates, and what happens from first message to launch is on how it works.
Where this sits on the price list
- Every sprint is priced on one published ladder: $700 for 5-day sprints, from $1,999 for 14- and 21-day builds, and from $2,500 for 30-day apps. Every price is on pricing.
- Not sure what the first version should include? The 5-day discovery sprint ends with a written scope and a fixed quote, and its $700 comes off the build if you book within 30 days.
- After launch, the monthly partnership covers a steady stream of changes for $2,500 a month, and you can pause it.
- For a bigger or different build, the project cost calculator and the MVP timeline estimator give a first number in a minute.
Questions
Product design: your questions answered
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.
An organised Figma file you own, a component library, a clickable prototype, and a handover call with your developers. The design decisions are written down beside the screens.
A coherent v1 product — typically 20 to 35 screens once states are counted. If your scope is clearly larger, I will say so before we start rather than run out of fortnight.
That is what the component library and the handover call are for. Designs that look finished but cannot be built are the usual failure here, so the system comes before the polish.
Then this is the wrong first step. Book the 5-day discovery sprint — designing an undecided product is the most expensive way to decide it.
Not in this sprint. This is design execution. If you need to find out what users want first, that is different work and I will point you at someone who does it properly.
Hiring a designer remotely?
If you are weighing who to bring in, hire a remote product designer covers who this sprint fits, what your developers get at handover, and when discovery comes first.
Every state designed, so developers do not have to guess
A 14-day product design sprint ships every screen with its empty, error and loading states, a component library to build against, a clickable prototype and a handover call. Fixed price: $1,999. No code ships.
| In scope | Out of scope |
|---|---|
| Every screen, including empty, error and loading states | Development: that is what the build sprints are for |
| A component library and a clickable prototype | Retrofitting a design system across a large existing product |
| Two rounds of revisions inside the fortnight | Pixel-matching a competitor |
Design and handoff bar
- Every screen has its empty, error and loading states
- Screens are built from the component library, not one-off layers
- The prototype clicks through each main flow
- Design decisions are written beside the screens
- Your developers have asked their questions on the handover call
Soft planning rule (not an SLA): lock the primary job early, review edge cases before launch week, and keep accounts and source in your name at handoff.
Extra questions
Which tool is it designed in?
Can the prototype be shown to investors?
Does it cover mobile and desktop?
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.