Founder · Engineer first
Built like hardware. Maintained like a protocol.
AgentRigor is founded by an electrical engineer. The training was in mixed-signal board bring-up, signal-integrity verification, and EMC pre-compliance — lab work where you can’t ship until the sweep is clean and the postmortem is written. That is the same standard we hold production AI agents to.
The bench wasn’t glamorous. Oscilloscope traces captured at three supply rails, across -20°C to 70°C corners, with EMI pre-compliance scans run before every rev-control commit. Every bug came with a regression sweep that replayed the failure — not a guess, not a vibe, an artefact that could be re-run.
That habit maps onto shipping AI agents that must stay accurate long after launch. Every prompt is versioned. Every change runs against an eval suite. Every incident ships with a regression that would have caught it. The observability dashboard is a lab readout — the agent is the part under test.
- EE artefacts brought forward: scope traces, corner sweeps, BOM rev-control, postmortems written before the next spin.
- AI delivery, translated verbatim: versioned prompts, regression suites, named on-call escalation, lab-grade observability.
- One named human on every engagement. The agent that ships in week two is not the agent that goes to production.
craft: mixed-signal layout · signal integrity · emc pre-compliance
artefacts: scope traces · corner sweeps · bom rev-control · postmortems
guard:ship the part — not a guess — trace every commit
Prior production runs
Home services, in production. Already running.
Three operators, three verticals, three agents in production today. Each tile below is the workflow, the role the agent plays, the prompt version, and the eval sweep that cleared it before go-live — not a résumé bullet.
Home services · HVAC
Two-shop, four-tech HVAC outfit
Saturday leads book themselves before sunrise.
An inbound lead-qualifier wired into the existing telephony, CRM, and Google Calendar. The owner keeps the phone number, the CRM, and the calendar; leads stopped sleeping in voicemail on weekends.
- Twelve routing rules translated to prompt guard conditions: emergency vs. quoted, single-zone vs. comfort call, existing customer vs. net-new.
- Eval sweep covers seven fixture types, three time-critical emergency patterns, and the four "do-not-route" intents the team had confirmed by hand.
- Escalation only fires on the cases the owner named by name. Everything else books itself into the calendar.
Home services · Plumbing co-op
Regional plumbing co-op, eleven trucks
A first pass at every Monday ticket, before 7am.
A dispatch assistant reads the overnight maintenance email, opens each ticket in the existing CRM as a job, and proposes a truck assignment against the published rota. The owner approves or rewrites in under two minutes per ticket.
- Reads the email digest, normalizes addresses against the service-area zip set, and refuses to schedule outside the rota.
- Flags jobs that don’t match any rota slot instead of guessing — escalations go straight to the dispatch phone with the original email quoted.
- Every dispatch decision is recorded as a prompt-traceable event with the prompt version and the eval id it cleared.
Home services · Electrical
Single-tech licensed electrical outfit
After-hours voicemail stopped eating emergency revenue.
An after-hours intake agent watches the missed-call queue, qualifies the urgency from the caller’s voicemail transcript, and either books a same-day slot or pages the tech on call. The tech’s Tuesday review is a single screen.
- Pulls urgency from a small set of explicit phrases the tech confirmed in iteration three, not a free-text classification.
- If the transcript contains anything outside those phrases, the agent pages the tech immediately. No guess-and-route on edge cases.
- Eval sweep checks against a labelled corpus of last year’s voicemails — false pages drop every commit.
Why home services, specifically. Repeatable routing rules, an identifiable integration stack (CRMs, telephony, calendars, field-service tools), clear after-hours revenue leakage, and an intact system of record that the agents don’t replace — they sit in front of. Read the case study that started the file:Home services lead response.
Test it on your own traffic
Two weeks. Fixed fee. Tell us the workflow.
Same protocol, founder on the kickoff. We’ll reply within one business day with a scope and a flat pilot fee. No SOW, no hourly meter.