Understand the problem before building the answer
Discovery is a structured engagement, typically two to three weeks, that produces a clear specification, a realistic budget, and a phased plan for a software project. You get a document you own completely, whether you build with us or not.
Most software projects that fail do not fail because the code was bad. They fail because the wrong thing was built. Requirements were assumed rather than investigated. Scope was agreed over email instead of earned through workshops. Discovery exists to prevent that.
What happens during discovery
The centrepiece is a workshop day. We spend time with the people who actually do the work, not just the people who manage it. We map how information flows through your business, where it gets stuck, and where manual effort is covering for missing systems.
Process mapping
We document how work actually moves through your organisation. Not how you think it moves, or how it was designed to flow five years ago, but what happens in practice. This step regularly surfaces inefficiencies and workarounds that are invisible to management. Read more about how we approach process mapping.
Data modelling
We identify what information your business relies on, where it currently lives, and how it relates to other information. This is the foundation for a system that works as a single source of truth rather than another disconnected tool.
User journey mapping
We trace the paths different people take through your systems: staff, managers, clients, suppliers. Each role interacts with data differently, and a system that works for one but frustrates another is a system that will be worked around.
Prioritisation
Not everything needs to happen at once. We assess each element by business impact, technical complexity, and dependency. The goal is to identify what to build first so you see value early, while laying the groundwork for everything that follows.
Between workshop sessions, we analyse what we have learned, identify risks and dependencies, and develop a phasing strategy that delivers value early while keeping complexity manageable.
What you get
Discovery produces four deliverables, each designed to give you the confidence to make an informed decision about what to build and how.
Current state analysis
A documented picture of how your business operates today: the workflows, the data, the tools, the workarounds. This alone has value. Most businesses have never had their operational reality written down in a single place. It becomes a reference point for any technology decision you make, whether or not you build with us.
Functional specification
A detailed description of what the software needs to do, structured around your actual workflows rather than abstract feature lists. This is the document a development team uses to estimate, plan, and build. It is specific enough to quote against and clear enough that a non-technical reader can follow it.
Phasing recommendation
A plan that breaks the work into stages, ordered by business impact and dependency. Phase 1 delivers the highest-value capabilities first. Later phases build on that foundation. This means you start getting return on your investment weeks after development begins, not months.
Budget with confidence intervals
Not a single number, but a range that reflects genuine uncertainty. Phase 1 gets a tight estimate because the scope is well-defined. Later phases carry wider bands because they depend on decisions made during earlier work. These are honest figures you can plan around, not optimistic guesses designed to win a contract. For context on what drives these numbers, see our guide on how much custom software costs.
The document is yours
This is worth stating plainly. The discovery output belongs to you. Entirely. If you take it to three other agencies for comparison quotes, we encourage that. If you decide not to build at all, the current state analysis and process maps still have value as internal documentation your team can use.
We are confident enough in our work and our pricing that we do not need to hold a specification hostage to win the build. The document should stand on its own merit, and so should we.
No lock-in. The specification is written in plain language against standard technology. Any competent development team can build from it. You are never dependent on us to interpret our own output.
Who discovery is for
Discovery is the right starting point when you know something needs to change but the detail is not yet clear. These are the situations where it delivers the most value.
If you already have a detailed specification and just need a team to build it, you may not need formal discovery. We will tell you that on the call.
How long it takes
Most discovery engagements run two to three weeks from kick-off to deliverables. The workshop day is the centrepiece, usually scheduled in the first week. The remaining time is spent on analysis, documentation, and refinement.
Smaller, well-defined projects can sometimes compress this to a single week. Larger or more complex situations (multiple teams, multiple locations, legacy systems that need auditing) may take longer. We will give you a clear timeline before you commit.
What happens after discovery
You have a specification, a budget, and a phased plan. From here, you have three options.
Build with us. Most clients do. The specification feeds directly into a custom build engagement, and the phasing recommendation becomes the development roadmap. There is no wasted work or repeated conversations.
Build with someone else. The specification is written to be portable. Take it to other agencies, compare quotes, and choose the team you trust most. We are comfortable with that comparison.
Decide not to build. Sometimes discovery reveals that the problem is smaller than expected, or that an off-the-shelf product would actually work. If that is the case, we will say so. You still walk away with a documented understanding of your operations that has value on its own.
Book a discovery call
The initial conversation is free, takes about thirty minutes, and comes with no obligation. Tell us what you are dealing with and we will give you a straight answer about whether discovery is the right next step. Read more about what working with us looks like, or get in touch directly.
Book a call →