§ Approach

Four movements. One business that runs.

Every TILRE® engagement follows the same arc — read the business, write the plan, install the operating system, hand the wheel back. Below: what actually happens inside each movement, and a sample of what you'd receive.

Click See an example on any movement to preview a representative deliverable.

I

Week 1 · 60–90 minutes

Diagnosis

The Read

An operator sits across from you and reads the engine — not the pitch deck.

The Read is not a discovery call. It's a working session. JB walks in (or joins by video) with one job: understand how your business actually runs today — the decisions, the bottlenecks, the pipeline, the money, the people — well enough to tell you what's broken before we ever talk about fixing it.

We pressure-test three things on purpose: (1) who the business depends on to close revenue, (2) what happens to pipeline when you're not in the room, and (3) where decisions stall. Most $1M–$10M operators already know one of these answers. Almost none of them know all three in writing.

You leave The Read with a short list of the 3–5 bottlenecks that are actually costing you money — ranked by what would unlock the most, fastest. That list becomes the spine of The Plan.

01

What you bring

  • Last 12 months of revenue by line / service
  • Current org chart (or a napkin sketch)
  • Your honest take on what isn't working
02

What you leave with

  • Shared read of the business in plain English
  • Ranked bottleneck list (3–5 items)
  • Initial view of the first 90-day install
II

Week 1–2 · Written

The Operator Brief

The Plan

One document. Plain English. The install sequence and the logic behind it.

The Plan is a single PDF — the TILRE® Operator Brief — delivered within seven to ten days of The Read. It is deliberately short. Ten pages, maybe twelve. If it can't be written in that length, it isn't clear thinking yet.

The Brief answers four questions, in order: (1) here is what we saw, (2) here is what we would install and in what sequence, (3) here is what each install should produce in weeks and dollars, and (4) here is the engagement that does it. No 80-slide deck, no consulting buzzwords — just the operator's read, on paper, with receipts.

You can share it with a co-founder, a board member, or a CFO and they will understand it without you in the room. That is the test.

01

What you bring

  • ~45 minutes to pressure-test the draft
  • Any internal constraints we should plan around
02

What you leave with

  • The TILRE® Operator Brief (PDF)
  • Prioritized install sequence with timeline
  • Scoped engagement proposal
III

Weeks 2–10

Embedded work

The Install

We build. The team runs the rituals. The business changes shape — on a schedule.

The Install is where most consulting engagements become Google Docs nobody opens. We don't do that. We embed with the team at a defined cadence — usually a weekly working session plus async support — and we build the things in the Brief with your people, not for them.

The work breaks into four tracks running in parallel: Structure (org, ownership, decision rights), Sales (process, stages, rituals, scripts), Operations (weekly cadence, scorecards, dashboards), and Leadership (what the founder is doing vs. what only the founder should be doing). Each track has an owner on your team from day one — so when we leave, the muscle stays.

Week four is the pivot week. By then most of the plumbing is in. The second half of the install is where behavior changes — where the team starts running the rituals without you prompting, and where the numbers begin to move.

01

What you bring

  • A team lead per track (we train them)
  • 1 weekly 60–90 min working session
  • Willingness to kill sacred cows
02

What you leave with

  • Installed org + ownership map
  • Written sales process + pipeline rituals
  • Live operating dashboard + weekly cadence
  • Decision-rights matrix (RACI, operator edition)
IV

Week 10+

We leave. It keeps running.

The Handover

The receipts, the rituals, and a business that doesn't need us in the room.

The Handover is the measure of whether any of this worked. We formally close the engagement with a written handover package — the operating manual of your business as it now runs — plus a live walk-through with the team leads who now own each track.

Our bar for leaving is simple: the weekly cadence runs without us for two consecutive weeks, the pipeline is being managed by someone other than the founder, and the scorecard is being updated on time by its owner. If any of those three aren't true, we stay until they are.

A quarterly tune-up is optional and most operators take it — not because they need rescuing, but because it keeps the standard honest. Two days per quarter, we sit with the team, re-read the numbers, and pressure-test what's drifting. Nothing more.

01

What you bring

  • The team that ran the install
  • Willingness to run it without us
02

What you leave with

  • Operating System binder (PDF + Notion/Doc)
  • Trained team leads per track
  • Exit scorecard — baseline vs. post-install
  • Optional quarterly tune-up cadence

§ Ready

Movement One starts with a single conversation.

The strategy call is the pre-read for The Read. 30 minutes, no deck, no pitch. You leave either with a clear next step or with a better picture of your own business — either way, it was worth the half-hour.