Business Analysis
Know what you're building before you build it.
Most failed builds were scoped in a meeting and quoted off a wishlist. We do the part in between: interviews with the people who do the work, the process as it really runs, and a scope document precise enough that a mobile, web or software team can price it — and precise enough that you can hold them to what they quoted.
What You Get
The parts that decide whether it works.
The Problem, Before The Solution
Time with the people who'll use it, so the build starts from what actually goes wrong on a Tuesday rather than from a feature list.
Flows, Screens And Scope
Every journey through the app or system mapped and agreed, with the screens each one needs — one document a designer and a developer can both work from.
A Data Model You Can Argue With
How your information really fits together, drawn before code, because it's the part that's expensive to change once there are users inside it.
Requirements A Developer Can Quote
Written as testable statements rather than wishes, so mobile, web and software estimates come back comparable instead of guessed.
What Not To Build
The features cut, deferred or replaced by something simpler, with the reasoning kept — usually the most valuable page in the document.
A Phased Roadmap
The build broken into releases that each stand on their own, so a first version reaches real users months before the last phase ships.
What lands in your hands
Requirements, flows and a costed roadmap for a mobile app, web app or software build — settled before anybody writes code.
The expensive mistakes in software are made before development starts. We spend time with the people who'll actually use the thing, map how the work is done today, and turn that into a scope a developer can quote and a board can approve — whether what follows is an iOS and Android app, a web application or a system that replaces a decade of spreadsheets.
What's included
- Stakeholder and end-user interviews, written up
- Process maps of how the work is done today
- User flows and screen-by-screen scope for app, web and software
- Testable functional and non-functional requirements
- Data model and an integration map of your existing systems
- A phased roadmap with an estimate against each phase
Our Process
A proven process. Exceptional results.
01. Discover
We understand your goals, audience and challenges.
02. Plan
We strategise and create a clear roadmap.
03. Build
We design, develop and bring your vision to life.
04. Launch & Support
We launch your project and support your growth.
Questions
Before you commit.
We already know what we want. Do we need this?
Usually you know the outcome rather than the build, and the gap between those is where budgets go. If a scope already exists we'll review it instead — that's a much smaller piece of work, and sometimes the answer is that it's fine.
Can we take the scope to another developer?
Yes. It's written to be quoted by anyone, and it's yours whether or not we build it. Plenty of clients analyse with us, tender the build, and come back with three comparable quotes instead of three different guesses.
How long does it take?
Two to four weeks for most projects, depending on how many people we need to speak to and how many systems it has to talk to. It's the phase that shortens everything after it.
Does this replace design?
No — it comes before it. Analysis decides what gets built and why; the mockups then decide what it looks like and how it feels. See /design/ui-ux-mockups for that half.
Ready to bring your idea to life?
Let's create something amazing together.
Firm quote against a scoped roadmap before any work begins.