Two kinds of pipeline run the agency. Sales pipelines move an account from a fresh lead to a signed customer (and from renewal-due to renewed). Delivery pipelines move the work itself through each service line — Website, Social, Meta ads, Google ads, SEO. Where a stage needs creative, it hands off to the production platform (app.csoul.cloud) instead of re-building the brief→video engine here.
Both pipelines below are seeded and live today as Pipeline → Stage records. A Deal sits on exactly one stage at a time and carries status (open / won / lost), oneOffValue, mrr, currency, serviceLine and an owner. When a deal is marked Won, the built-in automation flips its Company to isCustomer = true and lifecycle customer — that handoff is what kicks off delivery (Section B).
new-business.qualified.status set to won. Fires the deal-won automation.isCustomer=true + lifecycle customer. Delivery (Section B) begins.lost (with a reason) from any open stage; it leaves the active board but stays on the company timeline for win-back. Reopening sets it back to open on its last stage.renewals-expansion.churned).customer; retainer term extends. Expansion opens a new Engagement.isCustomer → true, lifecycle → customer (live automation).
Once a deal is Won, the work runs through a delivery pipeline on its Engagement. Each service line has its own stage shape below. These pipelines, the Engagement → Deliverable → Task model, and the stage names are an inference about your real workflow — please confirm or correct before we build. Stages flagged via platform do not re-implement creative here; they hand off to the existing brief→video engine on app.csoul.cloud and link the result back to the engagement.
Deliverable → Task records under the same Engagement, so history is preserved month over month.app.csoul.cloud — Social → Create (for reels / video) and Meta ads → Creative (the whole campaign wizard). Everything else stays in the CRM. The CRM never copies the brief→video engine; it stores a link to the platform campaign on the engagement and shows its status.Section A (Sales) is built and live — the New Business and Renewals & Expansion pipelines are seeded in CRM-1a with the deal-won → customer automation. Section B (Delivery) is entirely PROPOSED — confirm: the service lines are real, but the stages, owners and AI assists are our draft of how you run the work. Review each strip and tell us what to change.
See it in context: Journey follows one account across these stages end-to-end; Architecture shows the Engagement → Deliverable → Task data behind delivery and the platform link; AI details each assist named here; SOPs turns the stages into checklists.