Communities:
Build in Public
| # | Tweet | Community | Topic | Views ▼ | Ratio | Engagement | Posted |
|---|---|---|---|---|---|---|---|
| 1 | [video] Every automation expert has shipped a workflow, then found out it broke when the client did.
APIs time out. Credentials expire. A node gets a value it wasn't built for. The question was never "will it fail," it's "how fast do I find out."
So I built a self-fixing system for | Build in Public | — | 39.5K | 8.4x | 234 | Jun 1 |
| 2 | [image] I built an AI system that runs an entire outbound sales desk on its own.
A business wanted one thing that could handle the whole top of funnel: call the lead, reach the right person, qualify them, and book the meeting, then fall back to email for anyone who didn't pick up.
The | Build in Public | — | 11.0K | 1.9x | 227 | Aug 10 |
| 3 | [image] Just wrapped up a project that turned a 571,000-customer spreadsheet into something that actually works.
The client runs a subscription box business.
Their problem? Every time someone cancelled or paused their subscription, someone on the team had to check when to remove them | Build in Public | — | 3.6K | 1.1x | 147 | Mar 30 |
| 4 | [image] Mistakes are sometimes hard to avoid in tech. You build enough systems and one of them will go wrong.
Some years back, one of mine cost a client 95% of his investors.
An automation I built started sending multiple emails to his investor list. Not one email. Several. And these | Build in Public | — | 3.0K | 0.5x | 141 | Aug 18 |