Skip to content

03 — AI operations

AI that drafts the work, and a person who decides.

Vayrk Ops gives each service business four agent departments — Revenue, Scheduling, Leads and Customer Ops — that draft work for a person to approve. Nothing is texted, emailed, called or booked without that person.

My role
Built Vayrk’s side of Vayrk Ops, and Website Studio
Built
Oct 2026
Built with
Anthropic or OpenAI (customer’s key) · Fly.io · Supabase
Status
Accepted on Production on a demo workspace; off for customers
Vayrk· Exhibit 03 · AI operations
Sample data only
Website Studio: a sample roofing website in the preview, with Vayrk AI’s proposed headline applied but unsaved, and an Undo button.
Website Studio applying a proposed edit. Nothing is kept until a person presses Save. Staging, fictional business.
01 — The problem

Work gets lost between an inquiry and the next step.

Vayrk’s customers are trades that sell by inquiry, estimate and appointment: HVAC, roofing, plumbing, electrical, landscaping, pest control. Follow-up is where they lose work, because it depends on someone remembering.

02 — The approach

Agents draft. Vayrk sets the scope. People approve.

Each business brings its own model key, Anthropic or OpenAI. For every task Vayrk signs a grant (Ed25519) naming what the agent may read, and agents reach data only through Vayrk’s context routes. Approving a draft saves it; it is never sent on its own. The same rule runs Website Studio, the AI editor in Website Factory: it proposes edits, and it never saves and never publishes.

03 — How it works

Event in, draft out, a person decides.

  1. TriggerA business eventFor example, a new lead arrives
  2. Signed grantVayrk sets the scopeThe task may read only what the grant names
  3. AI · DraftAn agent drafts the workRevenue, Scheduling, Leads or Customer Ops
  4. Person · ApproveApprove or turn downApproving saves the draft; it never sends it
  5. RecordLogged, not sentEvery run lands in the audit log
Model step (the business’s own key)Human checkpointVayrk-side step

From the Vayrk Ops records, October 2026. Production acceptance passed on one demo workspace, then the kill switch was left on. No customer workspace is switched on.

  1. 01

    Trigger

    A business event, such as a new lead, queues a task. At most six an hour per business; tasks expire after 24 hours.

  2. 02

    Grant

    Vayrk signs exactly what the task may read. Agents see data only through Vayrk’s own routes.

  3. 03

    Draft

    The agent drafts with the business’s own key, under a spending limit set per business.

  4. 04

    Approve

    A person approves or turns it down. Approving saves the draft; nothing goes out automatically.

04 — Outcomes

What the record shows.

Each figure names its source. Development and Staging results are labelled as such; nothing here is a customer result.

Verified
0 of 20

Drafts sent without a person in the Staging run: 7 approved, 13 turned down.

Source: Vayrk Ops record · Oct 2026

Verified
$0.13

Model spend for that run, against a $2.00 monthly limit.

Source: Vayrk Ops record · Oct 2026

Verified
3,164 / 3,164

Tests passing across 123 suites, with 16 of 16 mutants killed.

Source: Vayrk Ops record · 19 Oct 2026

Want to build something like this? Let’s talk.