← All selected work
Revenue operations
One tested system from lead capture to customer access
Reframed a landing-page brief as the four connected systems it actually required: acquisition, payment, delivery, and operations.
Primary evidence5 days
to a launch-ready build
Situation
What the system needed to change
A medical educator needed to replace a fragmented WordPress-era funnel with a fast path from paid traffic through purchase and into a private learning area.
Constraints
The boundaries mattered.
- 01
Low-ticket economics made checkout friction and attribution important
- 02
EU payments required explicit SCA, tax, consent, and refund paths
- 03
Several external services could fail independently
Decisions
The important engineering choices
- Made PostgreSQL the source of truth instead of the email platform
- Used idempotent payment webhooks to orchestrate orders, access, email, and attribution
- Separated transactional email from marketing automation
- Automated browser, payment, refund, consent, and access checks before launch
Outcome
What the work left behind
- A complete lead, checkout, order-bump, upsell, and access flow
- Recoverable integrations with explicit launch checks
- A documented operating path for content, refunds, and production rollout