Give each system a clear job
- Decision
- Keep commercial truth in HubSpot and operational truth in Notion.
- Why
- Forcing sales context and detailed execution into one tool weakens both views and creates duplicate maintenance.
Case study · Revenue, delivery, and automation operating system
TH3RD GROUP — Revenue, Delivery & Automation OS
A commercial-to-operational system connecting CRM, delivery, automation, reporting, SOPs, and structured execution.
Product Operations & Automation Lead
- Active operating modelCommercial and delivery architecture
- Sanitized reconstructionPublic case study
01 · At a glance
The operating context
- Organization
- TH3RD GROUP
- Role
- Product Operations & Automation Lead
- Period
- Selected engagement
- System type
- Revenue, delivery, and automation operating system
Maturity and public status
- Active operating modelCommercial and delivery architecture
- Sanitized reconstructionPublic case study
02 · Context
What the environment demanded
Revenue activity, client onboarding, delivery, content and campaign operations, documentation, reporting, and finance visibility required one coherent operating model without collapsing every function into the same platform.
Nelcys shaped the service and delivery architecture, CRM structure, operational system, workflow automation, reporting cadence, SOPs, and website information and implementation direction in her role as Product Operations & Automation Lead.
03 · The real problem
The risk was larger than a messy workflow.
An operating model connecting market activity, client onboarding, delivery, campaign operations, documentation, reporting, and exceptions without forcing every function into one tool.
Commercial context and delivery execution lived in different systems and rhythms.
Onboarding, campaigns, reporting, and exception handling needed explicit owners and handoffs.
Automations had to support the operating model without obscuring decisions or removing human review.
The website and service narrative needed to reflect the actual execution model.
04 · Ownership
What I owned
I owned the framing, operating logic, constraints, acceptance model, and delivery direction. Implementation was completed with engineering and/or AI-assisted tools according to the engagement context; I do not claim to have hand-written every line.
- Defined the service architecture and market-readiness workflow.
- Structured HubSpot around commercial lifecycle and relationship context.
- Built the Notion operating model for delivery, governance, and documentation.
- Directed n8n workflow logic and human-review boundaries.
- Shaped client onboarding, campaign and content operations, reporting cadence, and finance visibility.
- Created SOP and governance patterns plus the website’s information architecture and implementation direction.
05 · System map
Boundaries before integrations.
HubSpot holds commercial truth, Notion holds operational truth, and n8n connects the two through explicit workflow rules. AI-assisted execution supports the work but does not own client, financial, or delivery decisions.
HubSpot
Holds commercial truth and relationship context.
Boundary: It does not become the detailed delivery workspace for every function.
Notion
Holds operational truth, delivery plans, documentation, decisions, and exceptions.
Boundary: Commercial lifecycle history remains in the CRM.
n8n
Moves approved context and triggers across commercial and operational workflows.
Boundary: Automation follows documented rules and preserves review for material decisions.
Human and AI-assisted execution
Supports research, drafting, summarization, reporting, and repeatable delivery tasks.
Boundary: Outputs remain subject to owners, standards, evidence, and human acceptance.
Systems in context
- HubSpot
- Commercial truth, lifecycle context, and relationship history
- Notion
- Operational truth, delivery control, SOPs, and decisions
- n8n
- Integration and automation across approved workflows
- AI-assisted tools
- Research, drafting, summarization, and execution support under human review
06 · Decisions and rationale
The judgment behind the system.
Tools change. The durable work is deciding what owns truth, what may move, what must stop, and what evidence is enough.
Automate transitions, not accountability
- Decision
- Use n8n to move approved context and trigger work while named owners retain decisions and acceptance.
- Why
- Automation can reduce handoff friction, but it should not hide who is responsible for the result.
Design onboarding as an operating workflow
- Decision
- Connect the commercial promise to delivery scope, owners, inputs, reporting, and exceptions.
- Why
- A signed agreement does not create delivery readiness by itself.
Keep AI output reviewable
- Decision
- Use AI for assisted research, drafting, and summarization under documented human review.
- Why
- Faster output only creates value when it remains aligned to the service, evidence, and client context.
07 · Implementation
How the model became executable
- Mapped the commercial-to-delivery lifecycle and assigned system ownership at each transition.
- Structured CRM, delivery workspaces, SOPs, reporting, and exception pathways around that lifecycle.
- Directed automation logic for repeatable handoffs and notifications.
- Aligned campaign, content, onboarding, finance, and client-delivery rhythms.
- Translated the operating model into website information architecture and implementation direction.
Guardrails
Where the system must stop
- Commercial and operational truth remain distinct and traceable.
- Material client and finance decisions retain human ownership.
- AI-assisted outputs require contextual review.
- Public language stays within Nelcys’s verified role and contribution.
08 · Outcomes
What changed
- Created a clearer operating model connecting revenue, onboarding, delivery, campaign execution, documentation, reporting, and exceptions.
- Reduced pressure to force unrelated functions into a single platform.
- Made system ownership, transitions, and review points easier to inspect.
- Connected brand and website direction to the operating reality behind the services.
09 · Evidence register
What the public record can show
Evidence is described conservatively. Any visual proof added to this page must be redacted, captioned, and checked before publication.
Diagram
Commercial-to-delivery system map
Shows how lifecycle context moves from CRM into operational planning and governed execution.
Sanitized evidence
Operating-system reconstruction
A sanitized view of delivery control, reporting, SOP, and exception structures.
Narrative record
Workflow rationale
Narrative record of system ownership, automation boundaries, and review points.
10 · What this proves