01PROBLEM
Problem statement
A plain-English description of the problem, the people affected, the current process and what success should look like.
GOALS / USERS / CURRENT PROCESS / SUCCESS MEASURESDISCOVERY / SCOPING / SPECIFICATION
Scope it
properly
first.
The most useful step before any build.
We turn an idea, a frustration or a half-written brief into a clear problem statement, realistic options and an outline specification you can build from.
01 / WHAT WE DOWHAT YOU GET
Clarity before
commitment.
Most software projects that go wrong were unclear at the start. Discovery and scoping fixes that by agreeing what problem you are solving, for whom, and what version one really needs.
The output is yours to keep, whether you build with Data Menu, a delivery partner or your own team.
02OPTIONS
Options & trade-offs
Build, buy, integrate or automate: the realistic routes compared on fit, risk, timeline and running effort.
BUILD VS BUY / INTEGRATIONS / RISKS / ASSUMPTIONS03SPECIFICATION
Outline specification
Scope, priorities, data, integrations and a phased plan for version one, written so a delivery team can estimate and start.
SCOPE / PRIORITIES / DATA / PHASED PLAN02 / OUR POINT OF VIEWSCOPE FIRST, BUILD SECOND
Fewer surprises.
Better software.
DISCOVERY / DIRECTION / DELIVERY
A short, focused discovery phase reduces rework later. It surfaces the hard questions early, while changing direction is still cheap.
03 / A CLOSER LOOKHOW DISCOVERY WORKS
From idea to
buildable plan.
We start with a discovery call to understand the problem and decide whether a scoping engagement makes sense.
If it does, we run focused workshops with the people who know the process, review your existing systems and data, then write up the options and an outline specification.
01Workshops with the people who do the work
02Review of existing systems and data
03A written plan you own
04 / PRACTICAL APPLICATIONSWHAT WE SCOPE
Any project.
Scoped clearly.
Discovery and scoping works for new builds, replacements and improvements to systems you already run.
01
Custom software and internal tools
02
Customer portals and platforms
03
Data pipelines and reporting
04
Business process automation
05
API and system integrations
06
AI features and workflows
07
Website rebuilds
08
Legacy system replacement
05 / OUR APPROACHIDEA TO SPECIFICATION
A clear path
to version one.
Scope and cost are agreed before work starts, and the engagement ends with a written output rather than an open-ended process.
Talk through your project01
Discovery call
Talk through the problem and agree whether scoping is the right next step.
02
Workshops
Map the current process, users, data and systems with your team.
03
Options
Compare build, buy, integrate and automate routes, with risks and assumptions.
04
Specification
Deliver an outline specification and phased plan ready for estimation.
06 / GOOD TO KNOWBEFORE WE GET STARTED
Questions,
answered.
Every project is different. Here are a few useful things to know before we start a conversation.
Do we have to build with Data Menu afterwards?
No. The outputs are yours. You can build with Data Menu, with a delivery partner or with your own team.
What do we need to prepare?
Nothing formal. A rough description of the problem and access to the people who know the process is enough to start.
Is this only for new software?
No. We also scope automation, integrations, data projects and replacements for systems you already use.
How is discovery & scoping priced?
Scope and cost are agreed with you before any work starts. Talk to us on a discovery call and we will explain the options.
DISCOVERY / START HERE
Start with a
clear scope.
Tell us about the idea or the problem. We will help you decide what to build first, and whether to build at all.
← Back to all services