01 / 21
Amplio Data · internal — Velo

Go to market.
Month over month.

The Velo growth plan, updated to where we actually stand in July 2026 — five disciplines, one north star, and the twelve month target model behind it.

Launch · Mon Aug 31, 2026 North star · recovered signals / week Cadence · Monday growth review Instrumentation · live
v2 · built 2026-07-22 · source: knowledge/velo/growth-strategy.md + growth-plan.md
Ground truth · Jul 22, 2026

Where we stand today.

Live

Product

Staging passed end to end Jul 10: plans, metering, freezes, seats, roles. Banner SDK 12.3KB against a 30KB budget. Billing still stubbed.

Live

Dogfood site 1

The v2 banner runs on veloconsent.com itself. Our own product on our own site — displacement starts at home.

Live

Measurement

GA4 spine live through the first party /m endpoint (GTM-MBS9C4KL), verified Jul 16: scan_start, scan_complete, deep_scan_request, early_access_signup, newsletter_signup, contact_submit — leads carry hashed email for enhanced conversions.

Live

Distribution

GTM Community Template submitted and in gallery review — ahead of the plan. Site at 37 indexable pages, one AEO post per day, honest scan tool.

Live

Hosting decided

D3 closed Jul 21: production runs on the Amplio Cloudflare account. Snippet host and edge api unblocked.

Open

The funnel starts at zero

Early access list: 0 signups. The capture machinery exists (deep scan invite, early access form) — what's missing is traffic to it and a nurture arc behind it. No spin: the list is what the next 30 days build.

Open

D4 — Leon arrangement

Role, revenue share, IP. Gates the Stripe flip (D5). Due before real money flows.

Decided Jul 22

Pilots — Amplio + Certify

Walter's call: ampliodata.io (replacing the Usercentrics we pay for, Jul 24) and Certify (first real client pilot, white glove, live by Aug 7). Cropple and Instalat stay as backups.

Open

GSC property

veloconsent.com still has no Search Console property — the AEO outcome loop stays blind until it exists.

The operating framework

Five disciplines, in order.

The order matters — teams that run these out of sequence scale funnels that leak.

1

Earn the right to grow

Never scale acquisition before the product is a must have. Roughly 40% or more must say they would be very disappointed to lose it.

2

Find the aha moment

The experience that turns a visitor into a devotee — then compress the time to reach it.

3

One north star

A single metric that captures value actually delivered, decomposed into an equation of levers.

4

High tempo testing

Weekly growth meeting, ICE scored backlog, several experiments a week, every result logged.

5

Work the whole funnel

Acquisition, activation, retention, revenue, referral. Language fit and channel fit are tested like product features.

Prerequisite for all five: instrumentation. Ours went live Jul 16 — the GA4 spine on the first party endpoint.

Discipline 1 · the stage gate

Earn the right
to grow.

Velo has zero external users today. Until must have status is proven, everything is organic and compounding only. With single digit pilot counts the test is a conversation, not a survey — but we ask the literal question and log the literal answer.

Held until G4 · displacement waves beyond 50 Held until G4 · any paid spend Held until G4 · partner scale Runs anyway · AEO, scan funnel, pilots, list

The Cookiebot wedge does not expire in a quarter. A broken first impression with agencies would.

The must have script — ask literally, log literally

  1. How would you feel if you had to go back to your previous consent setup? Very disappointed / somewhat / not really.
  2. What would you use instead, and why?
  3. What is the main benefit you get from Velo?
  4. Who do you think needs Velo most?
Pass bar: ≥40% very disappointed — or, at tiny n: the pilot asks to keep it, consent rate no worse than the incumbent, recovery visible in their report.
Discipline 3 · one metric

Recovered ad signals
per week.

Across live Velo domains: the count of conversions and events that Consent Mode v2 plus the edge recovery layer captured which the previous setup would have dropped. It is the value the positioning promises, it only moves when a customer is live and configured and getting results, and it sums naturally across an agency portfolio. Domain count alone rewards shelfware; MRR lags value by a quarter.

site visitors×scan rate×capture rate×signup rate×activation×domains per account×retention×ARPU

Every factor is a lever with its own experiments. The agency channel multiplies domains per account — 5 to 200 sites per win — which is why it outranks every other channel on impact.

Discipline 2 · the aha moment

The first recovery report
on your own data.

"Your old setup was dropping X% of your conversions; last week Velo recovered N of them." The moment the product stops being a compliance checkbox and becomes a revenue instrument. The free scan is the pre purchase proxy — one continuous narrative arc:

scan verdictdeep scan — what fires anywaysignupbanner livefirst recovery report
Instant
Scan verdict — live today, and honest by design. "Nothing detected" is inconclusive, never "clean".
< 30 min
Signup to banner live, self serve on Free. Snippet paste, banner renders, Consent Mode v2 verified — with a visible checklist. 72h white glove on Server.
7 days
Banner live to the first weekly recovery report. The report format is the product demo.
The scan flow · as built, in production today

Two scans. One honest funnel.

/scan · chrome scan modal · footer scan squarestatic scanverdict: green / amber / reddeep scan invite — the email askdeep scan report
Stage 1 · static scan

Name what's there

POST /api/scan fetches the homepage server side like a first time visitor — no JS. Reads CMP signatures, tags (GTM, GA4, Meta, TikTok…), a visible Consent Mode v2 default, and tracking cookies in Set-Cookie. Detection dictionaries live in packages/detect, shared with the product scanner.

Honesty contract: absence = "not detected in the initial load", never a definitive claim. Entry points prefill via /scan?url=<domain>.
Stage 2 · deep scan

The question worth an email

Under every verdict: "does your banner actually hold tags back?" POST /api/deep-scan loads the site in real headless Chrome (Browser Rendering), clicks nothing, and records every tracker request and cookie that fires before consent. Email required — unless the visitor is already known, then we don't ask twice.

Guardrails: daily capacity counter · lead stored deepscan:<day>:<email>:<host> in LEADS KV · Resend notify to hello@.
Stage 3 · measured

Every step is an event

scan_start → scan_complete (with the verdict) → deep_scan_request → early_access_signup, pushed via the veloDL/veloLead helpers, through GTM to the first party /m endpoint into GA4. Leads carry hashed email as user_data for enhanced conversions. CTA branches: green → "Get the full audit"; amber and red → "Fix it with Velo".

Source: scripts/pages/scan.html + src/worker.ts + v2/head.html (apps/marketing).
Open builds — precise

1. Nurture arc on captured emails (plan 1.3): four Resend emails, scan verdict → what it costs → how recovery works → launch offer; trigger on deep_scan_request and early_access_signup. 2. Verify veloconsent.com in Resend — until then the branded sender falls back and sandbox delivery is owner only, so nurture cannot ship first. 3. Surface deepscan:* keys in the ops velo view next to lead:* so captures are visible daily. 4. Product side events (signup, banner_live, cmv2_verified, first_report_viewed) still to instrument in the console — the aha funnel is blind after the site handoff until they exist.

The funnel · the idea portfolio

26 ways to grow.

Acquisition Activation Retention Referral Revenue bubble size = confidence
98 76 5 IMPACT harder to ship easy to ship high impact · easy — do these first 1234567891011121314151617181920212223242526
01Displacement 8.002Weekly recovery report 8.003Scan CTA 8.004Onboarding scan 8.005AEO daily 8.006Badge on Free 7.707Land and expand 7.308Renewal anchoring 7.309Monthly rescan 7.310Sub 30 min self serve 7.011Agency program 6.712GTM template 6.713Banner playground 6.714CMP market tracker 6.715Shareable scan report 6.716LinkedIn engine 6.717Annual prepay 6.718WordPress plugin 6.319Partner margin 6.320Migration concierge 6.321Consent benchmarks 6.322Scan grade badge 6.323Regulatory alerts 6.324Shopify App Store 6.025Consent teardowns 6.026Directories 6.0
SOURCE · growth backlog v2 — the number in each bubble is its ICE priority rank · size = confidence · rescored every Monday · detail on the next three slides
The portfolio · acquisition

Nine ways in.

Cookiebot refugee displacement

I
C
E
8.0

The Aug 2025 repricing is a documented migration wave. Our own CMP fingerprinting builds the list; the outreach engine sends it. Like for like swap, flat pricing.

How: scorer fence → enrich → verify → outreach engine · built W32 · nothing sends before G4.

Scan as the primary CTA

I
C
E
8.0

A tool, not a form. The deep scan invite already captures email on every verdict — what remains is routing traffic to /scan and the nurture arc behind it.

How: scan led hero A/B on home-b · nurture after Resend domain verify.

AEO daily content

I
C
E
8.0

One answer shaped post per day, already on autopilot — the compounding channel. Commercial and comparison pages come post launch.

How: velo-aeo-daily, 13:00 · GSC property is the missing loop.

GTM Community Template

I
C
E
6.7

Distribution inside the exact tool the ICP opens daily; every gallery search for "consent" is free placement. Submitted, in review.

Agency partner program

I
C
E
6.7

Rapid first: portfolio pricing, white label, margin built in. Comparison portals route each agency to Velo vs the exact CMP they already license.

Directories + launch week

I
C
E
6.0

G2 and Capterra profiles prepared now, submitted when public. Launch post for backlinks and entity signal, not the ICP.

WordPress plugin

I
C
E
6.3

NEW — the wordpress.org directory is where Complianz and CookieYes built their whole funnel. Every CMP search inside wp-admin is free, permanent distribution.

Needs: plugin wrapper around the snippet + directory review · post launch build.

Shopify App Store

I
C
E
6.0

NEW — session metered pricing fits app billing natively, and consent apps rank on daily "GDPR" searches. Second store, after WordPress proves the motion.

Needs: app wrapper + listing · sequenced behind the WP plugin.

CMP market share tracker

I
C
E
6.7

NEW — publish what our scans already see: which CMPs run where, by country and platform. The industry dataset nobody has; an AEO magnet and backlink engine.

Needs: aggregate scan data + a quarterly page · aggregates only, Rule #22 safe.

Also scored, in the ledger backlog: LinkedIn engine 6.7 (point the Mon/Wed/Fri routine at Velo) · consent teardowns 6.0 (public behavior only, every claim verified).

The portfolio · activation & retention

Get them live. Keep them fed.

Onboarding scan as the ramp

I
C
E
8.0

Every plan opens with "here is what you were losing" — sets up the recovery aha, makes the weekly report a payoff.

Sub 30 minute self serve

I
C
E
7.0

Snippet paste → banner renders → CMv2 verified, with a visible checklist. The PLG floor everything stands on.

Migration concierge

I
C
E
6.3

Import the incumbent config, side by side preview, cutover checklist. Built only if objection data demands it.

Banner playground

I
C
E
6.7

NEW — configure the banner live on the site (colors, layers, copy) and leave with your snippet. The demo card exists; make it an editor.

The weekly recovery report

I
C
E
8.0

Value restated in the customer’s own numbers, every week. The retention trigger — the most important email in the product.

Monthly rescan

I
C
E
7.3

"Your site changed — here is what’s new." Already in the entitlements; the job is making the email good.

Regulatory change alerts

I
C
E
6.3

New law, new enforcement, new default. Velo watches so you don’t have to — cheap content, high perceived vigilance.

Consent benchmarks

I
C
E
6.3

NEW — "your consent rate vs sites like yours" inside the weekly report, from our own aggregate once ~30 domains are live.

The portfolio · referral & revenue

Loops, not blasts.

"Powered by Velo" badge

I
C
E
7.7

Every consented pageview on a Free domain is an impression in front of people who deploy CMPs. Paid removes it.

Reality: since Jul 21 the badge sits on the preferences layer only — D1 decides Free’s first layer.

Shareable scan report

I
C
E
6.7

One click "send this report" to a client, a boss, a dev. B2B referral is forwarding a useful artifact.

Partner margin

I
C
E
6.3

The agency’s recurring cut makes every agency a commissioned sales force. Structural referral.

Scan grade badge

I
C
E
6.3

NEW — sites that pass get an embeddable "consent verified" badge linking back. The SSL Labs grade play: verified sites advertise us.

Land and expand

I
C
E
7.3

Flat multi domain pricing: adding a domain costs nothing at first, then metering grows the account. Domains per account is a first class metric.

Renewal shock anchoring

I
C
E
7.3

Displacement copy and comparison pages anchor on the incumbent’s real renewal math — verified numbers only.

Annual prepay

I
C
E
6.7

NEW — two months free on annual at the metering step. Cash up front funds the seed budget; churn drops a tier.

Pricing this rides on

Free · €0Pro · from €7/moServer · from €149/mo

Session metered, flat across domains. Stripe flip held on D4.

Discipline 4 · high tempo testing

The Monday
machine.

One weekly growth review — Walter + Leon, 25 minutes, Claude runs the numbers beforehand. Given the scheduled task fleet, execution capacity is not the constraint. Decision speed is.

1. North star + funnel vs targets 2. Ship / iterate / kill last week 3. Pick 2–3 experiments, rescore ICE 4. Blockers + decisions

Growth ledger

One row per experiment: hypothesis, ICE, dates, result in numbers, decision. Same discipline as the AEO learnings loop — the house pattern that already works.

Message testing

home-b is the standing A/B vehicle. Recovery led versus price led versus compliance led heroes, judged on scan starts and captures. The winner writes the outreach subject lines too — language fit is one system across site and email.

Live

Instrumentation

GA4 event spine through the first party /m endpoint on the site Worker, verified Jul 16. Scan, lead capture, and signup events flow; the growth panel reads from here.

The 90 days · phase and gate map

Gates, not dates, decide.

The dependency spine: G0 unblocks pilots → pilots unblock the must have gate → the gate unblocks wave 1 → wave 1 results unblock scale. Everything else runs in parallel and does not wait.

Phase 0–1 · now

Foundations + funnel

Jul 13 – Aug 2

Instrument ✓ · hosting ✓ · dogfood 1 ✓ · scan capture, dogfood 2, pilots 1–2

G0 mostly cleared · G2 two pilots live
Phase 2

Launch prep

Aug 3 – 28

Displacement list built (not sent) · directories ready · dry run ≤ 30 min · Stripe flip

G3 launch readiness
Phase 3

Launch

Mon Aug 31

Signup opens · directories + template submitted · one note to the warm list

shipped
Phase 4

Proof

Aug 31 – Sep 4

Must have conversations with every pilot at ~30 days live; fix the leakiest step

G4 must have gate
Phase 5

Displacement

Sep 7 – 27

Wave 1: ~50 Cookiebot refugees. Review against the outreach engine's standing bar

G5 wave review
Phase 6

Scale

Sep 28 – Oct 18

Rapid signed · comparison portals · badge loop measured · expansion experiments

G6 90 day retro
Then

The model takes over

Nov → Jun 27

Waves step 50 → 150 → 300/wk if the bar holds; second agency; the MoM curve on the next slide

plan v2 at the retro
The model · Jul 2026 → Jun 2027

Month over month.

Live domains — targetsMRR, blended — targets
065 130195260 259 182840 5882114 154202 260 €95€600€4,250 launch · Aug 31 JulAugSep OctNovDec JanFebMar AprMayJun 27
SOURCE · MoM target model v2.1 — ambitious, grounded · 2026-07-22 — targets, not actuals · recalibrated at every Monday review · full table next slide
The model · targets by month end

The numbers behind the curve.

MonthLive domainsSignupsPayingMRRMoM
Jul 2026
2
00€0
Aug 2026 · launch Aug 31
5
100€0+150%
Sep 2026
9
352€30+80%
Oct 2026 · G6 retro
18
706€95+100%
Nov 2026
28
11012€200+56%
Dec 2026
40
15520€360+43%
Jan 2027
58
21031€600+45%
Feb 2027
82
27545€950+41%
Mar 2027
114
35563€1,450+39%
Apr 2027
154
45086€2,100+35%
May 2027
202
560112€2,950+31%
Jun 2027
260
685142€4,250+29%

Jun 2027 · where it lands

260 live domains
142 paying accounts
€4,250 MRR, blended

Targets, not actuals — model v2.1, rebuilt from real data at every Monday review from W31 on.

ARPU expands, ~€12 → ~€30. Session metering, the Server tier, and multi domain agency accounts do the expanding — land and expand, not price rises.

The tail is agencies, not luck. Monthly domain adds step 7 → 12 → 24 → 58: waves scale 50 → 500 sends a week only while the reply bar holds; Rapid from October, Adfluencers (14 clients) from November. December tempered.

Everything after launch assumes G4 (Fri Sep 4) passes; the north star baselines from the first pilot reports in W31.

The model · marketing budget & pacing

Money follows
proven loops.

The stage gate is also the budget gate: €0 paid until G4 passes. Until then the whole machine — scan, AEO, outreach, deep scans — runs on ~€50/mo of fixed infra (Workers paid plan incl. Browser Rendering, Resend, domains). Then paid unlocks stepwise — seed doubled for the aggressive curve — and from spring the cap is pegged to revenue so spend can never outrun proof.

The pacing rule

monthly paid cap = max( €1,200 seed, 50% × last month MRR )

Seed unlocks stepwise after G4 — Sep €600 → Oct €1,000 → Nov+ €1,200 — each step only if the guards hold. The 50% of MRR term takes over from June.

Guards — checked every Monday

Blended paid CAC ≤ €150 · payback ≤ 6 months (CAC ≤ 6 × ARPU) · activation ≥ 60% holds. Any guard fails → pause spend, fix the funnel, resume. Pausing is free; a leaky funnel with paid traffic is not.

MonthPaid capMRR targetRule applied
Jul – Aug 2026€0€0pre G4 — organic only
Sep 2026€600€30seed step 1 · after G4 (Sep 4)
Oct 2026€1,000€95seed step 2 · Sep guards held
Nov 2026 – May 2027€1,200€200 – 2,950full seed
Jun 2027€1,475€4,25050% × May MRR · ~€11.5k paid, full year

Where the first euros go — and how

Search intent only, one channel at a time: "cookiebot alternative", "consent mode v2", CMP comparison queries — the buyers already in motion. No broad social. Max 2 concurrent paid experiments, each a ledger row with ICE and a pre registered kill metric before it spends a cent.

Mechanics: Google Ads shared budget, daily = cap / 30.4 · spend vs cap read at the Monday review · CAC from GA4 paid attributed signups (enhanced conversions already live via veloLead) · caps are proposals — Walter moves them, the ledger records why.
The model · channel distribution & budget

Where growth comes from.
Where money goes.

Domains by channel — Jun 2027 target mix

How the 260 live domains decompose. Agencies carry the tail; paid stays the smallest slice by design.

Agency portfolios
104 · 40%
Displacement outreach
62 · 24%
Organic — scan + AEO
50 · 19%
Paid search
29 · 11%
Product loops — badge, stores
15 · 6%
Measured, not assumed: every install carries a source tag (console field + GA4 first touch) — the mix is read at the Monday review; these shares recalibrate with it.

Paid budget by channel — ~€11.5k year one

The pacing caps from the previous slide, distributed. One channel proves itself before the next opens.

Google Search — intent queries
€7.5k · 65%
Experiment reserve
€1.7k · 15%
Microsoft Ads — cheap B2B CPCs
€1.2k · 10%
G2 / directory placement
€1.2k · 10%
Rules: Google Search opens first (Sep, post G4) on "cookiebot alternative" / "consent mode v2" intent; Microsoft and G2 unlock only after Search holds the CAC guard for 2 months; the reserve funds ledger experiments, never top ups. Fixed infra ~€50/mo rides outside these caps; organic channels cost fleet time, not cash.

Shares recalibrate every Monday from the install source tag · agencies + displacement carry ~64% of the curve — which is why D4 and the Rapid signature outrank any ad decision.

Automating the strategy · what it takes

Run it on rails.

The fleet already runs half this plan unattended. Six builds put the rest on rails. Machines prepare — the Monday review decides. Nothing sends, spends, or migrates past a gate on autopilot.

Already on rails

The running half

AEO post daily (velo-aeo-daily) · outreach engine with claim verification and cadence caps built in · scan funnel fully evented · deploy cycle + ops dashboard refresh.

Needs: nothing — running today.
Build 1

velo-growth-daily task

Pulls the GA4 funnel, LEADS KV counts, ledger state, and spend vs cap every morning; renders the growth panel on ops and auto prepares the Monday pack.

Needs: nothing new — GA4 and KV creds exist. First build, this week.
Build 2

Nurture engine

Resend sequences fired by deep_scan_request and early_access_signup — the four email arc from verdict to launch offer, then evergreen post launch.

Needs: Resend domain verified (the blocker) · a small sequence Worker on a cron over LEADS KV.
Build 3

Displacement autopilot

Velo segment inside the existing outreach engine; wave size steps 50 → 150 → 300 → 500 a week automatically while the G5 reply bar holds, halts when it breaks.

Needs: list built W32 · sender infra reused · a G4 pass flips it on.
Build 4

Recovery report generator

The weekly email per live domain — consent rate, recovered signals, € range — generated from console data. Hand built for the pilots first; the format is proven before it is automated.

Needs: product events (signup, banner_live, cmv2_verified) · template signed off on Amplio + Certify.
Builds 5 + 6

Pacing guard · CRM sync

Daily spend vs cap with CAC guard alerts into the Monday pack; deepscan and lead keys auto staged into crm.veloconsent.com so no capture ever sits unseen.

Needs: Ads account decision (reuse Amplio's vs a Velo account) · a KV to CRM cron.
Near term checkpoints · first pass, recalibrated every Monday

What "on track" means
before the model kicks in.

Fri Jul 31

Funnel live

≥ 20 scan runs a week · ≥ 35% capture rate on scan reports · dogfood 2 live · Certify install scheduled · first recovery report sent.

Mon Aug 31 · launch

Launch ready

Warm list ≥ 200 · 4 live domains · ≥ 40 AEO posts with first citations logged · dry run ≤ 30 minutes.

Mon Sep 14

Post launch pulse

≥ 20 signups since launch · activation ≥ 60% · median time to live ≤ 30 minutes · wave 1 out · G5 review Sep 21.

Fri Oct 16 · G6

90 day retro

≥ 18 live domains · ≥ 6 paying accounts · backlog rescored · plan v2 written from the ledger, not from hope.

Every week, regardless of phase: recovered signals per week — up and to the right from the first report on. Wave reply bars are the outreach engine's standing thresholds, inherited.

What can break it · and what may never break

Risks and guardrails.

D4 unsettled while revenue starts. Hard ordering: no Stripe flip before the Leon arrangement. Worst case, launch runs stub billing and manual invoices.

Pilot slips → gate slips → wave slips. Two dogfoods derisk the install path first. The wedge does not expire — hold the gate, never skip it.

Launch week swallows delivery time. Launch actions are Claude and Leon heavy by design; Walter's launch day is one note to the warm list plus monitoring.

Deliverability and claim holds on wave 1. The standard engine path has verification built in; claims are pre verified when copy is drafted, not at send time.

Verified claims only. No statement that a competitor or prospect lacks something without a resolved container and a rendered screenshot. Comparison pages meet the same bar as outreach.

Only the proven figures — 34% hidden sessions, 20–40% recoverable, +37% ROAS, 72h setup — always ranged, always qualified. Never an invented stat, customer, or testimonial.

Scan honesty is the moat. "Nothing detected" stays inconclusive under any CTA pressure. The scan converts because it is trustworthy.

Migration order — revised Jul 22. Certify pilots pre launch by Walter's call, with a white glove bar: zero downtime, Carme informed, rollback ready. Odisei still migrates only after the gate.

Decisions still open

The next
fourteen days.

D1 · badge on Free's first layer — reopened by the Jul 21 banner change; the referral loop rides on it D4 · Leon arrangement — by Aug 7, gates Stripe D5 · Stripe flip — Aug 12, after D4 D6 · AEO byline — Walter vs team, by Jul 31

This deck restates knowledge/velo/growth-strategy.md and growth-plan.md as of 2026-07-22. The plan is rebuilt at the 90 day retro; the model is rebuilt every Monday. Growth is decided weekly — not in decks.

this week

Unblock the capture loop

Verify veloconsent.com in Resend (nurture can't ship before it) and surface deepscan:* leads in the ops velo view — the capture exists, make it visible and followable.

Fri Jul 24

Dogfood 2 — ampliodata.io

Replace the Usercentrics we pay for. One fee gone, before and after consent rates into the ledger.

by Fri Aug 7

Pilot — Certify

White glove install, Carme informed, baseline captured; first recovery report the week after. Backup if it slips: Cropple.

Fri Jul 31

Nurture v1 loaded

Four emails, scan verdict to launch offer. Humanized, every claim qualified.