Book a call

The engagement

You don’t have to understand AI. You have to understand your own business.

That’s the part most AI projects skip, and it’s the part we start with. There’s no software for you to set up, no prompts for you to write, and no dashboard you have to configure before it becomes useful. We build it, we run it, and we teach your people to run it with us.

Here’s the whole thing, in order.

First, a call

Fifteen or twenty minutes, free, and deliberately short. Enough to hear roughly what’s going on, answer whatever this site didn’t, and tell you where you’d come in.

If we’re not a fit, you’ll hear it on this call. That happens, and it’s a better outcome for both of us than a proposal nobody should sign.

If you want somebody to actually dig into the business before you commit to anything, that’s a longer paid working session rather than this call. Either is a fine place to start.

Then we build the foundation

This is the stage owners brace for, because "we’ll map your processes" sounds like six weeks of meetings you have to sit in. It isn’t, and the reason is worth explaining.

We interview you and the people who actually do the work. Then an AI employee on our side takes the transcripts and the materials you already have, the price lists, the policies, the answer somebody retypes twenty times a week, and produces a first draft of how your process runs today. If parts of it are already documented, we start from what you have and extend it instead of starting over.

You’re not filling in a template. You’re reacting to a document that already exists, which is a shorter and different job than authoring one.

Then comes the part that isn’t documentation. Once the process can be seen, we design what it should look like with AI employees in it. Which steps a teammate carries, which ones stay with a person because judgment belongs there, and where you want to be asked before anything moves forward. That second document is what the build actually runs on.

Your business information gets organized so it can be used safely, and the limits get set.

What you have at the end of this stage: two versions of how your business runs, the one you have now and the one you’re building toward, with the approval points marked on it. If you stopped here and did nothing further, you’d keep both. For most owners it’s the first time the operating rules have lived anywhere outside their own heads.

We call this part Ground Truth, which is a term borrowed from engineering. It means the verified data a system gets measured against. It’s also just the true ground the rest of it stands on.

Then we build your AI employees

Each one is built on that written process. What it says, what it offers, what it declines, and the exact point where it hands a conversation to a person with the full context attached.

You review it and you test it yourself, with real questions and awkward ones. All of that happens in a sandbox that’s separate from anything live. Builds and changes get tested there before they reach production, and that applies to our own work as much as to yours.

We’ll tell you now what that first round of testing is for. It isn’t to confirm the thing works. It’s to find what we didn’t capture, because on a first pass through a real business we won’t have caught all of it. Then we refine, you test again, and it goes live after your sign-off. That’s a term of the engagement rather than a courtesy.

They work on the channels your clients already use to reach you, and we define that set with you rather than handing you a fixed list. WhatsApp, text, phone, email, the chat on your site, whatever your business actually runs on. Nobody downloads anything or learns anything new, they just start getting answered.

What you have at the end of this stage: work getting done that was previously waiting on a person who was busy.

Then your team takes the controls

This is the stage that decides whether any of it lasts a year.

Your people learn what each AI employee does, how to read the record, what to approve and what to send back, and where the edges are. We stay on to operate and improve the workforce, and improvements arrive as proposals you look at rather than as changes you discover later. The version answering your clients is a version you approved.

What you have at the end of this stage: a team that can run this, and a firm that runs it with them.

What you actually have to do

Three things, and they’re the three nobody can do for you.

  • Decide how the work should run

    We hand you the process we drafted, and what comes back is rarely a correction. It’s usually a decision. There’s a step we missed. There’s a gap you’d never noticed until you saw it written down. Or, most often, “I want to be asked before that happens.” Those are calls about how your own business should operate, and they’re yours to make.

  • Test it before your clients do

    You run real scenarios against each AI employee, more than once, and tell us where it’s wrong.

  • Approve what needs approving, once it’s running

    Minutes in a day rather than a job.

What you don’t do: configure software, write prompts, manage a tool, or become technical.

How much of your time that adds up to

We’re not going to print an hours figure here, because the honest range is wide enough that a number would be a guess dressed up as a fact.

What moves it: how many people hold pieces of the process, how complex those processes are, whether anything is already written down, and how many rounds of refinement the build needs before it’s right.

You’ll get a real estimate of your team’s time in the written proposal, scoped to your business. It’s a number worth having, and it’s only worth having after somebody has looked at how you actually work.

Roles grow into departments

The first AI employee usually handles the loudest problem. Once it’s running, the pattern extends, and you add in the order your business actually needs rather than in the order a platform sells.

Client communication. The front desk that answers, qualifies, and quotes. The follow-up that happens on schedule. The support line that handles the routine and escalates the rest with context attached.

Marketing and brand. Research, drafts, the weekly production cycle. Our own runs this way, which is where this website’s messaging came from.

Internal operations. Not everything an AI employee does touches a customer. Turning meetings into documented process, keeping the operating knowledge current, preparing the work your team reviews. Most of our own AI employees work here and never speak to a client.

Each one gets its own floor on your dashboard, which you can walk into and see what happened.

What it costs

Every engagement is scoped and priced individually, and we don’t publish a price list because we’d be guessing about your business. What we can tell you now:

Nothing is billed by the hour. You’re buying a scope and an outcome, not somebody’s time.

The diagnostic work comes before any build, and it’s paid. A short readiness assessment of your data and processes, priced modestly, with the fee credited toward the build if you go ahead within 60 days.

The build is a one-time engagement. Scoped in writing before anything starts.

Running it is a monthly fee , because the AI employees operate on our infrastructure and we maintain, monitor, and improve them.

Scope moves the number. How much information there is and what state it’s in, how many functions you’re starting with, how much volume runs through them.

No guarantees, at any level. We don’t promise a percentage or an hours-saved figure, because we’d be making it up. What we do instead is agree with you up front on what we’re solving and what outcome we’re after, and hand you a written picture of how the work runs today, so there’s something real to measure against later.

Only a written proposal binds either of us, and it says what’s included and just as plainly what isn’t.

Twenty minutes. Not a demo.

Bring the question you’d ask if you were trying to catch us out. That’s the one we want.

Book a discovery call

Or write to hello@thewayfinderOS.com and tell us in three sentences what your business does and where it hurts. A person will answer you.