OneAIAgency maps one real workflow in your business, works out what it's costing you, and hands you a ranked list of fixes. When a fix needs automation or custom software, we build it. Nobody recommends a tool here until we've seen how the work actually gets done.
We work with owner-led businesses and small software teams. The problems that bring them in tend to look like this:
If two or more of these describe your week, the audit is worth a conversation.
The audit is a decision-making engagement. You come out knowing what to fix, what it's worth, and what to leave alone, whether or not you hire us for the build.
We pick one workflow worth looking at and the people who touch it. If AI isn't the right answer for you, you'll hear that here.
We map how the work happens today: who does what, in which tool, and how long it takes. We talk to the people doing the work, not only the owner.
Each opportunity gets a dollar figure for time cost, revenue lost and revenue upside. We use the low end of every range and note where each number came from.
What to fix with process, what the tools you already pay for can handle, what's worth building, and the next step for each.
A short, plain-English readout built around your own numbers. It covers:
Builds are scoped one at a time, each with its own one-page agreement and a fixed price. We start with whatever the audit ranked first.
Connect the tools you already use so records, updates and reports move on their own, instead of being retyped.
Assistants that answer from your own documents, qualify incoming leads, or summarise a week of activity for the owner.
Code for the jobs off-the-shelf tools handle badly, from internal tools to AI features inside a SaaS product to predictive models on your own data.
A 90-minute session for owners and managers on what AI can do for your business and where to start. It ends with a plan your team agrees on, and hands-on training for your staff can follow.
So the roadmap is something we'd be willing to deliver, and nothing gets lost in a handover.
Plenty of business software has automations and integrations nobody has switched on. If one of those solves the problem, we'll tell you, even though it means a smaller project for us.
Some jobs outgrow drag-and-drop platforms. We write the code ourselves, in Python and on the Claude API, so you aren't stuck with whatever a template allows.
Each build has a written scope, a delivery date and a price agreed before work starts. Prove the first one works, then decide on the next.
Two connected offers. The audit tells you where AI and automation would genuinely help. Builds are sold separately, one at a time, only for what the audit points to. Not ready to pick a workflow yet? Start with the AI Leadership Workshop.
Scope, delivery date, price, what data the build can read, where it's hosted and who owns what. Signed before we start.
A first build is scoped tightly enough to ship in a week or two. Read-only access to your systems wherever that's possible.
You use it with real work, tell us what's off, and we make a round of changes included in the price.
Take it from there yourself, or add a monthly retainer for support and the next build on the roadmap.
Fifteen minutes is enough to tell whether an audit makes sense for you.
Book a 15-minute call →A 90-minute session for owners and managers, usually at your office. Your team comes in curious about AI and leaves with a shared picture of what it can do for your business and a plan for where to start. If your staff need hands-on help afterwards, we can train them too.
Some people on the team use it, some are wary of it, and nobody has decided what it's for in your business.
Leadership agrees on the goal, the first use cases to look at, and who owns the next steps.
How Zapier went from a company-wide “code red” on AI to 89% of its staff using it every day, and what it did in what order.
What your team looks like once AI handles the repetitive parts: what gets automated, and where people spend their time instead.
For each one, why it matters, what good looks like, and a question for your team to answer together.
First steps for every pillar, laid out over three horizons: the next 3 to 6 months, 6 to 12 months, and the year after.
The framework the workshop is built on. Each pillar ends with an activity your team can start the following week.
Decide what you want AI to achieve, list the use cases worth doing, and rank them by business impact and effort.
A short AI manifesto and plain rules on which tools and data are fine to use, so people experiment without guessing.
Who builds things, inside the company or out, and how to test an idea in a few weeks before spending real money.
Training that starts with leadership and reaches every role, plus a few early adopters who help everyone else.
Leaders using AI themselves, giving people permission to try it, and sharing what worked.
Tracking outcomes like hours saved and revenue, not just activity, so you know what's paying off.
The workshop is for the people who set direction. If you want your staff using AI in their daily work, we follow it with hands-on sessions for them.
Sessions use the documents and tasks each group already handles, not generic examples.
People use the tools during the session on their own work, with help on hand when they get stuck.
We help you pick and coach three to five early adopters who answer questions after we've left.
How many sessions, and how long, depends on your team's size and where they're starting from.
Start with a 15-minute call. We'll talk about who'd attend and what you want out of the session.
Book a 15-minute call →There's no package menu because no two workflows cost the same to fix. You see the numbers from the audit first, then a written price for the build, then you decide. Workshops are quoted the same way: a written price before anything is booked.
For a limited number of businesses while we build our first case studies.
A 90-minute session for your owner and managers, priced before anything is booked.
Priced after the audit, against the value it showed, and written into a one-page agreement.
Starts once something is live. Separate from the build, so you never have to commit to it up front.
All of these get talked through before you see a number.
Reading from one tool is simpler than keeping three in sync.
A build that only reports on your data is smaller and safer than one that changes it.
Some jobs fit an existing automation platform. Others need software written from scratch.
AI usage and hosting have monthly costs. We estimate them up front and agree who holds those accounts.
A digest for one owner is different from a tool your whole team or your customers rely on.
If records are inconsistent, some cleanup has to happen first, and we'll say so in the quote.
Start with a 15-minute call. If an audit makes sense, we'll set it up from there.
Book a 15-minute call →OneAIAgency LLC is an AI consulting and implementation practice in Ames, Iowa. We help owner-led businesses and small software teams work out where AI is worth using, then build it properly.
Alex runs every audit and writes every build. He's a software engineer by training, with hands-on work across automation platforms and code: Voiceflow, Relevance AI and Make.com on one side, Python, the Claude API, Supabase and scikit-learn on the other.
"I'd rather tell you a setting in software you already pay for fixes your problem than sell you a build you don't need. The audit exists so that call gets made on your numbers, not on hype."
No tool gets named until we've watched how the work is done today and talked to the people doing it.
Every dollar figure in a readout says where it came from. We use the low end of a range, so the real result is more likely to beat the estimate than miss it.
Built-in features and existing integrations get checked first. New software is the last resort, not the opening pitch.
One workflow, one build, one agreement. The next build waits until the first one is earning its keep.
Read-only wherever the job allows, and everything a build touches is written into its agreement.
Platforms when they're enough, code when they aren't. The right choice is whatever you can keep running after we're done.
Book 15 minutes with Alex. No slides, just a conversation about one workflow.
Book a 15-minute call →Short write-ups on how we decide what's worth automating.
Most of the software a small business runs has automations nobody switched on. Why that's the first thing we look at.
The three numbers every opportunity gets, why we use the low end, and why the owner's estimate isn't the last word.
Repetition alone doesn't make a task a good candidate. What we look for before recommending a build.
Can't find yours? Email alex@1aiagency.com.
The quickest route is a 15-minute call. If you'd rather write first, use the form or email Alex directly.
It goes straight to Alex's inbox, and he'll reply to the email you give.