Product
Run the whole lifecycle, under human approval.
You acquired the users. Onboarding got built; the at-risk and win-back stages did not. PatternSix is an AI-operated lifecycle service: AI colleagues build and iterate on your email, in-product and messaging programmes, while a named human owner approves every template, consent decision and material journey change.
What PatternSix is
A lifecycle team's work, operated by AI colleagues.
PatternSix designs and runs onboarding, activation, at-risk, win-back and expansion journeys across email and in-product channels. AI colleagues carry out the operating work; accountable humans govern it.
The operating work, done continuously
AI colleagues draft and revise copy, construct and maintain trigger and sequencing logic, segment contacts, schedule sends, and iterate on timing and variants against engagement signals — across many journeys and many accounts.
The whole lifecycle, not just onboarding
A common split is roughly 90% onboarding and 10% everything else, leaving the at-risk and win-back stages — where revenue quietly leaks — unattended. PatternSix keeps the later stages live rather than deferred.
Attached to the tooling you already run
The service connects to your existing CRM and email tooling as the system of record and draws on upstream acquisition and product-usage data. It does not ask you to replace what you have.
The cost line it targets
The wedge is human labour, not per-profile tooling.
What the service operates
Six modules, one governed programme.
Each module is operated by AI colleagues within boundaries a named human owner sets and approves.
Journey Designer
AI colleagues construct behaviour-based trigger and sequencing logic across the full lifecycle, shifting programmes from time-based to behaviour-based triggers. The human owner approves journey logic before any material change goes live.
Message Studio
AI colleagues draft and revise copy and content variants for each channel and lifecycle stage. Templates require human brand approval before deployment.
Segmentation & Targeting
AI colleagues segment contacts using upstream acquisition and product-usage data. Segments feed trigger logic, while consent state governs eligibility.
Consent & Suppression Controls
Suppression rules, consent state and unsubscribe handling are enforced as configured constraints rather than left to discretion. Advertising and data-protection compliance decisions remain with the human owner.
Send-Level Audit Trail
Every send is recorded with a full account of what was sent to whom and why. This gives the human owner an auditable basis for oversight and review.
Performance Iteration
AI colleagues monitor engagement signals and iterate on send timing and variant performance continuously. Material changes to journey logic are surfaced for human approval.
How a programme runs
From a new user to a governed, iterating journey.
The same path every operated account follows.
Onboarding and activation
When a new user or lead enters via connected acquisition and product data, AI colleagues place them into a behaviour-based onboarding sequence, draft stage-appropriate messages and schedule sends. The human owner approves templates and journey logic before activation, and every send is logged to the audit trail.
At-risk and win-back recovery
AI colleagues monitor engagement and usage signals to detect at-risk and lapsed contacts, then trigger targeted recovery journeys — the high-value stages under-resourced teams routinely skip — with suppression and consent state enforced automatically.
Template and material-change governance
Before any new template or material change to journey logic goes live, it is routed to the accountable human for approval. Approved changes deploy, and every resulting send is recorded for later review.
Continuous performance iteration
AI colleagues test send timing and content variants against observed engagement across many journeys, apply non-material optimisations continuously within approved templates and logic, and surface material logic changes for human sign-off.
How autonomy is bounded
Architecture, human control, and the compliance boundary.
Autonomy is bounded by design rather than assumed. AI colleagues do the operating work; named humans govern, approve and hold the fiduciary duty.
- In-product
- Messaging
- Consent-governed
- Owned channels only
AI colleagues operate; humans stay accountable
AI colleagues run continuously and at low marginal cost across many journeys and accounts. Human accountability is exercised at defined control points: approval of templates, consent-handling rules and any material change to journey logic before it goes live.
What AI colleagues may not change alone
AI colleagues may iterate autonomously on non-material optimisations — send timing and content variants within approved templates and logic — but cannot alter approved journey logic or consent rules without human sign-off. Brand, budget and compliance decisions remain human-owned.
Consent enforced as a constraint, not a discretion
Suppression, consent state and unsubscribe are enforced as configured constraints the system cannot override, so no message reaches a contact who has not consented or has opted out. Advertising and data-protection compliance decisions remain with the human owner.
A complete send-level record
Every send is recorded with a full account of what was sent to whom and why, giving the human owner an auditable basis for oversight of regulated, owned-channel communication. The service does not undertake paid acquisition.
Direction, not a promise
Where the product is heading.
These are planned stages of development, stated as direction rather than commitments or forecasts.
Design partners, live journeys
A small cohort of design-partner clients from the FTLAB ecosystem runs live onboarding, activation and initial at-risk/win-back journeys across email and in-product channels, with human approval gates and send-level audit operational. The focus is validating that AI-operated delivery under human governance produces output comparable to a human specialist and building reference relationships.
Full-lifecycle coverage
Coverage extends across onboarding, activation, at-risk, win-back and expansion, with maturing segmentation and continuous performance-iteration loops running across multiple accounts. Reference-led sales begins with North American early- and growth-stage buyers, positioned against the agency-retainer comparable, and consent and audit controls are hardened for the primary market.
Repeatable at low marginal cost
The service operates many journeys across a growing client base at low marginal cost, supported by a repeatable onboarding and governance playbook and accumulating cross-account performance data. Geographic sequencing extends toward Europe following early traction, subject to buyer-census verification.
Before you commit
Questions operators and governance owners ask.
Who approves what before it goes live?
A named human owner approves messaging templates, consent-handling rules and any material change to journey logic before deployment. AI colleagues carry out the operating work within those approvals; the human owner holds the fiduciary duty.
How do you ensure no message reaches someone who opted out?
Suppression, consent state and unsubscribe are enforced as configured constraints the system cannot override, rather than left to discretion. Every send is recorded with a full account of what was sent to whom and why, so the constraint can be demonstrated across every account.
Can AI colleagues change journey logic on their own?
No. AI colleagues iterate autonomously only on non-material optimisations — send timing and content variants within approved templates and logic. Material changes to journey logic or consent rules are surfaced for human approval before they go live.
Does this replace my existing email or CRM tooling?
No. The service attaches to your existing CRM and email tooling as the system of record and draws on upstream acquisition and product-usage data. It operates the lifecycle programme on top of what you already run.
Which channels does PatternSix cover?
Email, in-product and messaging channels for consent-governed, owned-channel communication. The service does not undertake paid acquisition.
How does approval workload stay manageable as journeys grow?
Human accountability is concentrated at defined control points — templates, consent rules and material journey-logic changes — while routine, non-material optimisation runs within those approvals. The approval surface is the set of material decisions, not every individual send.
Keep the whole lifecycle live, without a lifecycle hire.
Tell us about your user base and the journeys you have and have not built. We will walk through how PatternSix would operate them under your approval.