V-Plan USA · Software · internal tooling
Discovery in days. Delivery in weeks. A third of the team.
// Summary
We embedded inside V-Plan's team, mapped their end-client requirements in real time, and rebuilt the delivery pipeline end to end. Engineering went from seven people to two. End-to-end delivery dropped from eight weeks to three.
// Context
V-Plan USA's delivery cycle was eight weeks end-to-end. Discovery happened in one conversation, the spec got written from interpretation, and engineering spent most of the cycle on business logic and scaffolding. The team was seven engineers and growing — and every new feature cost as much as the last.
// What broke
The pipeline. Discovery was disconnected from spec. Spec was disconnected from build. Build was disconnected from test. Every handoff lost fidelity, and every loss compounded across the next handoff.
// What we did
Four steps. One pipeline.
Embed
We sat with V-Plan and their end client in the same room. Mapped the real requirement live — not from a brief, not over Zoom afterwards.
Specify
Same-day spec, written from the conversation. Engineering started every build with full clarity. No reiteration. No contract amendments.
Build
Rebuilt the workflow so engineers worked on architecture, not scaffolding. The pipeline generated business logic and tests from the spec.
Compound
Specs, docs, and test coverage now generated as byproducts of the workflow. Every model improvement makes the pipeline faster — without anyone maintaining it.
// What's still running
The pipeline V-Plan operates today is the one we built. It's gotten faster three times in the last year, every time the underlying AI tooling improved — without anyone on V-Plan's side maintaining it.
// Results
Faster end-to-end delivery (8 wks → 3 wks)
Engineers on the build team
Reduction in test engineering hours
Discovery to spec
See where it's breaking in your pipeline.
Thirty minutes. To understand your pipeline and whether we can help.