MANUAL // CHAOSstate = degraded
| t | event | lands_in | status |
|---|---|---|---|
| 09:12 | form_submit | INBOX | unread |
| 09:41 | form_submit | INBOX | unread |
| 11:03 | phone_note | STICKY | lost |
| 14:20 | form_submit | INBOX | 3d delay |
| 16:55 | referral | MEMORY | forgotten |
response_rate ≈ 40%avg_reply = 6h+
REV_02.4·DEPLOY_WINDOW = 48H·REGION = EU-CENTRAL·MODE = DONE_FOR_YOU
Every lead gets a fast,
tracked follow-up.
Lead capture and follow-up infrastructure for local service businesses. Capture the inquiry, alert the right person, keep follow-up visible—without replacing the tools your team already runs.
// you own every account · no lock-in · tool fees stay in your name
KDS Leads — a service of KDS Projects · engineered by Luca Knaak
// probe · response latencysend a test lead, watch it acknowledge
kds://probe/latencyMONITOR
avg_ack45ms
last_ack41ms
route→ owner.mobile
acceptance_tests10passed before handover
lead_owner1clear owner per inquiry
manual_steps0follow-up runs on autopilot
install_time48hfrom kickoff to live
§00.1 / live_runtime
This is the system actually running.
A live stream of the webhook, acknowledgement, and routing events that fire for every inbound lead—the same pipeline your business would run.
kds://runtime/lead-responseLIVE
09:12:00REQPOST /webhook/lead200 · payload 1.4kb
09:12:03FNfn.acknowledge → queuedq:1
09:12:06OKmail.send customer_replyok · 42ms
09:12:09FNalert.route → ownerchannel=ops
09:12:12OKdb.insert leadsid=8842 · ok
09:12:15INFOcron.followup schedule+24h
09:12:18
uptime 99.98%avg ack 41ms0 dropped
§01 / architecture
The manual chaos vs. the automated system.
Same inbound volume. Two very different outcomes. We automate the handoffs where leads are usually delayed, forgotten, or trapped in a single inbox.
AUTOMATED // SYSTEMstate = nominal
| t | event | pipeline | status |
|---|---|---|---|
| 09:12 | ingest | → ack → route | ok |
| 09:41 | ingest | → ack → route | ok |
| 11:03 | ingest | → ack → route | ok |
| 14:20 | ingest | → ack → route | ok |
| 16:55 | ingest | → ack → route | ok |
response_rate = 100%avg_reply < 60s
AINGEST
Lead arrives
Form, inbox, or agreed source fires the workflow trigger.
BACK
Reply dispatched
Fast, brand-approved acknowledgement. Expectations set.
CROUTE
Owner alerted
Right person receives the lead, context, and next action.
DPERSIST
Nothing dropped
Every inquiry logged. Follow-up reminder auto-created.
§02 / operating_constraints
Not another chatbot demo.
The goal is not to make your business look “AI-powered.” The goal is to give every real inquiry a clear owner, a timely answer, and a visible next step.
- 01
Human-approved language before any customer-facing message goes live.
- 02
Least-privilege access accounts and subscriptions kept in your name.
- 03
Failure alerts + manual fallback so silence is never the default state.
- 04
Test data first documented handover for GDPR-conscious operation.
§03 / deployment
One working lead-response system in 48 hours.
founding_package
€390one-time
Founding rate for the first three signed clients. External tool fees are not included.
MANIFEST // included8 items
- 01One lead source connected
- 02Instant acknowledgement workflow
- 03Internal alert and lead routing
- 04Shared lead tracker
- 05One follow-up reminder sequence
- 06Ten documented acceptance tests
- 07Plain-language handover guide
- 08Fourteen days post-launch support
§04 / next_step
Book a 15-minute fit check.
Choose a time directly. No presentation, no pressure.
// cal.eu loads only after you click the booking button
prefer email? info@lucaknaak.com
good_fit_if []
You receive at least a few online inquiries each week
You already use email, forms, or a lightweight CRM
You want reliable follow-up, not an experimental AI project