Put this guide into practice. Use the free app brief builder to prepare a draft you can copy or download. Your answers stay in that tool’s tab until you choose to share them.
Start with one person and one task
An app idea becomes easier to build when you can describe who opens it and what they are trying to accomplish. “An app for my business” is a starting point. “A customer can request a service and see whether it has been confirmed” gives the project a specific job. Write one sentence in that form before listing features.
Describe what happens today
Explain the current process, including the inconvenient parts. Perhaps requests arrive in several inboxes, important details are missing, or a customer has to ask for the same update twice. The point is to identify work the app should simplify. If the current process is already reliable, explain what a digital version should improve.
Choose the first useful version
Make two short lists: essential for the first version, and useful later. A service request might need contact details, the requested service, a status, and a reply. Loyalty points, chatbots, maps, and multiple staff roles may be later additions. A smaller first version still needs to complete its main task from beginning to end.
Write a sample journey
Describe the experience in plain language: the customer enters their request, sees confirmation that it was saved, opens a private page, and receives the business’s response. Include what should happen when something goes wrong. If the network is unavailable, should the app keep a draft? If a request is declined, what should the customer see? These details help define a usable product.
Include access, content, and payments
Say who needs to sign in, what information is private, and who is allowed to change it. Note any existing website, brand assets, or business service that must be connected. If payment is involved, explain when it should happen and what the customer is paying for. Do not include passwords or banking details in a project inquiry.
Bring a realistic starting brief
A useful first inquiry includes your audience, main task, essential features, existing website, budget range, and preferred timing. “Not sure yet” is a reasonable answer. You can also link to an experience you like and explain the part that works for you. The goal is a shared understanding, followed by a written proposal that makes the build and its limits clear.
Worked example: a service request, from idea to brief
This illustrative example shows how to reduce an ambiguous “booking app” to a version that can be reviewed. It is a planning example, not a claim about a delivered client project.
- Audience and outcome
- A returning home-service customer requests a visit and checks the business’s response without repeating their details in a second message.
- Current process
- Requests arrive by email. The owner replies to ask for missing details, checks availability, and sends a confirmation. Customers sometimes mistake their first message for a confirmed booking.
- First version
- Collect service type, preferred day, contact details, and a short description. Save the request once, issue a reference, and show “Awaiting review.” Let the owner confirm or decline. Let the customer reopen a private status page.
- Later
- Live calendar availability, automatic routing, recurring bookings, loyalty points, and customer-to-customer messaging are excluded from this version.
- Success check
- A customer can submit, recover their reference, and see a decision. A second customer cannot read that request. A failed save never shows a success confirmation.
Three questions this example leaves open
- Can the customer edit a request after it is submitted, or must they contact the owner?
- What information is necessary to evaluate a request, and what can wait until confirmation?
- How will a customer recover access if they lose their private link?
Keep those questions in the brief. Guessing the answers can create more rework than leaving them explicitly undecided. The developer should resolve them with you before treating the scope as approved.
Prepare your own version
Download the first-version worksheet (plain text), or use the interactive brief builder. Replace the example’s nouns with your own audience and task. If your first version requires five different audiences, write a separate journey for each and decide which one must work first.
Have a project in mind?
Share what you know. We’ll review the idea and discuss a clear scope before any payment.
Start a project inquiry ↗