Reeve

Reeve runs your back office. You stay in charge.

Phone calls, text messages, appointment booking, invoices, and collections follow-ups — Reeve handles the back-office work that keeps a small service business running. The agent drafts; you approve. Over the first thirty days you review every action; eventually only the consequential decisions need a human glance.

Try the demo → Register for the closed beta

The plumber, the mobile mechanic, the HVAC tech: capable at the job, drowning in administration. They answer the same questions twenty times a day, miss callbacks while under a sink, send invoices three weeks late, and lose customers to whoever answered first. The work that pays them is twenty minutes; the work around it is six hours.

Who it's for

Small service businesses where the operator is also the bottleneck. The work is hands-on and the back office is one person — usually the owner — fitting it in around the actual work. Reeve is built for the verticals that fit this shape:

By design, Reeve is built around capabilities, not industries — the architecture is vertical-agnostic, and the platform reasons over your business through the operator-correction loop, not through hard-coded industry branches. The vertical pages below name the safety and workflow patterns common to each trade; the underlying behavior is the same shape for any small service business that fits the operator-as-bottleneck profile.

How it works

Reeve plugs into the channels you already use — your phone number, your email, your calendar — and starts handling the routine work alongside you. Over time it earns the right to handle more on its own.

  1. A customer reaches out. Phone call, text, or email — Reeve answers in your voice and gathers what's needed (the address, the problem, the preferred time).
  2. Reeve drafts a response. Booking the appointment on your calendar, sending the quote, writing the reminder, chasing the late invoice. The action is queued, not sent.
  3. You approve from your phone. Tap approve, edit the draft, or reject — every Phase 1 action waits for you. Routine and standard actions earn autonomy as the agent learns from your corrections.
  4. Only the consequential calls reach you. A refund, an unusual booking, a pricing exception — the things that genuinely need your judgment. The boring half ships on its own.

Where to go next

The product

The concrete surface: phone, SMS, email, calendar, invoicing, collections. One number, one inbox, one operator.

Pricing

Starting at $50/month per tenant, based on usage. Honest about what you invest in the first thirty days.

How it differs

Trust earned, not asserted. Constraints in code and data, not prompts. The agent is a planner; the database and the policy layer are the enforcers.

Trust and safety

Nine adversarial scenarios run on every change. OWASP LLM Top 10 and MITRE ATLAS coverage mapped openly. Try the demo against a HIPAA + TCPA gated tenant — the gates demonstrate themselves to you in real time.

The vision

Agents as accountable colleagues, not tools. A trust progression that's an honest engineering primitive instead of a vibe. An apprentice that learns the operator's particular business — not a one-size chatbot.

Reeve is in private beta with a small number of design partners. If you run a small service business and the description above sounds like your day, register interest in the closed beta or write to hello@reeve.tools.