The lead does not disappear into a voicemail.
The inquiry becomes a durable record with the contact, job, urgency, and next useful step organized.
AI office crew for trades · Founding cohort open
Hire the help that remembers.
At Petrichor builds and keeps a small AI office crew for trades businesses. It catches the lead, prepares the follow-up, remembers the job, and waits for your go before anything consequential leaves.
The world after rain—held in orbit. Chatter at the front. Trellis underneath. You stay the boss.
Nothing sends without your go
Work remembers across days
Built and maintained in Milwaukee
The crew wall · Original At Petrichor concept
Built forPlumbingElectricalHVACHandymanPaintingRoofingRemodeling
01 · The load
Your phone rings while your hands are full.
Leads, estimates, customer details, and follow-ups make a week heavy. The crew holds the recurring office work while you stay on the tools and keep the decisions.
The reply is ready when you look up.
Chatter gathers the facts. Trellis prepares the right draft and waits at the owner gate.
The open loop comes back on time.
The system remembers what remains unresolved and brings it back without quietly sending on its own.
The crew carries the repetition. You keep the decisions.
02 · Chatter & Trellis
One natural front door. One visible way through.
The conversation should feel easy. The work behind it should be bounded, inspectable, and honest.
Chatter
Chatter gives the owner a natural way into the system. It listens for the useful facts, keeps the thread intact, and turns the conversation into a clear pending request. Live customer calls remain gated behind disclosure, consent, and review.
- natural conversation
- structured lead intake
- context that survives the chat
handoff
Trellis
Trellis reads the work, applies the boundary, chooses the right crew lane, and keeps the route visible. If no safe route clears, it stops and says why.
- task-fit routing
- owner approval gates
- receipts for work and stops
Nothing goes out without your go. That is not a missing feature. It is the promise.
03 · The Studio
Choose a presence that feels like yours.
A visual identity is optional, friendly, and shaped with you. Choose a polished studio form, a warm creature, or a quiet abstract style—or keep things beautifully simple. Nothing is assigned, and nothing pretends to be a person.
Foundry · polished
Wilds · warm
Ink · quiet
Foundry
specialists in residence · six studies
Wilds
creature forms · five studies
Ink
quiet forms · three studies
A visual identity is a choice, not a requirement. These showroom works are synthetic style studies, use no employee or customer likenesses, and can be made warmer, quieter, simpler, or more playful to suit the team.
04 · Watch the handoff
See Chatter become accountable work.
Choose a realistic request and watch it cross the same five checkpoints every time. No magical completion. No hidden send.
Request
A homeowner asks for a ballpark estimate and the next available visit.
Chatter hears
The request joins the operating record.
waitingWork takes shape
Public lead; drafting allowed; sending and scheduling require approval.
waitingTrellis routes
A fast, task-fit drafting lane clears the gate.
waitingYou decide
The response and proposed visit wait for review.
waitingReceipt remains
The chosen route, draft state, and blocked actions are recorded.
waitingReady to observePlay the route to see the request cross each boundary.
receipt pending
This is a synthetic route fixture, not a live customer request. It explains the operating rule without exposing customer data or technical machinery. Behind it, each real route, stop, and approval point remains inspectable and receipted.
05 · The crew wall
A small office crew. One clear wall.
Your crew can prepare, organize, remember, and route. The wall keeps authority, money, customer sends, and destructive action on your side until you approve them.
Your side · The authority
You keep the wheel.
The system can make your decision easier. It cannot quietly make the consequential decision for you.
Customer sendyour go
Quote and scheduleyour go
Money or deletionhard stop
gateevery crossing leaves a reason
Crew side · The preparation
FD
FU
OF
Start with the role that removes the heaviest repeat work. Add another only after the first one proves useful.
The Front Desk
Catches the inquiry, structures the facts, and keeps the lead from vanishing.
Intake · context · urgencyThe Follow-Up
Prepares replies and reminders, then waits at the wall for your approval.
Draft · remind · returnThe Office
Keeps customer and job context connected so the week does not reset every morning.
Memory · records · receipts06 · Founding cohort
Trades-sized plans. No enterprise maze.
Begin with one role. Widen only when the receipts show it is helping. One-time setup is scoped separately after we map the workflow.
Your first role
$299 / month
One high-value office loop, remembered and maintained. The founding monthly rate stays locked for the cohort.
- one bounded recurring workflow
- durable working memory
- owner gates and receipts
- hosting and upkeep
The connected crew
$499 / month
Connected intake, follow-up, and office memory through one maintained operating record.
- several proven office loops
- shared customer and job context
- Chatter and Trellis routing
- monitoring and recovery
Your own environment
$999+ / month
Higher volume and a dedicated environment with explicit data lanes and company-scoped tools.
- isolated workspace
- local routes where required
- controlled external access
- watched and maintained
Monthly plans are the operating service. One-time setup is quoted only after the workflow, records, integrations, and approval points are understood. No checkout link is live on this page.
07 · What a week looks like
A working relationship, not a chatbot handoff.
Name the heavy loop.
We learn the real work, records, exceptions, and owner decisions.
Map authority and data.
Every tool, destination, send, spend, and sensitive lane gets a written boundary.
Build and prove it.
The pilot runs on real examples with visible stops and reproducible receipts.
Keep it alive.
We monitor, tune, recover, and adjust the route as the business changes.
08 · The proof
We run what we sell.
At Petrichor uses the same maintained operating pattern in its own work. A real trades-business proof slice includes private intake, redacted status, duplicate-aware importing, and scheduled catch-up. Raw customer records stay private.
Verified operating evidence · sanitized client-facing summary · no invented ROI40
New notes imported
One honest metric across two receipt-backed import runs in the current proof packet.
Duplicate-aware
Existing records linked
Matching preserved the operating record rather than multiplying it, including three manual leads that were not duplicated.
Scheduled
Catch-up does not depend on memory
Morning, midday, evening, and boot recovery keep the intake lane returning.
Owner-gated
Consequential action stops
Customer contact, quotes, scheduling, invoices, and money remain owner decisions.
Private records stay private
Public proof uses redacted status, never raw customer data.
Routes respect data class
Sensitive work can be held local or stopped instead of silently sent outward.
Authority is explicit
The agent prepares; the owner approves consequential external action.
Important work leaves evidence
What ran, what stopped, and why remains reviewable.
09 · After launch
The model is rented. The operating layer is maintained.
Models change. Providers fail. Workflows drift. The durable value is the memory, boundaries, routing evidence, recovery path, and human relationship around them.
Memory and record healthwatched
Route quality, cost, and latencyreviewed
Failed jobs and recovery pathsreceipted
Tool and authority changesre-gated
Business changes and new loopsgrown carefully
10 · Fit
Built for owners who want useful help without surrendering the wheel.
A good fit
- Recurring information work makes every week heavier.
- The business already has records, rules, and owner judgment worth preserving.
- You want one useful workflow proven before widening.
- You value privacy, review, and a maintained relationship.
Not what we sell
- An unattended system that runs the business without you.
- A generic chatbot dropped off after a demo.
- Guaranteed revenue, guaranteed security, or invented ROI.
- Hidden sends, spend, scheduling, quotes, or destructive action.
11 · Questions
The plain answers.
Where does our data go?
Only to approved destinations under the selected route. A dedicated server can keep company work in an isolated environment; sensitive lanes can require local execution or fail closed. Any allowed external route should be explicit.
Does the agent contact customers by itself?
Not by default. It can prepare and organize. Customer sends, quotes, scheduling, invoices, and money remain owner-approved unless a later route is separately authorized and proven.
What prevents drift or confident guessing?
The operating layer: durable records, scoped tools, explicit gates, evidence requirements, receipts, and human review. When no legal route can do the work, the system should stop rather than improvise.
What happens after the first workflow works?
We keep it maintained and add another loop only when the first one is reliably useful. Proven loops can then hand work to one another through the Business Spine.
What does it cost?
Founding is $299 per month, Business is $499 per month, and Dedicated starts at $999 per month. One-time setup is scoped separately after we understand the workflow and approval points.
Are the robots real?
The robots are an original concept visualization of the software crew and its clear work boundaries. At Petrichor sells and maintains software agents, not robot hardware, and never claims the software is a person.
The smell of rain, and the work that follows
Tell us what makes your week heavy.
We will find the smallest useful loop, map the authority around it, and show you what a careful first build looks like.
One real workflow · no generic demo · owner approval stays explicit