Skip to content
sevenweeks
Dubai · Product studio Sunday – Thursday Fixed price in AED
All posts

Product

Why we ship in seven weeks — and when we say no

28 July 2026 6 min

Seven weeks is not a productivity claim. We are not faster typists than anyone else.

It is a constraint we accept in exchange for removing the thing that actually consumes software projects: waiting.

Where the time really goes

Look at a six-month build honestly and the coding is rarely six months of work. The calendar fills with:

  • waiting for an estimate, then a revised estimate
  • waiting for a decision that needs three people in a room
  • waiting for a team to free up from another client
  • building something, then rebuilding it because a decision changed
  • a testing phase discovering things a weekly demo would have caught in March

None of that is building. Most of it is a consequence of leaving scope open and pricing by the hour, which quietly rewards everyone for taking longer.

What the constraint buys

Fixing the scope and the price before week 1 changes the incentives.

Decisions happen once. Week 1 exists to close them. Everything after traces back to something you agreed, so rework is the exception rather than the rhythm.

You see it working from week 3. A demo every Friday, on the real thing, not slides. When something is wrong you find out in days. The cost of a wrong assumption is a conversation, not a phase.

Nobody is billing for delay. If we are slower than we planned, that is our problem. The price and the date hold as long as the scope has not changed.

It ends. Projects without an end date drift. Seven weeks has a last day, and a handover on it.

The honest part

It only works because two things are true:

  1. The scope is fixed. Changes get priced before they get built. You always see the number and what it does to the date before you decide.
  2. You answer within 24 hours. One person on your side, empowered to decide. This is the requirement people underestimate. A project that waits three days for every answer cannot finish in seven weeks, and no amount of effort on our side fixes that.

When we say no

We turn work down. It is cheaper for everyone than finding out in week 5.

  • The scope cannot be cut to fit. Some products need more than seven weeks to be worth using. Usually we can carve out a first release that stands alone — but not always, and if not, we say so.
  • Nobody can answer questions. If the decision-maker is travelling for six of the seven weeks, the date is already gone.
  • It needs a regulated integration on someone else's timeline. Banking rails and government systems have approval queues we cannot compress.
  • The real goal is a document. Some organisations need a feasibility study. That is legitimate work, and we are the wrong studio for it.
  • The idea has not been decided. If you are still choosing between two products, seven weeks of building will not choose for you.

What happens if you fit

You get a fixed number in AED before anything starts, a demo every Friday from week 3, and a launched product with the repository, the designs, and every account in your name on the last day.

If you do not fit, you get told before you pay anything. That is the part we would want to be told.

Tell us what you want to build.

Share WhatsApp LinkedIn
Written by Sevenweeks

Thinking about building something?

Send a short brief. We reply within one business day, Sunday to Thursday.

§ Read next
WhatsApp