How it works

From one call to live in 3 days. Here's every step.

No black box. What happens after you book, what an AI employee actually does on a real call, where a human steps in, and how we prove it worked.

  1. A seven-question plan with answers checked off01Pick the jobSeven questions and a 30-minute review find the recurring job worth handing off first.
  2. Your phone, calendar, inbox and CRM wired to one AI employee02We build it into your toolsPhone, CRM, calendar, inbox. Limits set. Failure tested on purpose. Live by day 3.
  3. A monthly results report with dollars booked and a rising chart03You read the reportWhat it did, what it cost, what it returned. Add the next role when the first one pays.

The first 90 days.Every date is a promise in the 90-Day Results Guarantee.

  1. Day 0Plan review30 minutes. We confirm the job, the limits, and the one person on your side who approves what.
  2. Day 1AccessYou grant access to the phone, calendar, CRM and inbox the job touches. We set up the AI employee's own workstation and work identities.
  3. Day 2Build and breakWe connect your systems, write the approval rules, and break it on purpose to prove the fallback works. Then a dry run of approvals with you.
  4. Day 3First employee liveWorking in your real workflow, or the next month is on us.
  5. Days 4–30The team fills inThe rest of the team comes online one role at a time, each tested before it touches a customer. We monitor, handle exceptions and tune.
  6. Day 30First reportYour first results report in hand, or the next month is on us.
  7. Days 31–90Run and reportMonitoring, fixes and tuning every week. A results report every month.
  8. Day 90Results reviewThe report shows the job is owned against the numbers we agreed, or we keep working with no management fee, or you walk. Then: keep going, add a team, or stop.

The Day 3 clock starts when we have access to your systems. Every condition is on the pricing page.

One call, step by step.A 9:40 PM call to a flooring company, handled by its AI Receptionist.

  1. 01

    The call comes in

    It's after hours. Before, this went to voicemail and the homeowner called the next company on the list.

    9:40 PMInbound call“Hi, we've got water under our hardwood in the kitchen. Can someone come look at it?”
  2. 02

    It makes a plan

    The Receptionist works from a written job description: answer, qualify, book an estimate, confirm. Nothing outside it.

    9:40 PMPlanQualify: service area, job type, urgency. Then book the first open estimate slot.
  3. 03

    It answers from your approved sources

    Service area, hours and what you do come from answers you approved. It never makes up a policy.

    9:41 PMSource checkedService area: yes, in range. Water damage: “we inspect before we quote.”
  4. 04

    It does the work in your systems

    The estimate goes on your real calendar, the contact into your CRM, and a confirmation text to the homeowner.

    9:43 PMBookedEstimate, tomorrow 10:00 AM. Calendar ✓ CRM ✓ Confirmation text ✓
  5. 05

    A human makes the call

    The homeowner asks what it'll cost. Pricing is on your list of decisions that wait for a person, so it doesn't guess.

    9:44 PMWaiting on you“The owner will call you with a quote after the inspection.” Flag sent to your named approver.
  6. 06

    We broke it on purpose first

    Before launch we cut the calendar connection to see what happens. You don't find out how it fails from a customer.

    Before launchFailure testCalendar unreachable. Expected: no double-booking, no lost caller.
  7. 07

    It falls back safely

    When something's down, it takes the details, tells the caller when to expect a callback, alerts you, and retries. Nothing gets lost.

    FallbackSafe queueDetails saved, caller told “first thing tomorrow,” owner alerted, booking retried at 6:00 AM.
  8. 08

    It shows up in your report

    Every action is logged, and the month's work is counted from your own systems, not estimated.

    Monthly reportCounted1 after-hours call answered · 1 estimate booked · 0 decisions made without you

Example. Your AI employees work from your own job descriptions, sources and limits.

Every AI employee gets its own workstation.

An isolated cloud computer, set up for one role in one business. It holds only the apps, files and logins that job needs, and nothing else.

  • Identities by need. A work email, a phone number or a login is created only when the job requires it.
  • No shared passwords. Your own logins are never handed around.
  • No cross-client context. What it learns about your business stays in your business.
  • Revoke in one step. Turn off access any time. The log of what it did stays.
More on security and human control
Workstation · Receptionist · your business
Connected for this role
  • Phone line
  • Calendar
  • CRM
  • Text messages
  • Approved answers
Not connected
  • Bank and payments
  • Payroll
  • Other clients
Waits for a person
  • Pricing
  • Contracts
  • Refunds
  • Anything sensitive

The monthly report, four layers deep.Every number carries its source, its period and its caveat.

  1. 1Work completedCalls handled, follow-ups sent, posts published, records written. Counted in your systems, never estimated.
  2. 2Quality and reliabilityExceptions, rework, handoffs to a person, failures caught, fallbacks used.
  3. 3Operating impactResponse time, hours covered, hours back, against the baseline from day 0.
  4. 4Business outcomeJobs booked and dollars, only where we can show the method. Projections are never presented as results.

Plus what we built that month: roles added, connections made, rules set. See an example report

Works inside the platforms your business already runs on
Google Workspace
Google Calendar
Facebook
Instagram
YouTube
TikTok
QuickBooks
Square
Stripe
HubSpot
WordPress
Slack

How it works, answered straight.

What do I need to do?
Three things: a 30-minute plan review, access to the tools the job touches, and one named person on your side who answers approvals within a business day.
What tools does it work with?
The phone system, calendar, CRM, inbox and website you already run. If we can't connect to something safely, we tell you on the review call, before you pay for anything.
Will it talk to my customers without me?
Only inside the limits you set. Pricing, contracts, payments and anything sensitive wait for a person.
What happens when it gets something wrong?
Bounded retries, an alert, a safe queue, and escalation to your named person. We test failure on purpose before launch, so the fallback is already proven.
Who can see my data?
Each AI employee works on its own isolated workstation with only the apps, files and logins its job needs. No shared passwords and no cross-client context.
Can I turn it off?
Yes. Access can be revoked in one step, any time, and every action it took stays in the log.
What does the monthly report count?
Only what's counted in your own systems: calls answered, follow-ups sent, posts published, jobs booked. Every number carries its source and period. Estimates are never presented as results.

Find the first job worth handing off.

Seven questions. See what missed work is costing you and the team that fixes it. If it fits, a 30-minute review with Tony, and your first AI employee can be live 3 days after access.

Get my free AI workforce plan
Free · 4 minutesFour new engagements a monthKeep the plan either way