We build and host business agents that remember the work, respect hard boundaries, and stay maintained over time. The model underneath is rented and getting cheaper for everyone. The operating memory, the judgment, the upkeep, and the relationship are the durable part.
Live built for real business work
Bounded owner approval stays in the loop
Hosted kept sharp after launch
SCROLL: THE OPERATING MODEL
01: The Load
We lift the load.
Most AI hands you another thing to manage. We do the opposite. At Petrichor takes the recurring jobs that make a week heavy and runs them quietly in the background, so they stop living in your head.
Loop 01
The lead that never goes cold.
Every inquiry gets logged, followed up, and surfaced when it needs you. Nothing slips.
Loop 02
The estimate that goes out same day.
Job details gathered, a draft quote prepared, waiting on your one approval.
Loop 03
The follow-up that always happens.
Past customers, open jobs, and quiet weeks get the nudge they need, on schedule.
Start with one. Add more as they prove themselves. They begin to hand off to each other, and the week gets lighter.
02: The Work
Agents that remember. Systems that hold.
Most AI tools talk well for a week and then drift. At Petrichor builds the working layer around the model: memory, rules, review gates, receipts, and maintenance. The point is not a flashy demo. The point is a business system that still makes sense next month.
i
Memory
Customers, jobs, follow-ups, receipts, and owner preferences are kept in a durable operating record.
ii
Boundaries
No rogue spending, sending, scheduling, quoting, or destructive moves. The agent stops where the owner should decide.
iii
Receipts
Important work leaves a record: what fired, what changed, what stayed blocked, and what needs review.
iv
Upkeep
We host it, tune it, and keep the boring parts alive after launch, so the business does not inherit a science project.
03: What We Build
Small first. Useful fast.
◆Lead intake
◆Follow-up loops
◆Private records
◆Hosting & upkeep
Pilot · First System
Lead-to-Job Agent
Captures leads into a private record, turns them into next actions, drafts owner-reviewed replies, and keeps follow-up from depending on memory.
~$750–1,500 setup · $150–300/mo
Built around one real workflow
Private data stays private
Owner approves sends, quotes, scheduling, and money
Scale · Operating Layer
Business Spine
The deeper layer behind the day: lead board, field capture, estimates, books, mileage, customer follow-up, and review gates.
~$3–4k setup · $300–500/mo
Everything in the pilot, deeper
Hosted on infrastructure we operate
Maintenance, review, and improvement after launch
Dedicated · Private Server
Your Own Private Server
For businesses that want their data on a machine that is theirs alone, with no shared tenants.
Scoped per build · Hosted by us
One dedicated box for your company
Private agent home, memory, and records
Fully hosted, watched, and maintained by us
Pricing is directional. Every build is scoped before money moves, and every customer-facing action stays behind an explicit approval gate until it is proven safe.
04: Where It Lives
Hosted where the boundaries hold.
A useful agent needs more than a prompt. It needs a protected home, scoped tools, review gates, logs, and a human owner above anything sensitive. You reach the agent through one watched door; private records stay in their lane. Hover the diagram.
Your agent and the window you use
The brokered door: watched, logged, capped
Blocked from money, sends, and private lanes without approval
One door in.
Requests pass through a brokered route where keys, spend caps, and tool limits can be reviewed instead of hidden inside a prompt.
The record stays private.
Customer details, lead notes, receipts, and job records live in approved private destinations, not public proof pages.
Authority is explicit.
The agent can prepare and organize. It does not send, quote, schedule, invoice, or spend unless the owner approves that route.
05: The Proof
We keep receipts.
P/01
A real trades business has a private lead intake system with redacted receipts and duplicate-aware imports.
Verified systems include a Cloudflare intake worker, private R2 storage, a local import bridge, and a scheduled catch-up lane.
P/02
The lead-to-job loop is honest about authority: agents prepare and organize; the owner approves customer contact, quotes, scheduling, invoices, and money.
That boundary is not a footnote. It is the operating model.
P/03
We are our own proof. At Petrichor runs its own operations on the same platform we sell.
Our own company uses the agent stack, server discipline, review gates, and receipts before we ask anyone else to trust them.
P/04
Every sales claim gets marked as verified or flagged before it leaves the house.
No invented ROI. No fake autopilot. The discipline is part of what clients are buying.
Built carefully. Kept alive.
At Petrichor builds the operating layer around the model: memory, boundaries, receipts, and upkeep.