From Playbook to published Service
Publishing turns a Playbook into a Service that other people can pay to run. What the public contract says, and what a customer gets when they buy.
On this page
A Playbook is the method. A Service is that method published so other people can pay to run it. Same object, later stage: the Playbook is the Service's definition, not a separate thing sitting beside it.
The contract is the product page
When a Service is published it carries a public contract, and the contract is made of four statements the Playbook already had to make:
| Line | The question it answers |
|---|---|
| Trigger | What starts a run: you, a schedule, or an event |
| Intake | What you are asked for before the run begins |
| Artifact | What comes back |
| Delivery | Where it arrives, and in what shape |
Almost nothing else in this market publishes that before payment. A buyer usually gets a feature list and a demonstration, and finds out what the finished thing looks like after they have committed.
Publish what a run produces before somebody pays for it, not after.The thing worth copying
What a customer gets
Buying does not hand over the Playbook. It creates an Instance: the customer's own configured copy of the Service, holding their setup, their authorised tools and their data, kept apart from every other customer's.1
So one Service can have many Instances, and the definition stays with the operator who wrote it. Editing the Playbook is editing the Service; it is not editing anybody's data.
What is charged
A run. YAMO charges for the runs that happen and nothing for the ones that do not, which is why the run, rather than the Service or the Instance, is the unit that gets metered and receipted.
The figures are not published yet, so this post is not the place you will find them. The pricing page is where they will appear.
Notes
- 1Instance has meant two different things in older internal notes. The current and only meaning is the customer-scoped container described here, never "one complete execution", which is a run. ↩
More in this series
Read next
What a Playbook actually is
A Playbook is the method an expert captures, written down as a document the runtime follows. What goes in it, what a Play is, and what stays yours.What one run includes
A run is one execution of a Playbook, from the trigger that started it to the artifact it returns. It is also the unit that gets metered and receipted.The method is the asset
An expert who has delivered the same outcome enough times owns a method. Doing the work again by hand for every customer is what that method costs them.Connectors and Connections are not the same
A Connector is the tool a Playbook says it needs. A Connection is the authorisation that lets a run reach it. Two words, and the difference matters.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.
Read a Playbook that does this
Every template in the library publishes its contract and a real example output.