The expansion no pipeline review would have found, spotted from inside the delivery team.
Ad Hoc was a sub on another consultancy's contract at a federal agency: six people (a product manager, two designers, a few engineers) doing good work in a staff-augmentation posture. I wasn't on the contract. In Ad Hoc's matrixed structure, every delivery person answered to two managers: a business manager for the contract and the money, and a practice manager for the craft. I was the practice side, with about ten product and data people across accounts, and the PM on this one was mine to support. That support (deck reviews, prep for hard meetings, working through delivery snags) is what put me close enough to see what came next.
The signal was in the delivery
There was no single meeting where the opportunity announced itself. What there was, over months, was a pattern the team kept running into: the agency's teams competing for the same resources instead of building on each other's work, and everything built once, for one office, with nothing reusable left behind. Each project started from zero because the last one had ended at zero. None of it would surface in a pipeline review, because it wasn't a procurement. It was how the place built.
So I started shaping a proposal around the pattern: a few-week engagement to assess how they delivered and plant the seeds of delivering better. Pitching to grow, and offering to build their capacity, in the same motion.
Scoped with the client, not for them
The picture came from the delivery team; the audience came from the network. I found a path to a manager whose oversight ran broader than our corner of the agency, and the idea landed. What followed mattered more than any pitch: we iterated on the specifics with the government team, in working sessions, until the scope was as much theirs as ours. There was a two-pager somewhere in there. Nobody's decision turned on it. By the time the paperwork moved, the client was a partner in the plan, not the target of one.
The smallest instrument in federal procurement
We ran it as a micro-purchase, priced under the threshold. Federal procurement is slow, and every vendor claims to do everything; the fastest way to be different is to stop claiming and start showing. The micro-purchase meant weeks, not quarters, between yes and work. And what it bought was deliberately small: team-wide workshops, templates the agency could keep, and guidance for what to do after we left.
The case my own leadership was right about
The pushback came from inside. On paper, the return didn't justify the resources, and leadership said so. They weren't wrong.
So I covered much of the cost from my own overhead and staffed the work with people on the bench between projects. The invoice was never where the value was going to show up, and pretending otherwise would have lost the argument on someone else's terms.
The handoff, and staying near it
I led the early stakeholder conversations and the scoping, supported the first workshop, and showed up for the big meetings. The team led the work: the product manager I'd been supporting ran it, and because the engagement was design-heavy, the designers carried its core. As the delivery found its feet I stepped back, and the client's manager stepped back in parallel, both of us staying loosely attached.
What changed
Before, we were a sub on someone else's contract, known to the client as capable staff. After, we had a relationship of our own and a different standing: a firm that could advise the agency on how it builds, not just build for it.
What travels
Expansion signals live inside delivery, visible to whoever is standing there; no pipeline review finds what proximity finds. The first new engagement should be small enough that yes is easy and real enough that it proves the difference. And if the value won't show up on an invoice, be ready to fund it yourself, on purpose, and say so.