Questions Answered Before You Ask

Three ways to work together, with indicative ranges so you can self-qualify before we ever talk. Every scope is quoted in writing before any work starts — no hourly billing, no surprise invoices.

• →Architecture Audit — $1,500–$3,500. A 2–3 day forensic teardown of your storefront, ad tracking and retention stack, delivered as a prioritized written report with revenue-weighted fixes.
• →Conversion Sprint — $5,000–$12,000. A 4–6 week implementation program: the highest-impact 3–5 changes shipped directly into your theme, measured before and after.
• →Growth Retainer — $3,000–$8,000/month. Ongoing CRO, performance and Klaviyo work with a monthly roadmap, testing cadence and direct access.

The audit lands in 2–3 days, and the first sprint findings usually ship inside the first two weeks of implementation. But honest framing: a testing programme needs roughly 90 days before you can read the programme rather than a single result. Anyone promising you a conversion lift in month one is describing seasonality, not work.

• →Days 1–3: audit, baseline agreement, prioritized roadmap
• →Weeks 1–2: first batch of fixes shipped and live
• →Weeks 3–8: test cycles, read-outs, compounding revenue impact

Shopify is my home turf — OS 2.0 and Shopify Plus, Liquid, Shopify Functions, custom sections, headless Hydrogen/Oxygen where it earns its keep, and Jamstack (Astro) storefronts. I also take on WooCommerce and BigCommerce replatforming into Shopify Plus.

• →Storefront: Shopify OS 2.0, Shopify Plus, Hydrogen, Astro/Jamstack
• →Data & tracking: GA4, Meta Graph API, Conversions API, GTM, Shopify Web Pixels
• →Retention: Klaviyo flows, SMS, loyalty and subscription integrations

Yes. I am UTC+8, which overlaps the US East Coast evening, the European morning and the APAC workday. Sprint deadlines and incidents do not respect timezones, so I keep a written async trail — Loom walkthroughs, written notes and a shared board — so nothing depends on us being awake at the same moment.

Read access is enough to start: your GA4 property, your Meta Ads Manager account, and Shopify collaborator access. I do not need — and will not ask for — your Meta password or full admin rights on day one. Staging or a duplicate theme is preferable so your live store keeps trading while I work.

• →GA4 property (viewer)
• →Meta Ads Manager (advertiser read access)
• →Shopify collaborator access, or a duplicate theme branch
• →Klaviyo account read access for retention work

Always, and it is the default. Most of the engagements I run are under NDA because the work is commercially sensitive. I will publish anonymized case studies with the real numbers intact — your data, your metrics, your brand removed.

We agree the baseline before the first change ships, then track conversion rate, revenue per session, p75 field CWV (LCP, INP, CLS), click-to-landing loss rate and chargeback rate against it. If a test loses, it gets rolled back. No vanity wins, no screenshots of a good day.

No, and you should be suspicious of anyone who does. What I guarantee is the process: a documented baseline, a prioritized roadmap, changes shipped inside your theme, and measurement that either confirms or kills each hypothesis. The lift is the outcome — it is not a contract term.

I implement. Strategy handed to an in-house team usually dies in the backlog, especially when the fix is a Liquid loop, a Meta event, or a Klaviyo flow. I write the code, ship it into a staging theme, and hand over a Loom walkthrough plus written notes so your team owns it afterwards.

Yes, and this is a well-trodden path. I work white-label for agencies that need senior CRO and performance capacity without adding headcount — your team keeps the client relationship, I do the audit and the implementation, everything is delivered in your brand. It is also how I keep a steady pipeline without building a sales team.

Honestly, often no. Below roughly $50,000/month in revenue the fee would be a meaningful percentage of margin, and the cheaper fix is usually a well-built free Shopify theme plus one focused CRO session. I will tell you that on the first call rather than sell you a retainer you cannot justify.

On storefront, speed and CRO — yes, absolutely. On ad-spend efficiency and click-loss recovery — not yet, because there is no click data to reconcile. Start with the audit, get the site fast and conversion-ready, and revisit paid traffic when there is budget behind it.

You keep everything: the code, the Liquid, the Klaviyo flows, the GA4 events, the documentation and the measurement setup. The retainer is a convenience, not a lock-in. If the work is not paying, the exit should not be the hard part.