22 hours back in seven days
A B2B firm was doing its intake work by hand. Staff saved each website form, read it, checked the sender on LinkedIn, sent it to the right rep, and wrote a reply. The work took over 20 hours a week. An agency built a flow in n8n with the Claude API. Each new form starts the flow. Claude scores the lead from 1 to 10 on size, budget, and pain. High scores go to a Slack channel with a short summary and into the CRM. Low scores go to a nurture sequence.
Start with one job only. Fill in the three lines. Keep the bot on that job.
The one job this bot does: ______________________________
What it may do on its own: ______________________________
What it must ask me first: ______________________________
Two lines from this case, side by side. No new figures.
A B2B firm was doing its intake work by hand. Staff saved each website form, read it, checked the sender on LinkedIn, sent it to the right rep, and wrote a reply. The work took over 20 hours a week. An agency built a flow in n8n with the Claude API. Each new form starts the flow. Claude scores the lead from 1 to 10 on size, budget, and pain. High scores go to a Slack channel with a short summary and into the CRM. Low scores go to a nurture sequence.
In the first seven days the team got about 22 hours a week back. Reply time fell from an average of 4 hours to under 45 seconds. CRM entries came out the same each time, with no typing errors, per the agency.
The after line is the source's claim, not our measurement.
smalloffice.space · Get a case like this in your inbox each morning. Subscribe free
Read this case on your phone now, and keep it for later. Type your email. We send this case to that address, and you get the next cases each morning too.