Build with me / Blueprint

Blueprint

A full operating diagnosis for a company that has outgrown its systems.

Most growth-stage companies do not have a people problem or a product problem. They have an operating problem. The leadership team is smart, the revenue is real, and the business still feels harder than it should. That gap is almost always process tax: missing scorecards, unclear decision rights, meetings that produce nothing, comp bands invented on the fly. Blueprint names every piece of that tax and replaces it with systems that scale.

Format Scoped engagement
Timeline 3 to 4 weeks
Output Written playbook & 90-day plan

Companies that feel the seams starting to split.

The specific shape varies. The underlying pattern does not.

A written playbook, not a slide deck.

Forty to sixty pages of operating infrastructure, specific to your business, ready to hand to the executive who has to run it. Every section has named owners and a sequence for rollout.

Playbook sections
What shows up in the document.
  • Scorecards Metric owners, weekly cadence, review format. The numbers that actually tell you whether the business is healthy, not the vanity metrics everyone is already watching.
  • Decision rights A real RACI at the level that matters. Named individual accountable for every load-bearing decision. No committees disguised as accountability.
  • Meeting cadence Weekly, monthly, quarterly. Who attends, what they produce, what happens if a meeting is skipped. Written agendas that travel with the meeting.
  • Compensation Level structure, salary bands, equity philosophy, promotion gates. The thing every company eventually has to build the hard way.
  • Accountability How people know what they own. How you have the hard conversations. How you fire fairly and protect the team from a bad hire.
  • Operating rhythm Quarterly planning cycle, annual offsite structure, how strategy connects to weekly execution. The connective tissue most companies build accidentally.
  • 90-day sequence Week-by-week implementation plan with named owners. You do not have to figure out what to roll out first. That part is done.

Four weeks, one deliverable, clean handoff.

  1. 01

    Discovery. Week one.

    Eight to twelve interviews with the leadership team and senior operators. Review of current scorecards, comp plans, and meeting artifacts. Shadowing of one or two load-bearing meetings in person or on video. The first week is almost entirely listening.

  2. 02

    Diagnosis. Week two.

    A written diagnosis delivered to the CEO. Specific operating failures, where the team is paying invisible tax, and a priority order for repair. This is the document that determines what the playbook emphasizes. You sign off before I start building.

  3. 03

    Build. Week three.

    The playbook gets drafted. Sections ship as they firm up, not held until the end. You read scorecards on Tuesday, decision rights on Thursday, compensation the following Monday. Feedback happens in real time.

  4. 04

    Handoff. Week four.

    Two-hour working session with the full leadership team. Walk through the complete playbook. Name owners for each implementation step. Confirm sequence. A 30-day check-in follows to make sure the work has actually started.

Situations where this is the wrong answer.

Blueprint is sharp in the situations it was built for. It is the wrong move in a few.

You need something done this week. The engagement runs three to four weeks minimum and there is no compressed version.
You are under $3M in ARR. The patterns that call for this work have not fully emerged yet. An earlier-stage conversation is a better use of your time.
You want a consultant to run the business. That is a different engagement. Consider The Operator.
You want validation for decisions already made. The diagnosis will name what I actually see. If that is not what you want, we should not do this together.

Start with a call.

Thirty minutes to talk through what is going on, whether Blueprint is actually the right engagement, and what a scope for your specific business would look like. If it is not the right fit, I will say so on the call.

← Back to Build with me