How we track results

Typical priceIncluded in the engine setup fee. No separate attribution charge.

Typical timelineLive the day the engine launches. Reporting cadence weekly.

How we build it

1. Why attribution comes first

Performance pricing is the entire foundation of our model: you only pay when the engine delivers a qualified lead, a ranking improvement, a booked meeting, a closed deal, or revenue. None of that works unless both sides agree on what counts and have the data to prove it. So before a single message is sent or a single page is published, we get the measurement layer in place.

Definitions written into the engagement letter (what counts as a qualified lead, what counts as a ranking improvement, what doesn't)
The data source for each metric agreed up front, in writing
A deterministic attribution rule for ambiguous cases, also in writing
First-touch is the default. We don't retroactively claim credit for leads we didn't source.

2. Path A. We integrate with your stack

Most clients already pay for a CRM and analytics. We connect to what you have, write source data into the records you already work with, and use your tools as the source of truth.

CRM via API: HubSpot, Pipedrive, Salesforce, Close. Per-lead source citations on every record.
Analytics: GA4, Search Console, PostHog, or whatever you use. We pull from your existing properties.
Ad platforms: Google Ads, LinkedIn, Meta. We tag UTMs and read conversion events you already track.
Reporting: Slack or email summaries on whatever cadence your team prefers, on top of your existing dashboards.
Your data stays in your tools. We don't move it, copy it, or hold it hostage.

3. Path B. We build the attribution layer

If you don't have a CRM or analytics setup, we install a lightweight one as part of the engine build. No new vendor for you to manage, no extra subscription. It comes with the engine.

Lead source capture on your site: UTM, referrer, gclid, first-touch landing page
Form attribution wired into your existing forms or new ones we build
Call tracking through Twilio numbers when phone leads matter
A simple shared dashboard at a private URL you and we can both see in real time
A weekly numbers email to whoever on your team should see it
If you later move to HubSpot or similar, we hand the data over cleanly. Nothing is locked in.

4. What you see every week

Reporting is plain English, not a 40-tab spreadsheet. The same numbers that decide what we get paid are the numbers we share with you.

Per-lead source citations: where each lead came from, when, and what they did on your site
Weekly numbers email to your team with last-week vs prior-week deltas
Engine-specific metrics: ranking pulls per page (SEO), reply-rate by audience and angle (outreach), reactivation rate by segment (reactivation)
An honest commentary line on what's working and what's not
A monthly review call when the engine is large enough to justify one

5. What we don't claim credit for

We measure outputs the engine delivers. We don't claim credit for things we didn't do.

Downstream closed deals beyond the qualified-lead handoff. You and your sales team own the close. Revenue-share contracts are the exception, on agreed-upon definitions.
Channels we didn't touch. If a lead came in through your existing referral, we don't count it.
Brand search and direct traffic, unless we explicitly built a campaign that drove it.
We'd rather under-claim and keep your trust than over-claim and lose it.

Edge cases we handle

No CRM and no plans for one. We host a lightweight pipeline as part of the build, included in the setup fee.
Strict data-residency or SOC2 environments. We deploy connectors inside your environment and never store sensitive records on our side.
Multi-channel attribution disputes. We propose a deterministic rule (first-touch by default) up front and put it in the engagement letter, so there's no ambiguity later.
Offline conversions (sales reps closing in person). We push events back from your CRM so attribution stays whole.