Discovery & Technical Spec
Nobody should be quoting a £20,000 build off a conversation. Discovery is sold separately so the specification can be honest rather than optimistic.
Two to three weeks mapping the real process, the real data and the real integrations, ending in a technical specification and a costed plan that belongs to you - usable with us or with anyone else.
Most failed software projects were mis-scoped, not mis-built.
The expensive mistakes happen before any code is written: a quote given off a conversation, a spec describing what someone thinks the process is rather than what it actually is, and a build that discovers the difference in month four.
We sit with the people who do the work and map what actually happens. Often that changes what gets built; sometimes it shows that an off-the-shelf product would do, and we will tell you that too.
- ✓ A process currently held together by spreadsheets
- ✓ Systems that do not talk to each other
- ✓ You have had a quote and cannot tell whether it is realistic
- ✓ You need a spec you can take to more than one supplier
Good fit if
- ? The process is about to change substantially
- ? There is nobody internally who can make decisions on it
- ? You already have a detailed, current specification
Worth a conversation first if
What you get at the end
Process map
What actually happens today, from the people doing it - not from the process document.
Data model
What the system has to know, where that lives now, and what state it is in.
Integration inventory
Every system that has to connect, with what each one can and cannot do.
Technical specification
Written to be built from, by us or by anyone else. You own it outright.
Costed, phased plan
What to build first so something is usable early, and what each phase costs.
Ready to get started?
Tell us about your project and we'll put together a plan - no obligation, no jargon.