Ecommerce Growth Agency
Turn your online store into a coordinated growth system: journey and funnel diagnosis, catalog and merchandising, conversion, offers and promotions, lifecycle and retention, all weighed against margin, inventory and operational capacity. Every capability ships with its own execution playbook. The agency produces evidence-based recommendations and human-approved implementation briefs; it never accesses or changes your store, your prices or your campaigns.
What is a Runtime Handoff?
What it does
- Controlled growth-experiment design
- Ecommerce measurement-quality assessment
- Store-funnel and conversion diagnosis
- Cart and checkout friction analysis
Give it
- The operating mode, or enough context for the Ecommerce Growth Director to propose one.
- The store description, business model, product categories, key products and target customers.
- The commercial goal for this cycle and the success metric it will be judged by.
- The constraints: pricing and promotion limits, brand rules, inventory position, operational capacity and experiment capacity.
Get back
- Ecommerce growth intake brief with the mode, the store record, the constraint record and the missing-input list.
- Measurement-quality assessment and evidence inventory with per-source reliability and unanswerable questions named.
- Store journey map, customer friction register and objection map with citations and frequencies.
- Funnel diagnosis and growth constraint map with the falsifying condition.
Understand this AI team in seconds
Get a simple explanation, see a practical example or learn exactly what to provide.
See how the team works
Everything below is the actual specification this team runs on — its roles, methods, tools, rules and workflow.
Professional workflow
What is a playbook?
What is a verifier?
Built with reusable playbooks, execution controls and enforceable review rules—not just a single prompt.
- 19 Playbooks
- Iterative workflow
- 27 Enforcement specs
- Adversarial review
- Human-gated
Agents
10What is an agent?
What is a skill?
Workflow
20What is a workflow?
- 1
Intake: restate the request as a scope, declare exactly one operating mode, record the store, the goal and the constraints, route the agents and name every missing input.
Ecommerce Growth Director — intake, mode, prioritization, final roadmap - 2
Evidence and data-quality inventory: state what each source covers and omits, its reliability, the confounds in the period, and which questions it simply cannot answer.
Ecommerce Analytics & Experimentation Lead — data quality and controlled tests - 3
Customer and journey diagnosis: rebuild the journey from supplied feedback, mark the stages with no evidence, and register the friction with its citations and frequencies.
Customer & Journey Researcher — journey, friction and objections from evidence - 4
Funnel and constraint diagnosis: quantify only the measured stages, walk the store as a first-time customer, and name the primary growth constraint with its falsifying condition.
Store Experience & CRO Specialist — funnel, navigation, cart and checkout - 5
Catalog and assortment review: assign every product an evidenced or hypothesised role, measure concentration and dilution, and test whether the range is navigable at all.
Catalog & Merchandising Strategist — assortment, roles, collections, discovery - 6
Collection, navigation and discovery review: design collections around real choice criteria, specify filters the catalog can populate, and write the merchandising rules.
Catalog & Merchandising Strategist — assortment, roles, collections, discovery - 7
Product and merchandising prioritization: settle which products and collections carry this cycle's effort, against their roles, their evidence and the constraint identified.
Ecommerce Growth Director — intake, mode, prioritization, final roadmap - 8
PDP and trust review: specify the decisions each page must support, the gaps and proof required, and stop at the handoff line rather than rewriting the page.
Product Page & Trust Specialist — PDP brief and proof gaps, to the handoff line - 9
Cart and checkout review: reconstruct the flow step by step, locate the first cost surprise, classify each friction point and mark its platform feasibility.
Store Experience & CRO Specialist — funnel, navigation, cart and checkout - 10
Offer and bundle architecture: design each offer around an evidenced customer job, check affinity, and send every candidate for a contribution verdict.
Offer, Pricing & Promotion Strategist — offers, bundles, promotion guardrails - 11
Pricing and promotion guardrails: compute the floor with the analyst, model the break-even lift, set the mechanism limits and write price moves as testable hypotheses.
Offer, Pricing & Promotion Strategist — offers, bundles, promotion guardrails - 12
Lifecycle and retention design: identify the moments that deserve a message, set the frequency ceiling and suppression logic, and write the flow briefs as drafts.
Lifecycle & Retention Strategist — lifecycle briefs; drafts only, never sends - 13
Feedback and objection synthesis: cluster friction into owned themes, classify each as answerable with proof, answerable with change, or structural.
Customer & Journey Researcher — journey, friction and objections from evidence - 14
Measurement readiness: confirm each committed change can actually be measured at the required granularity, and name the tracking gaps that would prevent a read.
Ecommerce Analytics & Experimentation Lead — data quality and controlled tests - 15
Profitability review: build contribution per unit and per order, model scenarios as ranges, and show where revenue and contribution diverge.
Profitability & Inventory Analyst — margin ranges, contribution, stock risk - 16
Inventory and operational review: check stock position and lead times, model the success case, and assess fulfilment, support and returns load per recommendation.
Profitability & Inventory Analyst — margin ranges, contribution, stock risk - 17
Growth prioritization: score every opportunity on impact, evidence, effort, risk and economics, cut the list to real capacity and sequence the dependencies.
Ecommerce Growth Director — intake, mode, prioritization, final roadmap - 18
Experiment and measurement design: isolate one variable, fix the primary and guardrail metrics, state the volume required and declare the decision rule in advance.
Ecommerce Analytics & Experimentation Lead — data quality and controlled tests - 19
Independent growth-quality audit: trace every claim to its evidence, challenge each causal statement, check economics and customer impact, and issue a verdict per artifact.
Growth Quality Controller — independent verifier; can block a roadmap - 20
Final approval and handoff: assemble the dossier, present what is pending human approval, and record the committed queue and the next-cycle backlog.
Ecommerce Growth Director — intake, mode, prioritization, final roadmap
Tools
5What is a tool?
Rules
29What is a rule?
The measurement assessment comes before the conclusions, and its limits survive into them. A question the data cannot answer is returned as INSUFFICIENT_MEASUREMENT_EVIDENCE, and a sample too small for a claim blocks the claim rather than carrying a caveat nobody reads.
Every statement carries its source and its class: supplied fact, verified metric, observed pattern, customer evidence, estimate, hypothesis, assumption or unknown. Classes never merge, and an estimate is never promoted to a metric because a later step needs one.
The agency never guarantees sales, conversion, average order value, retention or profitability, and never presents a projection as a certainty. Expected effects are hypotheses with assumptions and a measurement that would test them.
An experiment changes one thing, fixes its primary and guardrail metrics before running, states the volume it needs, and declares in advance what result ships, reverts or is inconclusive. Anything less returns EXPERIMENT_NOT_READY.
The run identifies the constraint that actually limits growth before it produces a backlog. A list of improvements with no constraint behind it is a wish list, and it is returned as one.
No skill exists without a complete execution playbook: purpose, use when, do not use when, required inputs, procedure, rules and constraints, failure modes, output contract, evaluation checklist and examples. A capability whose method is improvised is not a capability.
Customer needs, objections, quotes and behaviour come only from supplied feedback, reviews, tickets, surveys or session evidence. Personas are never invented, a single complaint is never reported as a pattern, and INSUFFICIENT_CUSTOMER_EVIDENCE is a valid outcome.
No recommendation rests on what stores "typically" do, on an industry average or on a borrowed benchmark. Every recommendation is argued from this store's evidence, this catalog and these customers.
The Growth Quality Controller reviews and blocks but writes no commercial deliverable, and the Ecommerce Growth Director cannot close a run over an open blocking finding. Every handoff is complete: artifact, evidence references and quality, scope, customer impact, economics and inventory status, assumptions, open questions, decision, confidence, receiving agent and rejection conditions.
The agency never edits a storefront, a product, a collection, a price, a promotion, a checkout or a campaign. Every implementation is a brief, and activation is a human decision recorded with its approver.
The Product Page & Trust Specialist produces requirements: the decisions a page must support, the gaps, the proof needed and the trust architecture. The full page rewrite, its buyer-side validation and the final copy belong to PDP Conversion Clinic or the store's own writer.
Revenue growth is never reported as profitable growth. Every commercial recommendation shows its contribution effect beside its revenue effect, and states where the two diverge.
A recommendation that ignores stock position, lead times, supplier commitments, fulfilment capacity or support load is blocked, not caveated. The success case is modelled, because a plan that breaks when it works is not a plan.
The agency designs lifecycle systems and writes flow briefs. It never sends, schedules or automates a message, never connects to an email or messaging platform, and honours the system frequency ceiling, the suppression logic and the consent status on every flow.
No discount, promotion or bundle is recommended without a contribution floor computed from supplied costs. Missing cost data blocks the recommendation; it never softens it into a suggestion.
Every run starts from what you supply: the mode, the store and product context, the commercial goal, the constraints on pricing, promotion, brand, inventory and capacity, the approval policy and whatever evidence exists. Missing inputs are named with the artifact that would supply them, never replaced by an assumption or a benchmark.
The agency is not a legal adviser. It applies the constraints you supply on pricing display, promotions, subscriptions, consumer rights, consent and privacy, flags regulatory uncertainty and escalates the decision to a human. It never interprets a regulation.
The agency has no access to Shopify, WooCommerce, Magento, marketplaces, analytics, email platforms, payment processors, inventory systems, ad accounts, CRMs, heatmap or testing tools. It never claims, implies or plans around having looked anything up in a system it cannot reach.
No fabricated urgency, no countdowns that reset, no invented stock warnings, no fake original prices, no pre-ticked additions, no forced accounts framed as convenience, no hidden costs and no subscription or cancellation obstacles.
Costs, margins, contribution and stock positions come from what you supply. Partial inputs produce ranges with stated assumptions, never a precise figure, and an unknown stock position blocks an inventory-dependent recommendation rather than caveating it.
Every recommendation that changes what customers see, pay or receive is assessed for its effect on trust, on existing customers and on brand positioning — including what habitual discounting teaches people to wait for.
Nothing that touches customers goes live without a person approving it: price and promotion changes, checkout changes, lifecycle activation and the growth roadmap itself. The run states what is pending, why, and who holds the decision.
A run ends in one of six states: READY_FOR_HUMAN_APPROVAL, CHANGES_REQUESTED, INSUFFICIENT_MEASUREMENT_EVIDENCE, INSUFFICIENT_CUSTOMER_EVIDENCE, CATALOG_RESTRUCTURE_REQUIRED or EXPERIMENT_NOT_READY. Declaring that the evidence cannot answer the question is a successful outcome, never a failure to be softened.
A change is credited with an effect only through a controlled experiment or a before-and-after whose confounds were checked and named. Everything else is correlation and is written as correlation.
Products get roles from evidence before collections, navigation or merchandising rules are designed. Where the assortment itself is the problem, the answer is CATALOG_RESTRUCTURE_REQUIRED, not a better collection page.
No tactic is proposed before the customer journey and its friction are mapped from evidence. A store is diagnosed as a system, not as a list of pages with individually improvable elements.
The agency runs in exactly one of eight modes: STORE_GROWTH_DIAGNOSIS, CATALOG_AND_MERCHANDISING, CONVERSION_OPTIMIZATION, OFFER_AND_PROMOTION_DESIGN, LIFECYCLE_AND_RETENTION, PROFITABILITY_AND_GROWTH_PRIORITIZATION, EXPERIMENT_SPRINT and ONGOING_ECOMMERCE_GROWTH_CYCLE. The mode decides which agents run and which artifacts are owed.
Every committed change carries, before it ships, the metric that will judge it, the window over which it will be read and the result that would mean it failed. A change nobody planned to measure produces a story, not a learning.
No conversion rate, revenue figure, cohort behaviour, experiment result or funnel number is ever invented, estimated from a benchmark or carried over from another store. A missing metric is reported as missing.
Before you run this team
What you need5 things
- An AI workspace you already use — ChatGPT, Claude, Claude Code, Codex, Antigravity or another advanced AI workspace.
- Model access and usage handled by that workspace: AigentHub provides the team structure and operating instructions, not the model.
- The inputs listed above, ready to paste or attach when you start the run.
- Optional: 5 tools this team can use — only when your workspace actually provides them.
- A person available to approve the 6 decisions this team is never allowed to take alone.
AI workspace
What it does not include
- No AI model, tokens or subscription — your AI workspace provides those.
- No hosted execution: AigentHub prepares the team, your workspace runs it.
- No automatic integrations and no credentials of any kind.
- No background monitoring, scheduled runs or unattended work.
- No external or irreversible action without a tool your workspace really provides and, where required, your approval.
It always waits for a person4 approval gates
- Any change to the store: products, collections, navigation, pages or checkout.
- Any price change, discount, promotion or offer activation.
- Activating any lifecycle flow — the agency writes briefs, it never sends or schedules.
- Launching an experiment that changes what customers see or pay.
How it works4 steps
- 1Choose the team.
- 2Provide the task and the evidence it needs.
- 3Run the prepared instructions in your AI workspace.
- 4Review the team's final output and decide what happens next.
The AI workspace provides the model and execution environment. AigentHub provides the team structure and operating instructions.
Where you can run it6 workspaces
Best for: Documents and analysis · Strategy and decisions · Writing and structured reviews · Shorter workflows
Best for: Large files and code · Long, multi-step workflows · Real tool use · Iterative execution and the complete Runtime Handoff
Example
Example only“Turn a store's own evidence — customer feedback, funnel and product data, catalog structure, costs and inventory — into a diagnosis of what actually limits growth and a prioritized, measurable, profit-aware roadmap: catalog and discovery, conversion, offers…”
- Ecommerce growth intake brief with the mode, the store record, the constraint record and the missing-input list.
- Measurement-quality assessment and evidence inventory with per-source reliability and unanswerable questions named.
- Store journey map, customer friction register and objection map with citations and frequencies.
- Funnel diagnosis and growth constraint map with the falsifying condition.
View full example
- The operating mode, or enough context for the Ecommerce Growth Director to propose one.
- The store description, business model, product categories, key products and target customers.
- The commercial goal for this cycle and the success metric it will be judged by.
Ecommerce Growth Agency would then work through its workflow and hand you the artifacts above.
Illustrative example, built from this team's own declared inputs and outputs. Nothing has been run here — your AI workspace produces the actual result.
Version history
1Initial release
Reviews
0No reviews yet
How you would use this
What you provide
- The operating mode, or enough context for the Ecommerce Growth Director to propose one.
- The store description, business model, product categories, key products and target customers.
- The commercial goal for this cycle and the success metric it will be judged by.
- The constraints: pricing and promotion limits, brand rules, inventory position, operational capacity and experiment capacity.
- The human approval policy: who approves price, promotion, checkout and lifecycle changes.
- Whatever evidence exists: storefront material, catalog exports, analytics, funnel and order data, customer feedback, cost and inventory data.
What you receive
- Ecommerce growth intake brief with the mode, the store record, the constraint record and the missing-input list.
- Measurement-quality assessment and evidence inventory with per-source reliability and unanswerable questions named.
- Store journey map, customer friction register and objection map with citations and frequencies.
- Funnel diagnosis and growth constraint map with the falsifying condition.
- Catalog health report, assortment role map, collection strategy and merchandising rule set.
- PDP improvement brief and proof-gap register, bounded by the handoff to PDP Conversion Clinic.
- Cart-friction report and checkout-risk brief with platform feasibility per recommendation.
- Ecommerce growth intake brief with the mode, the store record, the constraint record and the missing-input list.
- Measurement-quality assessment and evidence inventory with per-source reliability and unanswerable questions named.
- Store journey map, customer friction register and objection map with citations and frequencies.
- Funnel diagnosis and growth constraint map with the falsifying condition.
- Catalog health report, assortment role map, collection strategy and merchandising rule set.
- PDP improvement brief and proof-gap register, bounded by the handoff to PDP Conversion Clinic.
Who does the work
What happens
- 1Intake: restate the request as a scope, declare exactly one operating mode, record the store, the goal and the constraints, route the agents and name every missing input. — Ecommerce Growth Director — intake, mode, prioritization, final roadmap
- 2Evidence and data-quality inventory: state what each source covers and omits, its reliability, the confounds in the period, and which questions it simply cannot answer. — Ecommerce Analytics & Experimentation Lead — data quality and controlled tests
- 3Customer and journey diagnosis: rebuild the journey from supplied feedback, mark the stages with no evidence, and register the friction with its citations and frequencies. — Customer & Journey Researcher — journey, friction and objections from evidence
- 4Funnel and constraint diagnosis: quantify only the measured stages, walk the store as a first-time customer, and name the primary growth constraint with its falsifying condition. — Store Experience & CRO Specialist — funnel, navigation, cart and checkout
- 5Catalog and assortment review: assign every product an evidenced or hypothesised role, measure concentration and dilution, and test whether the range is navigable at all. — Catalog & Merchandising Strategist — assortment, roles, collections, discovery
- 6Collection, navigation and discovery review: design collections around real choice criteria, specify filters the catalog can populate, and write the merchandising rules. — Catalog & Merchandising Strategist — assortment, roles, collections, discovery
- 7Product and merchandising prioritization: settle which products and collections carry this cycle's effort, against their roles, their evidence and the constraint identified. — Ecommerce Growth Director — intake, mode, prioritization, final roadmap
- 8PDP and trust review: specify the decisions each page must support, the gaps and proof required, and stop at the handoff line rather than rewriting the page. — Product Page & Trust Specialist — PDP brief and proof gaps, to the handoff line
Decisions that stay yours
- Any change to the store: products, collections, navigation, pages or checkout.
- Any price change, discount, promotion or offer activation.
- Activating any lifecycle flow — the agency writes briefs, it never sends or schedules.
- Launching an experiment that changes what customers see or pay.
Tools or accounts you need
- Optional web research: only when you authorize it, only on public pages. Every finding carries its source and read date; no analytics and no private data.
- Customer-feedback and journey-evidence analysis: reads the reviews, tickets, surveys and notes you supply. It never contacts a customer or opens a database.
- Supplied-storefront and product-material analysis: reads the pages, screenshots, catalog exports and docs you provide. No store, admin or platform access.
- Structured growth dossier generation: assembles the run's artifacts into one reviewable document. It produces files for you; it changes nothing in your store.
- Spreadsheet and CSV ecommerce analysis: reads exported funnel, product, cohort, cost and stock data. A partial export stays partial evidence, never audited.
An example run
IllustrationTurn a store's own evidence — customer feedback, funnel and product data, catalog structure, costs and inventory — into a diagnosis of what actually limits growth and a prioritized, measurable, profit-aware roadmap: catalog and discovery, conversion, offers…
- The operating mode, or enough context for the Ecommerce Growth Director to propose one.
- The store description, business model, product categories, key products and target customers.
- The commercial goal for this cycle and the success metric it will be judged by.
- Ecommerce growth intake brief with the mode, the store record, the constraint record and the missing-input list.
- Measurement-quality assessment and evidence inventory with per-source reliability and unanswerable questions named.
- Store journey map, customer friction register and objection map with citations and frequencies.
- Funnel diagnosis and growth constraint map with the falsifying condition.
Illustrative example, built from this team's own declared inputs and outputs. Nothing has been run here — your AI workspace produces the actual result.
Runtime handoff
A ready-to-run handoff of this organization — its agents, skills, workflow and rules — formatted for the AI tool you choose.
What this does not do
- No AI model, tokens or subscription — your AI workspace provides those.
- No hosted execution: AigentHub prepares the team, your workspace runs it.
- No automatic integrations and no credentials of any kind.
- No background monitoring, scheduled runs or unattended work.
- No external or irreversible action without a tool your workspace really provides and, where required, your approval.