Case study · Strategy-to-execution ecosystem, product intelligence, and automation

TH3RD GROUP — Website, Revenue OS & Market-Readiness Platform

Public website, revenue and delivery operations, automation, product intelligence, and market readiness working as one ecosystem.

Product Operations Lead · Automation Lead

Business Systems Architecture · Product Operations · Market Intelligence · Workflow Automation · AI-Assisted Delivery

Active operating modelRevenue, Delivery & Automation OS: commercial and operational backbone
In developmentTH3RD Compass: product-intelligence and market-readiness layer; module maturity varies
Sanitized reconstructionConnected public ecosystem case

01 · At a glance

What this system enabled

Business need: Public website, revenue and delivery operations, automation, product intelligence, and market readiness working as one ecosystem.
Nelcys’s role: Product Operations Lead · Automation Lead
What was delivered: Strategy-to-execution ecosystem, product intelligence, and automation
Core systems: HubSpot · Notion · n8n · TH3RD Compass

Maturity and public status

Active operating modelRevenue, Delivery & Automation OS: commercial and operational backbone
In developmentTH3RD Compass: product-intelligence and market-readiness layer; module maturity varies
Sanitized reconstructionConnected public ecosystem case

02 · Business need

What the business needed

Designed and built the commercial and operating layers behind TH3RD GROUP’s strategy-to-execution model—from the public website and service architecture to CRM, delivery, automation, product intelligence, and market-readiness workflows.

The website turns TH3RD GROUP’s Strategy · Systems · Execution model into a clear commercial journey for consumer brands and growing businesses.

The original Revenue, Delivery & Automation OS connects HubSpot, n8n, and Notion across CRM, client handoff, project delivery, campaigns, content production, reporting, SOPs, approvals, finance visibility, and operational governance. That system remains the commercial and operational backbone.

TH3RD Compass is an additive product-intelligence and market-readiness layer. It connects source-backed research, product records, evidence, readiness workflows, internal decisions, and operational follow-through without replacing the mature CRM and delivery systems.

The public commercial layer is an Astro + TypeScript static site with CI-validated publishing to GitHub Pages. Server-side inquiry handling is isolated in Cloudflare, which also provides a deployment fallback.

Nelcys owned positioning direction, information architecture, service hierarchy, page narrative, conversion paths, interaction rules, visual and implementation direction, QA, final acceptance, and AI-assisted website development.

Connected system / Six chapters

Add intelligence without replacing the operating backbone.

The Revenue, Delivery & Automation OS remains foundational. Compass expands the ecosystem with specialized intelligence, readiness, and decision support.

Chapter 01

Business and commercial model

The website turns TH3RD GROUP’s Strategy · Systems · Execution model into a clear commercial journey for consumer brands and growing businesses.

The public environment is an Astro + TypeScript static site with CI-validated publishing to GitHub Pages. Server-side inquiry handling remains isolated in Cloudflare.

Market opportunity
Diagnosis
Strategy and readiness
Systems design
Execution
Measurement

Chapter 02

Revenue, Delivery & Automation OS

The previous HubSpot, n8n, and Notion work is preserved as the ecosystem’s commercial and operational backbone.

HubSpot manages commercial truth. Notion manages operational truth. n8n moves and transforms approved data.

Commercial truth

HubSpot

Contacts, companies, deals, lifecycle, activity, proposals, follow-up, pipeline, revenue, accounts, and renewals.

Integration spine

n8n

Intake, normalization, routing, synchronization, schedules, alerts, monitoring, handoffs, and exceptions.

Operational truth

Notion

Clients, projects, RAID, campaigns, content, deliverables, approvals, reporting, finance visibility, SOPs, and governance.

Chapter 03

TH3RD Compass

Compass is the specialized product-intelligence and market-readiness layer. The module-level register keeps the direction visible without presenting the whole platform as production-ready.

DiscoverIn development

Surfaces product and market opportunities for structured investigation.

ProductsIn development

Maintains the working product record and its linked readiness context.

Product IntelligenceIn development

Connects research, classification, comparisons, and decision context.

ReadinessIn development

Turns evidence and requirements into inspectable readiness decisions.

Evidence & SourcesHuman review required

Retains source links, evidence status, provenance, and review context.

My DayIn development

Focuses role-specific reviews, decisions, exceptions, and follow-through.

WorkIntegration pending

Provides an intelligence-enriched action surface without replacing Notion.

CRM & lead visibilityIntegration pending

Presents synchronized commercial context while HubSpot remains authoritative.

Source ConnectionsIntegration pending

Controls authorized research inputs and connection state.

InvestigationsIn development

Orchestrates source-backed product, supplier, and market questions.

Human ReviewHuman review required

Keeps consequential readiness and commercial decisions accountable.

Evidence remains classified as observed, estimated, unavailable, review required, or verified so a sourced fact is never presented as an approved conclusion.

Chapter 04

How the systems work together

The website creates the commercial entry point. HubSpot manages relationships and revenue context. Notion manages execution. n8n coordinates system movement. TH3RD Compass adds product intelligence, source-backed evidence, and market-readiness decision support.

Public websiteAcquisition, education, qualification

HubSpotContacts, companies, deals, lifecycle

n8nIntegration, transformation, routing

NotionDelivery, campaigns, content, SOPs, reporting

TH3RD CompassProduct intelligence, evidence, market readiness

Commercial-to-delivery flow

Website inquiry
HubSpot contact, company, and deal
n8n validation and routing
Notion client, project, and onboarding
Owned execution

Intelligence-to-action flow

Product discovered
Source-backed research
Compass product record and readiness assessment
Human review and decision
Notion task, project, or campaign
Follow-through and reporting

Readiness-to-commercial flow

Market opportunity
Compass evidence and readiness
Strategic recommendation
HubSpot account or opportunity context
Execution plan in Notion
n8n synchronization

Chapter 05

Decisions and rationale

The detailed decision log below explains why HubSpot and Notion remain authoritative, why Compass stays specialized, why n8n remains necessary, and why evidence and AI outputs require human review.

View the ecosystem decisions ↓

Chapter 06

Governance and maturity

Revenue, Delivery & Automation OS: Active operating model
TH3RD Compass: In development · module maturity varies
Compass integrations: Integration and source authorization pending where noted
Compass CRM boundary: Isolated and fail-closed when disabled or unavailable; core Compass work does not imply production CRM authority
Evidence states: Observed · estimated · unavailable · review required · verified
Public case layer: Sanitized demonstration and narrative reconstruction

Compass CRM, lead, account, work, and task screens are described as synchronized operational interfaces or intelligence-enriched views unless verified implementation proves that Compass owns the underlying record. Market-readiness work is not regulatory approval, legal advice, guaranteed compliance, guaranteed retail acceptance, or guaranteed market entry.

03 · What needed to change

The operating risks to resolve

The public website, commercial pipeline, operating command center, and intelligence product needed distinct jobs without creating a fragmented ecosystem.
Compass screens such as CRM, leads, My Day, work, tasks, and accounts could become competing sources of truth if their authority and synchronization rules were not explicit.
Research and market-readiness conclusions needed traceable sources, evidence status, human review, and a clear path into execution.
HubSpot-to-Notion handoffs, Compass integrations, notifications, scheduled work, and reporting preparation required observable routing and exception handling.
Mature operational systems and new Compass modules needed honest, feature-level maturity labels rather than one platform-wide production claim.

04 · What I delivered

My role in the system

I owned the business outcome, operating logic, system boundaries, acceptance criteria, delivery direction, validation, and final acceptance. AI-assisted development and specialist collaboration supported implementation where the context required them.

Defined the strategy-to-execution ecosystem and the responsibility of each layer.
Structured HubSpot around commercial lifecycle, relationships, pipeline governance, account context, and Closed Won readiness.
Designed the Notion operating backbone for clients, projects, execution, RAID, campaigns, content, approvals, finance visibility, SOPs, reporting, and agent governance.
Directed n8n workflow logic for validation, normalization, routing, synchronization, monitoring, alerts, and exception handling.
Shaped Compass product requirements, modules, information architecture, readiness logic, evidence expectations, source connections, and human-review boundaries.
Defined how research and readiness decisions become owned execution in Notion and commercial context in HubSpot.
Directed website information architecture and implementation so the public promise reflects the operating model.
Governed AI-assisted delivery through constraints, priorities, acceptance conditions, validation, and final review.

05 · How it works

How the system works

Selected system

Public website

Uses Astro and TypeScript to communicate positioning, educate prospects, and begin qualification, with CI-validated GitHub Pages publishing and Cloudflare-isolated inquiry handling.

Boundary: It is the commercial front door, not the CRM or delivery system of record.

Systems in context

HubSpot: Commercial source of truth for relationships, lifecycle, pipeline, and revenue context
Notion: Operational source of truth for projects, campaigns, content, reporting, SOPs, and governance
n8n: Integration spine for transformation, synchronization, routing, monitoring, and exceptions
TH3RD Compass: Specialized product-intelligence, evidence, readiness, and decision-support layer
Astro · TypeScript · GitHub Pages: CI-validated static public website and service-conversion experience
Cloudflare: Isolated server-side inquiry validation and delivery, plus deployment fallback
GitHub: Source control, validation workflow, and compiled public-site publishing
AI-Assisted Development: Research, classification, drafting, summarization, and implementation support under human review

06 · How I think

The decisions behind the system

Tools change. The durable work is deciding what owns truth, what may move, what must stop, and what evidence is enough.

Keep HubSpot as the commercial source of truthContacts, companies, deals, lifecycle stages, commercial activity, pipeline, and revenue history remain governed in HubSpot.

Why: Commercial relationships and stage history require one authoritative CRM even when another product presents a specialized working view.

Keep Notion as the operational source of truthClients, projects, execution, RAID, campaigns, content, approvals, SOPs, reporting, and operational governance remain in Notion.

Why: Cross-functional execution needs one adaptable command center rather than duplicated task and project records.

Add Compass without replacing mature systemsCompass owns specialized product intelligence, evidence, readiness, investigations, and decision support.

Why: Rebuilding CRM and project-management functionality would create duplicate records, conflicting statuses, and unnecessary maintenance.
Guardrail: Compass CRM, lead, account, work, and task screens remain synchronized or intelligence-enriched views unless authority is explicitly verified.

Keep n8n as the integration spineUse n8n for validation, transformation, synchronization, routing, schedules, alerts, handoffs, and exception monitoring.

Why: Each platform has a distinct job, and reliable orchestration needs an observable integration layer.

Require source-linked research evidenceReadiness conclusions must retain sources, review context, and an explicit state: observed, estimated, unavailable, review required, or verified.

Why: Market and product recommendations must remain traceable, reviewable, and defensible.

Keep consequential AI output under human reviewUse AI for research, classification, drafting, synthesis, and implementation support while named people retain decisions and acceptance.

Why: Acceleration is valuable only when commercial and readiness decisions remain accountable to evidence and judgment.

07 · How it was delivered

From model to working system

Mapped the business model from market opportunity through diagnosis, strategy and readiness, systems design, execution, and measurement.
Preserved the HubSpot, n8n, and Notion operating architecture across inquiry, Closed Won, onboarding, project creation, campaigns, reporting, and exception handling.
Defined Compass modules for discovery, products, intelligence, readiness, evidence, sources, investigations, My Day, work orchestration, and human review.
Designed the intelligence-to-action path from source-backed research through readiness decision into owned Notion execution and reporting.
Defined synchronized Compass interfaces so CRM, lead, account, work, and task visibility does not silently create another system of record.
Directed AI-assisted implementation against source-of-truth boundaries, maturity labels, validation, and human acceptance.

Guardrails

Where the system must stop

HubSpot remains authoritative for commercial and relationship history.
Notion remains authoritative for operational delivery and governance.
Compass owns intelligence and readiness truth, not every record it displays.
n8n synchronization must be observable, repeatable, and exception-aware.
Observed, estimated, unavailable, review required, and verified evidence remain visibly distinct.
Every Compass module carries its own defensible maturity label.
Consequential AI-assisted outputs require contextual human review.
Market-readiness work is not regulatory approval, legal advice, guaranteed compliance, guaranteed retail acceptance, or guaranteed market entry.
Public language stays within Nelcys’s verified role and contribution.

08 · What changed

What changed

Preserved a coherent commercial-to-delivery backbone across HubSpot, n8n, and Notion.
Expanded the ecosystem with a specialized Compass intelligence and market-readiness layer instead of replacing mature systems.
Made commercial, operational, integration, and readiness ownership explicit.
Created traceable paths from website inquiry to delivery and from source-backed research to owned execution.
Exposed integration, source-authorization, human-review, and production-hardening dependencies before they could be mistaken for completed work.
Connected public positioning to the actual strategy-to-execution operating model.

09 · Public evidence

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
Strategy-to-execution ecosystem map
Shows the public website, HubSpot, n8n, Notion, Compass, and human-review boundaries as one connected architecture.
Sanitized evidence
Revenue, Delivery & Automation OS reconstruction
A sanitized view of CRM handoffs, operating control, campaigns, reporting, SOPs, governance, and exception paths.
Narrative record
Compass module and maturity register
Documents product-intelligence modules, source dependencies, integration state, human review, and production-hardening gates.
Narrative record
Intelligence-to-action flow
Shows how evidence and readiness decisions move into accountable execution without changing the underlying sources of truth.

10 · What this proves

Nelcys can move from business positioning into operating-model design, workflow architecture, automation, internal product development, and public website execution—without losing the boundaries that keep each system reliable.

Discuss a similar system