Commercial planning across audience, offer, acquisition, conversion and measurement, so the parts work toward the same result.
Capabilities
From demand creation to the infrastructure underneath it.
Revnix works across marketing, digital experience and revenue infrastructure. Sometimes the job sits inside one discipline. More often the result depends on several of them working together.
Three connected systems, three different commercial jobs.
Grouped by the job the work does, not by the department it would sit in at an agency.
Create demand
Build visibility, interest and qualified demand.
Convert demand
Turn attention into commercial action.
Operate growth
Build the infrastructure growth runs on.
Create demand
Build visibility, interest and qualified demand.
Strategy
What gets built, for whom, and in what order.
The plan for one push: who it is for, what it offers, where it runs, and what the landing experience has to do.
Growth Strategy
Useful when activity exists but each part is optimising a different number, or a new offer or location is being launched.
Revnix may own the growth plan, channel priorities, audience and market analysis, offer and message architecture, the measurement framework, and the order the work happens in.
Often paired with Campaign Strategy · Conversion Analytics · Revenue Operations
Revnix plans the work it then runs. This is not board-level corporate strategy, and it is not sold separately from execution.
Campaign Strategy
Useful when a launch, promotion, season or new service has to run across more than one channel and arrive somewhere that matches what the ad said.
Revnix may own audience, proposition and message, channel mix, campaign architecture, landing alignment, the tracking plan, and the reporting it is judged on.
Often paired with Google Ads · Performance Creative · Landing Pages
Acquisition
Buying attention where intent already exists, and where it still has to be created.
Paid search around commercially meaningful intent, measured beyond the click.
Paid social for demand that has not started searching yet, where the creative and the offer do the work.
Cross-channel paid planning above the individual platforms, on one shared measure of cost per outcome.
Google Ads
Useful when spend is running with no view of which queries produce enquiries, a new service needs demand before organic can reach it, or paid and organic are competing for the same terms.
Revnix may own account and campaign architecture, search and keyword strategy, query analysis and negatives, ad copy, bidding, conversion tracking, landing alignment, structured testing and reporting.
Often paired with Landing Pages · Conversion Analytics · Attribution
Search, Performance Max and remarketing. Shopping and feed management are not part of what Revnix sells.
Meta Ads
Useful when search volume is capped by how few people know the category exists, or existing enquiries need re-engaging cheaply.
Revnix may own campaign and audience architecture, offer and message, creative testing cycles, budget, pixel and conversions API tracking, and landing alignment.
Often paired with Performance Creative · Landing Pages · Lifecycle and Nurture
Paid Media
Useful when more than one platform is live and budget is decided channel by channel, or platforms report different conversion counts for the same month.
Revnix may own channel planning and budget allocation, spend pacing, platform selection, cross-channel measurement against one definition of an enquiry.
Often paired with Attribution · Campaign Strategy · Reporting and Dashboards
Organic discovery
Being found, and being understood well enough to be chosen, without paying per click.
Findable for the searches that carry commercial intent, and structured to be read correctly.
Pages written for a commercial job: being found, explaining a category, or answering the question that stalls a decision.
SEO and Search Visibility
Useful when paid acquisition is carrying all the demand, rankings exist for terms nobody buys from, or a migration or rebuild is planned.
Revnix may own technical SEO, commercial keyword and topic strategy, information architecture and internal linking, on-page work, content briefs against search intent, migration protection, and organic measurement.
Often paired with Content · Website Strategy · Website Development
Content
Useful when search strategy has identified pages that do not exist, or the sales conversation keeps repeating the same explanation.
Revnix may own content strategy against search and buying intent, briefs, service and category pages, decision-support material, campaign copy, and per-page measurement.
Often paired with SEO and Search Visibility · Offer and Message Architecture · Conversion Rate Optimisation
Commercial writing at a considered volume. Revnix does not sell publishing calendars by the article.
Audience and creative
What the audience actually sees, and whether it earns the next click.
Creative built to be tested, continuous with the page it sends people to.
A repeatable channel system, connected to the rest of acquisition.
Performance Creative
Useful when targeting has been optimised as far as it goes and the creative is now the variable.
Revnix may own concepts and copy, static and motion assets, variant sets that isolate one claim at a time, per-placement formats, and message continuity into the landing experience.
Often paired with Meta Ads · Landing Pages · Offer and Message Architecture
Convert demand
Turn attention into commercial action.
Experience strategy
What the experience has to do commercially, decided before anything is designed.
What the site is for, decided before it is designed: who each page serves and what it is responsible for producing.
How the offer is framed and ordered on the page: what is said first, what is proven, and what is asked.
Website Strategy
Useful when a rebuild is being considered, or pages exist that nobody can name a job for.
Revnix may own information architecture, journey mapping, page hierarchy and responsibilities, content structure, the conversion logic across the site, and the measurement the build has to support.
Often paired with SEO and Search Visibility · Website Design · Conversion Analytics
Offer and Message Architecture
Useful when the traffic is right and the page still does not convert, or different channels describe the same service differently.
Revnix may own proposition and message hierarchy, offer framing, audience-to-message alignment, and page-level messaging used consistently across campaigns and the site.
Often paired with Performance Creative · Landing Pages · Conversion Rate Optimisation
This is proposition and page messaging. Brand identity, naming and visual identity systems are not capabilities Revnix sells.
Build
Designing and shipping the experience, including the connections behind it.
The front-end build and the connections behind it.
UX and interface design for sites that have to convert, built as a system of reusable parts.
One page for one campaign, audience or intent, where nothing competes with the next action.
Website Development
Useful when a design needs implementing, the team cannot edit their own pages, the site fails a performance or accessibility review, or forms are not reaching the CRM.
Revnix may own front-end implementation, CMS setup and the editing experience the team will actually use, forms and validation, CRM and third-party integrations, analytics implementation, performance work, and the technical SEO requirements of the build.
Often paired with CRM Architecture · APIs and Integrations · Analytics
Website Design
Useful when a new site or section is being built, or the mobile experience is where most visitors are and where least attention went.
Revnix may own UX and wireframes, interface design, responsive behaviour across breakpoints, components and design-system work, accessible colour and type decisions, and conversion-oriented layout including where the copy goes.
Often paired with Website Strategy · Website Development · Enquiry, Booking and Intake
Revnix designs within an existing brand, or establishes the digital expression of one. It is not a brand identity agency.
Landing Pages
Useful when paid traffic is landing on a general page that answers a different question, or two offers need testing against each other.
Revnix may own offer and message, design and build, the form or booking step, conversion tracking, continuity from the ad, and the variants worth running.
Often paired with Google Ads · Performance Creative · Attribution
Conversion
The step where intent either becomes an enquiry or quietly does not.
Finding where people leave and changing the reason, from the data rather than from an opinion about the button.
The step where a visitor becomes a named enquiry: the form, the booking journey, and what is handed to whoever replies.
Conversion Rate Optimisation
Useful when traffic is adequate and enquiries are not, mobile conversion is a fraction of desktop, or a specific step is where the drop happens.
Revnix may own funnel and drop-off analysis, behaviour review, friction identification, hypotheses ranked by expected effect, implementation, and measurement of what the change did.
Often paired with Conversion Analytics · Offer and Message Architecture · Enquiry, Booking and Intake
Statistically valid split testing needs traffic volume most service businesses do not have. Where it is not there, the work is sequential change with honest measurement — and Revnix says which applies before starting.
Enquiry, Booking and Intake
Useful when the form asks for more than the first reply needs, bookings require a phone call to arrange, or the source is lost the moment the form is submitted.
Revnix may own form and field design judged against what routing and the first reply actually use, booking and scheduling journeys, qualification, validation and spam control, confirmation, conversion tracking, and the handoff into the CRM.
Often paired with CRM Architecture · Lead Routing · Lifecycle Automation
Lifecycle and measurement
The two capabilities that reach into Operate, because they cannot work without it.
What happens after the enquiry: follow-up, nurture and reactivation.
The journey measured as steps rather than one conversion number.
Lifecycle and Nurture
Useful when enquiries that do not book are never contacted again, or follow-up depends on whether someone remembered.
Revnix may own post-enquiry follow-up sequences, nurture for slower decisions, reactivation of past enquiries and customers, segmentation, email and SMS journey messaging, and the lifecycle logic they run on.
Often paired with Lifecycle Automation · CRM Architecture · Lead Management
The messages belong to Convert; the triggers and records they depend on belong to Operate. Revnix usually owns both halves, which is why the follow-up actually runs.
Conversion Analytics
Useful when the only number available is total form submissions, or two platforms report different conversion counts for the same week.
Revnix may own event and conversion definition, step-level funnel reporting, form and booking analytics, and behaviour analysis.
Often paired with Conversion Rate Optimisation · Analytics · Attribution
Operate growth
Build the infrastructure growth runs on.
Commercial systems
What a record is, what state it is in, and who is responsible for it.
The data model underneath commercial work: what a record is, what state it is in, and who owns it.
Assignment by location, service, ownership or priority — with the follow-up it triggers.
The states a lead moves through, what qualifies it to move, and the next action at each point.
Process, systems, data and handoffs when more than one team or platform owns the same outcome.
CRM Architecture
Useful when stages mean different things to different people, the same customer exists three times, or reporting is impossible because the fields it needs are free text.
Revnix may own objects and record types, properties and required fields, pipelines and lifecycle stages, ownership rules, views and permissions, deduplication and hygiene, and the handoff logic to whoever replies.
Often paired with Lead Management · APIs and Integrations · Attribution
Lead Routing
Useful when response time depends on who happens to check the inbox, a multi-location business assigns by hand, or nothing happens when the owner is away.
Revnix may own assignment rules, territory and service mapping, availability and working-hours logic, priority and value rules, round-robin or load balancing, fallback when nobody claims a lead, escalation on missed response, and the notifications and tasks that make assignment visible.
Often paired with CRM Architecture · Lifecycle Automation · Enquiry, Booking and Intake
Lead Management
Useful when nobody can say how many live enquiries there are, or leads sit in a stage for weeks because no next action was defined.
Revnix may own lead states and their definitions, qualification criteria, ownership at each state, response expectations and what happens when they are missed, next-action logic, and re-entry rules.
Often paired with Lead Routing · CRM Architecture · Reporting and Dashboards
Revenue Operations
Useful when marketing and the people who close are counting different things, a process only works when a specific person does it, or systems bought separately now contradict each other.
Revnix may own the commercial process end to end, system architecture and consolidation decisions, shared data definitions, handoff points and their entry conditions, and the measurement that tells everyone the same story.
Often paired with CRM Architecture · Attribution · Growth Strategy
RevOps is one capability here, not the whole of Revnix. It is the right label when the problem is coordination rather than any single platform.
Automation and integration
Work that should not depend on somebody remembering, and data that should not be retyped.
Moving data between systems that were not built to talk to each other, and keeping it consistent.
Follow-up, status changes, reminders and re-engagement fired by what the record actually did.
Narrow, reviewable model use inside an operational workflow.
Automating the operational work behind growth that nobody should be doing by hand.
APIs and Integrations
Useful when the booking system and the CRM disagree, someone exports a spreadsheet weekly to keep two tools aligned, or an internal system has no connector at all.
Revnix may own system-to-system data flows, webhook and event handling, custom API work where no integration exists, middleware and workflow tooling, field mapping and synchronisation rules, and error handling, retries and alerting when a sync fails.
Often paired with CRM Architecture · Website Development · Analytics
Lifecycle Automation
Useful when the first reply arrives hours after the enquiry, no-shows are never rebooked, or nurture stops the moment someone is busy.
Revnix may own post-enquiry follow-up, stage-change automation, appointment reminders and no-show recovery, nurture and reactivation triggers, internal notifications and task creation, and re-engagement of records that have gone cold.
Often paired with Lifecycle and Nurture · Lead Routing · CRM Architecture
AI-Assisted Workflows
Useful when someone reads every enquiry to decide what it is, call notes are never written up, or the same content has to be rewritten for four channels.
Revnix may own enquiry classification and tagging, summarisation into the record, lead research and enrichment, drafting a first reply for a person to approve, content transformation, and the confidence thresholds that send anything uncertain to a human.
Often paired with Internal Automation · APIs and Integrations · Lead Management
Every one of these has a defined review step and a defined failure path. Revnix does not sell autonomous agents, and will not put a model between a customer and a commitment.
Internal Automation
Useful when the monthly report takes two days to assemble, tasks are created by hand after every enquiry, or approvals happen over messages.
Revnix may own recurring task creation, notification and alerting rules, data movement and reconciliation between tools, approval and handover steps, and automated preparation of recurring reports.
Often paired with APIs and Integrations · Reporting and Dashboards · AI-Assisted Workflows
Data and measurement
Enough visibility to make a decision, described honestly enough to trust.
Source and campaign kept attached to a record from the first click to the closed outcome.
Measurement design: what is counted, how it is defined, and where the number comes from.
The recurring views people actually act on.
Attribution
Useful when the source is lost at form submission, platforms report more conversions between them than the business had customers, or budget is decided without knowing which campaign produced revenue.
Revnix may own source and campaign capture at the point of enquiry, UTM standards and governance, source continuity through the CRM record, agreed conversion definitions, offline and phone capture, and reporting logic that states its own method.
Often paired with Paid Media · CRM Architecture · Analytics
Platforms disagree, consent limits tracking, and some conversions happen in a phone call. The goal is continuity good enough to decide with, not a single perfect number.
Analytics
Useful when analytics was installed and never configured, a migration broke the tracking, or two people produce different numbers for the same question.
Revnix may own the measurement plan, GA4 and server-side event implementation, conversion and event definitions, funnel analysis, tag governance, and data-quality checks that catch a broken event before a month of decisions depends on it.
Often paired with Conversion Analytics · Attribution · Website Development
Reporting and Dashboards
Useful when reporting is assembled by hand each month, or the owner and the marketing team look at different dashboards.
Revnix may own stakeholder and executive reporting, campaign reporting, pipeline and lifecycle views, CRM dashboards for the people doing the work, operational views such as response time and unassigned leads, and automated recurring delivery.
Often paired with Analytics · Lead Management · Internal Automation
When the work crosses layers.
Spend is increasing. Nobody can say which campaigns produce revenue.
Every part can be competent and the answer still unavailable, because the source is dropped somewhere along the way. What changes is that a campaign can be judged on outcomes instead of clicks.
Enquiries arrive. Response time and ownership vary by the day.
Rarely a marketing problem, and rarely solved by more traffic. The enquiry has to arrive as a record, belong to someone by rule, and be visible when it has not been answered.
Organic visibility is improving. Qualified enquiries are not.
Usually the rankings are for terms that carry no commercial decision, or the pages that rank have no next step on them. Reporting rankings alone would hide both.
A new service has to launch with demand and a way to handle it.
A launch is the case where sequence matters most. Demand arriving before anyone has decided who answers it is the most expensive version of this work.
Platforms & tools.
The platform serves the commercial job. Scope starts with what needs to work, then the systems involved.
Acquire & measure
Google Ads- Paid search, campaign architecture and conversion measurement.
Meta Ads- Paid social, audience architecture and creative testing.
Google Analytics / GA4- Measurement plans, event implementation and data-quality checks.
Amplitude- Product analytics, behavioural insight and measurement design.
Operate & automate
HubSpot- CRM architecture, lifecycle operations and pipeline visibility.
GoHighLevel- CRM configuration, lead operations and automated follow-up.
Salesforce- CRM design, commercial process and reporting foundations.
ActiveCampaign- Lifecycle automation, segmentation and customer communications.
n8n- Workflow automation and systems integration.
Make- Workflow automation and systems integration.
Resend- Transactional email and customer communication delivery.
Supabase- Application data, backend workflows and connected operations.
AWS- Cloud infrastructure and reliable systems foundations.
Stripe- Payments, customer events and connected commercial workflows.
Scope follows the problem.
Revnix can own one capability, one system, or work across several when the commercial result depends on the connection between them.
Nothing on this page is a package. The list exists so you can recognise the work, not so that more of it gets bought.
Start with the problem
Bring us the problem.
You do not have to work out which capability it belongs to first.
