Why bundles
One bundle per floor,
Each Sage and Clover release pairs the SOPs, planning templates, calculators, and onboarding guides a single vertical actually runs on. Buying the bundle cuts the receipts and the rewrites down to one — one price, one release, one document set your team can fill in on the line, not admire in a meeting.
Bundles vs individual tools
The savings come from buying the
A bundle is not four tools with a discount sticker on the box — it is a single release bundle authored as one system. The saving is structural, not promotional.
One release sheet, not a stack of tools.
Every bundle ships as a single coherent release — SOPs, planning templates, calculators, and onboarding guides written to talk to each other. The individual tools you would otherwise stitch together cover a single move; the bundle covers a Monday-to-Friday on the floor.
One purchase receipt, one set of files.
A bundle is a single transaction with one download set in one folder. Buying the same components individually means a separate receipt per artifact, separate version histories, and the work of wiring the documents together on your end.
One update cadence, not four.
When a vertical changes — a new compliance ask, a new vendor, a new floor change — Sage and Clover revises one bundle at a time. The four parts stay in lockstep, so a staff lead never has to chase a single document that drifted from the rest.
What the bundle ships
- One cover sheet that names the floor and the scope of the release.
- A documented SOP set, paired with planning templates so the running version lives next to the policy.
- Calculators pre-wired to the SOP's inputs and onboarding guides written for the line, not the deck.
What you skip by buying the bundle
- Reconciling four separate purchases into one document set your staff will actually open.
- Tracking revisions across tools that ship on different cadences and drift over the year.
- Writing the glue document that names the workflow and links the parts — the bundle ships that document as part of itself.
How the bundle covers a workflow
Four parts of the bundle,
No vertical survives on an SOP alone — it survives on the SOP plus the planning template, the calculator, and the onboarding guide stitched into the same week. The bundle ships the four parts as one operating system, so each plays against the others instead of on its own island.
SOPs
The document your line lead opens on a Monday — the written version of what the floor actually does.
- Open the SOP at the start of a service.
- Hand the printed SOP to a floater when they arrive mid-shift.
- Mark up the SOP at Friday review with the changes worth a revision.
Planning templates
The week-ahead and quarter-ahead documents that drive prep from the floor up, not the deck down.
- Plan next week from the planning template on Sunday.
- Confirm vendor holds and staff coverage before the calendar goes out.
- Compare realised prep to the template at the weekly review.
Calculators
The pre-wired calculators that turn an estimate into a defensible number — food cost, plate cost, and the upcoming deadlines.
- Run the cost calculator before pricing a menu change.
- Track upcoming grant deadlines in the deadline tracker.
- Surface the numbers in the standup, not buried in a spreadsheet.
Onboarding guides
The document a new hire can carry with them on their first week — written for the line, not the deck.
- Walk a new hire through the onboarding guide on day one.
- Have them run the SOP with a partner by the end of week one.
- Pass the marked-up onboarding guide back at week two.
How the bundle gets reviewed
Revisions ride in on not a clock.
The cadence is event-driven, not date-driven — a bundle ships a new version when a vertical genuinely changes, not on a calendar tick. The rhythm below is how Sage and Clover decides what counts as “enough change to revise”.
A new compliance ask.
When a regulator publishes a new rule that touches a vertical — health, food safety, employment, accessibility — the bundle picks up a revision that names the change and threads it through the SOP, the planning template, and the onboarding guide.
A real floor change.
A vendor change, a new service model, a layout change. Each of these ships into the bundle as a marked-up revision; the previous version stays in the changelog so a returning visitor can compare.
A practitioner report.
When a studio-floor client flags an ambiguity in the wild, Sage and Clover revises the bundle to close it. The revision lands with a changelog line so a buyer who already downloaded the prior version knows what changed.
What we'll say out loud about cadence
- A revised bundle is published whenever a new floor change, vendor change, or compliance ask names itself — usually several times a year per vertical, never on a fixed calendar.
- Minor edits — typo fixes, one-line clarifications — do not bump the release. Visit the toolkit detail page to see whether your bundle has a newer file.
- If the calendar date on the bundle ships a fresh revision without a corresponding change on the floor, treat it with the right suspicion.
What you receive on a revision
When the bundle improves,
A revision is not a new product. Everything below lands on the same toolkit detail page you already have bookmarked — the same file set, the same button, a refreshed version.
A re-downloadable PDF for the revised bundle.
Every bundle has a Download PDF button on its toolkit detail page. When a revision ships, that button regenerates the file with the new content — re-download and re-circulate it to your line leads.
A refreshed shipping manifest on the toolkit detail page.
The bundle detail page stays the canonical record of what is in the release. A new revision updates the included-systems list, bumps the publish date, and refreshes the cover card — without moving the release to a new URL.
A written changelog line on the owner surface.
For buyers who want the short version, a changelog note names what changed in the new revision. The line lands as plain text so a staff lead can read it without opening the bundle to find the diff.
A notification window for new revisions (if you opted in).
If you provided an email at purchase, the catalog sends a single notification message per bundle revision. The notification names only the bundle you own and only the changes that reached the release.
Where to go next
Jump straight to
The links below are real pages already shipping. Open the catalog to scan every release, or land on a single-purpose tool if the bundle is more than your floor needs today.
Bundles & toolkit pages
- Browse every toolkitThe catalog — every release Sage and Clover ships, sortable by vertical.
- Nonprofit programs toolkitGovernance, finance, fundraising, and program operations on one bundle.
- Community kitchens toolkitLine systems fitted to community kitchen operations end-to-end.
- Restaurant toolkitFront-of-house, back-of-house, vendor coordination, and kitchen prep.
- Community wellness toolkitProgramming, intake, instructor onboarding, and member comms.
- Event producer toolkitRun-of-show, vendor coordination, and the documents that link them.
- Compare two toolkitsSide-by-side comparison of any two releases on the catalog.
When the bundle stops being enough
Bring us in for the engagement, not the release.
Multi-site rollouts, staff training, custom workflow design — the lane where a consulting engagement outperforms another self-serve toolkit. We'll scope it with your lead team.