Case Study
Case Study: SaaS CRM, Onboarding & Support Automation
We built a connected set of automations for a B2B SaaS company: lead enrichment and routing in the CRM with product usage signals, onboarding that starts on closed-won, AI ticket triage linked to the issue tracker, renewal and failed-payment signals, and a security questionnaire assistant. Sales, customer success, support and security now share the same context about each account instead of rebuilding it at every handoff.
- Company type
- B2B SaaS with a free trial and annual contracts
- Team involved
- RevOps, account executives, customer success, support engineers, security lead
- Systems connected
- CRM, product analytics, help desk, issue tracker, billing, Slack, n8n
- Delivery
- Scrum, 1-week sprints, about 9 weeks to full launch
The challenge
Where the practice started
Trial sign-ups and demo requests reached the CRM with an email address and little else. Reps researched each lead by hand, existing customers were sometimes routed as new leads and product usage never reached the CRM.
Handovers from sales to customer success were free-text notes. Onboarding plans were rebuilt in spreadsheets, and stalled accounts were noticed at renewal time.
Support triaged every ticket by hand with inconsistent tags, and duplicate bug reports meant customers were not told when their issue was fixed.
Renewal lists were pulled weeks before the date, failed payments were followed up inconsistently, and every enterprise deal waited on the security lead to rewrite questionnaire answers.
Goals
What the project had to change
- Every lead arrives enriched, matched and routed, with usage signals visible to sales.
- Every new customer gets an approved handover and a plan within a day of closing.
- Tickets are tagged and routed on arrival, and confirmed bugs are linked to one issue.
- Renewals and risk are visible a quarter ahead, and failed payments get a consistent follow-up.
- Security questionnaires are drafted from approved answers and reviewed, not rewritten.
What we built
What we built, as one connected system.
CRM enrichment and routing
We connected forms, trial sign-ups and usage events to the CRM through n8n, with enrichment from approved sources, domain matching, readable routing rules and a weekly pipeline report.
Service detailsClosed-won onboarding
Closed-won now produces a handover summary for the CSM to approve, an onboarding plan from the right template, milestone tracking from product analytics and stall alerts in Slack.
Service detailsTicket triage and bug loop
New tickets are tagged, prioritised and routed with a drafted reply as an internal note. Confirmed bugs are matched to open issues, and attached customers get an update when the fix ships.
Service detailsRenewal and payment signals
A renewal calendar from billing, a health view on agreed signals, renewal briefs for account owners and failed-payment follow-up timed around the billing retries.
Service detailsSecurity questionnaire assistant
An approved answer library, questionnaire import, cited drafts, a review screen for the security lead and export in the original format.
Service detailsArchitecture
How the SaaS workflows connect
- Input
- Logic and services
- AI step
- Data
- People
- Output
How it flows
- 1 Leads, usage events, tickets and billing events feed one n8n instance.
- 2 Workflows update the CRM and issue tracker, and AI steps draft summaries, triage tickets and questionnaire answers.
- 3 Sales, customer success and support act on prepared context; the security lead reviews every questionnaire answer.
- 4 Weekly reports show pipeline, onboarding progress, queue health and renewal risk.
How it behaves
How the system behaves day to day
What customers see
- Faster, relevant replies to demo requests
- A kickoff from a CSM who knows what was promised
- Support replies from the right specialist and a note when their bug is fixed
- A friendly message with a secure link when a payment fails
What the team sees
- Enriched, routed leads with usage signals
- Approved handovers and stall alerts
- Pre-triaged tickets with drafts
- Renewal briefs and cited questionnaire drafts
What the automation does
- Enriches, routes, triages and drafts on every event
- Applies opt-outs and stop rules across email
- Logs every step and alerts RevOps when a run fails
Edge cases and fallbacks
- An existing customer signs up for a new trial
- Routed to the account owner as an expansion signal.
- A ticket reports an outage
- Set to urgent and posted to the on-call channel with no draft.
- A questionnaire asks about a control the company lacks
- Marked as a gap for the security lead, never answered by the assistant.
- A card fails with a hard decline
- The follow-up asks for a new payment method instead of promising a retry.
- n8n or an API is unavailable
- Events are queued and replayed, and RevOps gets an alert.
Integrations
What we connected
HubSpot
CRMContacts, companies, deals, tasks and usage properties.
HubSpot CRM REST API and webhooks.
Zendesk
Help deskTicket tags, groups, internal notes and triggers for triage.
Zendesk Ticketing API and webhooks.
Jira
Issue trackingBug matching, issue links and resolution events.
Jira Cloud platform REST API.
Stripe
BillingSubscriptions, invoices, failed payments and retries.
Stripe API and Billing webhooks.
Mixpanel
Product analyticsUsage milestones for CRM, onboarding and health signals.
Mixpanel APIs.
Slack
Team alertsStall alerts, escalations, review requests and failure alerts.
Slack API and incoming webhooks.
n8n
Automation platformRuns the workflows, self-hosted or on n8n Cloud.
Your own n8n instance; we hand over every workflow.
How we delivered it
Week by week, one workflow at a time.
Delivery timeline
Typical time to launch: about 9 weeks, then support
-
01
Discovery
Week 1
We interviewed RevOps, CS, support and security, mapped every handoff, sampled tickets and questionnaires, and agreed data flows and sub-processors.
-
02
Design and access
Week 2
Routing rules, onboarding templates, ticket taxonomy, health signals and the answer library structure; API access and sandbox accounts.
-
03
Sprint 1: CRM routing
Week 3
Built enrichment, matching and routing; shadow-ran against manual routing; demo and sign-off.
-
04
Sprint 2: onboarding
Week 4
Routing went live. Built closed-won handover, plan creation and milestone tracking.
-
05
Sprint 3: ticket triage
Week 5
Onboarding went live. Built triage with suggestions as hidden notes while agents worked as usual.
-
06
Sprint 4: bug loop and renewals
Week 6
Triage routing went live for high-agreement groups. Built the bug loop, renewal calendar and payment follow-up.
-
07
Sprint 5: answer library
Week 7
Renewal briefs went to CS leadership for tuning. Cleaned and approved the questionnaire answer library.
-
08
Sprint 6: questionnaire assistant
Week 8
Built parsing, cited drafts, review and export; replayed past questionnaires.
-
09
UAT and handover
Week 9
Each team ran acceptance tests, we switched everything on, handed over run books and trained the team.
-
10
Support
Ongoing
Weekly check-ins during stabilisation, then monthly care.
Who does what
What the team does, and what automation does.
Automation does
- Enriches, matches and routes every lead
- Drafts handover summaries and creates onboarding plans
- Tags, prioritises and routes tickets with drafted replies
- Builds renewal calendars and health views
- Follows up failed payments around billing retries
- Drafts cited questionnaire answers
The team does
- Reps check enrichment and start conversations
- CSMs approve handovers and act on stall alerts
- Agents edit and send every reply and confirm bug links
- Account owners review renewal briefs
Account owner or team lead decides
- Decides pricing, discounts and contract terms
- Sets bug severity and engineering priority
- Approves every security statement before it leaves
- Decides which signals and thresholds define risk
Compliance handled
Privacy, consent and safety, built in.
Processor and sub-processor duties
Every vendor touching customer data was added to the sub-processor list with an Article 28 GDPR contract before go-live.
Source: gdpr-info.euB2B email rules
Sequences and payment emails honour opt-outs well inside the 10-business-day CAN-SPAM limit, which applies to business email too.
Source: www.ftc.govSender authentication
Lifecycle and sales email runs from domains with SPF, DKIM and DMARC and one-click unsubscribe on marketing mail.
Source: support.google.comAI disclosure
No customer-facing reply is sent without an agent; if that changes, Article 50 EU AI Act disclosure is added.
Source: artificialintelligenceact.euRenewal notices
Renewal and cancellation messages follow state auto-renewal laws, since the FTC click-to-cancel rule was vacated in July 2025.
Source: www.fenwick.comNo invented security claims
The questionnaire assistant drafts only from approved sources and the security lead approves every answer.
Outcomes
What changed for the practice
- Leads now reach the right owner with company context and usage signals instead of a bare email address.
- Every new customer gets an approved handover and an onboarding plan without anyone rebuilding it by hand.
- Tickets arrive tagged and routed, tags are consistent enough to report on, and customers hear back when their bug is fixed.
- Renewals and risky accounts are visible a quarter ahead, and failed payments get a consistent, polite follow-up.
- The security lead reviews drafted questionnaire answers instead of rewriting them for every deal.
What we track
The measures the practice watches.
Lead response
Time from sign-up or demo request to first owner touch.
Onboarding speed
Time from closed-won to kickoff and to each first-value milestone.
Triage quality
Share of tickets reaching the right group first time and agent edits per draft.
Renewal coverage
Renewals with a reviewed brief before the notice date.
Payment recovery
Failed payments recovered after follow-up.
Questionnaire turnaround
Days from questionnaire received to returned, and share of drafts accepted.
Cost estimate
What a project like this costs
-
Discovery and design
Handoff mapping, data flows, taxonomy and backlog for all five builds.
$1,000 – $2,200
-
CRM routing module
Enrichment, matching, routing and usage sync.
$700 – $1,700
-
Onboarding module
Handover summary, plan creation and stall alerts.
$700 – $1,700
-
Triage and bug loop module
Classification, drafts and issue linking.
$800 – $2,000
-
Renewal and payment module
Calendar, health view, briefs and payment follow-up.
$700 – $1,700
-
Questionnaire assistant
Answer library, cited drafts, review and export.
$1,900 – $5,600
-
Integrations
CRM, analytics, help desk, issue tracker, billing and Slack.
$300 – $1,100
-
Testing, UAT and launch
Shadow runs, acceptance tests, launch and training.
$400 – $1,500
-
Total project estimate
$6,500 – $17,500
Optional monthly care after launch is quoted with your proposal. Typical range for this scope: four workflows at our per-workflow range plus one AI assistant. Every company gets its own fixed quote after a free call.
Monthly running costs you pay directly
Estimates from the vendors' published pricing, checked November 2026. Billed to you by each vendor, never marked up.
- n8n: Self-hosted Community edition on your server, or n8n Cloud from about €20 a month (Starter) or €50 (Pro), billed annually.
- AI model usage: Billed by the provider per use; scales with ticket and questionnaire volume.
- Vendor plans: CRM, help desk, billing and analytics on their own plans.
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
How we deliver
Agile delivery, in 1 to 2 week sprints.
Every sprint
- 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 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 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 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
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
- Input
- Logic and services
- People
- Output
- Data
How it flows
- 1 A free call with the project manager and business analyst to understand the problem and whether it is worth building.
- 2 Discovery and design produce a written specification, data-flow map and a backlog with acceptance criteria.
- 3 The team builds in 1 to 2 week sprints; you review a demo at the end of each and accept or adjust.
- 4 Your team runs user acceptance testing, we launch, then monitor and improve under a support plan.
Tools we built
Free tools we built and use every day.
The Make It Flow platform
Website audits, monitoring and reports
- Website Security Scan FreeSSL, security headers, cookies and exposed file checks
- Email Deliverability Check FreeMX, SPF, DKIM, DMARC, MTA-STS and BIMI with ready DNS fixes
- Website Monitoring Scheduled re-scans, score emails and 5-minute uptime alerts
- Website Audit API Queue scans and read results via REST API with signed webhooks
- AI Search Readiness FreeCheck access for Google AI, Copilot, ChatGPT and Perplexity bots
Free website tools for practices
Services in this case study
CRM automation for SaaS: lead enrichment, routing and PLG signals
Enrich every trial and demo request, catch duplicates, route accounts to the right rep and push product usage signals into HubSpot, Salesforce or Attio so sales calls the right accounts first.
From $1,000 · About 4 weeks Details
SaaS customer onboarding automation
Start onboarding the moment a deal closes: a handover summary from the sales record, a kickoff plan for the CSM, milestone tracking and nudges when an account stalls before first value.
From $1,000 · About 4 weeks Details
AI ticket triage & bug loop for support teams
Tag, prioritise and route every support ticket on arrival, draft replies from your help center for agents to edit, and link confirmed bugs to Jira or Linear so customers hear back when they are fixed.
From $1,000 · About 4 weeks Details
Churn signals, renewals & failed-payment recovery
Surface renewal dates and churn signals months ahead, give account owners a one-page brief per account, and follow up failed subscription payments politely alongside Stripe or Chargebee retries.
From $1,000 · About 4 to 5 weeks Details
Security questionnaire assistant
Draft answers to vendor security questionnaires, CAIQ and custom spreadsheets from your approved answer library and policies, so the security lead reviews instead of rewriting the same answers every deal.
From $2,500 · About 5 to 7 weeks Details
Account owner or team lead decides
-
SaaS SEO Checklist: 12 Fixes for Software Company WebsitesSEO · 10 min read
-
Support Ticket Triage and Release Notes: A Workflow for Software CompaniesAutomation · 10 min read
-
User Onboarding and Offboarding Workflow for MSPs and IT TeamsAutomation · 9 min read
-
What Are AI Agents? A Plain-English Guide for Small BusinessesAutomation · 10 min read
-
LLM Evaluation Workflow: Tracking Regressions on Every ChangeAutomation · 8 min read
-
Gmail, Yahoo and Microsoft Bulk Sender Requirements (2026)Email Deliverability · 7 min read
-
UK Subscription Rules From January 2027: Draft Regulations ExplainedSEO News · 6 min read
-
What Is llms.txt and Do I Need One for My Website?Guides · 7 min read
Free 20-minute call
Want this built 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.
Sources we checked
Rules and product facts on this page come from these pages, checked in November 2026. This is general information, not legal advice; confirm the rules that apply to your practice with your own adviser.
- FTC: CAN-SPAM Act compliance guide for business
- Gmail: Email sender guidelines
- UK PECR regulation 22
- GDPR Article 28 (processor)
- EU AI Act, Article 50
- Fenwick: Eighth Circuit vacates FTC click-to-cancel rule
- Stripe: Automate payment retries (Smart Retries)
- Stripe: Using webhooks with subscriptions
- Cloud Security Alliance: CCM and CAIQ v4
- Chrome: What is Manifest V3
- Chrome Web Store: Limited Use policy
- Chrome Web Store: Register your developer account
- HubSpot API reference
- Salesforce REST API developer guide
- Attio REST API overview
- Pipedrive API reference
- Zendesk API reference
- Intercom developer docs
- Freshdesk API
- Jira Cloud platform REST API
- Linear developers
- GitHub REST API
- Chargebee API
- Mixpanel API overview
- Customer.io APIs
- Vanta developer hub
- Slack developer docs
- n8n self-hosting
- n8n pricing
- Google autocomplete phrasing checked for keywords (crm for saas companies, saas customer onboarding, ai ticket triage, security questionnaire automation, saas churn, chrome extension development)