Work
Campaigns, conversion experiences and the growth infrastructure underneath them, built to run as one commercial system.
Three kinds of evidence sit on this page, and each one is labelled: work delivered through Revnix, work done before it, and systems Revnix built for itself.
Revnix client work
Connecting acquisition, intake and follow-up.
A therapy practice taking most of its new clients from search, with enquiries landing in four systems that were never designed to meet each other.
Enquiries were arriving. What happened to them afterwards depended on who noticed, which inbox it landed in, and whether anyone re-typed it accurately. The work below follows one enquiry through the path Revnix rebuilt, in the order it happens.
Search
Paid and organic were answering different questions, so the two channels competed for the same terms and disagreed on which ones mattered. They now answer the same intent, and the enquiry arrives already qualified for a specific service.
Booking page
What the service is, when it is available, what it costs to start and what happens after the form is sent. The page is the client's own design language, and it holds the whole decision rather than handing it to a phone call.
Intake
Service, availability, contact preference and consent. Every field exists because routing or the first reply uses it; the clinical detail belongs in the session, not in a web form.
CRM
Before: a notification email, then someone re-entering the details into a spreadsheet, with the source lost on the way. Now the submission writes the record itself — service, site, source and consent — once, and nothing downstream has to guess.
Routing
This is the step where enquiries were being lost. Assignment now runs on service and location, with a response clock attached and an escalation if the clock runs out.
Follow-up and measurement
If no appointment is booked, a short sequence runs instead of the enquiry going quiet. And because the source stayed attached from the search onwards, the practice can read enquiries and booked appointments against the terms that produced them, in one view.
Service and location decide the owner. The response clock decides when it escalates.
An appointment booked in one system is visible in the other without anyone reconciling the two.
The details are written once, at intake, in the fields the rest of the path depends on.
The follow-up and the report read the same field the search wrote, so channel decisions stop being guesswork.
Evidence across the system
Demand, conversion and the infrastructure underneath, shown through the Leek Therapy work.
Search and campaign structure, built around the service and the intent behind the enquiry.
Create demand capabilitiesThe experience the click lands on, and the point where the decision is actually made.
Convert demand capabilitiesAll artifacts in this chapter: Leek Therapy, Revnix client work. Contact records use test details.
Prior professional experience
Work completed before Revnix existed, included as evidence of the operating experience behind the company. Accountability was shared with the organisations it was done inside.
Growth Fellow
Prior professional experience
Lifecycle messaging for banking and lending funnels, including SMS and push campaigns, audience splits and sequencing.
Chief Operating Officer
Prior professional experience
Go-to-market and the operations underneath it: how sessions were sold, how enquiries were handled, and the systems the team ran on day to day.
Earlier: Growth Analyst, Crumble Pakistan.
Revnix Lab · Internal build
Internal builds, used in the business rather than demonstrated in a deck. They prove capability, not a client outcome, and they are labelled that way.
CRM architecture, lead routing, lifecycle automation and attribution, built for Revnix’s own enquiries.
If it crosses acquisition, conversion or the infrastructure underneath them, tell us what is happening. You get back what Revnix would own, and in what order.
