What to put in a brief to get a fixed-price quote on a small app

What a quote actually depends on

A fixed price is a bet on effort. The developer is guessing how many screens there are, how much data gets stored, how many outside services are involved, and how many surprises are hiding in the details. Every question you leave unanswered becomes padding in the price or a change order later.

So the goal of a brief is not to sound technical. It is to remove guesses. If you cover the items below, most developers can give you a number, or tell you honestly that the project is bigger than you think.

• The one job the app does, in a sentence
• Who uses it and whether they need to log in
• The screens, listed one by one
• The data it saves, with example rows
• Outside services it connects to (email, payments, a spreadsheet)
• What is not included

Start with the job, not the feature list

Write one sentence in this shape: when this happens, this person does this, and the result is this. For example: when a customer submits a request, I get an email with the details and can mark the request as done. A sentence like that tells a developer more than a page of features.

Then say who touches the app. The biggest cost driver in a small build is usually whether people have to log in. A public page that anyone can open is much simpler than an app where different people see different things.

• Who creates information in the app (you, your customers, your team)
• Who only reads it
• Whether anyone needs an account, and whether roles differ (owner, staff, client)
• Roughly how many people will use it in the first few months

List the screens and the data behind them

Name every screen, even if the list is short. A sketch on paper, a photo of a whiteboard, or a screenshot of an app you like all work. For each screen, say who sees it and what they can do there.

Then describe the data. For each kind of record (an order, a request, a task), list the fields and give two or three real examples. If your information already lives in a spreadsheet, paste in a few rows with the column headers. This is the fastest way to show what the app has to hold and how messy real input looks.

• Screen name, who sees it, and the main action on it
• Fields for each record, and which are required
• Status changes (new, in progress, done) and who triggers them
• What people need to search, filter, or sort
• What should trigger an email or notification

Name every outside connection and rule

Say which outside services the app touches and who owns the account. Typical ones are email, Google Sheets, Stripe, a calendar, or a webhook into another tool. If you want deposits collected, the developer needs to know it should run through your own Stripe account. Each connection adds work and testing, so counting them matters for the price.

Also write down the rules, especially the edge cases. What happens when an event is full? What if someone cancels? Which dates or times are allowed? Small rules like these cause most of the surprises in a build, and stating them upfront is the cheapest time to deal with them.

If you already have a prototype from an AI builder or a previous developer, share the link or the code. Say what works, what breaks, and what you are not sure about. That turns an open-ended build into a bounded fix.

Say what is out of scope and what done looks like

List what you are not asking for. Common items: a native phone app, migrating years of old data, a full admin area for every setting, custom branding work, or payment plans. Saying so does not close the door on later versions. It keeps the first price honest.

Finish with three to five checks you will run to decide it is done. For example: I can submit the form from my phone, the email arrives with the photo attached, and I can mark the request complete. Add your budget range and your deadline too. A good developer will reply with their assumptions written out, so you can correct any that are wrong before work starts.

Where a fixed-price build fits

If your brief describes one job, a handful of screens, and one or two connections, it likely fits one of our three tiers. Micro is $249 and takes 3 business days: one single-purpose tool of up to 2 screens, no login. Tool is $749 and takes 5 business days: a multi-step tool with saved data, up to 5 screens, and one integration. Mini-app is $1999 and takes 10 business days: logins, roles, up to 10 screens, and up to 2 integrations. All include hosted links and full source code, plus 1, 2, or 3 rounds of tweaks, and the Mini-app adds 30 days of bug fixes.

For founders, the closest example is Finish your AI prototype, where an AI builder produced a project that almost works and the remaining job is making it solid. Send us the brief and we return a working preview within one business day. If we decline before work starts, you get a full refund. There is no refund after delivery. Hosting is included for 12 months, then $9.00 per month, or you can self-host.