Know which system to buy, build or keep next
Sounds familiar? We have too many tools and projects pulling in different directions, and no plan for what comes next.
Growing businesses tend to add software one problem at a time, until the customer database, the spreadsheets, the website and the booking tool each hold a different version of the same customer. Before anything new is bought or built, a specialist maps what you run today, where your data lives and which projects are already in motion. Projects are then ranked by value and effort and put in an order that respects what depends on what. Mapping takes longer with each extra tool, team and location, so the scope is fixed on a short call before anything is quoted. What you receive is a roadmap your team can follow and a decision note for each project.

What you get
- Map of your current tools, what each one is used for and where your data lives
- Notes on overlaps, gaps and manual workarounds between tools
- Candidate projects ranked by value and effort
- Build, buy or keep recommendation for each major project
- Phased 6–12 month roadmap with order, owners and dependencies
- Decision notes per project covering the people, data, time and budget it needs
- Review session to settle the final order with your decision-makers
Is this right for you?
- You pay for many tools and nobody is sure which ones still earn their place
- You have several digital projects competing for the same budget and people
- You need to decide whether to build something custom, buy software or keep what you have
- You're adding staff, services or locations, and the current systems are already straining
- You want a second view before committing to a large software purchase
What it changes
One agreed order for the work
Your team works from one ranked list. The next project is picked by value and dependency instead of by whoever asks loudest.
A clear picture of your systems
You can see which tools you run, what each one does and where the same data is kept twice.
Decisions with the reasoning kept
Each project carries a note on whether to build, buy or keep and why. Months later, someone can revisit the choice without redoing the analysis.
Scope and delivery
How we deliver it, what we need from you, what is not included. Timeline: Agreed after a short call; plan for 3–6 weeks for the first roadmap
How we deliver it
-
Set the scope on a call
We ask how many tools, teams and locations are involved and which decisions are pressing, then put the scope in writing.
-
Map tools, data and projects
Your software gets reviewed with the people who use it, and the map records where data lives and how it moves between tools.
-
Rank the projects
Candidate projects are scored by value and effort, with dependencies marked so nothing is scheduled before what it relies on.
-
Build the roadmap
Projects are grouped into phases across 6–12 months, each with an owner, what it needs and a build, buy or keep note.
-
Review and update it
We walk through the roadmap with your decision-makers. If you want ongoing help, we revisit it at agreed intervals as projects finish.
What we need from you
- A list of the software you pay for, with view or admin access where needed
- Time with the people who run each area, such as sales, operations and finance
- Projects already planned or under way, with any quotes or proposals you hold
- Your business goals for the next 12 months
- One decision-maker who can approve the final order
What's not included
A specialist looks at your situation first, so the scope is agreed after a short call.
Not included
- Building, setting up or buying the tools on the roadmap, which are scoped as separate projects (see System integrations & APIs and Custom web applications)
- A step-by-step review of individual workflows for automation (see Automation & AI assessment)
- Software licenses and vendor contracts
- Managed IT for devices, users and office networks
Limits to know
- Effort and value scores on the roadmap are planning estimates. Each project still gets its own scope and quote before it starts.
- The roadmap reflects your tools, budget and priorities when it was written, and it will need revisiting as those change.
Where it fits
What usually follows, what may already be in place, and what is planned alongside, with the reason for each.
This service: Digital roadmap & technology planning
3 connected services
After this
What usually follows once this is done.
-
Automation & AI assessment
Drills into the workflows the roadmap flags.
-
System integrations & APIs
When the roadmap calls for tools that share data.
Part of these packages
-
Ongoing digital partner
Optional add-on: A yearly plan when the business is adding tools and projects.
Common questions
Should I start with the starting-point review instead?
The starting-point review suits a small business unsure where to begin, and it names the first one or two steps. A digital roadmap is for established businesses with many tools and projects. It plans 6–12 months of work across all of them, with owners and dependencies.
Why is the scope agreed after a call?
Five tools used by one team can be mapped in a few conversations. Twenty tools spread across several locations take far more. The call tells us which you are, so the scope and the estimate match the work.
Will you recommend software you set up or sell?
We may, because we also quote for setup and custom builds. Each recommendation names the tool and the reason for it, and the notes flag where we could quote for the work. You can take any project on the roadmap to another provider.
Can the roadmap be kept up to date?
You can stop once the roadmap is delivered, or ask us to review it at agreed intervals, for example each quarter, as projects finish and priorities change. What each review includes is stated in writing.