Skip to main content
RuyaTech

Lead-Gen Pipeline: $30K in New Contracts From Automated Triage

A B2B services firm was drowning in inbound leads — hours of daily triage, with good prospects going cold before anyone replied. We built an AI pipeline that ingests their lead feed every minute, filters the noise, scores real prospects with an LLM, and drops qualified leads into Slack with one-click proposal drafting. It cut business-development time to ~5 hours a week and drove $30K+ in new contracts in 30 days.

AI AutomationSales EnablementAI AutomationLead GenerationLLM PipelineSales Enablement
What We Did
AI Lead Scoring, Human-in-the-Loop Review, Proposal Drafting
Industry
B2B Services · Sales Enablement
Timeline
Live & Self-Calibrating · $30K+ in 30 Days
Overview

The Founder's Problem

A B2B services firm had the opposite of a lead problem — they had too many. A high-volume feed of inbound inquiries poured in daily, but the real prospects were buried under noise. Qualifying them by hand meant hours of triage every morning, and by the time someone reached a good lead it had often gone cold. They were losing winnable deals not because the work wasn't there, but because no human could read, score, and respond fast enough. They needed the triage to happen automatically — without handing a bot the keys to send things in their name.

Challenges

What We Built

01

Challenge 1

A funnel that kills the noise before it costs a cent — The pipeline polls the client's opportunity feed every minute. Deterministic YAML rules — industry blocklists, red-phrase filters, budget floors, spam heuristics — strip out roughly 88% of the volume for free, and a 75-pattern keyword gate keeps only leads that match the client's actual service lines. The expensive LLM only ever sees the survivors, and the client tunes every rule themselves with no code changes.

02

Challenge 2

LLM scoring with a guaranteed schema — Each surviving lead is scored 0–100 by Claude against a hand-tuned 440-line rubric, using forced tool-use so the output is always structured: match score, category, engagement size, and a short reason. The provider is pluggable (Anthropic / OpenAI / Groq), prompts are cached to cut cost, and a Sonnet-to-Haiku migration we validated against the client's real decisions cut LLM spend ~3× while actually improving accuracy.

03

Challenge 3

A human-in-the-loop Slack workflow — Nothing is ever sent automatically. Qualified leads post to Slack as cards — prospect spend, engagement history, budget — with three buttons: Generate Proposal, Skip, Mark Submitted. One click drafts a full proposal in the client's own voice from few-shot examples built on their past winning proposals, plus separate answers to any qualifying questions. The team edits in place and sends — sub-minute from opportunity to reviewable lead.

04

Challenge 4

A system that gets sharper with use — Weekly crons ask the team for outcomes (meeting, won, ghosted) and feed them back into calibration. Offline scripts re-score labeled leads against the live rubric and compare the model to the client's actual pursue/skip behavior — a revealed-preference check that once caught and reversed a backwards prospect signal. Self-healing OAuth, 48h dedup, idempotent clicks, and 24h raw-data purges keep it production-grade and safe under retries.

Final Results

The Results

Business-development effort dropped to about five hours a week — the team now reviews pre-scored cards and edits ready-made drafts instead of trawling the feed. In a single 30-day window the pipeline drove $30K+ in new contracts: 292 proposals sent, 82 opened, 22 discovery calls, 4 new clients, including two contracts over $15K each. More than one in four opened proposals turned into a discovery call — because the voice and project references are the client's own, a drafted proposal performs like a hand-written one. And because outcome tracking recalibrates the rubric against deals that actually close, the system keeps getting sharper the longer it runs.

Lead-Gen Pipeline: $30K in New Contracts From Automated Triage — screenshot 1 showing ai automation product interface
Analysis

Why This Project Matters

This is what a real AI agent looks like in production — not a demo that breaks on the second prompt. The hard part wasn't calling an LLM; it was everything around it: a deterministic funnel so the model only scores what's worth scoring, forced-schema output so downstream code can trust it, a human in the loop so nothing embarrassing gets sent, and a feedback loop so the scoring tracks reality instead of drifting. We treated the client's pipeline like our own revenue — measured, calibrated, and engineered to recover deals, not just process data.

The LLM Only Sees What's Worth Scoring

See Technical Details

It's easy to throw every lead at a model and burn money. We did the opposite: deterministic YAML filters and a 75-pattern keyword gate remove ~88% of the volume before any LLM call, so Claude only scores genuine prospects. Forced tool-use guarantees a structured score every time, prompts are cached, and we migrated Sonnet to Haiku after validating it scored better on the client's real data — cutting LLM cost roughly 3× while still covering every surviving lead.

A Feedback Loop That Keeps the Scoring Honest

Most scoring systems drift the moment they ship. This one is audited: a 900-line prompt changelog records every rubric change as observation → change → verification, and offline calibration re-scores labeled leads against the client's actual pursue/skip decisions. That revealed-preference check caught a backwards prospect signal and reversed it. Weekly outcome tracking feeds real won/lost results back in, so the rubric tracks the deals that actually close — not a static guess.

Let's Talk

Ready to Build, Rescue, or Scale Your Product?

Tell us about your project. If it's a good fit, we'll schedule a strategy session.

Let's Talk

We respond within 4 hours during business hours. No obligation.

FAQs

Questions About Our Work

Common questions from founders exploring our portfolio and considering working with our team.

Yes — we'll walk you through relevant projects with detailed technical breakdowns and real results. Reach out and we'll share case studies specific to your industry and challenge.

Very likely. We've built AI automation systems, SaaS platforms, mobile apps, and web applications. During a consultation, we'll show you comparable work and explain how our team would approach your specific needs.

Our go-to stack includes Next.js/React for frontend, Node.js for backend, AWS/Firebase for infrastructure, and PostgreSQL/MongoDB for databases. For AI, we use OpenAI, AWS Bedrock, and custom models. We adapt based on your requirements and long-term goals.

We define success metrics upfront with each client — user growth, performance benchmarks, cost reduction, or revenue increase. The results in our case studies (like 600 paying members in 6 months for Bake Genie) are real, verified metrics.

Absolutely. Every project you see started as an idea. We'll analyze your requirements, share relevant experience, and give you honest business advice on the fastest path to launch. Reach out to get started.