Product reference · current implementation

Growth work should get more certain with every cycle.

GrowthLoop is a multi-product growth operations system for customer products. It is not a tool that markets itself. It helps a product team connect acquisition, meaningful activation, evidence, and the next safe action.

Start with a product See what is implemented

INPUTGOVERNED FEEDBACKOUTPUT

01Acquire

02Sign up

03Activate

04Attribute

05Learn safely

06Act again

Measured actions return as evidence—not assumptions.

One system of record for the decisions between “we acquired interest” and “we know what to try next.”

The operating loop

From acquisition to a better next action.

Every pass through the loop is designed to retain its context: what was attempted, which safeguards applied, what arrived from the product, and how reliable that evidence was.

01
Acquire
A source link or campaign gives each visit a traceable beginning.
02
Sign up
The connected product records a signed product event.
03
Activate
A meaningful in-product action distinguishes a real start from a visit.
04
Attribute
GrowthLoop connects outcomes to their source and labels data quality.
05
Learn safely
Experiments, approval rules, budgets, and evidence windows shape the decision.
06
Act again
The next action carries its policy, context, and audit trail with it.

Today Implemented

What the workspace already supports.

These are the current operational surfaces. Provider execution still depends on the relevant credentials, permissions, account capabilities, and policy checks.

Product boundaries

Onboard products independently, with separate configuration, credentials, budgets, policies, and records.

Controls before action

Set autonomy mode, approval requirements, budget limits, cooldowns, and an emergency stop before external work can run.

Meta organic Page posts

Prepare, review, schedule, publish, and reconcile the established organic Page-post workflow when the connected account supports it.

Attribution that shows its limits

Use secure tracked links and signed product events; preserve method and quality instead of quietly turning proxy signals into conversions.

Creative with provenance

Keep versioned creative details, media checksums, accessibility text, decision context, and review status together.

Experiment → learning

Define variants and evidence windows, evaluate the result, then apply evidence-backed learning to a versioned policy.

Email operations

The workspace includes product-scoped contacts, consent and geography checks, suppressions, sender status, campaign drafts, message status, and provider outcome ingestion. Sending remains gated by configured provider and sender verification.

Auditability

Decisions, approvals, external intents, reconciliation, outcomes, and policy versions are recorded so a result can be traced back to its conditions.

Next Future-facing

Where GrowthLoop is headed.

These are planned directions, not promises about what the current workspace already performs.

Broader channels, including WhatsApp only for opted-in users and provider-approved templates.
Richer lifecycle journeys that remain product-, purpose-, and consent-scoped.
Deeper analytics and experimentation beyond the current operational loop.
More product integrations, including a VestaViva event connection.

Practical roles

People set the boundary. The system keeps the thread.

Product owner

Defines the product’s goal, meaningful activation, channels, guardrails, budget, and when a human must approve an action.

Operator

Reviews creative and campaigns, works with experiments and learnings, and investigates anything that needs judgment or intervention.

Connected product

Receives traffic and sends signed events such as signup and activation so product outcomes can be measured in their source context.

In plain language

A simple system flow

A person discovers a product through a tracked source. The product records signup and the action that means the person actually got value. GrowthLoop connects those facts to the source, makes the evidence and its quality visible, then lets the team safely decide what to do next.

Boundaries & safety

Questions worth answering up front.

Does GrowthLoop automatically publish or spend?

Only within the product’s configured execution mode, approval rules, budget limits, and verified provider capabilities. Draft-only work does not mutate an external system, and emergency stop blocks new mutations.

What happens when attribution is incomplete?

The system keeps the attribution method and quality with the outcome. A degraded signal can be used only as an explicitly named proxy when policy allows it; it is not presented as a conversion fact.

Can one product’s data be used for another?

No. Product configuration, credentials, assets, budgets, decisions, contacts, and policies are kept product-scoped. Cross-product learning needs an explicit compatible scope and evidence trail.

A practical next step

Start by defining one product’s meaningful activation.

Then set its goal, controls, and connection details in the workspace. GrowthLoop can only improve the loop when the product tells it what “getting value” means.

Open GrowthLoop workspace