Northstar launch has a clear path to value
One renewal workflow, two integrations, 90 days and a fixed €37,000 price. Start with the RevOps pod; use the payback calculator to test savings before approving the wider rollout.
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.
View source data
Results5
| 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.
Results5
| 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.
Results5
| 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.
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
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
Decision requested
Approve the 90-day launch plan at €37,000 and nominate one executive owner for the weekly review. This starts discovery on 12 September and keeps the expansion decision evidence-led. A reply with a name and a date is enough; the contract follows the same day.
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
Northstar discovery workshop, 2026-08-28docs.example.com
cited in A launch small enough to finish, large enough to prove valueThe sequence, week by weekWhat we need before the twelfthWhat this proposal is built onDecision requested
Northstar adoption baseline, August 2026docs.example.com
cited in A launch small enough to finish, large enough to prove valueWhere a renewal’s fourteen days go todayCheck the paybackWhat this proposal is built on
commercial assumptions, reviewed with the Northstar team, 2026-09-01docs.example.com
cited in Check the paybackScope and price on one screenDecision requested