Attribution engineering
A protected deal-level source property populated by your own logic, so reporting can answer why rather than only what.
We are engineers, not an agency. We build the attribution, the grounding layer and the approval workflow your marketing team uses. What they say with it is theirs.
Four things we find in almost every marketing team whose reporting cannot answer why.
You can see that pipeline fell. Nothing in the dashboard tells you which decision caused it.
Source held at deal level and protected, so the question survives contact with a buying committee.
Marketing counts leads, sales counts opportunities, finance counts invoices, and none of the three reconcile.
Scheduled, matched on agreed keys, reconciled to invoiced revenue rather than closed-won optimism.
And a search of the intranet for whatever the last person wrote about this product.
Approved evidence, claims and product facts assembled so your team drafts from something true.
You cannot tell what was machine-drafted, who approved it, or on what basis.
Every AI-assisted asset carries who reviewed it, when, and against which evidence.
You can see that pipeline fell. Nothing in the dashboard tells you which decision caused it.
Source held at deal level and protected, so the question survives contact with a buying committee.
Marketing counts leads, sales counts opportunities, finance counts invoices, and none of the three reconcile.
Scheduled, matched on agreed keys, reconciled to invoiced revenue rather than closed-won optimism.
And a search of the intranet for whatever the last person wrote about this product.
Approved evidence, claims and product facts assembled so your team drafts from something true.
You cannot tell what was machine-drafted, who approved it, or on what basis.
Every AI-assisted asset carries who reviewed it, when, and against which evidence.
Swipe to explore
A wave activates two of the five build capabilities. Enablement runs alongside, and approval and audit are engineered into all of them rather than chosen instead of one.
A protected deal-level source property populated by your own logic, so reporting can answer why rather than only what.
The grounding layer, claim controls and review queue your team drafts with. We build the tooling, they write the words.
The evidence for a marketing decision gathered by a system, so the meeting argues about the decision rather than the numbers.
Setup, quality checks and dependency tracking, with conflicting or incomplete data caught before a campaign goes out rather than after.
Detection of incomplete, duplicated and contradictory records, and controlled corrections rather than silent overwrites.
Your team trained on the tooling we build, so the grounding layer and the approval queue get used rather than worked around.
HubSpot documents a deal's original traffic source as coming from the associated contact with the earliest activity for that deal.
Moving from contact reports to deal reports does not fix it. Whoever touched first wins the credit, which on a committee sale is often nobody who mattered.
HubSpot's knowledge base states deal and revenue attribution are Marketing Hub Enterprise only. On Professional it stops at contacts. Check what your subscription covers.
A separate deal-level source, populated by rules you control at creation, which nothing downstream overwrites.
Tied to invoiced revenue from your finance system, so marketing reporting and the management accounts agree.
You stop asking which channel got the most leads and start asking which one produced revenue you actually collected.
This is where an engineering firm differs from an agency. We build the controls. Your team makes the decisions inside them.
Anything a customer will see sits at draft or act-with-approval. It does not publish itself.
A factual claim is reviewed apart from the copy around it, because that is where the risk is.
No autonomous change to lists, suppressions or consent state. Ever.
Writes are limited to named properties, not general access because one action needed it.
Changing a reporting definition is a restricted action, or your trend data quietly becomes fiction.
Who reviewed an asset, when, and against which evidence. Queryable, not a report you run later.
An in-house engineering team that has delivered more than 300 technology projects. Work with engineers who have built this before.
Agents and integrations designed, tested and shipped by our own engineers. Nothing is subcontracted.
SpotDev is enrolled in the OpenAI Partner Network at Select tier, alongside HubSpot Diamond status and Custom Integration and Onboarding accreditations.
Honest evaluation of the right model for the work. We hold OpenAI Select Partner status and deep expertise in Anthropic's Claude, and we will say when the answer is the AI you already pay for.
No. We build the system your team writes with: the grounding layer, the claim controls, the review queue and the audit trail. The voice stays yours. If you want an agency, we will say so on the first call.
Not for what we build, and that is rather the point. HubSpot's knowledge base puts native deal and revenue attribution at Enterprise only. A protected deal property is an engineering answer to a licensing problem.
It is exactly the right time, because attribution engineering is largely data engineering. We assess completeness and matching before building anything, and tell you what has to be fixed first.
No. Anything customer-facing is drafted for approval, list and consent changes are restricted outright, and CRM writes are limited to named fields.
More than people assume. Brand voice and its own agents exist and may be enough. Where they are, use them. We build what is missing around them, which is usually the data layer and the audit trail.
From £10,000 per month as part of AI Accelerator, committed a quarter at a time. Model and platform usage is billed separately. Enterprise programmes are priced on complexity.
Then you stop. The baseline is captured before we build, so the quarterly decision rests on a comparison rather than a mood.
Related: AI Accelerator · AI for Sales · AI implementation
SpotDev is an OpenAI Select Partner and a HubSpot Diamond Solutions Partner. SpotDev is a separate company from OpenAI, and partner status does not constitute endorsement of SpotDev by OpenAI. OpenAI and ChatGPT are trademarks of OpenAI. HubSpot is a trademark of HubSpot, Inc. Claude is a trademark of Anthropic, PBC.