Services
A service is a productised piece of work — a monthly content package, an audit, a setup. Defining one means a client can order it, it produces a work order automatically, and it bills consistently. It is the difference between selling time and selling a thing.
Services
| Service | Price | Recurrence | Orders (90d) | State |
|---|---|---|---|---|
| Monthly content — 4 articles | £1,200 | Monthly | 18 | Live |
| Technical site audit | £850 | One-off | 6 | Live |
| Onboarding setup | £450 | One-off | 11 | Live |
| Legacy retainer | £2,000 | Monthly | 0 | Hidden |
The publisher catalog
For work that involves placing something somewhere — content, outreach, listings — the catalog holds the publishers and what is known about each. It is a reference the team works from rather than something a client browses, and it is the sort of institutional knowledge that otherwise lives in a spreadsheet somebody maintains alone.
Desk knowledge
A knowledge base for the team: how a particular client likes things done, how a publisher's process works, the playbook for a service. It is deliberately internal and never client-visible.
In practice a mature workspace has far more institutional knowledge in the comments on past work orders and projects than in any knowledge base — because that is where people actually write things down. When looking for how something was handled before, search the work first. The knowledge base is for what somebody sat down to write, which is always less.
What this does not do
A service can be ordered regardless of whether you have anyone free.
Variants are separate services.
A service has one price. Discounts are coupons.
An ordered service becomes a work order.
Questions
Can a service be hidden from some clients?
It can be hidden entirely; per-client visibility is not supported.
Does ordering charge immediately?
It depends on the service and its billing setup. See Billing.
Can services be bundled?
Not as a bundle object. Create a service that represents the bundle.