Fixed quote after a free call

MSP CRM automation for your managed services pipeline

Managed services deals start as a contact form, a referral from an existing client, a security assessment request or a call about a failing server, and they often sit in someone's inbox. We connect every source to one pipeline in HubSpot, the opportunities module of your PSA or the CRM you already run, automate follow-ups and proposal reminders, and hand signed clients into the PSA with the right company, contacts and agreement. A typical build costs $1,000 to $2,500 per workflow and takes about four weeks.

The problem

Why MSPs lose managed services deals between call and proposal

Most IT support companies sell through relationships: a referral, an accountant who recommends you, a prospect who downloaded a security checklist. Those leads arrive by email, phone and web form, and the owner or a single account manager keeps them in their head.

Proposals go out and then go quiet. Nobody knows which assessment requests turned into agreements, which marketing source brings clients who sign, or how long a deal waits between the discovery call and the proposal.

When a deal closes, someone retypes the company, contacts, sites and agreement into the PSA. Mistakes there flow straight into billing and ticket routing.

What we build

What our MSP CRM automation includes

One pipeline for every source

Website forms, assessment requests, referral emails, calls and event lists flow into one CRM pipeline, de-duplicated by domain.

Managed-services stages

New lead, discovery booked, assessment, proposal sent, negotiation, signed and onboarding, matched to how your team actually sells.

Proposal follow-ups

Reminders for the account manager and polite check-ins for the prospect after a proposal goes out, with stop rules once they reply.

Company enrichment

Domain, size, Microsoft 365 or Google Workspace usage from public DNS and the prospect's own answers, added to the record for the discovery call.

PSA hand-off

Signed deals create or update the company, contacts and site in the PSA through its API, so the onboarding project starts with clean data.

Pipeline reporting

A weekly email with new leads, proposals out, deals signed and monthly recurring value by source.

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 arrives

    A form, referral email, call note or assessment request creates or updates a company and contact in the CRM.

  2. 02 Automated

    First reply

    The prospect gets an approved acknowledgement and a link to book a discovery call.

  3. 03 Automated

    Stage moves

    Booked calls, sent proposals and signed agreements move the deal automatically where the tools allow.

  4. 04 Technician review

    Account manager follows up

    The account manager runs discovery, writes the proposal and records the outcome.

  5. 05 Engineer or vCIO decides

    Pricing and scope

    Agreement scope, pricing and contract terms are set by the owner or vCIO, never by the CRM.

How it behaves

How the MSP sales pipeline behaves

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

What the prospect sees

  • A quick acknowledgement and booking link after they get in touch
  • A discovery call with the account manager
  • One or two polite check-ins after the proposal, stopping when they reply

What the team sees

  • One pipeline board with every deal and its stage
  • Follow-up tasks with due dates
  • A weekly report by source and monthly recurring value

What the automation does

  • Captures and de-duplicates leads by company domain
  • Moves stages when calls are booked and proposals are sent
  • Creates the company in the PSA when the deal is signed

Edge cases and fallbacks

Two people from one company enquire
Matched by domain into one company with two contacts.
An existing client fills in the contact form
Flagged to the account manager instead of opening a new deal.
Personal email address only
Kept as a contact and flagged for a person to qualify.
CRM or PSA API unavailable
Leads are queued and retried, and the owner gets an alert.

Architecture

An MSP sales pipeline at a glance.

The setup we usually start from. We adapt it to the phone system and practice software you already use.
Web forms Contact, assessment Referrals Email and calls n8n Capture and dedupe CRM pipeline HubSpot or PSA Follow-ups Email reminders Account manager Discovery, proposal PSA company Created on signing
  • Input
  • Logic and services
  • Data
  • Output
  • People

How it flows

  1. 1 Leads arrive from web forms, assessment requests, referral emails and call notes.
  2. 2 n8n captures each one, matches it by company domain and creates or updates the deal in the CRM.
  3. 3 Approved follow-ups go to the prospect and tasks go to the account manager, who runs discovery and the proposal.
  4. 4 When the agreement is signed, the company, contacts and site are created in the PSA for onboarding.

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.

MSP CRM & managed-services sales pipeline project plan

Typical time to launch: about 4 weeks, then support

  1. 01

    Discovery

    2 to 3 days

    Lead sources, current tracking, sales stages, CRM choice and what the PSA needs at signing.

  2. 02

    Design

    2 to 3 days

    Stage definitions, follow-up rules, field mapping to the PSA, consent and duplicate rules.

  3. 03

    Build

    1 to 2 weeks

    Source connections, pipeline automation, follow-ups, PSA hand-off and the weekly report.

  4. 04

    Shadow run

    About 1 week

    Leads flow into the CRM while the team keeps its old habits, and we compare.

  5. 05

    Launch

    1 to 2 days

    Switch over and walk the owner and account managers through the board.

  6. 06

    Support

    Ongoing

    New sources, stage changes and reporting tweaks.

What it runs on

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

n8n HubSpot CRM API (deals and pipelines) ConnectWise PSA, Autotask or HaloPSA REST API Website forms and calendar booking Gmail or Microsoft 365 via Microsoft Graph Slack or Microsoft Teams for alerts

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, stages, PSA field mapping and reporting.

    $200 – $400

  • Build

    Capture, de-duplication, pipeline automation and follow-ups.

    $500 – $1,300

  • Integrations

    CRM, PSA, forms, email and calendar.

    $150 – $400

  • Testing and shadow run

    QA and a side-by-side run with your current tracking.

    $100 – $250

  • Launch and training

    Switch-over and account manager walkthrough.

    $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, PSA and n8n subscriptions are billed to you directly. A two-way CRM and PSA sync 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 or PSA: Your vendor's own plan (HubSpot, or the opportunities module of your PSA).
  • n8n: Free self-hosted Community edition, or n8n Cloud from about €20 a month (Starter) or €50 (Pro), billed annually.

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: commercial email rules

Sales follow-up emails must not use misleading headers or subject lines, must include a postal address and must honor opt-out requests within 10 business days under the CAN-SPAM Act.

Source: www.ftc.gov

UK: business-to-business marketing

PECR regulation 22 restricts unsolicited marketing email to individual subscribers; we keep consent and opt-out flags on every contact so sole traders and partnerships are handled correctly.

Source: www.legislation.gov.uk

EU and UK: processors under contract

Your CRM and automation host process prospect data on your behalf, so GDPR Article 28 requires a written processor contract with each of them.

Source: gdpr-info.eu

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

MSP CRM & managed-services sales pipeline questions, answered.

It depends on how you sell. Many MSPs use the opportunities module in ConnectWise PSA, Autotask or HaloPSA so sales and service share one database; others prefer HubSpot for marketing and forms. We help you decide and can automate either, including a sync between them.

Yes, through the PSA's REST API: ConnectWise PSA, Autotask and HaloPSA all expose companies, contacts and sites. We map the fields with you and keep a person in the loop for the agreement itself.

Yes. Off-the-shelf connectors exist, but stage models and agreement values do not always map cleanly between the two, so we design which system owns which field before syncing anything.

Partly. Follow-ups and source reporting are marketing automation, but the main goal is that every lead gets a fast reply and an owner. Marketing emails respect opt-outs and the rules where the prospect is based.

It can add simple signals your team agrees on, such as company size, current email platform or whether they asked for a security assessment. The account manager decides who to call first.

Leads by source, time to first reply, discovery calls booked, proposals sent, deals signed and monthly recurring value by source. We set the pipeline up to report these from day one.

Free 20-minute call

Want this for your it support & msp?

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