How to Write a Brief That Gets You a Fixed Price: The One-Page Spec and How the Day-1 Blueprint Works

A brief that gets a fixed price fits on one page: one user, one problem, three core features, a written out-of-scope list, and a 30-day success measure. With that, a builder can price the work and stand behind the number. Without it, you get a range that moves or an hourly bill.

I run ForgeApp, a one-person AI-native app studio in Dubai. I sell fixed prices, so I have a selfish interest in good briefs: a clear one is cheaper for you and safer for me. This article gives you the template I would want to receive, shows how the Day-1 Blueprint turns it into a locked scope, and compares a weak and a strong version of each line. No external statistics are needed here; where I mention ForgeApp prices they come from our pricing page.

Why can't a builder give a fixed price from an idea?#

Because a price is a promise about a scope, and an idea has none. "An app for my clinic" can be a booking page or a full patient system, and the gap in effort and cost between them is very large. Honest builders respond in one of three ways:

1. A wide range, which protects them and tells you little.
2. An hourly rate, which moves the risk to you.
3. A short scoping step, after which a fixed price is possible.

The third is the only one that gives you a number you can plan around. That step is the point of the brief. It is also why every ForgeApp build opens with a Day-1 Blueprint (more on that below) and why I wrote about the wider market in app development cost in the UAE.

What goes in a one-page spec?#

Here is the template. Copy it, fill it, and send it to any builder, including me.

1. WHO is it for?
   One main user, described by what they do (not demographics).
   Example: "A front-desk coordinator at a 3-doctor clinic."

2. WHAT problem do they have today?
   One or two sentences. How do they solve it now, and what hurts?

3. THREE core features (no more)
   Feature 1: the thing users came for.
   Feature 2: what makes feature 1 usable (accounts, dashboard).
   Feature 3: what lets you run the business (admin, notifications).

4. OUT of scope (the most important section)
   List what you will NOT build in version 1.

5. CONNECTS TO
   Tools, systems and data it must work with (calendar, WhatsApp,
   payment provider, spreadsheet, existing website).

6. LANGUAGES AND DEVICES
   Arabic, English, or both? Phone first or desktop first?

7. DATA
   What personal or sensitive data will it hold? Who may see it?

8. SUCCESS in 30 days
   One number you can check. Example: "10 bookings made without a phone call."

9. REFERENCES
   Two things you like, one you dislike, with links.

10. BUDGET AND DATE
    The ceiling you are comfortable with and the date that matters.

Fifteen minutes with this beats two hours of describing the idea out loud.

What is the difference between a weak and a strong brief?#

Each line of the spec can be vague or exact. The table shows the same idea written both ways. These are illustrative examples, not real client text.

The out-of-scope row does the most work. Every feature you exclude is a fixed-price risk the builder no longer has to cover.

Why only three core features?#

An MVP exists to test whether the core loop works for real users. Three features forces you to define that loop. I apply this rule to every 7-Day MVP, and I explain the reasoning in how to build an MVP in Dubai. A fourth feature is not a bad idea. It is the start of version 2.

If you have six must-haves, that signals a bigger package or two separate builds. At ForgeApp, a 7-Day MVP is 18,000 AED at the launch price (list 28,000), and Launch Ready, with a larger locked scope, is 65,000 AED (list 75,000). The Validator at 6,000 AED (list 12,000) fits when the real question is demand: a landing page, basic login and a waitlist in 3 days.

How does the Day-1 Blueprint work?#

The Day-1 Blueprint is not something you buy. It is included in every ForgeApp build. It is how a one-page brief becomes a locked scope.

1. Intake. You tell me the idea, the user, the problem and what success looks like in 30 days. If you have sketches or competitor links, bring them.
2. Scoring. Within 24 hours of your deposit, an AI pass scores your requirements for completeness, clarity and feasibility, and produces a feature breakdown, risk flags and a task list. I read it, correct it and take it into the session.
3. Scope freeze. We choose your three core features and agree what is out.
4. Spec. I write the one-page spec.
5. Approval. You approve it, or you reject it and get your full deposit back.

Nothing is built until step 5. If you arrive with a brief in the template above, steps 1 to 3 go quickly and most of the session is spent on the out-of-scope list, which is where the real decisions are.

What mistakes make a brief unpriceable?#

Seven I see most often:

1. Describing a solution, not a problem. "A mobile app with push notifications" tells me nothing about who needs what.
2. No out-of-scope list. Everything is implicitly in.
3. "Like Uber, but for X." It names a company with thousands of engineers. Name the one flow you need.
4. Hidden integrations. "It should connect to our system" without saying which one.
5. Undecided language. Arabic right-to-left changes layouts. Decide early. If Arabic matters for your customers, see which AI model handles Arabic best if your product includes AI.
6. Unspoken data. If the app stores personal data, say so. It affects what you build. Read the UAE PDPL checklist first.
7. No decision-maker. Three stakeholders with three opinions produce a fourth scope. Name one person who approves.

What should I do before I send the brief?#

• Talk to five potential users, even for ten minutes each. The Day-1 Blueprint helps with scope, not with demand.
• Check whether a subscription already does the job. See build vs buy for UAE SMEs.
• Decide your ceiling. A fixed price works best when you name a budget range.
• Gather links, screenshots and files in one folder.
• Pick a date that matters and say why.

Questions#

What should a brief for an app quote include?#

One page: who the user is, the problem, three core features, what is explicitly out of scope, the systems it must connect to, the language and device requirements, and what success looks like in 30 days. Add links to anything you like and anything you hate.

Why do some agencies refuse to give a fixed price?#

Because the scope is unknown. A fixed price needs a fixed scope. If the brief is vague, the agency either pads the price or bills by the hour and the risk lands on you.

What is the Day-1 Blueprint?#

It is included in every ForgeApp build, not sold separately. On day one you get your scope locked in writing, an estimate, the risks flagged and three core features defined in a one-page spec. If you reject it, your deposit is refunded in full.

How long should a brief be?#

One page is the target. If it needs ten, you probably have several products. Pick the one that tests your riskiest assumption first.

Do I need technical knowledge to write a brief?#

No. Describe the people, the task and the outcome in plain language. The builder turns that into technical choices. Technical terms you are unsure of are better left out than guessed.

Have a brief, or just an idea?

• See the pricing, Day-1 Blueprint included
• Book a 20-minute call

ForgeApp prices are from forgeapp.ae/pricing. The example brief lines are illustrative and are not client text.