Most companies run two agencies that blame each other. V12 is one senior team building the product and the pipeline against a single number — so nobody has to translate between them.
How we work
Internal tools, customer portals and platforms built around how your business actually runs.
Fast, well-structured sites and storefronts that hold up under real traffic and real editing.
Demand programmes built on one funnel model, so channels stop competing for the same credit.
Measurement you can defend in a board meeting, and a test queue that keeps compounding.
We are not the cheapest option and we are not the biggest. These are the differences that actually change outcomes.
Software and marketing sit in the same standup. When conversion drops, nobody argues about whether it’s a code problem or a campaign problem — the same team fixes it.
First production release inside four to six weeks on most engagements. We’d rather learn from something real than defend an estimate written before anyone used it.
You get the repository, the accounts, the documentation and the reasoning. Every engagement is built so you could take it in-house tomorrow.
The people in the pitch are the people doing the work. No account layer translating between you and whoever actually writes the code.
Diagnosis is short and written down. Building starts early and ships often. The last phase never really ends, which is the point.
Week 1–2
We audit what exists — code, funnel, data, tooling — and interview the people closest to the work. Output is a written diagnosis naming the constraint, not a list of everything that could be improved.
Week 2–3
One scope, one success metric, one sequence. We agree what we are not doing in this phase, which is usually the harder half of the conversation.
Week 3–12
Two-week increments, each ending in something demonstrable in a real environment. You see progress in the product, not in a status report.
Ongoing
Instrumented release with rollback, monitoring and alerting in place before traffic arrives. Training and documentation ship with the work, not after it.
Ongoing
A standing test queue against the current constraint, reviewed monthly. Small compounding gains beat one redesign a year.
Operating figures we hold ourselves to across every engagement, not a highlight reel of best cases.
Software, web and growth programmes since 2019
From kickoff to production on build engagements
Clients continuing into a second engagement phase
Measured on mobile at launch across shipped sites
Sample figures shown for layout. Replace with verified, auditable numbers before publishing performance claims.
Attributed by role and sector — we don’t publish names or logos without written permission.
The first thing they did was tell us the project we asked for wasn’t the one we needed. That conversation was uncomfortable and it saved us most of a year.
We had working software in five weeks. Every agency before them wanted four months of discovery before showing us anything.
They fixed our measurement before touching our budget. Turned out we’d been scaling the two channels that weren’t working.
Handover was genuinely complete — repository, documentation, runbooks. Our own team picked it up in a fortnight without a support contract.
Illustrative quotes shown for layout. Replace with permissioned, attributable client statements.