One operating system to run the whole customer journey — from first lead to recurring revenue, with AI woven in.
CreatiSoul is a digital-marketing agency (India-based, serving Indian & some foreign clients). The Agency OS is a standalone CRM that runs the front of house — sales, client relationships, delivery management and billing — and links to the existing production platform (app.csoul.cloud) that runs the back of house: the AI ad-creative factory. This page is the map of the whole system, so we can align before we build deeper.
3 + 1
pillars + an AI layer
5
service lines delivered
2 ✓
build phases live (CRM-0, CRM-1a)
Single-tenant
CreatiSoul's own team · roles owner / admin / member / viewer
1
Front of house ↔ Back of house
two systems, one link
The Agency OS is deliberately split. The CRM is the new system we are building — it manages everyone you sell to and everything you owe & deliver. The platform already exists and stays focused on what it does best: turning briefs into AI-generated video & image ad creative. They are loosely coupled and meet at a single link — a Company in the CRM points to a client on the platform; an ads/social Engagement hands a brief over and pulls the finished creative back.
Already live at app.csoul.cloud. The AI ad-creative factory.
Campaigns & briefs — intake → research → ad sets → briefs wizard
AI video & image — per-clip generation engine (Higgsfield, etc.)
Personas & characters — reusable persona + character library
Winning ad formats — format library that steers briefs
Stack: existing production platform + BullMQ host worker + S3 media. The CRM does not rebuild any of this — it links to it.
Why the split matters: the CRM owns the relationship and the money; the platform owns the making of the creative. A Meta-ads or social Engagement in the CRM links straight to the platform's brief engine instead of duplicating it — one source of truth for sales & billing, one for AI production.
2
Three pillars + an AI layer
Everything in the CRM rolls up into three jobs — win the work, deliver the work, get paid for the work — with an AI layer that assists across all three so the small team moves like a big one.
Defaults to the Claude Code subscription (zero-config)
layered in per phase
3
Entity glossary
BuiltPlanned
The shared vocabulary of the system, grouped by pillar. Built = already shipped as a Payload collection in CRM-1a. Planned = designed but not yet built. Field names in monospace are real schema fields.
CRM & SalesPillar 1
CompanyBuilt
The account / business you sell to. Holds lifecycleStage, isCustomer, billing details, GSTIN, currency & the platform-client link.
ContactBuilt
A person at a Company — the human you actually talk to. Many contacts can belong to one company.
LeadPlanned
An inbound enquiry in an intake inbox, with dedup, before it becomes a Company + Deal. Sources live now: website forms + manual entry.
DealBuilt
A sales opportunity in one pipeline + stage, with status open/won/lost, oneOffValue or mrr, currency, serviceLine & owner.
Pipeline / StageBuilt
An ordered set of stages a Deal moves through. Two seeded: New Business & Renewals & Expansion.
ActivityBuilt
A timeline entry — note / call / email / meeting / system — logged against a company, contact or deal.
DeliveryPillar 2
EngagementPlanned
A unit of service per service line (e.g. Meta ads for Acme), opened when a deal is won. The container for delivery work.
DeliverablePlanned
A concrete output within an engagement — a designed page, a month of posts, a campaign launch — usually one per delivery stage.
TaskPlanned
The smallest assignable to-do that rolls up into a Deliverable. Owned by a team member, with a due date.
↗ Platform link
Ads / social engagements don't store creative — they hand a brief to app.csoul.cloud and pull the generated video / image back.
BillingPillar 3
InvoicePlanned
A GST-correct bill (CGST/SGST or IGST, or LUT export for foreign) made of line items, in the account's currency.
LinePlanned
A single charge on an invoice — description, qty, rate, tax treatment — tied to a deliverable or retainer period.
SubscriptionPlanned
A recurring retainer that auto-generates invoices each cycle and carries the account's MRR.
PaymentPlanned
Money received against an invoice — via Razorpay (India) or PayPal (foreign) — reconciled back to the invoice.
4
Build roadmap
2 phases liveCRM-1b next
A phased path from foundation to a full operating system. Foundation & the core collections are already live; the custom Warm UI is the immediate next lift, then lead intake, delivery, billing, payments and dashboards layer on. The AI assist features are folded into each phase as it lands.
Razorpay (India) + PayPal (foreign); reconcile payments & run dunning.
Planned
6
CRM-6
Dashboards
Pipeline, revenue (MRR / collections) & delivery health for the whole business.
Planned
How to read this package
This is the Overview — the executive summary of CreatiSoul Agency OS. The sibling pages go deeper: Journey walks a customer from first touch to renewal; Architecture shows the data model & how CRM links to the platform; Pipelines maps every sales & delivery stage; SOPs documents the operating procedures; AI details the integrated assist layer.
Anything tagged PROPOSED — confirm is an inference about your specific process and needs your sign-off before build. Only CRM-0 (foundation) and CRM-1a (Company / Contact / Deal / Pipeline / Stage / Activity + deal-won automation + 2 seeded pipelines) are actually live today; the rest is the agreed plan.