How it works
Six steps from kickoff to a weekly cadence
The first week is hands-on — we get oriented, baseline your sites, and ship the first round of approved changes. From week two, Pam runs the cadence and you get a structured report every Friday.
Process
- 1
Discovery & access
You~1 dayShort kickoff call to map your sites, payment flow, email tool, and analytics. We get read-only access — never write access — to the systems we'll review.
Output: Access checklist · signed scope · success metrics
- 2
Baseline assessment
Us~3 daysPam runs the first deep crawl. We layer human review on top — structure, content clarity, mobile/desktop, payment trust signals, broken links, metadata.
Output: Baseline health report (PDF) · before-state snapshot
- 3
Tenant confirmation
You~2 daysYou review every proposed change in a corrections worksheet — accept, reject, or edit. Nothing ships until you confirm.
Output: Corrections worksheet · approved change list
- 4
Apply & verify
Us~3 daysWe implement the approved changes — payment A/B variants, copy rewrites, broken-link fixes, email sequence patches, metadata updates. Each change is verified before it goes live.
Output: Live changes · verification log
- 5
Weekly cycle starts
Pam~7 daysPam takes over the cadence: daily crawl, weekly deep scan, A/B monitoring, email validation. You get a structured weekly report every Friday.
Output: Weekly report (PDF) · action items
- 6
Ongoing operations
Pam~30 daysEvery change continues to require your sign-off. Triggers — conversion drops, content drift, automation failures — escalate to a human on our side immediately.
Output: Monthly deep review · before/after report on request
Cadence
What runs when, and what triggers a human on our side.
| Frequency | What runs | Trigger |
|---|---|---|
| Daily | Site crawl · error detection · uptime check | Automatic — 04:00 local |
| Weekly | Full scan · A/B test review · email validation · weekly report | Automatic — Friday 09:00 |
| Monthly | Deep content review · before/after report | Automatic — first of month |
| On trigger | Conversion drop · page change · automation failure | Threshold breached |
Operating principles
What you can count on every week.
Read-only by default
We get read access. You retain write access. Changes ship through your existing publishing flow, with your sign-off.
Nothing ships without tenant sign-off
Every change is shown to you in a worksheet first. You accept, reject, or edit. Pam only applies what you explicitly approved.
Structured PDF report every Friday
Same format every week — status pill, KPI tiles, validation checks, per-site status, audit trail. Skim it in 2 minutes.
Human escalation on every trigger
When Pam detects a conversion drop, content drift, or automation failure, a human on our side is paged before you are.
FAQ
Do you need admin or write access to our site?
Do you need admin or write access to our site?
No. Read-only is enough for monitoring. For changes, we hand you a worksheet — you (or your team) publish through your existing flow.
What does the first week look like?
What does the first week look like?
Day 1: kickoff and access. Days 2–4: baseline assessment. Days 5–6: you review the corrections worksheet. Day 7: approved changes go live and the weekly cadence begins.
Which tools do you support?
Which tools do you support?
Most stacks. We've worked with Webflow, WordPress, Shopify, Stripe checkout, Klaviyo, ActiveCampaign, GA4, Plausible. If your stack isn't listed, ask.
Can we cancel anytime?
Can we cancel anytime?
Yes. Monthly plans, no lock-in. You keep all the reports we've generated.
Want to see the format first?
The sample weekly report shows exactly what lands in your inbox every Friday.