Process
Diagnose first. Build second. Report in dollars.
Every engagement follows the same spine because the failure modes repeat: programs built before anyone measured the audience, and results reported in opens nobody can spend. Here is the sequence, what each phase produces, and where the benchmarks come from.
Audience audit
We connect to your ESP (Klaviyo, Omnisend, Braze, or Customer.io) read-only and build the map: engagement scores for every profile, RFM tiers, revenue by segment, and a GlockApps deliverability baseline across Gmail, Outlook, and Yahoo. You see exactly which share of sends produces revenue and which produces complaints.
You get: Findings deck + segment architecture + deliverability baseline
Roadmap and priorities
Findings become a 90-day plan ordered by expected revenue impact. Deliverability repairs come first when placement is broken, since every other fix multiplies by inbox rate. Each roadmap item carries its benchmark: what the metric is now, what the category average is, what we expect to reach.
You get: 90-day roadmap with per-item benchmarks
Build
Segments, flows, signup forms, and authentication fixes go live in your accounts, never ours. Flow builds follow the audience map: suppression rules, segment-specific timing, and offer depth by RFM tier. Everything is documented as we go so your team can operate it without us.
You get: Live segments, flows, forms + documentation
Test and report
Monthly A/B tests run against your own baseline for at least two full cycles before we call results. Reporting is in revenue per recipient, placed-order rate, and placement, the same units as Klaviyo's public benchmarks, plus complaint-rate alerts set at 0.1%, under Google's 0.3% enforcement line.
You get: Monthly report in revenue terms + working session
The audit phase is sold as a fixed $3,900 project, so you can see the method before committing to a build; the fee credits toward program work. Scope and current numbers for all three engagement types are on the pricing page, and the three write-ups on the proof page each show this sequence running against a different problem.
Process questions
Why do you insist on the audit before any build work?
Because the audit changes the plan. A client who arrives asking for new templates usually leaves the audit fixing suppression or deliverability first. One meal-kit audit showed 64% of sends going to silent profiles; no template redesign would have mattered until that was addressed. Two weeks of diagnosis protects ten weeks of build.
Do we keep everything if we stop working with you?
Yes. All segments, flows, templates, and documentation live in your ESP account under your ownership from day one. The handover at the end of a program build includes a recorded walkthrough. Retainer clients who leave keep every asset and the monitoring configuration; only our monthly involvement ends.
How much of your process is automated versus human?
Scoring models and monitoring run on data: engagement scores recompute continuously, seed tests run monthly, complaint alerts fire at 0.1%. Judgment stays human. Which segments to build, what an A/B result means, when a channel should be cut: those calls are made by the strategist who owns your account.
What size list does this process fit?
The economics work best from roughly 10,000 to 250,000 profiles. Below 10k, a full audit usually finds too little structure to pay for itself, and we will say so on the call. Above 250k, the method holds but timelines stretch, especially deliverability recovery, which moves at mailbox-provider speed regardless of agency effort.
Find out where your list is leaking revenue
A 30-minute call. We look at your last 90 days of sends, tell you what we see, and you leave with two or three fixes whether we work together or not.