- 01
A CRM built around how you actually sell.
Pipelines, properties and permissions mapped to your real sales process, not the default setup.
Six services. One revenue system.
Services
A CRM built around how you actually sell.
Pipelines, properties and permissions mapped to your real sales process, not the default setup.
Six services. One revenue system.
Services
Selected work / Page Pros
Three years with one subscription business. The revenue system built from nothing in 2023, then hardened as volume found every seam in it.
Multi-year engagementE-commerce services2023 — 2026
The engagement
Page Pros sells three subscription products to small businesses across the US and Canada, and onboards 300 to 350 new customers a month. In 2023 it had none of the machinery that implies. No store, no billing, no CRM, no marketing engine. We built it.
Then we stayed, which is the part worth reading. Most case studies end at handover, where the system is at its most theoretical and nothing has been stress-tested by a real week. This one has an after. Eighteen months of a business running hard through the thing we built, a core platform replaced while it ran, and a customer base that turned out to be less than half the size the reports claimed.
A system’s design is a hypothesis until volume tests it. Two chapters, in order.
01 Chapter one — the build
Store, subscriptions, payments, marketing, and CRM designed as one system rather than bought one problem at a time. Then the test: in late 2024 the marketing platform had to come out of a live subscription business, and the engine kept running while it did.
Read the build →
02 Chapter two — the hardening
Four systems each held their own version of every customer. Identity resolved across all of it, the payment paths rebuilt so a routine card expiry stopped manufacturing new customers, and the churn signal nobody was reading.
Read the hardening →
Start the diagnostic →