Retention and expansion: a case study playbook for public sector and GovTech

This edition is written for public-sector business development leads and GovTech commercial teams. In public sector and GovTech, public-sector buying is procurement-led and rewards credentialed, patient engagement, so the way you install retention and expansion has to reflect that reality from day one.

Names removed, numbers preserved. This is a real retention and expansion engagement, reproduced as a playbook. Client had product-market fit, a rev team of eleven, and a stalled pipeline.

Week one: diagnosis. The stated problem was "not enough leads". The actual problem was treating CS as a support cost centre, which had been masked by inbound velocity that peaked two quarters earlier.

Weeks two to three: rebuild the target list from scratch and re-cut the trigger. Retention and expansion works when one point of NRR is worth more than five points of new logo growth; the client had drifted away from that first principle.

The binding constraint we see in public sector and GovTech is almost always procurement cycles and credentials, not product-market fit. Retention and expansion is only useful in this vertical when it is pointed at that constraint — not at a generic growth number borrowed from another category.

Weeks four to six: live at 20% of previous volume, quality bar raised. Gross and net revenue retention moved every week, though absolute numbers stayed modest.

Weeks seven to twelve: ramp. By week ten the number was ahead of the pre-stall baseline. By week twelve it was 40% ahead. Cost per outcome was roughly halved.

What we would repeat: the diagnosis step, the quality bar, and the weekly review. What we would kill sooner: two tools we bought in month one that added noise instead of leverage.

The client's own summary at the end of quarter one: "we thought we needed more of everything; we actually needed less of the wrong things." That is usually the lesson.

Concretely for public sector and GovTech: one framework agreement unlocks years of downstream demand. That is the reason it is worth installing retention and expansion properly rather than half-heartedly across three vendors.