Who are we helping?
Name the people who will use the app. What are they trying to do? What do they already understand? Start with one audience you can describe in ordinary language.
“This is for our operations team, who coordinate customer requests across three separate spreadsheets.”
What is difficult today?
Describe the current problem before listing features. Look for repeated work, delays, mistakes, or places where people get stuck. A specific problem gives the project a useful direction.
What is the smallest useful version?
Choose the few things that must work for someone to benefit. Separate those essentials from things that can wait. A focused first version gives you something real to learn from.
What needs to fit?
Note your budget, timing, existing tools, and any important data or access needs. These constraints help shape a plan that fits your work.
How will we know it helped?
Define a practical outcome: fewer repeated tasks, a smoother customer experience, or a process people can complete without help. Decide what progress should look like before building.
We’re building for [who]. Today, they struggle with [problem]. The first version should help them [essential task]. We need to work within [constraints]. We’ll know it’s useful when [outcome].
You can use this brief in your own planning or bring it into a conversation with us. Early answers are enough to begin.