---
title: "Rhumbix saved $25K/month with Lindy — customer story"
description: "Rhumbix consolidated n8n, Make and Zapier into one assistant, onboarded its entire sales org in days, and documented $25K/month in savings."
url: "https://www.lindy.ai/case-study/rhumbix"
---

[![Rhumbix](https://www.lindy.ai/_sherpa/assets/generated/7f1d8147-rhumbix-logo.Bd6Do3Xh_dd7g2.webp)](https://www.rhumbix.com/)Customer story

# Rhumbix onboarded its entire sales team in days — and documented _$25K a month_ in savings.

A construction-tech GTM team had already tried n8n, Make and Zapier. The automations worked, until they didn't. What replaced all three took five minutes to set up.

[Try for free](https://chat.lindy.ai/signup)[Talk to sales](https://www.lindy.ai/contact-sales)

![Two teammates asking Lindy questions in a Slack channel; Lindy answers each with the source it used.](https://www.lindy.ai/_sherpa/assets/generated/be716af7-p-team-qa.BG95e0c7_zyEw9.webp)

**$25K/mo**Cost savings vs. manual workflows

**5min**Setup time per user, zero engineering

**80%**Of GTM work now handled by Lindy

Figures from a board-level ROI study conducted by Rhumbix after adoption.

## At a glance

One of construction tech's most AI-forward GTM teams — without the maintenance bill

#### Company

Rhumbix

#### Industry

Construction technology

#### Contact

David Gabriel  
VP of Marketing

#### Consolidated

_n8n_ _Make_ _Zapier_

#### Used for

_Lead generation_ _Lead outreach_ _Meeting prep_ _Email triage_ _Scheduling_ _Data automation_

## Before & after

Same team, same stack, two very different weeks

David had already automated his way into a second job: maintaining the automations.

* _✕_Fragile chains that broke when any upstream detail changed
* _✕_Constant maintenance, owned by one person
* _✕_Only the technically inclined could touch them
* _✕_Three separate tools to keep alive

That's why they chose Lindy.

##### The stack being maintained

n8n _needs upkeep_

Make _needs upkeep_

Zapier _needs upkeep_

Three tools, one person who could maintain them.

Zero configuration. The team connected calendars and inboxes and were running the same day.

* _✓_Five minutes to a working teammate, per person
* _✓_Nothing to maintain — no builder to open
* _✓_Whole sales org onboarded after one workshop
* _✓_Reps join with a simple OAuth connect

Live across the org in days.

##### The stack today

Lindy _nothing to maintain_

One assistant, and no builder for anyone to open.

## How it works

Four things Lindy does for Rhumbix every day — click through them

### Setup in minutes, not weeks

Unlike the workflow builders David had tried, Lindy required zero configuration. His team connected their calendars and inboxes and were running the same day.

"I don't know any AI agent that has taken me five minutes to build, even using Claude Code."

![Connecting a Slack account in Lindy, showing the actions it can then take.](https://www.lindy.ai/_sherpa/assets/generated/50cabad9-p-setup.BIkTcIag_ZBmVv0.webp)

Lindy product UI

### Prep that changes how reps show up

Before every call, Lindy surfaces who the team is meeting, what has been discussed before, and what is still open.

Five back-to-back meetings on a Friday. At 8AM Lindy flagged the conflict and offered to schedule a prep block before the first call — before David had thought to.

![Lindy's daily brief in a Slack DM, listing the day's meetings and who the user is meeting.](https://www.lindy.ai/_sherpa/assets/generated/08fa587b-p-brief.DRcLAkho_ZxQOBk.webp)

Lindy product UI

### Delegating from anywhere, over text

The texting integration changed everything. David now hands off work from the gym, between calls, or on the go.

After a podcast prep call he texted Lindy to generate a script from the recording. Lindy created the doc and sent it to the podcast team — all over text, nowhere near a desk.

![An iMessage thread with Lindy handling two delegated reminders.](https://www.lindy.ai/_sherpa/assets/generated/298bf9d4-p-imessage.DFJK2fmd_Z1TjYhX.webp)

Lindy product UI

### Plug-and-play for every rep

No technical onboarding. Reps connected their accounts through a simple OAuth flow and started using Lindy immediately — asking about upcoming deals, checking for missed emails, reviewing meeting notes.

"Having the assistant proactively reach out to take things off of your plate is just such a sigh of relief."

![A sales rep asks Lindy to run a deal handoff; Lindy updates HubSpot, creates the doc, briefs CS, and waits for approval before sending.](https://www.lindy.ai/_sherpa/assets/generated/7c5b6168-p-deal-handoff.BwuhW0Sx_hX3JC.webp)

Lindy product UI

> Deploying Lindy felt like flipping a switch. I don't know any AI agent that has taken me five minutes to build, even using Claude Code.[**David Gabriel**](https://www.linkedin.com/in/dave-gabriel/) VP of Marketing, Rhumbix, at the time of this project Now Principal, AECO Marketing Leadership & AI Innovation at Autodesk, following its acquisition of Rhumbix

## Results

What Rhumbix documented after adopting Lindy

* **$25K/mo**In cost savings against doing the same volume of work by hand.
* **5 minutes**Setup per user to a working teammate, with no engineering required.
* **Days**To onboard the full sales team, actively using Lindy after one internal workshop.
* **80%**Of go-to-market work now handled by Lindy, which became the operational backbone.
* **3 tools**Replaced — n8n, Make and Zapier consolidated into a single assistant.

The impact went past efficiency. With Lindy carrying the operational load, reps moved out of admin and context-gathering and into strategic and creative work. David described it as a levelling-up moment for the organisation.

## What it connects to

Rhumbix connected the tools it already used — nothing was replaced

![Gmail](https://www.lindy.ai/_sherpa/assets/generated/522fc229-i-gmail.CxgsKpdw_1xjk9K.webp)

![Slack](https://www.lindy.ai/_sherpa/assets/static/editorial/820f2316-i-slack.svg)

![iMessage](https://www.lindy.ai/_sherpa/assets/generated/a4c1b05d-i-imessage.B96k7PKJ_Z1tg6I0.webp)

![HubSpot](https://www.lindy.ai/_sherpa/assets/static/editorial/eee22134-i-hubspot.svg)

![Notion](https://www.lindy.ai/_sherpa/assets/static/editorial/a6dbc63f-i-notion.svg)

![Zoom](https://www.lindy.ai/_sherpa/assets/generated/1a3334e2-i-zoom.DwDtEB2W_2cHv1B.webp)

![Google Sheets](https://www.lindy.ai/_sherpa/assets/generated/45f53975-i-sheets.CeM0D3D2_Z17GS3V.webp)

## What's next

### Other departments have asked for the same model

The results were visible enough internally that teams beyond go-to-market have asked to adopt Lindy the same way. With the execution layer handled, David could point the team at higher-leverage work.

The bar he set at the start hasn't moved: anything the team adopts has to work on day one for people who will never open a builder.

## Put a teammate in your Slack.

Free to try. Running in about five minutes, like it was for David.

[Try for free](https://chat.lindy.ai/signup)[Talk to sales](https://www.lindy.ai/contact-sales)
