Skip to content
Case Studies

The operating model, in the room.

Qualitative writeups of how a fractional executive bench shows up in a real engagement. No fabricated metrics. No anonymous logos. The shape of the work, in writing.

Case Study 01DogfoodIn flightPublished · Updated

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

Week 1

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.

Week 2

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.
Case Study 02Engagement walkthroughIllustrative compositePublished

A multi-location operator coordinating one function

A composite walkthrough of how the bench shows up for a multi-location service business. The pattern below is synthesized from operators we have spoken with and from PQV’s own dogfood engagement. No real client name, no fabricated metric. The shape of the work, in writing.

The seat the founder was sitting in

A service business running three locations, with marketing, sales, and operations spread across three separate vendors who never talked to each other. The founder was the integration layer. Marketing campaigns ran without the operations team knowing. Sales follow-up referenced offers that had already been pulled. Sunday nights were brief-writing nights because nobody else knew enough to write them. When something broke at one location, the marketing team was the last to find out.

What the bench took on

A single intake replaced the three vendor relationships. A named Marketing operator owned the content cadence, brand voice, and campaign artifacts. A named Sales operator took the outbound and pipeline lanes. A named Operations operator owned the cross-location coordination and the cadence of the weekly digest. Every brief landed with the cross-lane context built in: marketing knows what operations is dealing with, sales references the actual offers running this week, and the audit trail covers all three lanes in one log.

What changed in the room

Marketing briefs stopped contradicting operational reality. The Friday digest reflected what was actually in market and what was actually breaking. When a location had a real issue, the marketing surface caught up within twenty-four hours instead of running stale promotions for a week. The founder stopped being the message-runner between three vendors. The work that used to require Sunday-night reconstruction started landing on Monday morning, finished.

Tier the engagement starts at

Pipeline Builder is the natural entry point for a multi-location operator because it covers the marketing operator plus the sales operator. Revenue Operations is the next step when the cross-location operations workload exceeds what the founder can carry as the integration layer.

Case Study 03Engagement walkthroughIllustrative compositePublished

A professional practice running a real operating cadence

A composite walkthrough of how the bench shows up for a partner-led professional practice. Synthesized from the pattern of practices that came to PQV with strategy in their heads and a CRM nobody loved. Illustrative, not a real client.

The seat the partners were sitting in

A partner-led professional practice with strategy that lived in conversations between two or three partners and rarely made it into writing. Decisions made on Monday were already drifting by Thursday because nobody had a current source of truth. Marketing happened when a partner had bandwidth. The pipeline number was a guess updated by the partner who happened to look at the CRM that day. Client follow-up emails got re-typed every week because no template existed that the partners actually trusted to send under their names.

What the bench took on

The partner conversations got captured as written specs the same day they happened. A Marketing operator ran the practice's outbound, content, and brand voice with named accountability and a weekly review pass. A Customer Intelligence operator turned the existing client book into a real engagement timeline the whole partner group references. Client communication templates landed as artifacts the operators can run on their own, with the partner review pass only on the categories that truly require it.

What changed in the room

Strategy stopped drifting between Monday and Thursday because the spec was on paper before the conversation ended. The partner group started referencing the same document instead of remembering different versions of the same conversation. The pipeline number became defensible because the same person did not have to update it from memory. Client follow-up moved off the partners' desks for the categories that did not require partner judgment, and the partners got that bandwidth back for actual practice work.

Tier the engagement starts at

Revenue Operations is the right entry point for a partner-led practice because the customer intelligence operator carries the existing book of business and the operations operator runs the cadence the partner group has been trying to keep in their heads.

What lands here next

More walkthroughs as the work matures. As named operators ship inside real engagements and the audit trail covers more lanes, we add the patterns worth writing down. Each walkthrough covers the seat the buyer was sitting in, what the bench took on, and what changed in the way the room moves. Qualitative. Honest. No fabricated metrics. No anonymous logos.

See the operating model from the inside.

A complimentary Discovery Sprint is the fastest way to see what the bench would look like in your business.

Start your Discovery SprintRead the pillar essays