Case studies · three anonymized builds

What a fixed-scope build
actually moves.

Three anonymized before/after workflow stories from the segments Routelet works in: lead follow-up for a solo service business, CRM hygiene for a small property team, and review replies for a home-service operator. Every metric is the actual KPI we shipped the build to move.

Three anonymized before/after stories

One workflow per segment. One metric per build.

Each story is the segment we work in, the business we worked with (anonymized), the metric the build was scoped to move, and the two-line takeaway that came out of the post-launch review.

Solo dental practice · service
A one-chair dental office running on three missed-call-a-day vibes and a paper schedule. The owner spent mornings typing the same replies into Instagram DMs, the website form, and a Google Sheet.
Before

6+ hrs / week lost to manual replies

and a steady drip of leads who never heard back

After

~2-minute response on every inbound

Stack · n8n + Claude (drafted replies, owner-approved)

Takeaway
  • Speed-to-lead did the selling — the practice stopped losing consults the same week.
  • The owner kept final-say, so the system earned trust instead of asking for it upfront.
3-agent indie real-estate team · property
A small independent real-estate team sharing one shared CRM that had drifted badly — 200+ dead leads, duplicate rows on every agent, and a "stale follow-up" queue nobody owned.
Before

200+ stale leads + duplicate rows

and a team that had stopped trusting the CRM

After

a clean database, weekly automated prune flagging stale follow-ups

Stack · n8n + Make.com (ingest, dedupe, weekly prune)

Takeaway
  • The win was the workflow, not the tool — a once-a-week prune the team actually opens.
  • Trust in the CRM came back faster than expected, because the data finally matched the deal sheet.
Home-service operator · trade
A local HVAC-and-plumbing operator buried in two-week-old Google review replies. The team could write the replies fine — they just never wrote them, and the rating was drifting down because of it.
Before

2-week reply lag · 3.5★ average

and a queue of un-answered reviews piling up

After

same-day replies · 4.7★ average

Stack · n8n + ChatGPT (drafted replies, owner-approved)

Takeaway
  • A monotone average can move in a quarter when the queue is the bottleneck, not the words.
  • Owner-approved drafts kept the tone on-brand without forcing the operator into the loop.
Your workflow could be next

See what we could build for you — book a free audit.

One 30-minute screen-share, a two-page memo on where the leaks are, and a fixed-scope quote sized to the tier your scope matches. Reply within one business day — or pick a slot directly and skip the wait.

Book a free auditSend your scope instead

Fixed scope, signed in writing. One operator, one n8n runtime, one weekly Loom.

Three segments, one process. The free audit is the actual deliverable — the tier your scope matches just tells us what to put in the contract. Prefer email? touchflow@polsia.app

— Routelet · TouchFlow