What we build in Slack
The best notification and approval surface most businesses already own. Also the easiest place to build something everyone mutes within a fortnight, which defeats the purpose entirely.
Slack is the best notification and approval surface most businesses already own. The engineering is trivial; the design is not. We build in it when a person needs to act or know now: approvals with interactive buttons writing the decision back to the source system, failure alerts with enough context to act on, time-sensitive handoffs, and daily digests instead of per-event noise.
We do not use it for anything that needs to be found again later. On the free plan message history is limited, so Slack is unsuitable as an audit trail: it is the interface, never the record. Apps and incoming webhooks cost nothing on top of the per-user subscription you already pay.
What it is, and where it sits
Slack is where your team already is, which makes it the natural place for an automation to reach a person. We use it for three things: telling someone something happened, asking someone to approve something, and alerting when something broke.
The engineering here is trivial. The design is not: the difference between a useful Slack integration and an ignored one is entirely about volume and relevance.
What we build in it
- Approval flows with interactive buttons (approve, reject, request changes) writing the decision back to the source system
- Failure alerting from every workflow, with enough context to act on
- New lead and deal notifications routed to the owner, not broadcast to everyone
- Digest summaries replacing per-event noise
- Slash commands for lookups against your systems without leaving Slack
- Escalation when something has waited too long
How it is priced
| Model | What you pay for | Best when |
|---|---|---|
| Per user | Slack itself, which you already pay for per user. | Already settled. An automation adds nothing to it. |
| Apps and incoming webhooks | Nothing extra. | Every integration we build in it. |
| Free plan | Nothing, at the cost of limited message history. | Never, if a decision needs to be evidenced later. Write it back to the source system instead. |
Slack is the interface, never the record.
When to choose it, and when to think twice
Slack is the right surface when a person needs to act or know now. It is the wrong surface for anything that needs to be found again later.
One channel for failures that need a human, one for approvals, and a daily digest for everything informational. Three channels, all of which stay worth reading.
We hold no reseller agreement with this vendor, take no affiliate commission, and do not resell licenses. You buy your own subscription directly. It is the only arrangement under which our recommendation means anything.
Want the cost model run on your numbers?
Tell us your workflows and volumes and we will show you the three-year cost across every option.
You will talk to Fayez or Kareem. Nobody else.