I build AI agents into the Microsoft 365 you already own.
Not a chatbot in the corner — a system that owns a workflow: it reads what arrives, works the standard cases itself, hands your people the exceptions, and logs every step where you can check it. Built agent-first on the Power Platform, in your tenant, and you own the source. When a job is big enough to build for, I build. When it isn't, I tell you what to buy off the shelf instead, and I don't take a cut. The reality check below is how we find out which one your week needs.
Agent-first systems, on the platform your licence already includes.
An agent-first system puts the software in front and your people on the exceptions. Orders get read and entered as they arrive, the chasing happens on its own, the Friday report assembles itself — and the odd cases land on a person's desk with everything they need attached. It's built with Power Apps, Power Automate and Copilot Studio, the tools inside the Microsoft 365 most companies pay for and never switch on.
I commission before I hand over. The first production agent I built shipped only after passing all eight of its guardrail evals — written tests for the ways an agent goes wrong, not a demo that worked once — and the suite caught four defects on the way that would otherwise have gone out the door. I've also priced the platform down to the credit, so a build arrives with what it costs to run each month, not a shrug.
It lives in your tenant and you own the source. Any Microsoft licence it needs, you buy direct — I resell nothing. If you fire me, everything keeps working and everything stays yours.
And Millwright's own back office runs on the same tables, flows and controls I'd put in your building. I don't sell a shape I don't run. One of those controls, live today: an invoice can't exist until the guarantee question has been answered — and if I try to skip that step, a flow reverts the invoice. The rules hold against me too.
The bar for building is deliberately high — about thirty hours a week on a single job — and most jobs don't clear it. For those I'll name something off the shelf and take nothing for it. The refusing is why you can trust the building.
Every owner is asking the same two things right now.
How do I actually use AI in my business, and am I getting left behind? Fair question. The market is answering it badly, mostly by selling you the fear.
Here is the honest version. You are not behind. Most of what is being sold to you right now will not survive contact with your business, and the reason isn't that the technology is fake. It's that the people selling it have never run an operation like yours. A demo works because somebody picked the inputs. Your business doesn't get to pick its inputs.
So the useful question isn't whether to use AI. It's which twenty minutes of your Tuesday are worth handing to a machine, and which ones aren't. That's an operations question, and it has an answer you can check.
Most company AI pilots produce nothing measurable. Everyone in this industry knows it. Nobody puts it on their homepage.
The thing eating your week is not AI shaped.
In a company of 10 to 100 people it's almost always the same handful of jobs, and it's never the one the owner expects. Nobody has ever added it up. Adding it up, out of your own numbers, is the first thing the reality check does.
Every one of these is three numbers: how many times a week, how many minutes each, and roughly what the person doing it earns. Multiply them out on the whiteboard and the week stops being a matter of opinion.
- Somebody retypes orders out of email into the accounting system
- The same report gets rebuilt by hand every Friday, from the same three places
- Quotes get assembled from a price sheet and last month's PDF
- Someone spends their week chasing timesheets, photos, signatures and receipts
- Two systems that don't talk to each other, and a person is the integration
Agent-first when the job is big enough. Off the shelf when it isn't.
Every job the check finds gets one of three verdicts, and the report says why — including the one where you shouldn't hire me at all.
Build it
One job is eating enough hours to build around. Then I do the work I'm actually here for: an agent-first system on the Power Platform — it works the standard cases itself and hands your people the exceptions. It sits in your tenant, you own the source, and any Microsoft licence it needs you buy direct. Fixed price, quoted after the check, never before.
THE MARQUEE — WHEN THE JOB CLEARS THE BARSet it up
The tool exists, but nobody there has the hours to configure it properly or connect it to anything. Small fixed-price job, usually about a week. You can also hand this to your own admin, and the report is written so they can follow it.
SOME OF WHAT I FINDBuy it
Somebody already sells software that does this, often for less than a phone bill. I name it, tell you what it runs, and you're using it this month. I don't resell anything and I don't take a cut, so there's no reason for me to steer you. If a $60 a month product does 80% of a job, building the 100% version is malpractice.
MOST OF WHAT I FIND — AND I SAY SOFive hours a week, across everything I find, is the bar I have to clear to get paid at all. About thirty hours a week on a single job is the bar before I'll build anything. That's roughly 1,500 hours a year, most of one person's working year going into one job.
The second bar is much higher than the first, deliberately. Under it, building costs more than the problem does, and the honest answer is don't build it. That answer is what you're buying.
If you want to test one job against those bars yourself, there's a calculator here that runs the same arithmetic. It's free, seeing the answer doesn't cost an email, and it's honest enough to tell you to leave the job alone.
The AI Reality Check.
How we find out whether anything in your week is big enough to build for — and what deserves a cheaper answer. A reality check on what AI can actually do in a company your size, pointed at the people selling it to you, not at you.
- 45 to 60 minutes, once. A call, or I come to you if you're near Atlanta. I walk your week with you and write down what gets done by hand, how often, and by whom. You don't prepare anything.
- A written report, a few days later. Every manual job I found with the arithmetic beside it. Three to seven fixes ranked by effort against payoff. Which of the three answers each one gets, and what it costs. A four-day plan for the first one.
- A 30 minute call to walk you through it. Then it's yours. Take it to your own admin, take it to another shop, or hand the parts you want done back to me. There's nothing to sign at the end.
If I can't find at least five hours a week of manual work I can help you get rid of, you pay nothing. Worst case, you lose an hour.
The five hours get counted in front of you, out of your own numbers, while we're still in the room. Not estimated afterwards in a document you can't check.
I'm not selling you tools I've never had to run.
Anyone can take a weekend course and start selling AI to small businesses. Most of the people doing it have never had to keep a company running on a system after the invoice cleared. That's the job I've done for twenty-two years.
Twenty-two years running operations, all of it on your side of this table — the one who gets sold the system, has to make it work with the staff and the process already in the building, and owns it when it doesn't. I'm not a software person who found your industry. I'm an operations person who got tired of the workaround being me.
That's what you're actually buying. When something I put in fails, somebody's Tuesday stops, and I have been that somebody enough times to be careful. It makes me conservative about what I'll tell you to automate, which is the opposite of how this industry behaves. Most of what I find, I'll tell you to leave alone.
Things I'd rather tell you now than have you find out.
Scope honesty is most of what I'm selling. If any of these is a dealbreaker, better we both know in the first ten minutes.
- I'm not your IT support. No laptops, no email problems, no passwords, no networks. If that's what you need, I'll say so and you'll want a different phone number.
- I don't do 2am for clients. This kind of software isn't being used at 2am. If something breaks overnight I find it in the morning and fix it, and your Tuesday looks the same either way.
- Your data stays in the Microsoft account you already own, and I never keep a copy of it. If a job works better with an AI model that isn't Microsoft's, then part of what it reads leaves that boundary, so I put that in writing first and you switch it on yourself, or we don't use it.
- I build on one platform, Microsoft's. The reality check works whatever you run, and the recommendations stand either way. But if your business lives somewhere else, I probably won't be the one building.
Ask for the reality check.
Email me what your company does and roughly how many people you have. I'll come back with the two or three questions I need and a time. If it's obviously not a fit, I'll tell you that instead, and it costs you one email.
Ask for the reality checkKEVIN@MILLWRIGHT.WORKS · ATLANTA, GEORGIA · WORKS REMOTELY