Now welcoming two new partnerships
A sample engagement

What an engagement actually looks like

A composite drawn from real engagements, with details changed. A 14-person, founder-led company: real customers, one part-time VA, no operating layer, and a founder doing all the connecting.

Week 1 · Diagnosis

First we map how the company runs.

The first week is interviews, shadowing, and reading. Every engagement starts with the same map: the six areas, scored honestly. Here's what this one looked like.

AreaWeek-1 findingState
Executive operations Founder inbox at 400+ unread; every meeting unprepped Gap
Leadership execution & integration KPIs exist on paper; nobody updates or reviews them Broken
Projects & initiatives Two active projects, both healthy Healthy
Support staff & delegation One part-time VA; the rest of the admin load is scattered across the team Gap
Systems & AI Documents scattered across three drives; travel booking broken Broken
Transitions Nothing pending Healthy

The scope followed the map: this engagement covered four of the six areas, with baselines counted the same week.

Days 1 to 90 · The build

What we set up in 90 days.

Five tracks ran in parallel. Each item shows what we set up and what it changed.

Executive layer

Inbox rules plus an AI triage layer on the founder's email

400+ unread to inbox zero by week 3, held there since

Agenda automation: every recurring meeting gets an agenda and pre-read built from live documents

Meetings start on the work, not on catch-up

A key-people log: every important conversation captured with owner and next step

Nothing said in a meeting gets lost

Fundraising support: data room kept current, investor follow-ups tracked

Follow-ups out within 24 hours of every call
Leadership rhythm

KPI scoreboard rebuilt: five numbers, one owner each, updated weekly by rule

First complete scoreboard in the company's history

We attend the weekly leadership meeting, run the agenda, and send same-day follow-ups

Decisions leave the room with an owner and a date

Decision log opened and reviewed weekly

Zero decisions reopened for lack of a record
People & culture

Onboarding process written and run for the next hire

First day fully planned before the offer was signed

Offboarding checklist with access removal

No more lingering accounts

Recognition rhythm: one consistent monthly habit, run by us

Started month two, hasn't been missed

Core policies drafted for counsel review

A real handbook instead of a folder of intentions
Process repair

Travel booking was broken: six emails and a double booking per trip. Replaced with one request form, a booking SOP, and a preferred-vendor list

One form, one confirmation, zero double bookings since
Special projects

The company's first quarterly team day: venue, agenda, budget, vendors, and the follow-up survey, planned and run by us

The founder walked in with a printed agenda, same as everyone else

Board meeting preparation: materials assembled, rehearsal scheduled, follow-ups tracked

Deck done two days early instead of the night before
Systems

One document structure across the company, migrated and mapped

Anyone can find anything in two clicks

Two overlapping tools retired; the keeper configured properly

One subscription cancelled, one source of truth

SOPs written for the VA's recurring work, and admin tasks pulled off the team's plates into that lane

Tasks start and finish without the founder's input
Prioritization

How we decide what gets built first.

Everything above went through the same filter. Each candidate is placed by impact and effort, and the weekly priority order comes off this map, not off whoever asked loudest.

High impact Low impact Low effort High effort DO FIRST SCHEDULE NEXT FIT IN LATER LAST IN LINE Inbox rules + AI triage Travel booking fix KPI scoreboard + weekly rhythm Document migration Onboarding process Recognition rhythm Tool consolidation
The cadence

The fixed points of every week.

These are the anchors that never move. Around them, the week fills with the build tracks above: project pushes, vendor coordination, event preparation, documentation, and whatever the impact map says is next.

Daily

Inbox triaged by rule, follow-ups out, the decision log current.

Monday

Priorities set against the impact map. The founder sees the week's plan by 9am.

Wednesday

We're in the leadership meeting: agenda run, scoreboard reviewed, follow-ups out the same day.

Friday

The two-minute summary: what closed, what needs a call, what's queued for Monday.

The term

Everything above happened inside one 90-day term.

Engagements run in 90-day terms, and every term has the same shape: embed, run, review.

EmbedWe learn, map, and take over the agreed work.
Run & improveSteady delivery while the system underneath gets simpler.
ReviewThe numbers, together.
Day 1Day 30Day 90
Baselines counted in week one
First monthly review at day 30
Day-90 results conversation
Beyond day 90

How we stay engaged.

The first term builds the operating layer. After that, none of it stops: we keep running the founder's executive operations, the leadership rhythm, the support staff's direction, and the systems underneath, every week. On top of that standing work, new projects keep arriving: a hire to onboard, an event to produce, a system to level up, a transition to manage. At each day-90 review we put the numbers next to the week-one baselines and set the next term's priorities together. Here's what this engagement's second term opened with, alongside everything already running.

  • Client onboarding documents automated from the signed proposal
  • Second cycle of the recognition rhythm, plus the first culture survey
  • Vendor cost review across all recurring subscriptions
  • KPI scoreboard v2: two numbers replaced with ones that predict, not report
  • The next quarterly team day, now a standing tradition we run

Your company's version of this map gets drawn in the first week. Request a consultation or take the fit check first.