Growth engineering for B2B and D2C marketing teams

Verne turns the traffic you already pay for into more qualified leads. We fix the pages and forms where visitors drop off, make your site readable to search engines and AI answers, connect forms to your CRM so no lead waits, and set up tracking that shows which channel brought each deal.

What your funnel is worth, in your numbers

Put in last month’s figures. The maths shows the leads and revenue your traffic produces now, and what one more point of conversion would add.

6,000
1.5%
15%
US$4,000
Currency
  1. Visitors6,000
  2. Leads90
  3. Deals14

Each month your traffic brings

90 leads, US$54,000

One more point of conversion is worth

US$36,000 a month

That is US$432,000 a year, or US$3,600 a month for each tenth of a point. Most conversion work moves tenths, so this is the figure to weigh each fix against.

Where growth engineering works

  • Websites and landing pages

    Most people meet your business on a phone screen before they ever call. Pages built to load fast and make the next step plain.

  • Conversion rate optimisation

    Forms, pricing pages and calls to action changed one at a time, with the result read from your own analytics.

  • SEO and AI-search visibility

    Pages search engines can crawl and facts AI assistants can quote, with structured data and content that renders without scripts.

  • Marketing automation and CRM

    Every form lands in the CRM with its source, the right person is told, and follow-up starts the same day.

  • Analytics and attribution

    A tracking plan with named events, conversions sent from your server, and deals tied to the channel that started them.

  • Brand and market listening

    Monitoring is only useful if each signal lands somewhere accountable. Mentions and reviews routed to a named owner.

For your engineers

Stack

Next.js or your current CMS; GA4, PostHog or Mixpanel; Google Tag Manager with server-side tagging; HubSpot, Pipedrive or Salesforce.

Tracking

A tracking plan with event names, properties and owners. Conversions fire on confirmed success, never on the button click. UTM rules, consent mode and deduplicated server events.

Search

Server-rendered pages, self-referencing canonicals, XML sitemaps, schema.org markup per page type, Core Web Vitals budgets, and crawler access for AI assistants.

Experiments

Sample size fixed before a test starts, one primary metric, a set run length, and no early stopping on a good day.

How we find the leak

We start from your analytics and CRM. Each stage of the funnel gets a number: visits, form starts, completed forms, replies, meetings and deals. The biggest drop between two stages is where the first change goes.

We change one thing at a time and agree the measure before the change ships. When a page has too little traffic for a fair test, we say so and use session recordings and customer interviews.

Thirty thousand visits a month and four demo requests

A Toronto logistics-software company paid for traffic that arrived and left. Analytics said the demo form converted at 9%. Sales said they saw four demos a month.

Both teams were right about something, and every meeting started with the argument.

  1. Find which number is wrongThe conversion event fired when the button was clicked, before validation. Every failed submit counted as a lead.
  2. Fix the measurement firstEngineers moved the event to the confirmed server response and sent each lead to the CRM with its source, so marketing and sales count the same rows.
  3. Then fix the pageSession recordings showed visitors hunting for price. The pricing page now shows ranges, and the demo form asks four questions instead of eleven.
  4. A person calls each testEach change ran as an A/B test with its sample size agreed up front, and the head of marketing called the result.
tag-manager/demo_form.js
submitButton.addEventListener("click", () => {  track("demo_request");});form.addEventListener("submit", async (event) => {  event.preventDefault();  const res = await submitDemo(new FormData(form));  if (res.ok) track("demo_request", { lead_id: res.leadId });});
  1. Analytics auditdemo_request fired 2,712 times in 30 days. The CRM received 118 leads.
  2. EngineerThe event now fires on a confirmed server response and carries the CRM lead ID, so both systems count the same leads.
  3. Your head of marketingApproved, and asked for the old figures to be annotated in past reports.

Questions about growth engineering

Do you run our paid ads?

We build what the ads land on: pages, forms, tracking and follow-up. Media buying stays with your team or agency, and we give them conversion data they can check.

Can you work on our existing site?

Yes. Your hosting, domain and accounts stay in your name, and we work through access you can remove at any time.

How do you measure AI-search visibility?

We check an agreed list of buyer questions in ChatGPT, Perplexity and Google’s AI Overviews each month, record which sources each answer cites, and track referral visits from those assistants in your analytics.

How soon will we see more leads?

Tracking and form fixes show first, because they act on traffic you already have. Search work takes months. We agree the measure for each change before we make it.

Find the leak in your funnel

Share read access to your analytics and CRM. In the diagnostic we measure every stage and price the fix for the biggest drop.