Article5 min readUpdated
Design Before Development: Why It Cuts Rework Cost
Design before development lowers rework cost. See what changes during development really cost, with a worked example and when to skip it.
Should you do design before development?
Yes, for most products with more than a few screens. Design before development means that a designer plans the screens, the flow and the look first, and developers build from that plan. The main reason is cost. A change on a drawing takes minutes. A change in built code takes days.
This article is only about cost and rework. If you want to know whom to hire first, read designer or developer: who to hire first. Here we ask a narrower question: what does the order do to your bill?
What does changing design during development really cost?
It costs the building time, the testing time and the time to fix what the change breaks. A change in a design file costs only the designer's edit.
Here is a hypothetical worked example. The numbers are invented to show the method.
Suppose a booking app has 24 screens. The owner sees the working app and decides that login should come after browsing, not before. This touches 4 screens: login, OTP, home and booking summary.
If the change is made after building:
- 4 screens × 1.5 developer days = 6 developer days.
- Suppose a developer day costs ₹2,000: 6 × ₹2,000 = ₹12,000.
- Add 2 days of re-testing: 2 × ₹2,000 = ₹4,000.
- Total: ₹12,000 + ₹4,000 = ₹16,000.
If the change is made in the design file:
- A designer edits 4 screens and links them again.
- This is about half a day of design time.
The same decision costs ₹16,000 later and a small design edit earlier. One such change may not hurt. But products have many such changes, and each one lands on the most expensive stage.
The change also costs time. The developer waits, other work stops and the launch date moves. The money is the part you can count. The delay is the part you feel.
Why do developer estimates improve when designs exist?
Estimates improve because every developer prices the same list of screens. Without a design, "build a booking app" means different things to different people.
Imagine you ask two developers to quote. One imagines 12 simple screens. The other imagines 30 with admin features. One quotes ₹1,50,000 and the other quotes ₹4,00,000. You cannot compare them. They are not quoting the same product.
With a design file, both see the same 24 screens. They can count the screens, spot the hard parts and say "this payment screen needs extra work". Quotes still differ, but now the difference is about price and skill, not about imagination.
A design file also reduces the risk of a surprise bill. When a developer quotes from screens, the bill is closer to the quote, because there are fewer unknowns. Read Figma developer hand-off checklist to see what a developer should receive.
What do you need designed before the first line of code?
You do not need every pixel. You need enough to remove the expensive guesses.
- The list of screens. Every page or screen the product will have.
- The flow. The order of steps for each main job, with what happens on failure.
- Wireframes. Simple black and white layouts that show what is on each screen.
- The main screens in full design. At least the screens that carry money or trust, such as checkout.
- Rules for repeating parts. Buttons, colours and text sizes, so developers build them once.
The work in my own process follows this order: understand, map the flow, wireframe, design the interface, then prototype and hand off. Each step answers questions that developers would otherwise guess.
How long does design delay the start of development?
Design adds time at the start, but it often saves time overall. App or website design usually takes 2 to 4 weeks in my practice, depending on the number of screens and user roles. See how long does design take for a fuller breakdown.
You do not have to wait for all of it. Design the main flow first. While developers set up the base, such as the server and database, the designer completes the remaining screens. This overlap shortens the wait.
When is development first fine?
Starting with code is fine in some cases. It would be dishonest to say design always comes first.
- A very small tool. If one person builds a simple tool for their own use, a drawing adds little.
- A technical test. If the question is "can this be built at all?", a developer needs to try, not a designer.
- A fixed, known pattern. If you are building a standard admin table, the developer may already know the pattern.
- No budget for design and building together. A rough build to find out whether anyone wants the product can come before design. Just accept that you may rebuild.
In these cases, plan for rework. Say to yourself that the first version is a test, and do not treat it as final. For help with deciding what to build first, read MVP design: what to build first.
What goes wrong when developers guess the design?
Developers are skilled at building. They are not paid to decide your business flow. When no design exists, a developer must choose many small things alone: the order of steps, the label on each button, what happens when a field is empty.
Each guess may be reasonable. But the owner sees it only when the screen is built. Then the owner says "this is not what I meant", and the developer rebuilds.
Think of a restaurant ordering app. The developer places the "Add to cart" button at the bottom of the screen. The owner wanted it beside each dish. This looks like a small change. But it touches the menu list, the cart and the checkout, because they all depend on where items are added.
A drawing would have shown the button in the right place on day one. That is the whole point. The drawing is where disagreements are cheap.
What if the product is already built?
Then the question changes from design-first to redesign-or-rebuild. Often you can fix the worst screens without starting again. Read app redesign or rebuild to decide.
The cost logic stays the same. Change the expensive parts while you still can. Mark the screens that cause the most confusion, redesign those, and ask developers to quote only those.
How can you start without overspending?
Start with the money flow. Ask a designer to draw only the screens a customer uses to pay or book. Show the drawing to five real users. Then ask developers to quote.
For a project like that, the UI/UX design service page explains how I price by screens and user roles, so you can plan before you commit.
Frequently asked questions
Does design before development always save money?
+
Not always. It saves money when changes would otherwise happen after building. For a very small or technical test, starting with code can be cheaper.
Can design and development happen at the same time?
+
Yes, if the main flow is designed first. Developers can set up the base while the designer finishes other screens.
Do developers need full designs to give a quote?
+
They need at least the screen list and flow. Full designs give the most accurate quote, because every screen is visible.
Working on something like this?
Tell Tithi what you are planning. You get a clear scope, a fixed price and a timeline before any work begins. I reply to every enquiry within 24 hours.