← COMPARECompare / Make

Waveloom vs Make

Make is a visual builder for scenarios you design. Waveloom is a background agent that watches your inbound and surfaces only what matters. Here is when you want which.

  • Gmail
  • Slack
  • Notion
  • Linear
  • HubSpot
  • Google Calendar
  • Web watches
Example_cardIllustrative
Needs youHubSpot · 09:12
Contact went quiet right after a pricing question
A HubSpot contact has gone quiet since asking about pricing
No reply in 9 days since pricing came up. A short follow-up is drafted. Nothing sent.
Review draftDismiss

Make is a visual automation platform. You lay out a scenario on a canvas: a trigger, a chain of steps, branches, error handlers. You can see the whole flow at once, and for multi-step logic that is a real advantage.

Waveloom has no canvas. It is a background agent for founders and operators. It reads Gmail, Slack, Notion, Linear, HubSpot and Google Calendar, follows web watches, and shows you a handful of cards a day. Each card has a one-line reason. When a reply is needed, there is an editable draft. Two background actions exist, reply by email and reply in Slack, and both wait for your approval.

What each is for

MakeWaveloom
What it is forDesigning and running multi-step scenariosDeciding what in your inbound matters
You buildScenarios on a visual canvasNothing. Connect sources, set watches
Human in the loopWhere you place oneAlways, for anything that sends
Best whenThe logic is known and branchingThe input is unpredictable

Where each is the right call

Where Make is the right call

You have a process with real structure. Order comes in, check inventory, branch by region, update two systems, notify someone if a step fails. Make lets you draw that and watch each run move through it. You can reason about a complex flow because you can see it.

Make does not decide whether a given email is worth your morning. It executes what the scenario says. That is what makes it dependable.

Where Waveloom is the right call

The hard part is not the steps. It is judgement. Most of what lands in your tools does not need you, and the few things that do are buried.

Waveloom processes items in small batches and scores every item for confidence. Low confidence is dropped. If unsure, nothing happens. A hard cap limits how many cards a batch can create and how many notifications go out per day, a topic that already has a card doesn't get a second one (new events join its thread), and quiet hours hold notifications. The feed is quiet most of the day and shows what it reviewed, so you know it looked.

A card that does appear explains itself. If a HubSpot contact goes quiet after a pricing question, the card says so and offers a draft. Nothing leaves without you.

There is also a morning brief, once a day. If the night was thin, it produces nothing rather than a card that says "nothing much".

Using both

Keep your scenarios. Make handles the processes you have designed. Waveloom handles the inbound you could not design for.

If you need a canvas or outreach, Make or another tool is the better fit. See use cases for examples, and the market research watch for web watches.

What_it_does
  • Reads your connected tools and web watches in the background
  • Scores every item and drops the low-confidence ones
  • Explains each card in one line and drafts the reply when one is needed
  • Sends an email or Slack reply only after you approve it
What_it_won't_do
  • Give you a canvas
  • Run outreach
  • Send on its own
  • Act as a chatbot
Founding_beta

Invite-only. Small cohort.
You talk to the founder.

Seats open in small batches as the system proves itself on real inboxes. Join the waitlist and you'll hear from me directly, not from a drip campaign.

Unsubscribe anytime