I build the software
your business actually runs on
Not a strategy deck. Not a pilot program. The specific thing that removes the spreadsheet holding your operation together, or connects the two systems that have never spoken, or answers the phone at seven at night.
The average small business using AI saves about 5.6 hours a week. That is the honest size of the prize. It is not a transformation, it is most of a working day back, every week, forever, for a one time build cost you can see before you agree to anything.
Free · about a minute · no email required to see your result
Every small business is running on one thing that should not be load bearing
Usually it is a spreadsheet. Sometimes it is one person's memory, or an inbox folder, or a whiteboard somebody photographs before wiping. It works, right up until the business grows past it, and then it fails in a way that costs a customer.
Research puts real numbers on this. Roughly 68 percent of businesses lose productivity to manual data reconciliation, and finance teams alone burn something like 15 hours a week fixing spreadsheet discrepancies. That is not a technology problem anyone talks about at conferences. It is just quiet, expensive friction.
My work is narrow and specific: find the load bearing thing, and replace it with something that will not break when you double. I have done it 39 times across my own operations and for clients, 21 of them documented publicly on this site with what they do and how they were built. Nothing on the evidence shelf is a mockup.
Six things I build
Named by what you would recognize rather than by architecture. Most projects are one of these. The larger ones are three of them wearing a trench coat.
Automate a workflow
A sequence you run over and over by hand becomes something that runs itself: intake to quote, order to invoice, job to status update, application to follow-up. Anything where a person is currently the wire between two systems is a candidate, and it is usually the fastest project to pay for itself.
- ›Copy and paste between two tools
- ›A checklist somebody follows every time
- ›Work that only happens when one person remembers
Replace a spreadsheet
The spreadsheet that runs a core part of your business, has parallel versions, broke last month, and only one person truly understands. It becomes a real application with a database behind it, validation, history, and more than one person able to touch it safely.
- ›Multiple versions of the same file
- ›Formulas nobody wants to touch
- ›One person is a single point of failure
Connect your systems
Your CRM, accounting, email, calendar, storage and industry platform stop being islands. Data moves between them on its own, including across the platforms that never shipped an API, where the workaround is reading the documents they already publish.
- ›Entering the same data twice
- ›Reports that need three exports
- ›A tool that will not integrate with anything
Build a custom app or portal
When nothing off the shelf fits, a real application: an internal tool your team runs the day from, or a client-facing portal where customers see their own status without emailing anyone. Built on standard infrastructure you can own outright rather than rent forever.
- ›Paying per seat for 20% of a platform
- ›Clients constantly asking for updates
- ›Your process does not fit the software
AI agents and assistants
Voice agents that answer the phone and book real calendar events, email agents that draft in your voice, and assistants that answer questions from your own documented knowledge instead of improvising. Wired to real tools, so they can actually do things rather than take a message.
- ›Missed calls after hours
- ›The same question answered 30 times a month
- ›An inbox that eats the morning
Reporting and dashboards
Numbers that are correct on a Monday without anyone preparing them. Scheduled collectors read the systems that already hold the truth, so the dashboard reports on the business instead of reporting on how diligently somebody updated the CRM.
- ›Reports built by hand each month
- ›Nobody trusts the dashboard
- ›Discovering a problem a quarter late
The shapes repeat everywhere
The vocabulary changes and the underlying problem does not. A contractor chasing subcontractor updates and a distributor chasing supplier confirmations are running the identical broken process with different nouns. Pick the closest fit, or pick none of them and describe your own.
Chasing subcontractor updates and rebuilding the same client progress report every week.
Retyping orders between the order platform and the CRM, and margin nobody can see per line.
Proposals assembled by hand, and utilization numbers that only exist once a month.
Missed calls after hours, scheduling by text, and paperwork that comes back from the truck late.
Inventory living in three places at once, and support answering the same question all day.
Scope tracked in a spreadsheet, and client status updates eating the account team.
Supplier confirmations by email, and pricing that depends on one person remembering.
Intake on paper, reminders by hand, and a front desk that cannot answer two calls at once.
Leads scattered across portals, and follow-up that depends entirely on who remembers.
Not listed? That is genuinely fine and fairly common. Describe your business in the diagnostic and it will route on the bottleneck rather than the industry label.
What is already running
Peak One Builders
Visibility across every active build, subcontractor workflows automated, and client project updates that go out without anyone assembling them. A named client in a completely different industry from where these systems started.
How it works →21 documented builds
Each with what it does, how it was built, what it cost to run, and where it broke. Across 39 systems and 50 platforms integrated. You can read the architecture before you ever speak to me, which is the point.
Browse the builds →A voice agent that books
801-316-8544 answers, holds a real conversation, and puts an actual event on an actual calendar. Not a sandbox. The fastest way to judge whether I ship working things is to make one of them do its job.
How it was built →SIPS, mapped end to end
My promotional-software platform reverse-engineered into one interactive map — 232 routes, 105 tables, every request traced to the row it writes. It lives behind an application, and it is the clearest proof I ship real systems.
Apply for access →Four steps, no surprises
- 01
Look at the real work
A call where you show me what actually happens, including the ugly parts. Most of the value in the first hour is naming which problem is worth solving, and it is frequently not the one you called about.
- 02
Scope and a fixed number
You get the specific thing being built, what it will and will not do, the timeline, and a price that does not move. If I think the honest answer is a $30 tool instead of a project, I will say so.
- 03
Build it against your data
Not a demo on sample records. It runs on your actual jobs, clients and files, because that is the only way the edge cases surface before you are depending on it.
- 04
Hand over the keys
It runs on infrastructure in your name, and you get the documentation. You are not renting access to your own operations, and you are not stuck with me to keep the lights on.
What this costs
Nobody in this category publishes a number, which is a tell. Here are mine. Fixed project pricing, not a monthly retainer, and the run cost is whatever the infrastructure genuinely costs passed straight through.
A single, well-defined process automated end to end. The right place to start, because it proves the approach on your real data before anyone commits to anything larger.
Several connected workflows, a custom internal tool, a client portal, or a spreadsheet replaced properly with a real database and real permissions behind it.
The whole operation: connected systems, a documented company knowledge base, agents, and reporting that maintains itself. Normally staged over months rather than bought at once.
When you should not hire me
If an off the shelf product already does the job at a reasonable price, buy it. I will tell you which one on the call and not send an invoice. A large share of the "we need custom software" conversations I have end with me naming a tool that costs forty dollars a month.
If the process you want automated is not written down anywhere and changes depending on who is doing it, automation will make the inconsistency faster rather than fix it. Document it first, even roughly. That is free and it is the actual bottleneck.
If you need enterprise compliance work, multi entity financial consolidation, or a team of engineers on retainer, I am the wrong size. I am one person who ships, which is an advantage up to a point and a hard ceiling past it. I would rather say that now than three months in.
Common questions
How much does AI automation cost for a small business?
A single automated workflow normally runs $1,500 to $4,000 to build with a run cost under $50 a month. A larger connected system runs $4,000 to $12,000. For comparison, the broader market sits at roughly $2,500 to $8,000 for one workflow, and most agencies charge $997 to $5,000 a month as a retainer on top. I quote fixed project prices instead of retainers, and the run cost is whatever the infrastructure actually costs, passed through.
Do you only work with promotional products companies?
No. That is where I built the deepest systems and it is why the proof on this site leans that way, but the work is industry agnostic. Construction, professional services, e-commerce, field service and trades all have the same underlying shapes: a spreadsheet doing too much, two systems that will not talk, and a person acting as the wire between them.
Should I build custom software or just buy a tool?
Buy first, almost always. If a proven product covers the need at a reasonable price, buying is the correct answer and I will tell you that for free. Build when your workflow, your data, or the thing that makes you different genuinely does not fit anything on the market, or when per-seat pricing on software you use 20 percent of has quietly become one of your larger bills. Most healthy small businesses end up hybrid: bought tools for the commodity parts, custom for the part they actually own.
Is Zapier or Make enough, or do I need custom work?
For a single well-defined automation between two popular apps, no-code tools are genuinely the right call and cheaper than hiring anyone. They stop being the right call when the logic branches heavily, when the data needs to be cleaned or reconciled first, when one of the systems has no API, or when the workflow is one you cannot afford to have fail quietly. The most common regret I hear is weeks lost fighting a no-code tool on a workflow that needed real integration work from day one.
How long does a project take?
A single workflow is normally one to three weeks. A larger system is four to ten. The variable is almost never the code, it is the state of your data. If the same client exists three times under three spellings, cleaning that is real work and I would rather show you that up front than discover it halfway through.
Do you work with businesses outside Utah?
Yes. I am based in Salt Lake City and I like meeting Utah clients in person, which is genuinely useful in the first session. The work itself is remote and the majority of it is done over calls and shared screens, so location is not a constraint.
Who owns the software when it is finished?
You do. It runs on accounts in your name and you get the documentation. I am deliberate about this because the alternative, where a consultant hosts your operations on their account and you rent access to your own data, is a bad position for you and I would not accept it either.
What if the AI gets something wrong?
Then the design was wrong. Anything touching money or a commitment to a customer gets deterministic code rather than a language model, because a model that is confidently slightly wrong about a quantity is far more dangerous than one that fails loudly. Models are for judgment and language. Code is for correctness. Mixing that up is the single most common failure I see in AI projects.
We are not technical. Is that a problem?
It is the normal case and it is not a problem. You need to be able to explain how your business works. I handle the rest, and if you ever need to understand a decision, I will explain it without jargon. The measure of success is that your team uses the thing without thinking about it.
How do we start?
Either take the free diagnostic, which asks what industry you are in and where the time goes and returns a specific read plus a price band in about a minute, or book a call and skip straight to talking. Neither one costs anything and neither one puts you on a list.
Start with the diagnostic
Three questions about your business and where the time goes. You get a specific read on your bottleneck, the builds that map to it, and a price band. Before any email address is asked for.