The problem
Inbound requests land in a shared inbox where they age. Which ones were answered, which became clients, which evaporated — nobody knows without scrolling.
Premium · à la carte
Leads
Inbound submissions, triaged into real work.
Form submissions land as leads with a status workflow — a human qualifies them into contacts, deals and projects.
The actual Leads module — same theme, same layout as the app. Example data.
The problem and how sSystm solves it
How sSystm does it
Leads collects inbound form submissions into one queue with a clear status workflow. A human triages: qualify into a CRM contact and deal, or close. Nothing converts automatically — the pipeline stays honest.
What Leads gives you
Built deep, so the module actually carries the weight of real client work.
01
One inbound queue
Every public-form submission lands as a lead with form source, status and timestamp. No more inbox archaeology.
02
Status workflow
From new to qualified or closed — the state of every inbound request is visible at a glance.
03
Human conversion
A person decides what becomes a contact, a deal, a project. AI reads the queue; it does not pollute your CRM.
04
Read-only over MCP
Your AI reads leads via sstm://leads to brief you on the queue — the resource is deliberately read-only.
Leads on the MCP surface
The exact tools and resources your MCP-connected AI gets for this module — verbatim from the live server.
Resources · read
1sstm://leadsYour AI, via MCP
Your AI reads the lead queue over sstm://leads — summarising, prioritising, drafting replies — while conversion into CRM records stays a human act.
How the human gate worksLeads · Premium — à la carte
Put Leads
to work.
Join the waitlist — when your spot opens, your workspace is provisioned on your own Cloudflare account and you switch on the modules you need. Inbound submissions, triaged into real work.
When you're in: no email, no password — one Cloudflare grant · core workspace free · your data lives in your own account