Can I get an estimate with just an app idea?
An idea is enough to start a conversation. For a useful estimate, explain the user's starting point, the steps they take and the result they should see. Include what your staff need to do behind the scenes. A developer can then identify unresolved questions and state the assumptions behind an estimate.
If your idea is still broad, speak to a few intended users and describe one task they struggle with today. A manual trial can help you decide which part deserves to become software. When you are ready to find a supplier, use our guide to hiring someone to build an app.
Do I need designs before I contact a developer?
You can start with notes or a rough sketch. Share existing designs if you have them and explain which decisions are still open. Ask the supplier whether their proposal includes designing screens, reviewing them with you and adapting them after feedback.
For example, a sketch of an inspection form can show the information a technician enters. A few sentences should also explain who assigns the job, who reviews the result and what happens without a connection. These details help the team estimate the whole workflow.
Start with the outcome and the people
“We need an app for our business” leaves the important work undefined. Write down who will open it, what they currently do, and what a completed task looks like. Identify the person who decides scope and the people who will test whether it works.
A customer, a field worker and an administrator are different roles. Naming them helps a developer identify permissions, screens and supporting systems. Include countries, languages, likely devices and connectivity conditions. Those describe the product's audience, which may be different from the country where the buyer is based.
A completed first-release example
Illustrative planning example: an equipment inspection log. This is not a bbigcheese client project or a delivery promise.
| Brief field | Example answer |
|---|---|
| People and task | A technician records an inspection during a site visit; a coordinator reviews submitted visits. |
| Android journey | Choose assigned equipment, complete the inspection, attach an optional photo, save and submit. |
| Backend and admin | Keep equipment and visits together; a coordinator assigns work and filters submitted visits in a web admin panel. |
| Offline rule | A technician can save a draft without connectivity. The app clearly distinguishes a local draft from a submitted visit. |
| Acceptance example | A saved draft remains available after closing and reopening the app. A coordinator only sees it once submission succeeds. |
| Deferred work | Live location tracking, automatic scheduling, predictive maintenance and a customer portal. |
The offline rule exposes a real question: what happens when someone submits twice, or another person changes the equipment record? The developer should clarify it before promising the final scope. You can describe the desired result without prescribing how to implement it.
Choose launch essentials by following one complete journey
An MVP is a usable first release that tests the central task. A small feature list is not enough if the user cannot finish that task. For each feature ask what would fail without it, what evidence it helps collect, and whether a simpler process could work during the first release.
Put later ideas in a separate list. A marketplace, chat, AI assistant or complex report should not enter the first release simply because another app has one. Conversely, basic error handling, permissions and data recovery are part of making the agreed workflow usable; calling something an MVP does not make them irrelevant.
Our own apps show different boundaries: Gut Elements concentrates on logging and reviewing a private diary, while Learn serves enrolled students with lessons, quizzes and progress. Describe the boundary of your product just as clearly.
Bring the material that can change the estimate
- Existing designs, brand assets, content and app references, with a note about what you like in each.
- Documentation for a website, API, CRM or other system the app must use.
- The operations staff need to perform in an admin panel.
- Any data that needs to move from an existing product, described without exposing private records.
- The reason for a deadline, such as a planned course launch, and the dependencies behind it.
Use “needs advice” where you do not know an answer. That makes uncertainty visible instead of turning an assumption into an accidental promise. The backend guide can help you fill in the administration and data sections.
Write checks both sides can observe
Replace “fast and easy to use” with a few concrete demonstrations: a user can recover access, a permitted staff member can update an item, a failed payment does not unlock paid content, or an unsent draft is clearly labelled. Agree detailed acceptance criteria with the team once discovery is complete.
Keep the same dated brief when comparing suppliers. Ask each team to identify exclusions and unresolved questions against it, rather than rewriting the brief to match a quote. Use our quote comparison worksheet for that next step.
Free to use and share
Your copyable worksheet
Download the plain-text version or select and copy it below. No account or email address is required. Keep passwords, API keys and real customer records out of a project brief.
Read and copy the full worksheet
ANDROID APP PROJECT BRIEF Prepared with bbigcheese · https://bbigcheese.com Copy, adapt and share with any development team. No account is needed. Do not include passwords, API keys or real customer records. 1. Business and people Business / project name: Person who approves scope and accepts delivery: Who will use the Android app: What those people do today: The single task the first release must improve: How you will tell whether the first release is useful: 2. First release Main user journey, from opening the app to finishing the task: Must-have features: Features deliberately left for later: Who signs in, and what each role may see or change: What must work with no internet connection: Countries, languages and Android devices to support: 3. Backend and administration What data must be shared between users or devices: What staff need to do in the admin panel: Existing website, API or business system to connect: External services, payments or subscriptions: Content and data that need to be prepared or imported: 4. Delivery and budget Designs, brand assets and reference apps already available: Target date, the reason for it and dependencies: Budget and currency (state whether tax is included): Who owns store, cloud, domain and payment accounts: Who will operate the app and respond to users after launch: What must be demonstrated before each milestone is accepted: Questions where you need advice:
Questions and answers
Do I need technical specifications before contacting a developer?
No. Start with users, the task, essential features, existing systems and the result you expect. The technical approach can be discussed during scoping.
How detailed should an app brief be?
Detailed enough to describe one complete user journey, who may do what, the data involved and what is excluded from the first release. Unanswered questions should be written down rather than guessed.
Can I use the template with another development team?
Yes. The template is free to download, edit and share. No account or email address is required.
Our own published apps
The product examples refer to apps we build and run ourselves. Their pages link to the published listings and explain the relevant scope.