Internal platforms

How to Build an Automated Sales Pipeline for Your Agency

An automated sales pipeline has two parts: an internal platform that holds your leads and meetings, and automations that keep it up to date. Build a contacts database and a meetings database, add pages and buttons on top, then use Make.com to create records when a call is booked, prompt the closer after the call, send follow ups and start onboarding when a lead is closed.

Ask your AI about this guideChatGPTClaudePerplexityMarkdown
Key takeaways
  • Start with two databases: contacts (your leads) and meetings (your sales calls), linked to each other.
  • Use the email address as the unique field so automations can find a lead later.
  • Record buttons for Follow up, Closed and Lost turn stage changes into one click actions that can also trigger automations.
  • Four automations cover the pipeline: log a booked call, prompt the closer after the call, send a follow up email, and start onboarding on close.
  • The structure matters more than the tools, so the same build works with other platforms and automation software.

What does an automated sales pipeline need?

A pipeline that depends on people typing updates into a CRM will go out of date. Once the data is stale, nobody trusts it and nobody uses it. The fix is to build the system in two layers.

The first layer is an internal platform that acts as your CRM. It stores leads, shows every sales call and gives your team pages to work from. The second layer is a set of automations that feed that platform and react to what happens in it.

We built this example on Noloco for the platform and Make.com for the automations. The tools are only an example. If you use Airtable, Google Sheets, Zapier or another app builder, the same structure applies.

How do you set up the databases?

Everything sits on top of the database, so build it first. You need two tables that link to each other, because each contact can have meetings.

  • Contacts: client stage (lead, active client or lost client), sales stage, company name, name, email, phone number, estimated value, lead score, qualified, no show, assigned project, assigned meetings, follow up date and notes.
  • Meetings: date, meeting name, meeting type (such as sales call or team meeting), duration, assigned employees, assigned contact, notes and meeting link.
  • Make the email field unique and use it as the primary field. Names and companies can repeat, but an email address identifies one lead.
  • Use single option selects for stages. The sales stages in this build are lead, booked call, follow up, closed and lost. Rename or add stages to match your own process, such as a second call booked or a proposal stage.
  • Use a slider for lead score (we used 1 to 5 as an example) and yes or no fields for qualified and no show.
  • Link the tables with linked record fields: assigned project and assigned meetings on contacts, assigned contact on meetings.

How do you build the CRM pages?

With the data in place, build two sections in the platform: a sales breakdown and a meeting overview.

The leads page is the main working view. Show it as a board grouped by sales stage, and filter it so it only shows contacts in the sales cycle. Hide the fields you do not need on each card, make the name a heading and only show estimated value when it is not empty. Closed and lost can be hidden from the board because the overview page covers them.

  • Sales breakdown page: charts for the active pipeline value (leads that are not closed or lost), the lead count, a funnel by stage and a line chart of sales calls per month, plus lists of closed leads and lost leads.
  • Individual lead page: sales stage, estimated value, created date, company name, qualified status shown green or red, lead notes with inline editing, assigned meetings and assigned project (each shown only when they exist), and an edit tab.
  • Meetings pages: sales calls as cards sorted by newest, filters for employee and date, and a Join now button in place of a raw link.
  • Follow up Central: a calendar of leads that are not closed or lost, are in the follow up stage and have a follow up date. Phone and email fields open the phone app or email client in one tap.
  • Meeting breakdown: an upcoming meetings calendar and a past meetings grid, with filters for type, employee and contact.

How do record buttons speed up the pipeline?

Record buttons let a closer move a lead without editing fields. We added three. Closed is green and moves the lead to the closed stage. Lost is red and moves it to lost. Follow up is orange and asks for a follow up date.

Use a modal button for anything with side effects. It asks for confirmation first, so nobody starts an onboarding sequence by accident. Use a one click button for simple changes. Each button runs an action such as updating the record, and later it can also run a workflow or send data to Make.com.

How do you build the four automations?

Each automation covers one gap in the pipeline. Together they keep the platform current and push your team to act.

  1. Log booked calls: in Make.com, trigger from Calendly when an invite is created. Add a router with a filter so only sales call events pass. Create a lead record, then a meeting record linked to that contact. Send a confirmation email through Gmail and a Slack message to the closers with a link to the lead page.
  2. Prompt the closer after the call: set a Calendly workflow to email the host when an event ends, with the lead email and event name in the body and a unique subject line. In a second Make.com scenario, watch Gmail for that subject, parse the email and event name with a text parser, search Noloco by the email field, then send a Slack message asking the closer to update the lead card.
  3. Follow up in one click: edit the Follow up button so it sets the follow up date and also moves the lead to the follow up stage. Add a Noloco workflow that emails the lead and sends a push notification to the person who pressed the button.
  4. Start onboarding on close: edit the Closed button so a Noloco workflow creates a project record from the lead (company name as the project name, status set to onboarding, start date as today, linked to the contact). Then call a Make.com webhook so your usual onboarding steps can run from there.

Which settings are easy to get wrong?

In the first automation, name your sales call event clearly in your booking software. The router filter checks the event name, so a unique name stops team calls and client calls from creating leads.

Make.com checks for new emails on a schedule, not instantly. We used a 30 minute interval. The maximum results setting limits how many emails it processes per check, so raise it if you take many calls.

When you link a lead in a Slack message, the lead page link is the same for every record apart from its unique ID, so insert that ID from the record you just created or found. Use the text content of the email in the parser, not the HTML content.

Use plain Slack text to start. Slack blocks let you add buttons and better formatting later.

How can you extend the system?

Once the base works, these additions make it stronger:

  • A Slack app so closers can press Follow up inside the message.
  • A recording automation that adds the recording link to the meeting record when a call ends, using a tool like Zoom or Fireflies.
  • An end of day summary so closers report and the CRM stays current.
  • A call claiming system so closers can take calls when the assigned person cannot make it.
  • Sales KPI tracking from the qualified and no show fields, such as qualify rate and close rate, in a sheet or Looker Studio.

Questions people ask

Do I need Noloco and Make.com to build this?

No. The video above uses them as examples, and the structure is what matters. Any app builder with a database, such as Airtable or Google Sheets, and any automation tool, such as Zapier, can follow the same design.

What fields should a sales CRM database have?

For contacts: client stage, sales stage, company name, name, email, phone number, estimated value, lead score, qualified, no show, follow up date and notes. For meetings: date, name, type, duration, assigned employees, assigned contact, notes and link. Make email the unique field.

How does the CRM stay up to date without manual entry?

A Make.com automation triggers when a call is booked in Calendly. It creates the lead and the meeting in the database. After the call, a second automation reminds the closer to update the lead, with a direct link to the right record.

How do you move a closed lead into onboarding?

Add a Closed button to the lead. When pressed, it updates the stage, creates a project linked to the contact and sends the lead data to a Make.com webhook. From there you run your own onboarding steps.

Rather have it built for you?

Fluxomate builds internal tools and AI agents for agencies. On your stack, owned by you.

See if you qualify