02/05Case

AutoClose: lead capture through to close, in one platform

Not an automation layered over an existing CRM: one platform covering the whole path from capture to conversion, built on the principle that teams do not adopt a system that takes the wheel away from them.

PRODUCTIZED BUILD · MANUAL OVERRIDE ON EVERY WORKFLOW

Sector
Sales operations
Stack
n8n · SMS · email · voice · calendar · custom dashboard
Surface
One console, capture to close
Form
Productized engagement

The problem: leads going cold in the gap between tools

Lead management scattered across disconnected tools and running on manual habit. Leads arrive through several channels and get worked in whatever order someone happens to open them. Follow-up depends on a person remembering. Scheduling is a separate back and forth. The record of what was actually said to a lead lives in inboxes and phones.

The result is familiar: good leads go cold while someone works a worse one, and nobody can reconstruct why.

The approach

Leads are captured across multiple channels and scored by an AI model that predicts which ones to prioritize, with scoring accuracy reported at 97 percent. Follow-up fires automatically across SMS, email and calls, personalized per lead, booking links included. Scheduling runs on an integrated calendar with real-time availability, so the appointment is booked inside the same flow rather than negotiated separately. A communications hub logs every interaction automatically. Quotes and reporting live in the same system.

Accuracy figure as reported by the build's own evaluation

The design principle that matters: automation with the manual override kept intact. Every workflow runs on its own by default, and a human can step in and take control of any one of them at any point.

The system

AUTOCLOSE / CONSOLE / DASHBOARD DEMO DATA
AutoClose dashboard: pipeline, follow-up queue and appointments in one screen
FIG. 01 The whole system at a glance: pipeline, follow-ups, appointments. Figures shown are seeded demo content.
AUTOCLOSE / CONSOLE / LEAD LIST DEMO DATA
Lead list with an AI score column per lead
FIG. 02 The AI score is a column on every lead, so prioritization is visible instead of asserted. Emails, phones and addresses are redacted; the scores are seeded demo content.
AUTOCLOSE / CONSOLE / COMMUNICATIONS HUB DEMO DATA
Communications hub logging every interaction with a lead across channels
FIG. 03 Every touch logged automatically, which is what makes the pipeline auditable instead of anecdotal.
AUTOCLOSE / CONSOLE / REPORTS DEMO DATA
Reports view with response rates by channel
FIG. 04 Response rates by channel. The interface computes it; nobody assembles it. Figures are seeded demo content.

How it fails safely

FailureWhat happens instead
Automation misfires on an edge caseA human takes manual control of that workflow without switching the rest of the system off.
Follow-up depends on memoryIt does not. Sequences fire on schedule, and every touch is logged with the lead.
Nobody can reconstruct a dealThe communications hub holds the full interaction history per lead, automatically.

Result

  • One platform replacing a scattered set of tools across capture, scoring, follow-up, scheduling, quoting and reporting.
  • Rep attention routed by a visible AI score instead of inbox order.
  • Follow-up no longer depends on anyone remembering, and every touch is logged automatically.
  • Full interaction history per lead, which makes the pipeline auditable instead of anecdotal.

Built by Hisham Hanawi. This is an internal tools and dashboards build.

Leads going cold in a tool gap?

100% JOB SUCCESS · TOP RATED PLUS · 583 HOURS / 6 ENGAGEMENTS

Source: Upwork profile, verified 2026-08