RevOps case: from a Pipedrive nobody trusted to a pipeline you steer on

    A growing B2B company with data in 4 systems and leads that waited 2 days. What we did per week, what we built, what it costs and what we do not promise.
    Case StudySander VergouwenUpdated: 16 November 2026

    In short

    A growing B2B company had a Pipedrive nobody trusted. Data sat in 4 systems, leads came in through 6 entry points and waited more than 2 days on average for follow-up. In 7 weeks we rebuilt the setup with 2 pipelines and 12 fields instead of more than 40, then spent 90 days adjusting. The client stays anonymous and we publish no revenue figures.

    Source: Sales Surge project file, client anonymousAs of: 1 February 2026

    In this article
    1. Where the company started
    2. Weeks 1 and 2: agreeing what a lead is
    3. Weeks 3 to 5: what we built
    4. Weeks 6 and 7: training on their own data
    5. The 90 days after go-live
    6. What a RevOps project like this costs
    7. What we do not promise
    8. Frequently asked questions
    from kickoff to go-live
    7 weeks
    fields per deal
    40+ → 12
    pipelines: New Business and Expansion
    2
    of adjusting after go-live
    90 days

    Client

    Growing B2B company (anonymous)

    Used

    Pipedrive, Make.com, CloudTalk, PandaDoc

    Challenge

    Leads came in through 6 entry points, 2 of them undocumented. Fewer than 30% of deals had all their information filled in. Nobody trusted the numbers.

    Approach

    First one workshop on what a lead and an opportunity are. Then the setup, the training and 90 days of adjusting.

    Where the company started

    The company had a Pipedrive account, but nobody steered on it. Customer data lived in 4 systems, and each system kept its own version of the customer. So the same question got a different answer depending on where you looked.

    Leads came in through 6 entry points. Two of those were not written down anywhere. On average a new lead waited more than 2 days for a first contact.

    A deal had more than 40 fields. Fewer than 30 percent of the deals had all their information filled in. So every report started with the question of whether the numbers were right. Nobody trusted them.

    • 4 systems with their own version of the customer.
    • 6 entry points for leads, 2 of them undocumented.
    • More than 2 days on average before a lead got a first contact.
    • More than 40 fields per deal, complete on fewer than 30 percent of the deals.

    Weeks 1 and 2: agreeing what a lead is

    We did not start in Pipedrive. We started with one workshop on definitions. Everyone in the room thought they meant the same thing by lead and opportunity, and they did not.

    A difference like that usually looks like this: marketing calls every form a lead, sales only after a first call. Then the same contact counts twice in one report and not at all in another. As long as that stays open, every dashboard you build afterwards shows a number that half the team disputes.

    At the end of week 2 there was a page of agreements: when something is a lead, when it becomes a deal, who owns it at each step and what the exit rule of every stage is. That page decided the setup, not the other way round.

    Weeks 3 to 5: what we built

    The setup took three weeks. We built two pipelines, New Business and Expansion, because a new customer and an existing customer who buys more go through different steps.

    We cut the fields from more than 40 to 12. We kept the fields that a decision depends on, such as deal value, source and next step. Everything else went, or moved to the organisation record where it belonged.

    Workflows now enforce follow-up. A new lead is assigned to an owner and gets a task straight away, so it no longer waits in an inbox. Every morning at 8:00 a scan looks for deals that sit in a stage twice as long as normal, and puts them in front of the owner.

    Around Pipedrive sit the other tools in this case. Make.com carries data between systems, CloudTalk handles calling and PandaDoc handles proposals. Every automation has error handling: a failure is logged and sends an alert, so nothing breaks quietly.

    Weeks 6 and 7: training on their own data

    We trained the team in three sessions of 2 hours. One for reps, one for managers and one for admins, because each group does something different in the CRM.

    We trained on the company's own deals, not on a demo account. A rep who sees their own pipeline in the new setup asks different questions than someone clicking through an example.

    From go-live there is a pipeline review of 30 minutes every Monday morning. That review is where the new agreements stick. If a deal has no next step, it comes up on Monday, and after a few weeks nobody wants that to happen.

    The 90 days after go-live

    After go-live came 90 days of adjusting with a weekly check-in. In the first month the team also had support for questions in between.

    The work in 90 days like these is usually small. A field that nobody fills after all. A stage where deals pile up because the exit rule is unclear. A report that managers read differently from what was meant. You only find those things once a team works in the system every day.

    What a RevOps project like this costs

    We do not publish what this client paid. What we can tell you is how the price is built. A RevOps implementation like this one, with definitions, setup, integrations and training, starts at €9,500. The larger RevOps tier starts at €19,500. A Pipedrive implementation on its own costs €2,950 to €13,500, depending on the number of users. Extra pipelines and data cleanup are separate items. The full list is on our pricing page.

    Adjusting after go-live runs on a retainer, priced in the quote. We bill per phase, always before that phase starts. So you know the price of the next step before you say yes to it.

    What we do not promise

    Changes in daily work show right away: follow-up is faster and manual work disappears. What it does to conversion and revenue you only measure after 2 to 3 months, and we do not predict that up front.

    This approach also does not fit everyone. With one salesperson and twenty deals a year, a workshop on definitions is overkill. And if nobody in the team has time for a Monday review, the setup slowly drifts back to how it was.

    Frequently asked questions

    How long did this RevOps project take?

    Seven weeks from kickoff to go-live. Weeks 1 and 2 went to definitions, weeks 3 to 5 to the setup and weeks 6 and 7 to training. After go-live came 90 days of adjusting with a weekly check-in. The work in 90 days like these is usually small, such as a field that nobody fills or a stage that needs a clearer exit rule.

    What does a project like this cost?

    We do not publish what this client paid. A RevOps implementation like this, with definitions, setup, integrations and training, starts at €9,500. The larger RevOps tier starts at €19,500. A Pipedrive implementation on its own costs €2,950 to €13,500, depending on the number of users. Ongoing adjusting after go-live runs on a retainer, priced in the quote. You get a fixed price per phase before the work starts.

    Why did you cut the fields from more than 40 to 12?

    Because fewer than 30 percent of the deals had all their information filled in. Forty fields that nobody fills give you no data, just empty columns. We kept the 12 fields that a decision depends on, such as deal value, source and next step. Everything else either went or moved to the organisation record.

    How did the team get used to the new setup?

    Three training sessions of two hours, one each for reps, managers and admins, on their own data. Each group does something different in the CRM, so each got its own session. Then came a fixed pipeline review of 30 minutes every Monday morning, where any deal without a next step comes up.

    Can this approach work if we do not use Pipedrive?

    The order works on any CRM: definitions first, then the setup, then training and a fixed review rhythm. The build in this case is Pipedrive, where we are a Platinum Partner. We also work in HubSpot, Zoho and Lumo. If you run something else, say so in the first call and we tell you straight whether we are the right fit.

    Partners in this case

    Click a badge to sign up with our partners:

    Sander Vergouwen

    About the author

    Sander Vergouwen

    Co-founder of Sales Surge

    LinkedIn

    See where your growth opportunities are.

    We set up your CRM and connect it to everything else. What does not exist yet, we build.