# Systems I built

> Four systems I built for service businesses, each placed on the client lifecycle stage it serves and labelled with how far it has been tested.

I built four systems, each for one stage of a service business's client lifecycle. Two turn leads into replies, one sets up a new client's project, and one keeps customer records in step across tools. Each carries a status label for how far it has been tested. None is installed for a client yet.

A service business wins and keeps clients in four stages: getting found, turning leads into clients, doing the work, and keeping records straight and failures caught afterwards. I put every system I build on one of those stages, so you can go straight to the one where your week gets stuck.

## Where each system sits

*Diagram: Acquire has nothing ready yet. Convert has the inquiry desk and lead to reply. Deliver has client launch. Maintain has data intake sync.*

## What the status labels mean

Each system page shows the same ladder of labels, from built through logic-tested and connector-tested to production. A system carries the highest label it has earned. Production means running for a client, which nothing I have built does yet. The template library lists every template I have ready to show, with its stage and label, including two that have no page yet.

- [A drafted reply to each lead, approved from my phone before it sends](https://signalnine.io/systems/inquiry-desk): AI drafts replies to lead emails that pass a junk screen, from my business facts. Risky asks get flagged, and nothing sends until I approve it on my phone.
- [Website form leads, scored and answered with a reply I approve](https://signalnine.io/systems/lead-to-reply): A system I built: each website form lead is checked, added to HubSpot once and scored. Gmail sends the drafted reply when I approve it in Telegram.
- [Records from forms and emailed PDFs, kept in one place that stays right](https://signalnine.io/systems/data-intake-sync): A system I built that keeps the right version of each customer record in Airtable. Forms and emailed PDFs feed it, and HubSpot copies from it.
- [From signed deal to running project](https://signalnine.io/systems/client-launch): Client onboarding automation I built. One form with the signed proposal sets up the Drive folder, ClickUp tasks, Slack channel and welcome email.

## Questions

**Have any of these been installed for a client?**

Not yet. The inquiry desk has run on SignalNine's own inbox since 2026-09-07, and the other three have run on test accounts I own. Each system page sets out what has been proven so far and what has not.

**Which stage should I look at first?**

The one where work waits longest for a person. If leads sit for hours before anyone answers, start with Convert. If a signed client waits days for their project to be set up, start with Deliver.

**Can I download these and run them myself?**

Not yet. Each one has to load into a fresh account and run cleanly there before I offer it as a download. The template library shows where each one stands.

[BOOK A FREE CONSULTATION](https://cal.com/mashrur-signalnine/30min)

## Related

- [n8n template library for service businesses](https://signalnine.io/templates): Every workflow template I have ready to show for service businesses, with its stage and how far it has been tested. None is offered as a download yet.
- [What a reliable automation looks like](https://signalnine.io/guides/reliable-automation): Five properties any automation should have, checkable by an owner who doesn't build: logged runs, named alerts, one send per approval, safe reruns, an owner.

---
Mashrur Rahman, Founder, SignalNine. Published 2026-10-04, updated 2026-10-05.
Canonical: https://signalnine.io/systems