RevOps & GTM Projects: specific pieces of your sales system, with a start and an end
Twenty-two fixed-scope projects — from ICP and TAM sourcing to handoffs, forecasting and CRM implementation — that you can buy one at a time or in the order the Diagnostic sets. Each one delivers something that works inside your stack and comes documented.
If any of these sounds familiar
The target account list is rebuilt from scratch every quarter
Nobody trusts the previous one because nobody remembers what criteria it was built on. That's an ICP and TAM project, not an attitude problem.
Deals are single-threaded, and the one contact isn't the person who signs
There's no map of the buying committee, so every opportunity depends on a single contact who might leave or stop replying.
Two people pull the same month's report and get two different numbers
Without a glossary or defined metrics, the forecast gets argued over instead of read.
What was promised during the sale isn't written down when the project starts
The handoff from sales to customer success lives in the memory of the rep who closed the deal, and the customer notices in the second week.
You're asking AI to analyse a CRM that's half empty
Automation arrives before data hygiene, and it confidently returns conclusions about data that doesn't exist.
Each piece on its own looks small. Together, they're why you're missing the number.
Fixed-scope projects, not a retainer in disguise.
Every project has a scope agreed in writing before it starts, a deliverable that works inside your CRM and your tools, and an end. They're grouped into five categories — data and ICP; messaging and outreach; CRM, data and forecasting; content and demand channels; and CRM implementation — and bought on their own or in the order the Diagnostic sets. The three demand channels are the exception: they're billed monthly, because that work never ends.
What we deliver
Five categories, and the right piece in each one
You can buy each project on its own. The Diagnostic tells you which comes first; if you already know, we agree the scope in one session and get started.
Data and ICP
Who you sell to, stated with criteria someone else can apply, and the universe of accounts built and prioritised on them.
ICP definition
Your ICP, defined from your product or service and your competitors: verifiable criteria and exclusion criteria, documented.
TAM sourcing
Finding potential customers by firmographic criteria: the full universe of accounts that fit.
Account scoring
Prioritisation of the book of business (BoB) based on firmographic data and signals, with the score explained.
Enriched TAM
Definition and identification of signals in the TAM: what shows an account is in market, and how to detect it.
Buyer persona mapping
Defining and finding the relevant roles at target accounts: who decides, who evaluates and who uses it.
Territory mapping
Splitting accounts and territories across your reps, with written rules and no overlaps.
Messaging and outreach
What you say, to whom and when: the differentiated message, the campaigns that carry it and the signals that decide when to reach out.
Value proposition
Definition of the value proposition for the ICP, differentiated from the competition and written for each buyer profile.
Automated outreach
Building the LinkedIn and email communication campaigns: sequences by segment, connected to the CRM.
Signal monitoring
Ongoing analysis of the signals you've identified, to reprioritise your book of business and time your outreach.
CRM, data and forecasting
What happens inside the CRM between first contact and renewal: the handoffs, the alerts, the clean-up and the numbers that come out of it.
CRM enrichment
Loading target-account and contact data into the CRM, with the source of every data point.
Handoff BDR → AE
Playbook and agents that analyse the deal information to prepare the handoff from prospecting to sales.
Handoff AE → CS
Playbook and agents that analyse the deal information to prepare the handoff from sales to customer success.
Deal gap analysis
CRM configuration and agents that identify red flags in each opportunity and propose the next action.
Data hygiene
Review of the CRM data and the changes needed to keep a healthy database over time.
Workflows between applications
External automations between applications: manual transfers become flows with a log and an owner.
Forecasting
Definition of the key metrics for forecasting, a glossary of what each number means and tracking dashboards.
Content and demand channels
What makes someone raise their hand: the sales materials and the three channels bought by the month, measured in opportunities.
AI content generation
Case studies, one-pagers and battlecards created with AI from your real cases, applying your judgement.
SEO and AEO
MonthlyAppearing in search engines and in AI answers for the searches your ICP makes.
Content and lead magnets
MonthlyPublishing so that someone raises their hand: content pieces, lead magnets and the flow that turns them into conversations.
Paid media
MonthlyPaid campaigns measured in opportunities, not clicks. The ad spend is paid directly to the platform.
CRM implementation
The CRM built on your process, not the other way round. Two tools, chosen by the size of the team and by what has to happen after the contract is signed.
Attio implementation
Implementing Attio as the CRM for teams of fewer than ten people selling.
HubSpot implementation
Implementing HubSpot as the CRM for larger teams or teams with post-sales needs.
Who it's for, and who it isn't
How a project works
- [01]
Scope
What gets built, what's left out, what we need from you and what we deliver. If you're coming from the Diagnostic, it's already written; if not, we agree it in one session.
- Deliverable: scope document with deliverable, deadline and fixed price
- [02]
Build
Inside your stack and with your team, in pieces that go into production as they are ready. Whatever isn't used gets fixed or removed.
- Cadence: weekly review of what has been delivered
- [03]
Delivery and adoption
Documentation, a playbook for the people who operate it and a hands-on session with the team so they can use it on their own. We leave when it works without us.
- Deliverable: documented system + adoption session
What you walk away with
What it costs, up front
We fix the figure with the scope, in writing, before we start. If you've done the RevOps & GTM Diagnostic, it comes straight from it. What drives it: the specific project and its scope, the number of people, accounts or contacts it covers and the integrations needed with your CRM and your tools.
Before you ask
Each project is quoted on its own, and the price is agreed in writing with the scope before we start (if you're coming from the Diagnostic, it's already in there). The factors that move it are listed here. We don't publish a "from" price because twenty-two different projects don't share the same floor, and a figure that only holds for one would mislead on the other twenty-one.
What comes before and after
Pick the piece you need
Tell us how your pipeline works today and we'll tell you honestly where we'd start, or whether we're the right fit.
30 minutes, no sales pressure.