HubScope
Framework
Product
Package
Artefacts
Book a session
Every modernisation we have watched stall, stalled on the current state. The discovery package is the fix: a short, fixed-price sprint that leaves you with a shared map of what you actually run, and a plan you can take into a funding conversation.
A fixed-price sprint, sized to what you need. We interview your people, ingest your systems, and hand back a living map of your current state, a roadmap you can fund, and a clear view of what is worth doing first. Run entirely remotely, and you pay at the end.
Every system you actually run, and how they depend on each other, on one map. It stays yours, and it stays current.
The interviews are where the insight actually shows up, so they are in every sprint. We write up what we heard, plainly, including the themes that came up more than once.
The work sequenced in the order the dependencies allow, so you can take it into a budget conversation without redrawing it.
One picture of what pays back quickly, what is worth the investment, and what can safely wait.
Each one is handed over as a printable A4 page and as live data in your own map. See the worked examples below.
Real examples from Northwind, our demonstration council estate. The map is live, so pan it and open a node or two. The one-pagers open at print scale, and print exactly as you see them.
Every system in the estate and the dependencies between them, on one canvas. Yours is handed over as a live workspace in HubScope, not a snapshot, so it keeps pace as the estate changes after we step out.
Every sprint hands back the same four 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.