New Lead → Booked Client
The flagship 8-node pipeline — the actual sequence a new Loudframe inquiry moves through, end to end. Watch it run, step through it manually, or pick a different lead to see the branch logic fire.
Automations
Rule-based, no autonomous reasoning — trigger in, action out. Six automations run Loudframe's day-to-day; five of them are also nodes inside the flagship pipeline.
New Inquiry Router
Trigger: a new submission on Loudframe's contact form. Action: tags it by service category and posts it to the right column on the internal ops board. One trigger, one action, no branching.
"Need a new site with online booking, budget ~$10k"
[SIMULATED DATA]Tagged: Web Redesign · posted to Ops Board → New Leads
Lead Nurture + Invoice Sequence
Two named sequences: a 3-touch nurture sequence for not-ready leads, and an invoice reminder sequence for active clients.
Contract & Invoice Reader
Extracts client name, deliverables, price, terms, due date, signature status from SOWs/contracts/invoices; cross-checks against the CRM record and flags mismatches.
Fit Score
Outputs fit_score, qualification_reason, recommended_action, and missing_fields from the raw contact-form submission.
Support Triage
Standalone — never appears in the flagship chain.Priority + queue + a suggested draft response queued for Ismail's review — triage/draft only, never auto-sent.
Inbound:
Single Source of Truth
Fires whenever any other automation or agent touches a contact; updates stage, dedupes, and timestamps who/what last touched the record.
Novak & Reyes Interiors
Stage: Client
Last touched by: Contract Reader automation, 2m ago
- New Inquiry Router — created lead 9d ago
- Fit Score automation — scored 84/100, qualified 9d ago
- Prospect Brief Agent — attached research brief 9d ago
- Outreach Agent — drafted + sent first-touch email 8d ago
- Contract Reader — extracted signed SOW, no mismatch 2m ago
Agents
Autonomous, tool-using, reasoning-capable — these don't just fire a rule, they decide. Two reuse the flagship pipeline's own scripted run rather than a second copy of the same content.
Meeting Notes Agent
Single tool, single job: takes a call transcript and produces a structured summary + action items list.
Project Health Agent
Scans active projects/calendar, flags at-risk ones, and drafts a client status update for approval.
Rule: Flag: no update in 5+ days, OR milestone due within 48h with open blockers.
At risk: Hartley Studio — Rebrand
New Client Onboarding
Satisfied by the Pipeline view — the full 8-node chain is this workflow.
go to Pipeline view ↑Outreach Agent
Drafts personalized first-touch outreach referencing the prospect's stated project type + research brief, proposes meeting times from real calendar availability.
Reusing Run A pipeline data (node 4 — Outreach Draft) at reading size.
Client Concierge Agent
Resolves simple client questions end-to-end in conversation by querying the live project record — no human needed.
Prospect Brief Agent
Researches a prospect's company before a sales call — what it does, industry, size signal, competitors — into a one-page brief.
Reusing Run A pipeline data (node 3 — Prospect Brief) at reading size.
Nerve Watchdog
Satisfied by the Watchdog view — the meta-agent overseeing every other automation and agent.
go to Watchdog view ↑Watchdog
"Nerve Watchdog" — the meta-agent. Detect → decide → act: it reads every other node's status chip,
not a single business function. The rows below read the same PipelineEngine
state driving the Pipeline view live — run/step the pipeline there and watch it change here.
Simulate a failure
[SIMULATED DATA]Forces Node 7 (Contract Reader) into an error, then plays the Watchdog's detect → auto-retry → resolve sequence. This is a demo trigger you invoke — nothing plays unprompted.
Platform
Custom AI platform — Nerve itself. Not another feature: one shared data layer every automation and agent above reads from and writes to.
One shared data layer
[BUILT]This wasn't 13 disconnected tools bolted together — it's one platform, built once, and this is the same kind of platform Loudframe builds custom for clients. Hover or click any node to see what it reads or writes on the shared client record.
"This is what I actually watch. Every lead that comes into Loudframe, every draft before it sends, every contract that gets read — it all passes through this one screen before I do anything else."
I built Nerve because I was running six different inboxes and tools to do what one console should do. Now I build the same kind of platform for clients who are drowning in the same way I was — one shared data layer, one visual language, one place to watch the whole business work.
— Ismail Bentounsi, Loudframe