Packs
A pack is a bundle of schema, views, workflows, policies, and connector maps that installs onto your workspace in one approval. Packs are how categories like CRM and CMS exist in Wavetable: as opinions you install, not products you buy.
Because a pack compiles into ordinary artifacts, everything it ships is yours afterward: diffable, forkable, editable, reversible. If the pack’s opinion stops fitting your business, change it. You are never waiting on a vendor roadmap.
Agency GTM pack
The CRM opinion. Installing it gives you:
- Companies and deals with stages and amounts, deals belonging to companies,
- a pipeline board and an open-pipeline metric, pinned to your Canvas,
- a stale-deal follow-up workflow that drafts a nudge when a deal goes quiet,
- a gated welcome email for new form fills: drafted automatically, sent only after approval.
Within one session on a fresh workspace, you have a working pipeline that shares its substrate with your email, revenue, and site traffic.
Content pack
The CMS opinion. Installing it gives you:
- posts with bodies and editorial states,
- an editorial board view for the writing pipeline,
- scheduled publishing workflows,
- traffic attribution: because the site script and the content live in one graph, “which posts drive paying customers” is a question, not a data-engineering project,
- a stale-draft reminder so drafts do not rot.
Published posts serve over a public content API, so your site can render straight from the substrate.
Installing, forking, updating
Installation is an artifact diff in your Inbox like any other change: you see exactly what schema, views, and workflows a pack will create before you approve. Updates from upstream arrive as diffs too, and your local edits are visible against them. Rollback works the same as for any artifact version.