PQV onboarding itself as a Custom Stack customer
We do not ship the operating model to customers until we have run it on ourselves. PQV is the first Custom Stack engagement on the bench. The pattern here is the same pattern any other Custom Stack customer would see: a real Discovery Sprint, a written roadmap, named operators, a human review pass, and a weekly digest. The work in flight today is what every customer will recognize when they walk in.
The seat we were sitting in (the challenge)
A young company carrying every function on the founder. Marketing, sales, brand, operations, finance, and customer follow-up all running off the side of one desk. Strategy lived in conversations that did not get written down. Decisions made on Monday were already drifting by Thursday. The work that did happen happened in bursts. The work that did not happen lived in a notes app and a tab graveyard.
What the bench took on (the solution)
Named operators absorbed the marketing site rebuild, the sales narrative, the Discovery Sprint flow, the client portal scaffolding, the weekly digest, the audit trail surface, and the operating cadence. The founder kept the strategic calls and the human review pass before anything shipped. The bench did the production. One function, one record, one cadence.
What changed in the way the room moved (qualitative outcomes)
Work stopped living in scattered notes and started landing in a log you can scroll. A weekly digest replaced the late-night catch-up sessions. Drafts went through a human review pass before anything left the building. Prospect conversations stopped requiring memory reconstruction. The function got coordinated. The audit trail got readable. The room got quieter.
Why we lead with the dogfood
We do not publish numbers we cannot verify, and we do not put customer logos on a wall before the work has compounded. The honest first case study is the one we can stand behind: us, running the operating model on our own business, in public, in writing. New case studies land here as engagements mature.
Week by week, in writing
Audit pass and the written room
The bench started with a working audit of the current state. Brand voice, public copy, sales narrative, customer pathway, operating cadence, and the audit trail surface all got written down for the first time. The founder had been carrying it in his head; the bench moved it onto paper. The output was a readable picture of what PQV actually was on day one, including the gaps. Nothing got rebuilt yet. The room got written down.
Statement of work and the first weekly digest
The bench drafted the internal statement of work that PQV-as-customer would sign if it were any other Custom Stack engagement. Scope, named operators, review pass cadence, weekly digest format, and exit terms all written like a real contract. The first weekly digest landed: what shipped, what is in flight, what the founder needs to decide. The digest was the first artifact that read the way a customer would read it. The format got tightened the same week.
What PQV-as-customer is learning (and any customer would too)
- The first valuable artifact is the audit, not the rebuild. The room has to be written down before it can be changed.
- A weekly digest formatted for the founder is not the same artifact as a weekly digest formatted for a customer. The reader is the spec.
- Most decision delay is reconstruction delay. When the trail is current, conversations start at the decision, not the briefing.
- Saying no to a deal that quietly breaks the operating model is part of the work, not an exception to it.
- The human review pass catches the contradictions that personal discipline cannot. Discipline is mostly an infrastructure problem.