The latest articles on DEV Community by Miki Lallouz (@miki_lallouz_5e7d8f534658). https://dev.to/miki_lallouz_5e7d8f534658 https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F1814752%2Fdbd9a1e4-ade7-4456-8f11-7b12d51e1a9f.png https://dev.to/miki_lallouz_5e7d8f534658 en Miki Lallouz Sun, 26 Jul 2026 02:08:26 +0000 https://dev.to/miki_lallouz_5e7d8f534658/speed-to-lead-is-an-engineering-problem-winning-the-job-in-under-2-seconds-4gl4 https://dev.to/miki_lallouz_5e7d8f534658/speed-to-lead-is-an-engineering-problem-winning-the-job-in-under-2-seconds-4gl4 <p><em>Disclosure: I run Auto-Respond, an AI lead-response tool for home-service businesses. This post is about the problem, not a pitch. The product link sits at the bottom.</em></p> <p>Most "lead management" advice treats speed as a nice-to-have. For local service businesses it is close to the whole game, and it turns out to be an interesting systems problem.</p> <h2> The number that matters </h2> <p>Dr. James Oldroyd's lead-response research at MIT found that waiting even 5 to 30 minutes to respond makes you roughly 100x less likely to ever reach a lead. Harvard Business Review's audit of thousands of US companies found the median first-response time was measured in hours, and a large share never responded at all. The business that answers first usually books the job.</p> <p>So the target is not "respond quickly." The target is: first meaningful reply in under 2 seconds, 24/7, with no human in the loop for the first touch.</p> <h2> Why it is harder than a webhook plus an autoresponder </h2> <p>A canned "Thanks, we'll be in touch" hits the 2-second bar and loses the job anyway, because the lead moves on to whoever actually answered their question. A real first reply has to:</p> <ul> <li> <strong>Normalize very different inputs.</strong> A Yelp "Request a Quote", a Thumbtack lead, a Facebook Messenger message, a Facebook Lead Ad, an Instagram DM, and a Google Local Services Ads lead all arrive in different shapes, over different APIs, with different rate limits and reply windows.</li> <li> <strong>Understand intent, not just keywords.</strong> Job type, location, and urgency decide whether this is a booking or a tire-kicker.</li> <li> <strong>Ask the right next question</strong> and keep the thread going until the lead books or opts out.</li> <li> <strong>Recover missed phone calls.</strong> A contractor on a roof cannot pick up. A missed call should trigger an instant AI voice callback so the lead is still answered.</li> <li> <strong>Follow up on a schedule</strong> (day 1, 3, 7) and stop automatically the moment the customer replies, so you are persistent without being spam.</li> <li> <strong>Hand off cleanly</strong> to a human and the CRM once the lead is qualified.</li> </ul> <p>Each of those is a small thing. Doing all of them within a couple of seconds, across six channels, reliably, is the actual product.</p> <h2> Lessons from building this </h2> <p>A few things that were not obvious going in:</p> <ol> <li> <strong>The latency budget is spent before you write a word.</strong> Channel webhook, intent parse, reply generation, channel send. If the customer should see a reply in under 2 seconds, each hop gets a tiny slice, so you design for the slow channel, not the fast one.</li> <li> <strong>Idempotency matters more than you expect.</strong> Lead platforms retry webhooks. Answer the same lead twice and you look broken.</li> <li> <strong>"Stop" logic is a feature.</strong> Persistent follow-up only works if it reliably detects a reply or booking and then goes quiet. Getting that wrong is worse than not following up at all.</li> <li> <strong>Voice is a different failure surface.</strong> Text you can queue. A missed-call callback has to happen now or it is pointless.</li> </ol> <h2> If you just want it to work </h2> <p>If you run a home-service business and do not want to build any of this, that is what Auto-Respond does: it answers Yelp (including Request a Quote), Thumbtack, Facebook Messenger, Facebook Lead Ads, Instagram, and Google Local Services Ads leads in under 2 seconds, qualifies the job, books it, follows up on day 1, 3 and 7, calls back missed calls, and syncs to your CRM. Setup takes a couple of minutes.</p> <p>Vendor-neutral buyer's guide to picking an AI answering service: <strong><a href="https://auto-respond.com/blog/best-ai-answering-service/" rel="noopener noreferrer">Best AI Answering Service in 2026 - How to Choose</a></strong></p> <p>Happy to answer questions about the speed-to-lead side in the comments.</p> automation ai startup saas