Services for software and SaaS companies

SaaS automation for the work around the product: pipeline, onboarding, support and renewals

Make It Flow builds automated business solutions for B2B software and SaaS teams: a CRM that knows which trials are worth a call, onboarding that starts the moment a deal closes, support tickets triaged before anyone opens them, renewal and churn signals surfaced while there is still time, security questionnaires drafted from your approved answers, an AI support agent and the browser extension your customers keep asking for. Your people keep every decision about customers, pricing and the roadmap.

Your stack stays the system of record

Accounts live in HubSpot, Salesforce or Attio, tickets in Zendesk or Intercom, subscriptions in Stripe or Chargebee. We connect them through their documented APIs and webhooks instead of adding another database to keep in sync.

People own customers, prices and the roadmap

Automation enriches, routes, drafts and reminds. Account executives, CSMs, support engineers and product managers approve what reaches a customer and decide anything commercial or technical.

Built to pass your own customers' security review

You are usually a processor for your customers, so we map every vendor that touches their data, keep sub-processors listed and design for GDPR Article 28 contracts, CAN-SPAM and the EU AI Act from the start.

Services

SaaS automation, from first sign-up to renewal.

Each one is a focused project with a fixed quote, a written plan and a handover you own.
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 sta... How we built it

Case Study

Case Study: SaaS CRM, Onboarding & Support Automation

Read the full case study

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.

Leads and trials Forms, sign-ups Product usage Analytics events Tickets Help desk Billing Subscriptions n8n Four workflows AI steps Summaries, triage CRM Accounts and tasks Issue tracker Linked bugs Sales, CS, support Review and act Security lead Questionnaires Weekly reports Pipeline, health
  • Input
  • Logic and services
  • AI step
  • Data
  • People
  • Output

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.

Platform integrations

The software you already use, connected.

Practice systems, CRMs, phones, payments and reviews, connected through documented APIs, webhooks, n8n and custom code.
All integrations

HubSpot

CRM

Contacts, companies, deals, tasks and usage properties.

HubSpot CRM REST API and webhooks.

Salesforce

CRM

Leads, accounts, opportunities and custom objects.

Salesforce REST API, with access set up by your admin.

Attio

CRM

Records, lists and notes for lighter CRM setups.

Attio REST API.

Pipedrive

CRM

Persons, organisations, deals and activities.

Pipedrive API.

Zendesk

Help desk

Ticket tags, groups, internal notes and triggers for triage.

Zendesk Ticketing API and webhooks.

Intercom

Help desk and messaging

Conversations, tickets and hand-offs from an AI agent.

Intercom REST API and webhooks.

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.

Tech we work with

Any language, any stack.

Make It Flow delivers automated business solutions: workflows, integrations, AI assistants and the apps around them. Our team works in whatever language and stack fits the job and the systems you already run.

Automation

n8nWebhooksREST and GraphQL APIsScheduled jobs and queues

Backend

PythonPHP and LaravelNode.js and TypeScriptJava

Data

SQL (MySQL, PostgreSQL)Google Sheets and AirtableData sync and ETLReporting dashboards

Frontend and mobile

JavaScript and TypeScriptTailwind CSSJava and Kotlin for AndroidBrowser extensions

AI

Claude, Gemini and OpenAI modelsRetrieval on your own documentsModel Context Protocol (MCP)Evaluation sets

Cloud and DevOps

DockerLinux serversGitHub ActionsMonitoring and backups

FAQ

SaaS automation answered.

SaaS automation connects the systems a software company runs on, such as the CRM, help desk, billing, product analytics and issue tracker, so routine handoffs happen by themselves: leads get enriched and routed, onboarding starts on closed-won, tickets get triaged, renewals get flagged early. People still own every conversation and commercial decision.

Fixed quotes start at $1,000 to $2,500 per workflow and $2,500 to $7,500 for an AI agent such as a support agent or security questionnaire assistant. A browser extension or custom integration starts from $6,000. Vendor subscriptions and AI usage are billed to you directly by each provider.

CRMs such as HubSpot, Salesforce, Pipedrive and Attio; help desks such as Zendesk, Intercom and Freshdesk; Jira, Linear and GitHub for engineering; Stripe and Chargebee for billing; Mixpanel and Customer.io for product and lifecycle data; and Slack for alerts. We confirm the route for your stack before quoting.

Not if they already do the job. We often configure around them and build what they do not cover: the link between support, CRM, billing and engineering, and the reporting across all of it.

Yes. We work remotely with software teams worldwide and design for CAN-SPAM in the US, GDPR and the EU AI Act in the EU, and UK GDPR and PECR in the UK. Our engineers work in every common language and stack.

A single workflow usually goes live in three to five weeks. A connected set of workflows is delivered in one-week Scrum sprints, one workflow at a time, in about nine weeks.

Free 20-minute call

Show us where context gets lost between your teams

Book a free 20-minute call. We look at your CRM, help desk, billing and product data, point out the handoffs worth automating and send a fixed quote for the ones that pay back.

Book a free 20-minute call