You don’t need a formal document. You need clear answers to five questions: what problem does it solve, who is it for, what’s the one thing it must do on day one, what platform matters most, and what’s your rough budget.

The five questions worth answering first

  • What problem does your app solve, in one sentence?
  • Who is it for, specifically, not “everyone”?
  • What’s the one thing it absolutely must do on day one?
  • Does it matter more on iOS, Android, or both?
  • What’s your rough starting budget, even a range is useful?

A simple brief template you can copy

Copy this into an email or our contact form, filled in with your own answers:

  • The problem: [what’s frustrating or missing right now]
  • Who it’s for: [type of user, not just “everyone”]
  • The one core thing it must do: [the single most important action]
  • Platform: [iOS / Android / both / not sure]
  • Budget range: [your honest starting point]
  • Anything else useful: [examples of apps you like, timing, constraints]

What NOT to worry about yet

  • Pixel-perfect design, that comes during the build, not before it
  • Every feature you might eventually want
  • Technical architecture, that’s our job to work out
  • Having the “perfect” business plan finished first

What happens once you send this over

We read it, ask any follow-up questions we need, and come back with an honest read on which package fits and what a written quote would look like. No call is required to get that first answer, though we’re happy to talk it through if that’s easier.