Skip to main content
YAMOYAMO
Fractional ops

Playbooks for fractional ops specialists

You rebuild the same reporting rhythm at every company you join. Capture it once and the next engagement starts from your method rather than from nothing.

Where the time goes

Every engagement starts by rebuilding the last one.

  • The weekly report is reassembled from the same places, by hand.
  • What you set up leaves with you when the engagement ends.
  • The number of clients you can hold is the number of rhythms you can run.
What you give, what you get

The contract, in four lines

Every Service on YAMO publishes the same four things. Nothing here is a promise about the future: it is what a run does.

Trigger
On demand, or on a schedule that matches the reporting rhythm
Intake
The period to cover, and the accounts the numbers come from
Artifact
The report you already produce, in the format you produce it
Delivery
Back in the account that started the run, priced per run
Before you build one

Common questions

Does the client keep it when I leave?

That is your decision, and it is a publishing decision rather than a technical one. A Service you publish is theirs to run; a Playbook you keep private stays yours.

Can one Playbook serve more than one client?

Yes. Each customer gets their own Instance — their configured copy — so the method is shared and the setup, the data and the runs are not.

The rest of the site

Where to go next

Start here

Build the Service you already deliver

Copy a Playbook out of the library, point it at your own references, and run it.