valha

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.

Launch window
90 days
12 September to 11 December
First workflow
Renewals
41 renewals a month in the pilot pod
Success measure
-30%
manual handoffs per renewal

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.

Two-thirds of the cycle goes to waiting and gathering dataDays
days per renewal by step, median of twenty renewals, August 2026
Waiting on a handoff6.2
Gathering account data3.1
Internal approval2.4
Paperwork and signature1.8
The customer call0.5
View source data

Results5

stepDays
Waiting on a handoff6.2
Gathering account data3.1
Internal approval2.4
Paperwork and signature1.8
The customer call0.5
source: Northstar adoption baseline, August 2026
interactive view

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

WhenMilestoneOwnerDeliverable
Week 1Renewal workflow mapped, baseline agreedNorthstar RevOps + usBaseline sheet, signed off
Weeks 2 to 3CRM and billing connectedOur integration leadAccount context in one view
Weeks 4 to 7Pilot with the RevOps podNorthstar pod leadFriday exception review, four times
Weeks 8 to 11Measure against the baselineBoth teamsHandoff count, cycle time, adoption
Week 12Rollout decisionNorthstar executive ownerGo, 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

ItemWhat it includesWhenPrice
Discovery and baselineWorkshop, workflow map, baseline sheetWeek 1€8,000
Two integrationsCRM and billing, read and write, testedWeeks 2 to 3€14,000
Pilot supportWeekly exception review, fixes inside 48 hoursWeeks 4 to 11€12,000
Rollout workshopDecision pack and the wider plan, if you goWeek 12€3,000
Total, fixedNo day rates, no change orders inside this scope90 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.

🚀
ProposedKick-off workshop
12 Sept
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.

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

  1. Contract and invoice for the first two items issued the day the executive owner is named.
  2. Workshop pack and the baseline template sent five working days before 12 September.
  3. Sandbox access requested from Northstar IT in the first week so the integrations are not waiting on it.

Sources

  1. 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

  2. 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

  3. commercial assumptions, reviewed with the Northstar team, 2026-09-01docs.example.com

    cited in Check the paybackScope and price on one screenDecision requested