Publishing and pricing
Publishing a Playbook so other people can pay to run it: the public contract a Service carries, who configures an Instance, and what is charged.
Publishing turns a Playbook into a Service: the buyable thing, carrying a public contract that says what a run is triggered by, what it asks for, what it produces and how the result arrives.
Posts under this topic cover what changes at that moment. A customer gets an Instance, which is their own configured copy with their setup and their data in it. You keep the definition.
On prices
YAMO charges per run. No figure is published yet, so nothing here names one.
Other topics
Packaging expertise
Turning a method you already follow into a Playbook: what belongs in it, what a Play is, and how the finished thing stays yours to keep editing.Running services
What happens between a trigger and a finished artifact: intake, the ordered Plays, the approvals you keep, and the receipt at the end of a run.Connectors and data
The tools a Playbook declares and the Connections that satisfy them: what a run can reach on your behalf, and what stays exactly where you put it.Pricing
How YAMO charges: you pay for the runs you make, and nothing for the ones you do not. What a run is, what it includes, and what publishing costs.Who it's for
The six kinds of expert YAMO is built for, and what changes when the method you already follow becomes a Service that somebody else can run.