Six services, with pricing.
We run GTM engineering, paid media, LinkedIn content, RevOps and BDR with your team, in tools you own, and train your team to run them. Pick a service to see what each tier covers and what it costs. Selling to a short list of named accounts? See them run as account-based marketing.
A problem outside these six, such as a website AI assistants can read or a slow job inside the business? We take those on as AI engineering projects, quoted per project.
Pipeline numbers everyone trusts.
We clean up your HubSpot or Salesforce, set the rules for who owns each lead and how fast they reply, and build the reports your board asks for, then keep them true with your team.
- What it costs
- From $6,000 a monthWhat it covers →
- What happens first
- A read-only audit: we map your CRM and list what is wrong.
- What you keep
- The definitions, the rules, the reports and the change log, in your CRM.
Week one, and every week after.
Pick a step to see what we do, what you approve, and what you keep. A ringed step waits for your yes.
Systems built for
What it costs, and what you get.
The audit comes first, and the plan is written before anything changes. The monthly fee covers the build and the support that keeps it true.
- A monthly retainer to build the CRM right and keep it that way. A defined build, such as a CRM rebuild or a migration, is a fixed-price project.
- Prices are per month, in US dollars. You commit a quarter at a time.
- The first call ends with a scope and a number.
- Every price we publish, on one page →
Retainer
For a team whose CRM needs an owner every month.
- From$6,000a month
- A read-only audit, and a written plan you approve before anything changes
- A one-page definition for each stage, signed by sales and marketing
- Duplicates merged and fields cleaned under rules you approved
- A weekly data-health report to the person who owns the CRM
- Routing by territory, account and size, with a timer on the first reply
- Qualification built from your closed-won deals, with enrichment filling the gaps
- Pipeline, conversion and source reports, checked against finance
- Rules changed as your team changes, and every change in a log
- A thirty-minute review every two weeks, and a shared Slack channel
- A quarterly review of what to build next
Fixed-price project
For one defined build: a CRM rebuild or a migration.
- Price
- Quoted on the call
- Scope, price and dates agreed in writing before work starts
- The audit and the definitions first, then the build in the order you approve
- Documentation and training for your admin at the end
Every tier
- Run in tools in your name, from the first day
- Your approval on every send, ad, post and CRM change before it goes out
- Documented as it is built
- Run with your team in the loop, tested and improved at every review
Who it is for, and who it is not.
Three teams this is built for, and three asks we would decline on the first call.
Built for
- A buried RevOps team
- You need enrichment, scoring and routing in the CRM, and the team is consumed by a migration or a renewal. We build alongside them, document it as we go, and keep it running with them.
- Before the first RevOps hire
- You are about to hire someone to own the CRM. We build the foundation first, so the hire starts on a system that works instead of inheriting the mess.
- Three pipeline numbers
- Sales, marketing and finance each report a different pipeline. One definition for each stage, written down and built into the reports everyone reads.
Not for
- Demand
- RevOps does not create demand. It routes, qualifies and reports the demand you have. If the pipeline is empty, start with outbound or ads.
- Changes without a plan
- We change nothing until you approve a written plan. If the ask is to fix it tonight without one, we are not the right firm.
- A clean-up with no owner
- A CRM cleaned once and owned by nobody is messy again in a quarter. We work with a named person on your side, and if there is none, naming one comes first.
A CRM the reps work around, and what replaces it.
Revenue operations fails in three places, and each one costs deals before anyone notices.
- Data
Duplicate accounts, empty fields and three versions of the same deal, so nobody trusts a report.
One record per account and contact, required fields enforced, and a health report that tells you when it slips.
- Routing
Leads sit in a queue until someone notices. The first reply comes days later, if it comes.
Every lead has an owner the moment it arrives, a timer on the first reply, and an alert when the timer runs out.
- Reporting
Sales, marketing and finance each report a different pipeline number.
One definition for each stage and each source, written down and built into the reports everyone reads.
What we build in your CRM.
Four parts, built in the CRM you already have. Each one is documented as it is built, in your own instance.
Record health
Duplicates, empty fields and orphaned contacts are found, fixed under rules you approved, and watched from then on.
- Merge rules written down and approved before anything is merged
- Required fields enforced where the data is entered
- A weekly health report to the person who owns the CRM
IllustrationOne account, cleaned up
In your HubSpot or Salesforce
A company your team sells to
What Before the clean-up After the clean-up Records for the company Several, each holding part of the history One, merged under the rule you approved Its contacts Some orphaned, linked to nothing Each linked to the account Required fields Left blank when entered Required where the data is entered Who watches it Nobody Your CRM owner, in the weekly health report Can a report rely on it? No. Yes. What this shows: Each fix to the account was made under a merge rule you approved, and your CRM owner keeps watching it. Routing and response time
A new lead is assigned the moment it arrives, the owner is told in Slack, and a timer starts on the first reply.
- Rules by territory, account, size and existing relationship
- A response timer on every inbound lead
- An alert to the owner and their manager when it is missed
IllustrationThe routing rule, as written
In your HubSpot or Salesforce
Who owns a new inbound lead
Existing relationshipIf someone on your team already works with them, it goes to that person.
AccountIf the company is already assigned, it goes to the account's owner.
Size and territoryOtherwise it goes to the rep who covers that size of company in that region.
The reply timerStarts when the owner is told in Slack.
If it runs out, the owner and their manager are both alerted.
ApprovedPart of the written plan, before any lead was routed by it.
Your yes
What this shows: The routing rule is written down in your CRM, and it went live only after you approved it in the plan. Engagement tracking and qualification
Who visited your site, engaged with your LinkedIn content or replied is tracked, scored against your closed-won deals, and routed to the right person.
- Site visits and content engagement written to the contact
- Qualification rules built from your own closed-won deals
- Enrichment fills gaps before a rep opens the record
IllustrationWhat counts toward the score
In your HubSpot or Salesforce
What happened Written to Toward the score? A visit to your pricing pageTracked on your own site. Written toThe contact, with the page Toward the score?Counts A comment on your LinkedIn postEngagement with your content. Written toThe contact, with the post Toward the score?Counts A reply to a sales emailFrom your sending tool. Written toThe contact, with the email Toward the score?Counts A visit from a company unlike your won dealsStill tracked, so nothing is lost. Written toThe contact, with the page Toward the score?Scores low What this shows: Engagement is written to the contact in your CRM, and the score is built from your own won deals. Definitions and reports
Each stage has a written definition and an owner. The reports are built on those definitions, so the same number appears wherever it is quoted.
- A one-page definition for each stage and source
- Pipeline, conversion and source reports built once
- Checked against finance before anyone reports from them
IllustrationThe definitions page
In your HubSpot or Salesforce
What each stage means
LeadSomeone at a company you sell to who has asked to hear more.
Qualified leadA lead that looks like your won deals and has agreed to talk.
OpportunityA qualified lead that sales has accepted and is working.
CustomerA signed deal that finance has on its books.
ReportsEvery pipeline, conversion and source report uses these words.
Checked against finance before anyone reports from them.
SignedBy sales and marketing, before anything was built on it.
Your yes
What this shows: Sales and marketing sign one page of definitions before any report is built, and it stays in your CRM.
An agent does the work. It waits for your yes.
Two illustrations of the system running: the bulk work done by an agent, with a person approving the change that matters, and what the CRM records when every outcome is written back.
The agent does the bulk work. A person approves the change that matters.
It reads the CRM, scores and writes, line by line, and stops at the one line marked needs approval until your owner says yes.
An agent reads the CRM, scores each account and writes the tiers, stops at the line that needs approval, waits for the CRM owner to approve it, then finishes the write-back.
Every outcome lands in the CRM the moment it happens.
A reply, a meeting, a stage change: each one a pulse, each one a stamp on the record. The flat stretch is the tool that did not write back.
A pipeline from Lead to Won with a heartbeat running along it. Each reply, meeting and stage change is a pulse that lands as a stamp on the CRM record. One flat stretch is a tool that did not write back.
Who does what.
Agents do the bulk work of a clean-up, through access you can revoke. A person writes the rules down, you approve them, and nothing is deleted without a record of what and why.
Agents do
- Find duplicates across your records
- Fill the gaps in a record before a rep sees it
- Do the bulk work of the clean-up, once the plan is approved
A person
- Maps your objects, fields, owners and stages, read-only, before anything changes
- Writes down every merge rule before it runs
- Documents each field, rule and report as it is built, with a change log
Waits for your yes
- The definitions page, signed by sales and marketing
- The clean-up plan, in writing, before any record changes
- Every merge rule, before it runs
On the record.
“Warmup really helped us elevate our approach to GTM. We were manually managing lists and contacts, tracking what we could. WarmUp helped track who engaged with our LinkedIn content, visited our site, and automated the qualification process so we could route them to the right place.”
“Mike and the WarmUp team really came through for us when we needed to test outbound with different personas. They walked us through their messaging process, built solid lists based on what we told them we were looking for, and actually got us in front of Agile coaches - which wasn't easy. Good people to work with.”
“What I find both unique and refreshing in working with Warmup is their efforts to refine the prospect lists such that 90-95% of the companies that Warmup eventually presented were in our target market. The time savings aspect of this one element cannot be understated, not to mention how this illustrates that Warmup is not just listening to our needs but also acting on that information.”
Gary SchwartzFormer CEO, MTS Scanners“Our company MTS scanners have been working with Deisy at warm-up for sometime. Deisy is a quick learner has great phone presence and is able to connect with strangers on the other side of a call. Deisy does her homework has access to great lists and has been Very accommodating to MTS over the months that we work together.”
What the first three months ask of you.
The audit first, then six weeks of build, then a review with your CRM owner every two weeks.
Build
Weeks 1 to 6
What it takes from youAdmin access to your CRM and two working sessions to agree definitions and routing.
The audit, the definitions, the clean-up, routing, qualification and the first reports.
Run
Month 2 onward
What it takes from youA thirty-minute review every two weeks.
We watch data health, fix what breaks, and change the rules as your team changes.
Improve
Month 3 onward
What it takes from youName your CRM owner, and approve each change before it goes in.
Each review with your CRM owner decides what changes next: a rule tightened, a field retired, a report the board asked for. Every change goes in the log.
What buyers ask about RevOps.
What is RevOps, and how do we know we need it?
RevOps is the work of making sure marketing, sales and finance run on the same data: one definition of a lead, one rule for who owns it, and one pipeline number. You need it when leads wait, reports disagree, or nobody trusts the CRM enough to plan from it.
How is RevOps priced?
A monthly retainer with a published starting price, covering the audit, the clean-up, routing, qualification, the reports and the support that keeps them true. A defined build with a clear end, such as a CRM rebuild or a migration from another system, is quoted as a fixed-price project before work starts. The first call ends with a scope and a number.
What does the retainer include, and what does it not?
Included: a read-only audit and a written plan, one-page stage definitions, duplicates merged and fields cleaned under rules you approved, a weekly data-health report, routing with a reply timer, qualification built from your closed-won deals, pipeline and source reports checked against finance, a review every two weeks, and rule changes as your team changes. Not included: creating demand, and a migration, which is scoped as its own project.
Is it a project or an ongoing retainer?
Both exist, for different jobs. A rebuild or a migration has an end, so it is a fixed-price project with scope, price and dates agreed in writing first. Keeping the CRM true has no end, so that is the monthly retainer. Many clients start with the audit on the retainer and add a project when the audit shows one is needed.
Do you work in HubSpot or Salesforce?
Both. If you run something else, say so on the first call and we will tell you straight whether we can do the work.
Will you change our CRM without asking?
No. The audit is read-only. You get a written plan of what we would change and why, and we change nothing until you approve it. Every change after that goes in a log, nothing is deleted without a rule you approved, and your data stays in your CRM, reached through access you grant and can revoke.
How long does a CRM clean-up take?
The audit takes about two weeks. The first changes land in weeks three and four, and the whole build runs about six weeks. A very large or very messy CRM takes longer, and we tell you after the audit.
Who does what between your team and ours?
You give us admin access, join two working sessions to agree the stage definitions and the routing rules, approve the written plan, and name the person who owns the CRM. We do the audit, the clean-up, the rules, the reports and the documentation, and we work through every change with your owner.
Where do the reports live?
In your CRM, as standard HubSpot or Salesforce reports built on the stage definitions everyone signed: pipeline, conversion and source, checked against finance before anyone reports from them, so the number the board sees is the number sales and marketing see. Nothing lives in a tool of ours.
How do outbound, ads and content show up in the CRM?
Each one writes to the same record: outbound touches and replies, ad leads with their campaign, LinkedIn engagement with the post that drew it. Routing and the stage definitions then decide what happens to every lead the other services create, which is why RevOps runs under everything else we do.
Who is this for, and who is it not for?
For a RevOps team buried in a migration or a renewal, a company about to make its first RevOps hire (we build the foundation, so the hire starts on a system that works), and any team where sales, marketing and finance report three pipelines. Not for anyone who needs demand created, wants changes made tonight without a plan, or has nobody on their side to own the CRM.
Can you guarantee more pipeline?
No. RevOps does not create demand. It makes sure the demand you have is routed fast, qualified honestly and reported the same way by everyone. That is where deals are lost without anyone noticing.
Do you use AI on our CRM data?
AI agents find duplicates, fill gaps and do the bulk work of a clean-up. Every merge rule is written down and approved by you before it runs, the work happens through access you can revoke, and nothing is deleted without a record of what and why.
What happens if we stop?
The fee stops, and nothing has to move. The fields, rules, reports and change log were built in your own instance and documented as they went in, so there is nothing to export and nothing to switch off. If you would rather your admin run it, we plan the handover with you and train them. How long that takes depends on how complex the CRM is, so we do not promise a date.
What RevOps hands the other five.
Take one service or all six. Either way every tool is in your name, and each service passes something concrete to the next.
- Every other service writes to the CRM this one keeps true: outbound touches, ad leads, content engagement.
- Routing and the stage definitions decide what happens to every lead the other services create, and give the BDR one definition of a meeting.
See RevOps at work on one signal, with the call, your approval and what you keep: A champion changes jobs, A visit from an account on your list, A request from your website, A deal that went quiet. Or read all the signal plays.
- GTM engineeringOutbound from buying signals, run in your own Clay (the data tool we build in) and CRM.
- Paid mediaLinkedIn and Google Ads aimed at the accounts you chose, measured as cost per opportunity in your CRM.
- LinkedIn contentPosts in your own voice from a weekly interview, with the people who engage matched to your target accounts.
- this pageRevOpsRevenue operations for a CRM your team trusts: clean records, leads routed to an owner, qualification that matches your closed-won deals.
- BDRA named rep who calls when a signal gives a reason to. We employ the rep; the list is built in your own Clay and CRM, and every call and note is kept in your CRM, open to your team.
- Team trainingWorkshops and programs that teach your own sellers and marketers to build signals, lists and plays, on-site or virtual, practised in your own Clay and CRM.
Show us your pipeline report.
Thirty minutes. Share your screen and we will tell you what we see: where records disagree, where leads wait, and what we would fix first.
Or skip the form
- Call+1 463 283 6462
- Pick a timeOpen the calendar












