valhaNorthstar launch has a clear path to value
Northstar can reach a measurable launch outcome in 90 days by starting with the revenue-operations team, not attempting a company-wide rollout. The work is deliberately narrow: one workflow, two integrations, and a success measure both teams can inspect every Friday. The price is fixed at €37,000, and the only decision this page asks for is a start date.
Source 1Northstar discovery workshop, 2026-08-28Source 2Northstar adoption baseline, August 2026Source 3commercial assumptions, reviewed with the Northstar team, 2026-09-01
A launch small enough to finish, large enough to prove value
The workshop made the constraint clear: the team does not need another transformation programme. It needs one visible operating win before the end of the quarter. The proposal therefore keeps the first release inside the renewal workflow, where the baseline already shows manual handoffs and avoidable delay, and measures one thing.
Where a renewal’s fourteen days go today
The adoption baseline timed twenty renewals end to end. The customer conversation takes half a day. Everything else is the organisation talking to itself: six days waiting for a handoff between sales, finance, and customer success, three more gathering account data that already exists in two systems. That waiting is the target, and it is why the two integrations come before anything else.
days per renewal by step, median of twenty renewals, August 2026
View source data
| step | Days |
|---|---|
| Waiting on a handoff | 6.2 |
| Gathering account data | 3.1 |
| Internal approval | 2.4 |
| Paperwork and signature | 1.8 |
| The customer call | 0.5 |
The sequence, week by week
Five milestones, each with one owner and one deliverable that either exists or does not. The rollout decision at week twelve is made on the measured numbers, not on a steering-committee promise, and stopping is an acceptable outcome of the pilot.
| When | Milestone | Owner | Deliverable |
|---|---|---|---|
| Week 1 | Renewal workflow mapped, baseline agreed | Northstar RevOps + us | Baseline sheet, signed off |
| Weeks 2 to 3 | CRM and billing connected | Our integration lead | Account context in one view |
| Weeks 4 to 7 | Pilot with the RevOps pod | Northstar pod lead | Friday exception review, four times |
| Weeks 8 to 11 | Measure against the baseline | Both teams | Handoff count, cycle time, adoption |
| Week 12 | Rollout decision | Northstar executive owner | Go, adjust, or stop, on the numbers |
Scope and price on one screen
Fixed price, four lines, nothing billed by the day. If the pilot stops at week eight, the rollout workshop is not invoiced. Anything outside the renewal workflow is a separate conversation, and we will say so before starting it rather than after.
| Item | What it includes | When | Price |
|---|---|---|---|
| Discovery and baseline | Workshop, workflow map, baseline sheet | Week 1 | €8,000 |
| Two integrations | CRM and billing, read and write, tested | Weeks 2 to 3 | €14,000 |
| Pilot support | Weekly exception review, fixes inside 48 hours | Weeks 4 to 11 | €12,000 |
| Rollout workshop | Decision pack and the wider plan, if you go | Week 12 | €3,000 |
| Total, fixed | No day rates, no change orders inside this scope | 90 days | €37,000 |
Who does what
The pilot fails if it becomes our project running inside your company. It works when the RevOps pod owns the workflow from week one and we own the plumbing and the Friday review.
Northstar
One executive owner, the RevOps pod lead, and two hours a week from each of the four pod members. Access to the CRM and billing sandboxes by week two.
Us
A delivery lead on site for the workshop and every Friday, an integration engineer for weeks two and three, and a 48-hour fix commitment during the pilot.
The rhythm
Friday, 30 minutes: exceptions from the week, the handoff count, and one decision. Nothing else recurring. The baseline sheet is updated live, so there is no status report to write.
Proposed
12 Sept
Kick-off workshop
On site, 09:30 to 13:00, RevOps pod and the executive owner
What we need before the twelfth
Three things, none of them large: the name of the executive owner, sandbox access to the CRM and the billing system, and the last three months of renewal records so the baseline is real from day one. The workshop pack will be with you five days before.
What could go wrong, and what we do about it
The billing API was reviewed in the workshop and the read path is straightforward. If the write path slips, the pilot starts on read-only data in week four and the write path lands during it; the handoff measure does not depend on it.
Adoption is measured weekly from week four. If fewer than three of the four pod members are using the workflow by week six, the Friday review becomes a redesign session, and the rollout decision is pushed by two weeks at no extra cost.
Then the numbers say so and the rollout does not happen. That is the point of measuring: a pilot that cannot fail is not a pilot. The baseline and the measurement method are agreed in week one so the result is not arguable in week twelve.
What this proposal is built on
Every number above comes from one of three documents, all shared with the Northstar team already.
The renewal workflow map and the constraints the team named
Twenty renewals timed end to end, the source of the chart above
A RevOps lead who ran the same 90-day sequence last spring, available on request
After approval
- Contract and invoice for the first two items issued the day the executive owner is named.
- Workshop pack and the baseline template sent five working days before 12 September.
- Sandbox access requested from Northstar IT in the first week so the integrations are not waiting on it.
Sources
- 1Northstar discovery workshop, 2026-08-28
https://docs.example.com/northstar-workshop
cited in A launch small enough to finish, large enough to prove value · The sequence, week by week · What we need before the twelfth · What this proposal is built on · Decision requested
- 2Northstar adoption baseline, August 2026
https://docs.example.com/northstar-adoption
cited in A launch small enough to finish, large enough to prove value · Where a renewal’s fourteen days go today · What this proposal is built on
- 3commercial assumptions, reviewed with the Northstar team, 2026-09-01
https://docs.example.com/northstar-commercials
cited in Scope and price on one screen · Decision requested