Primary source: raw strategy transcript
A source-grounded map of how Collective sells simple outcomes externally while building an internal operating system for repeatable delivery, lead intelligence, knowledge reuse, dashboards, and governed agent workflows.
Diagram
The centre is the internal OS. The outer nodes are the client-facing offer, reusable workflows, intelligence systems, and governance loops.
2,284-line raw chat transcript containing founder prompts, corrections, approvals, assistant synthesis, and the CKF prompt.
393-line CKF summary with source index, glossary, evidence ledger, risks, KPI ladder, operating cadence, and QA pass.
Approved commercial shape
The website and sales story should lead with outcomes. The OS, agentic workflows, Dragonfly, HyperCTRL.ai, and deeper governance logic stay mostly internal unless they help a specific audience make a better decision.
Generate qualified enquiries through campaign strategy, paid media, lead pages, tracking, and optimisation.
Build trust, authority, education, and familiarity before buyers are ready to enquire.
Improve what happens after enquiry: onboarding, qualification, follow-up, speed-to-lead, and handoff.
Diagnose growth constraints, set the operating rhythm, and reserve executive visibility for mature clients.
Operating model
The source material repeatedly separates product pillars from the internal workflow layers that make delivery repeatable.
Audit the client, define fit, identify missing inputs, and choose the first growth constraint to solve.
Capture practical brand, offer, audience, proof, objections, tone, and domain knowledge for execution.
Build lead pages, campaign assets, forms, tracking, creative inputs, launch checklists, and reporting setup.
Turn extracted knowledge into SEO, blogs, social content, authority assets, and distribution workflows.
Capture post-lead signals, call summaries, MQL/SQL logic, objections, source quality, and sales handoff data.
Use dashboards, diagnostics, tests, and client feedback to improve the whole path from attention to opportunity.
Map human work first, standardise it, benchmark output, then introduce governed agentic assistance.
Agentic rule
The raw transcript approves a human-benchmark-first path. Codex can accelerate the documentation, tooling, comparison, and QA work, but the human owner keeps judgment, approvals, and rollback.