Ask a marketing team how the website is performing and you will usually get traffic figures. Ask how many opportunities it produced last quarter and the room goes quiet.
This is not incompetence. It is an architectural problem: in most companies, the website and the sales pipeline are two disconnected systems with a human copy-paste operation between them. Nobody instrumented the path, so nobody can report on it.
The four disconnections
The site cannot be changed quickly. Every copy change is a ticket, a sprint and a deploy. So the site says what the company did eighteen months ago, and campaigns run on pages built by whoever was free that week.
Forms email an inbox. The enquiry arrives as unstructured text in a shared mailbox. Someone reads it, decides whether it matters, and re-types it into the CRM — usually the next morning, usually with the source information lost.
Qualification happens after the delay, not before. Sales works the queue in arrival order because there is no signal to work it in any other order. Good opportunities cool while someone processes noise.
Attribution is reconstructed at quarter end. By hand, from partial data, badly. The number produced is not trusted by anyone who understands how it was made.
Each of these is fixable. Fixing one of them changes very little; fixing all four changes what the site is.
Build a landing system, not landing pages
The single highest-leverage change for most B2B marketing teams is to stop building campaign pages one at a time.
A landing system is a constrained library of blocks — hero, proof, comparison, FAQ, form — with typography, spacing, responsive behaviour and accessibility already solved. Marketing assembles a page from blocks and writes copy. That is the whole workflow.
The trade-off is real and worth stating: you give up per-page bespoke design. In exchange, a campaign page ships in an afternoon instead of waiting three weeks for development capacity, every page inherits the same performance and accessibility baseline, and results become comparable across campaigns because the instrumentation is identical.
For a team running two campaigns a year, this is over-engineering. For a team running two a month, it is the difference between a marketing function that can move and one that cannot.
Make the form part of the system
A form that emails an inbox is a dead end. A form that is part of the system:
- validates on the client and the server, in the visitor's language
- records source, campaign, landing page and referrer on the submission itself
- writes into the CRM directly, deduplicated against existing records
- routes to a named owner rather than a shared queue
- confirms to the sender that a person will reply
None of this is technically difficult. It is simply nobody's job in the usual arrangement, which is why it usually does not exist.
Qualify before a human sees it
Once submissions arrive structured, qualification becomes possible before anyone reads them. Start with rules — company size, stated need, budget indication, existing customer, obvious spam. Rules are cheap, transparent, and handle most of the volume.
Where rules are insufficient — free-text descriptions of a problem, ambiguous fit — an agent can score against your written criteria and attach a short rationale a salesperson can read in five seconds.
The critical constraint: qualification orders the queue, it does not reply to anyone. The agent decides what a human sees first. A human still decides what to say.
Speed is a feature you have to defend
Performance is not a launch-day achievement, it is a property that decays. Every added script, every unoptimised image, every third-party tag moves it in one direction.
Treat it as a budget: agree the target as a number before development starts, enforce it in CI, and make regressions fail the build. A site that was fast at launch and is slow eighteen months later is the normal outcome of not doing this.
What "accountable for a number" actually requires
Put plainly, the site can be held accountable when you can answer:
- which page produced this opportunity
- which campaign produced that page's traffic
- how long it took from submission to first human contact
- what proportion of submissions were worth contacting at all
Every one of those is a data question, and every one is answerable only if the path was instrumented end to end. That is the work. The visual design matters — but it is not what turns a website into a sales system.