HubScope
Package
Artefacts
Product
Book a session
Every modernisation we have watched stall, stalled on the current state. The discovery package is the fix: a fixed-price sprint where we interview your people, discover your systems, and hand back a validated single source of truth; one your team, your funders and the copilots your staff already use can all query.
22 systems still read from the legacy CRM. The riskiest dependencies are rates billing and the consents portal, which use its customer records daily. The validated order has single sign-on landing first, so retirement can start from month 2.
Northwind living map · 138 systems · validated in 15 interviewsIt is the month 3 decision point on the roadmap. The sign-off pack is one view: the migration order, the owners affected, and the scores your team agreed in week four.
A fixed-price discovery sprint in one of three sizes. We interview your people, discover your systems, and hand back a validated source of truth for your current state; one your team, your funders and your copilots can all work from.
Every system you actually run and how they depend on each other, on one canvas. Validated by your people, current after handover, readable by your language models.
The work sequenced in the order the dependencies allow, ready to take into a funding conversation without redrawing it.
Every candidate initiative ranked with your team into do first, fund next and park, with the value and effort scores you agreed.
Up to 30 interviews, validated into everything. The conversations are how we work, not a deliverable; what your people know lands in the artefacts instead of living in heads.
Real examples from Northwind, our demonstration council estate. The map is live; pan it and open a node or two. The one-pagers open at print scale and print exactly as you see them.
Language models are only as good as the context they are handed, and most organisations cannot hand them a current state anyone has signed off. After the sprint, you can.
What talks to what stops being a meeting. Your people ask the copilot they already have open, and the answer comes back from the map your own team validated.
What a change touches becomes a question with an answer. Dependencies surface while the work is still being scoped, not in the incident review afterwards.
New starters and incoming vendors hold the whole estate on day one, instead of absorbing it as tribal knowledge over their first year.
One week, four weeks or eight: every sprint hands back the same three artefacts, sized to your estate. Fixed price, agreed up front, paid at handover.
Book a discovery sprintHubScopeDiscovery sprintNine candidate initiatives, scored with your team in the final week and sorted into three bands. Systems counts how many of your 138 each piece of work touches, read straight off the live map.
| Rank | Initiative | Value | Effort | Systems | Window |
|---|---|---|---|---|---|
Do firstMonths 0 to 3Cheap, uncontested, and everything else gets easier once they are done. | |||||
| 01 | Consents portal APIThree teams rekey the same applications by hand. Two weeks of work removes all of it. | 5 |
1 |
3 | M0–M2 |
| 02 | Name an owner for every systemForty one systems had no named owner. The cheapest risk reduction on the list. | 4 |
1 |
41 | M0–M4 |
| 03 | Single sign-on rolloutRemoves 18 local logins, and gives the CRM and warehouse work one identity to build on. | 4 |
2 |
18 | M0–M3 |
Fund nextMonths 3 to 18Worth the investment, and the order below is the order the dependencies allow. | |||||
| 04 | Retire the legacy CRM22 systems still read from it. Migration order comes straight off the dependency map. | 5 |
3 |
22 | M2–M8 |
| 05 | Data warehouse consolidationThree overlapping warehouses become one, so reporting stops disagreeing with itself. | 4 |
4 |
12 | M3–M11 |
| 06 | Rates billing replatformThe long play, and the one the long-term plan funds. Needs trustworthy reporting first. | 5 |
5 |
31 | M10–M18 |
Park until it mattersRevisit at renewalReal work, but nothing else in the estate is waiting on it. | |||||
| 07 | Payroll upgradeContractual rather than strategic. Schedule it around the CRM migration, not against it. | 2 |
4 |
6 | — |
| 08 | GIS licence tidy-upA small annual saving with almost no delivery risk. Do it when a fortnight frees up. | 2 |
1 |
4 | — |
| 09 | Intranet refreshThe most requested item in the interviews, and the one nothing else depends on. | 1 |
2 |
2 | — |
HubScopeDiscovery sprintThe same seven pieces of work, placed in the order the estate allows rather than the order they were asked for. Every row carries what has to land before it can start.