Fixed quote after a free call

CRM automation for SaaS companies that sell to businesses

Sign-ups and demo requests land in the CRM as an email address and not much else, and product usage sits in a separate tool. We build a workflow that enriches each new lead from approved sources, matches it to existing accounts, routes it to the right owner by territory or segment, and writes product usage milestones from your analytics into the CRM so reps see which trials are active. A typical build costs $1,000 to $2,500 per workflow and takes about four weeks.

The problem

Why SaaS CRMs fill up with half-finished leads

In a B2B SaaS company the CRM is supposed to be the single view of every account, but the data that matters arrives from everywhere: website forms, free trial sign-ups, the in-app chat, a partner referral, a webinar list. Each lands half-filled, and reps spend the first ten minutes of every lead on research that a workflow could do in seconds.

Product-led motions add a second gap. The signal that a trial is serious, such as several teammates invited or an integration connected, lives in Mixpanel, Segment or your own database. If it never reaches the CRM, sales calls the loudest form fills instead of the accounts actually using the product.

What we build

What our CRM automation for SaaS includes

Lead enrichment on arrival

Company, size band, country and industry added from the sources you approve, with anything uncertain labelled rather than guessed.

Duplicate and account matching

New contacts matched to existing companies by domain, so a second sign-up from a current customer goes to the account owner, not a new SDR.

Routing rules you can read

Territory, segment and round-robin assignment written as plain rules, with an owner and a first task created in the CRM.

Product usage signals

Milestones such as workspace created, teammates invited or integration connected written to the CRM record from your analytics or database.

Follow-up sequences with stop rules

Short, approved emails that stop when the lead replies, books a call or unsubscribes, sent from your own domain.

Pipeline and source reporting

A weekly view of leads, meetings and opportunities by source and segment, built on the CRM fields the workflow keeps tidy.

Who does what

Automation does the chasing, people make the calls.

Every step is marked: what runs on its own, what a member of staff reviews and what stays with a person who decides.
  1. 01 Automated

    Lead or sign-up arrives

    A form, trial sign-up or chat creates or updates a contact through the CRM API.

  2. 02 Automated

    Enrich and match

    Approved sources add company context and the contact is matched to an existing account where one exists.

  3. 03 Automated

    Route and task

    Rules assign an owner and create a first task; product milestones update the record as they happen.

  4. 04 Team review

    Rep reviews

    The rep checks the summary, adjusts anything labelled uncertain and starts the conversation.

  5. 05 Account owner or team lead decides

    Commercial calls

    Qualification, pricing and whether to pursue the account are decided by the account executive or sales lead.

How it behaves

How the SaaS CRM workflow behaves

What each person sees and what runs in the background, including what happens when something goes wrong.

What the prospect sees

  • A prompt, relevant reply after a demo request or sign-up
  • A call from one rep, not three
  • A short follow-up sequence that stops when they reply or unsubscribe

What sales and RevOps see

  • Leads arriving with company context and an owner
  • Product milestones on the account record
  • A weekly pipeline view by source and segment

What the automation does

  • Enriches, matches and de-duplicates each lead
  • Applies routing rules and creates tasks
  • Syncs usage milestones and honours opt-outs across sequences

Edge cases and fallbacks

Sign-up from a free email domain
No company is guessed; the lead is routed to the self-serve queue and labelled.
Existing customer signs up again
Matched by domain and sent to the account owner as an expansion signal, not a new lead.
Enrichment source returns conflicting data
Both values are kept and flagged for the rep instead of overwriting.
Contact unsubscribes mid-sequence
All sequences stop and the opt-out is recorded on the CRM record.
CRM API limit or outage
Events are queued and retried in order, and RevOps gets an alert.

Architecture

A SaaS CRM pipeline with usage signals at a glance.

The setup we usually start from. We adapt it to the phone system and practice software you already use.
Forms and demos Website, webinars Trial sign-ups App database Usage events Mixpanel, Segment n8n workflow Enrich and dedupe CRM HubSpot, Salesforce Account owner Tasks and calls Follow-ups Email with stops Weekly report By source, segment
  • Input
  • Logic and services
  • Data
  • People
  • Output

How it flows

  1. 1 Form fills, demo requests, trial sign-ups and product usage events reach one n8n workflow.
  2. 2 Each lead is enriched from approved sources, matched to an existing account and checked for duplicates.
  3. 3 The CRM assigns an owner and a task, and approved follow-ups start with clear stop rules.
  4. 4 A weekly report shows leads, meetings and pipeline by source and segment.

Project planner

How the project runs, phase by phase.

Typical durations for a first version. Your proposal lists the exact phases, dates and what you sign off at each step.

CRM automation for SaaS: lead enrichment, routing and PLG signals project plan

Typical time to launch: about 4 weeks, then support

  1. 01

    Discovery

    2 to 3 days

    Lead sources, current CRM fields, routing rules, enrichment sources you are allowed to use and the usage milestones that matter.

  2. 02

    Design

    2 to 3 days

    Field mapping, matching and duplicate rules, routing table, sequence wording and opt-out handling.

  3. 03

    Build

    1 to 2 weeks

    Source connections, enrichment, matching, routing, usage sync and the weekly report.

  4. 04

    Shadow run

    About 1 week

    The workflow proposes owners and enrichment while reps keep routing by hand, and we compare.

  5. 05

    Launch

    1 to 2 days

    Switch on routing, walk sales and RevOps through the rules and the report.

  6. 06

    Support

    Ongoing

    New sources, territory changes and field updates as the go-to-market changes.

What it runs on

Real products only, connected through the access each vendor provides. See all integrations

n8n HubSpot CRM API or Salesforce REST API Attio or Pipedrive API Mixpanel or Segment for usage events Your email provider with SPF, DKIM and DMARC Claude or OpenAI for lead summaries

Cost estimate

What it costs, line by line.

Estimates to plan with. Your fixed quote follows a free call, once we have seen your systems and volumes.
  • Discovery and design

    Sources, field mapping, routing table and usage milestones.

    $250 – $450

  • Build

    Enrichment, matching, routing, sequences and error handling.

    $450 – $1,200

  • Integrations

    CRM, forms, product analytics and email provider.

    $150 – $450

  • Testing and shadow run

    QA and a side-by-side run against manual routing.

    $100 – $250

  • Launch and training

    Switch-on, RevOps handover and run book.

    $50 – $150

  • Total project estimate

    $1,000 – $2,500

Optional monthly care after launch is quoted with your proposal. Fixed quote after a free call. CRM seats, enrichment data and n8n are billed to you directly. A two-way product usage sync for a large event volume may need a second workflow.

Monthly running costs you pay directly

Estimates from the vendors' published pricing, checked November 2026. Billed to you by each vendor, never marked up.

  • CRM subscription: Your CRM vendor's own plan (HubSpot, Salesforce, Attio, Pipedrive or the one you use).
  • n8n: Self-hosted Community edition on your own server, or n8n Cloud from about €20 a month (Starter, billed annually) or €50 (Pro).
  • AI model usage: Billed by the provider per use; short lead summaries usually cost little at typical B2B lead volumes.

What pushes cost up

  • Systems without an API, or with integration access that must be requested from the vendor
  • Writing data back into your core system rather than only reading from it
  • Several locations, brands or very different processes to support
  • Custom apps, dashboards or a voice line on top of the workflows

What keeps cost down

  • One location and one clear process to start with
  • Cloud software with a documented API
  • Using tools you already pay for instead of adding new ones
  • Approved wording and sample data ready at the start
Get a fixed quote

Privacy and consent

Rules we design for, with the sources.

General information to plan with, not legal advice. Your counsel or data protection adviser confirms what applies to your practice.

US: CAN-SPAM covers B2B email

The FTC guide says CAN-SPAM makes no exception for business-to-business email, opt-outs must be honoured within 10 business days and each violating email can cost up to $53,088.

Source: www.ftc.gov

Gmail bulk sender rules

Senders of 5,000 or more messages a day to Gmail need SPF, DKIM and DMARC, one-click unsubscribe for marketing mail and a spam rate kept below 0.30%.

Source: support.google.com

UK: PECR marketing rules

Regulation 22 of PECR sets the consent and soft opt-in rules for marketing by electronic mail to individual subscribers, with a simple way to refuse in every message.

Source: www.legislation.gov.uk

How we deliver

Agile delivery, in 1 to 2 week sprints.

We deliver in short Agile sprints using Scrum, so you see working software every one or two weeks instead of waiting for a big reveal at the end.

Every sprint

  1. 1 Sprint planning. At the start of each sprint we agree which backlog items we will finish, each with written acceptance criteria you can check.
  2. 2 Daily stand-up. A short internal check-in on progress and blockers. You get a written update in your Slack or Teams channel, not another meeting.
  3. 3 Sprint review and demo. At the end of each sprint we demo what was built on test data or in a shadow run, and you accept it or ask for changes.
  4. 4 Retrospective. The team looks at what went well and what to change in the next sprint, and we share anything that affects you.

How scope stays under control

Product backlog
Every feature, fix and question in one prioritised list you can see at any time.
Acceptance criteria
Plain-language conditions for "done" on each item, agreed before work starts.
Change requests
New ideas go into the backlog with an estimate. Nothing changes scope or price without your written approval.
User acceptance testing (UAT)
Before launch your team tests the real workflow against the acceptance criteria and signs off.

Tools we use

Jira, ClickUp or Trello for the backlogSlack or Microsoft Teams for updatesGitHub for code and version historyLoom or a live call for demos

Project manager / Scrum master

Runs the sprints, keeps the backlog and timeline honest, and is your single point of contact.

Business analyst

Maps how the work runs today, writes the workflow specification and acceptance criteria with your team.

Automation engineer

Builds the n8n workflows, integrations, AI steps and error handling.

Backend developer

Writes custom code where a no-code step is not enough: APIs, data sync, secure storage.

Frontend / mobile developer

Builds forms, booking pages, dashboards, web apps or Android apps when the project needs them.

QA engineer

Tests every workflow against the acceptance criteria, including edge cases and failure paths.

DevOps engineer

Sets up hosting, access, backups, monitoring and alerts, and the deployment pipeline.

Who does what at each phase

Free call
Project manager, business analyst
Understand the problem, check it is worth automating and outline a rough range.
Discovery
Business analyst, automation engineer
Map the current process, systems and data, and agree success measures.
Design
Business analyst, automation engineer, backend developer
Write the workflow specification, data flows, compliance notes and backlog with acceptance criteria.
Sprints
Automation engineer, developers, QA
Build, test and demo in 1 to 2 week sprints; you accept or adjust after each demo.
UAT and launch
QA, DevOps, project manager
Your team tests and signs off, we switch on, monitor closely and train the team.
Support
Automation engineer, DevOps
Stabilisation window, then optional monthly care with monitoring and changes.

A point of contact

One person who can answer questions and approve decisions, with about an hour a week during the project.

Access

Admin or API access to the systems involved, created as separate accounts with the least access needed.

Sample data

Real but non-sensitive records (or de-identified ones) so we can design and test against reality.

Approved wording

Message templates, policies and consent wording (for SMS, your opt-in and opt-out text) reviewed by you.

Vendor agreements

Signed agreements with the software vendors that will handle personal data, such as a BAA or processor contract.

Time for testing

A few hours from the people who will use the system, for the demos and user acceptance testing.

Working system

Workflows, integrations and any apps running in your accounts, under your keys.

Documentation

Workflow specification, data-flow map, run book and exported workflow files.

Training

A walkthrough for the team and a short recorded video for new starters.

Handover

All access, credentials and code handed over; you can keep us or take it in-house.

Stabilisation window

Fixes for anything that does not meet the agreed acceptance criteria after launch.

Support options after launch

  • No plan

    You run it yourselves after the stabilisation window and contact us when you need a change.

  • Monthly care

    Monitoring, error alerts, small changes and updates each month, with an agreed response time.

  • Priority care

    Faster response times for business-critical workflows and a monthly review call.

How a project moves through our team

Free call PM and analyst Discovery Process and data Design Spec and backlog Sprints Build, test, demo Your review Accept or adjust UAT and launch Sign-off, go live Support Monitor and improve
  • Input
  • Logic and services
  • People
  • Output
  • Data

How it flows

  1. 1 A free call with the project manager and business analyst to understand the problem and whether it is worth building.
  2. 2 Discovery and design produce a written specification, data-flow map and a backlog with acceptance criteria.
  3. 3 The team builds in 1 to 2 week sprints; you review a demo at the end of each and accept or adjust.
  4. 4 Your team runs user acceptance testing, we launch, then monitor and improve under a support plan.

FAQ

CRM automation for SaaS: lead enrichment, routing and PLG signals questions, answered.

The one your team will keep clean. HubSpot suits many SaaS startups because marketing and sales share one record and the API is well documented; Salesforce suits larger sales teams with complex territories; Attio and Pipedrive are lighter options. We automate whichever you choose and can help you decide.

Yes. We send a short list of meaningful milestones, such as teammates invited or an integration connected, from Mixpanel, Segment or your own database to the CRM record, rather than every event. Reps see the signal without drowning in data.

From sources you approve and are licensed to use: your own sign-up data, the company website, public registries and any enrichment provider you already pay for. Anything the workflow cannot confirm is labelled uncertain for the rep to check.

It is lead handling rather than lead buying. We make sure every lead that already reached you is enriched, routed and followed up consistently. We do not scrape contact lists or send cold email on your behalf.

Usually. We map your custom objects and fields during discovery and write to them through the API. If a field needs to change, we agree it with RevOps before the build starts.

Time from sign-up to first owner touch, share of leads enriched without manual research, duplicates caught, meetings booked by source and how many active trials received a sales conversation.

Free 20-minute call

Want this for your software & saa?

Book a free 20-minute call. We will look at how the work runs today, tell you honestly whether it is worth building and give you a fixed quote if it is.

Book a free 20-minute call