Weran — a tick and a cross sharing one stroke WERAN
Use case 01 · Lead response

A lead arrives at 11 pm. Your system replies in 40 seconds.

A message lands in your form, Instagram DM or WhatsApp. It is qualified against your criteria, routed to the right person, acknowledged instantly — and nothing waits for morning. Fixed scope, two weeks, and a demo of the system running on your real channels before the final invoice.

What you get

One pipeline, five moving parts. Each is visible and testable on its own.

  • Capture from every source — website form, Instagram, WhatsApp, email. One inbox, nothing scattered.
  • Qualification in your words — AI reads the message against your criteria: budget, service, location, urgency. Not a generic chatbot.
  • Routing — hot lead to the right person's phone with context attached; the rest to a daily list. No one triages an inbox by hand.
  • Instant acknowledgement — the lead gets a real reply in under a minute: we got your message, here's what happens next. Written in your tone, approved by you in advance.
  • The daily picture — every lead, its status, its response time. You see the funnel you currently guess at.

The numbers

Price
$1,500–2,500 fixed
Timeline
2 weeks to live
Stack
n8n + Claude + your CRM
What moves the price
Sources connected, CRM complexity, languages

The audit maps where your leads currently leak — free, 30 minutes, and the map is yours to keep whatever you decide after it.

Questions people ask

If yours isn't here, ask it on the audit call.

Does the AI talk to my customers?

It acknowledges and qualifies — two moves with clear boundaries. It confirms the message arrived, asks up to two clarifying questions, and books nothing, promises nothing, quotes nothing. A human closes every lead.

What if it misjudges a lead?

Every qualification carries the message, the reasoning and a confidence level. Low confidence or anything unusual goes to a human with the full context — you read one line and decide. And for the first month you see every decision it makes, so trust is earned, not assumed.

Do I need to change my CRM?

No. The system sits on top of what you use — HubSpot, Pipedrive, a Google Sheet, anything with an API or an inbox. If your CRM is a spreadsheet, we start there and it works.

Who owns it when you're done?

You do — accounts, code, credentials, documentation, everything. Handover includes 30 days of support. After that an optional retainer keeps it tuned; without it, it keeps running.

What does it actually run on?

n8n for the flows, Claude for reading and drafting, your existing accounts for channels. The same architecture we run in production on our own systems — 150,000+ messages a month across 30+ sources.

← All use cases