One portal for 50+ clients, scoped before a line of code.
- 76sub-features mapped, in 21 groups, before the build
- 140hours fixed for the first version, before starting
- 4systems behind one portal
- 50+clients served through it
To answer one client, the team opened four things: billing in Stripe, the infrastructure in Netbox, the contracts in a file store, the requests in a ticketing tool. None of them agreed with the others, and nothing arbitrated. The client saw none of it, asked by email, and waited for someone to assemble the answer.
Before building, we mapped: seventy-six sub-features in twenty-one groups, split into a first and a second version, with the hours for the first fixed before the work began. Then one portal, for the client and for the staff, on the same base, the four systems became four tabs of one thing.
Licence, contract, invoice and ticket live in one place that can be queried. The team stopped being the glue between four screens, and the client stopped asking. An IT company buys from whoever shows the scope first; here the scope was the product before the product existed.
- 01Scoped before built.Seventy-six sub-features in twenty-one groups, the first version's hours fixed before it started.
- 02One place for every answer.Licence, contract, invoice and ticket together, and queryable.
- 03Clients stop asking.They see what they used to request by email.
- MapMap: done
- ConnectConnect: done
- AutomateAutomate: done
- AIAI: prepared
Stop bridging your systems by hand.
Tell us which two systems don’t talk. You’ll leave the first call with a real scope, not an invitation to another call.