Bernot Software
Flagstaff, Arizona
Your team is doing work that software should be doing.
Most people come to me about AI, and it earns its place in plenty of the work. The bigger win is usually quieter: taking what your Northern Arizona business runs on memory and habit, and making it produce the same result every time, faster.
No pitch deck. We look at one task that is costing you time and I tell you whether it is worth automating.
Where the hour goes
- Taproom Distributor invoices, re-keyed into accounting by hand
- Contractor Job-site photos and notes, turned into an invoice that evening
- Clinic or practice Intake forms, typed a second time into the record system
- Shop or retail Stock counted in three systems that never quite agree
- Brokerage or title office The same handful of facts, onto form after form
Different trades, the same hour, gone again next week.
Small businesses don’t lose time in big chunks.
They lose it fifteen minutes at a time, to work nobody would choose to do. Three patterns show up in almost every shop I walk into, and all three yield to fairly ordinary automation.
The same data, typed four times
A name and address arrive by email, get keyed into a form, copied into a spreadsheet, then re-typed into the software that actually bills for it. Every hop is a chance to fat-finger a digit.
One person is the system
There is a process that only works because someone remembers all of it. When they take a vacation, the process takes one too, and nobody else can pick it up without a two-hour explanation.
Tools that refuse to talk
Your CRM, your scheduler, your accounting, and your document templates all work fine. None of them work together, so a human gets to be the integration layer.
Whatever fits the job, and nothing more than that.
The platform is a consequence of the problem, not a preference. Sometimes the answer is a whole application. Often it is a small, unglamorous piece of automation that quietly removes a chore.
Automation & AI assistants
Document generation, data entry that fills itself, records pulled from public sources, and assistants that draft the first version of work a person then checks.
How this works →Web applications
Internal dashboards, client portals, booking and intake flows. Things your team opens in a browser and your customers can use on a phone without pinching to zoom.
How this works →Mobile & desktop apps
For work that happens in a truck, on a job site, or on a machine where the data needs to stay put. Native apps that keep working when the signal doesn’t.
How this works →I have been doing this remotely for national companies. I would rather do it here.
For the last several years my client work has been remote and national: gaming and hospitality, HR and payroll, cybersecurity, infrastructure platforms. Serious systems, real constraints, good people. But I never once saw the office.
The businesses in Flagstaff have the same problems. A taproom re-keying distributor invoices is doing the same work as a payroll platform moving records between systems, just without a department to throw at it, and without anyone local who can build the fix.
That is the gap I am pointing at now. Same engineering, applied twenty minutes from your front door instead of three time zones away.
Industries I have built for
- Gaming & hospitality Back-end services for a national operator
- HR & payroll APIs for a platform used by small employers
- Cybersecurity Back end and cloud infrastructure
- Health & fitness Stabilising the cloud infrastructure under a management platform
- Higher education Records systems and live availability boards
- Real estate Document automation for an Arizona brokerage
Four steps, and you can stop after any of them.
-
A free consult
Thirty minutes. You describe the task that keeps eating your week. I ask how it actually gets done today, including the parts that are nobody’s job officially.
-
A written proposal
What I’d build, what it would cost as a fixed price, and how long it takes. If I think the honest answer is off-the-shelf software you already own, I say that instead.
-
Build, in visible pieces
You see working software early and often, not a status report. If the shape is wrong, we find out in week one rather than at delivery.
-
Launch, then I run it
It goes live on infrastructure I operate, monitor, and keep patched. You get working software and one person answerable for it, instead of a server somebody on your team has to learn to look after.
I can drive to your office.
Watching the actual work happen is worth more than any requirements document. Most of the good ideas in a project come from noticing the workaround someone has quietly built for themselves: the sticky note on the monitor, the spreadsheet that is not supposed to exist.
That is hard to get from an offshore team on a different clock, and it is the reason the work is priced by the outcome rather than by the hour.
What you get either way
- A fixed build price, and the monthly running cost, both quoted up front
- Hosting, updates, backups and monitoring handled, not your problem
- Your data stays yours: no resale, no training on it
- Plain English about what AI is and is not good for
- An honest “you don’t need this” when that is the answer
- A realistic start date, not an optimistic one
The questions that come up first.
What does a project cost?
It depends entirely on the job, so I quote a fixed price after the free consult rather than publishing a number that would be wrong for you. A narrow automation that removes one recurring chore is a very different project from a client-facing application, and I will tell you which one you are actually asking for.
Are you going to replace my staff with AI?
No, and I would be suspicious of anyone promising that. The work worth automating is the work your people already resent: re-typing, copying between systems, filling the same form again. AI is useful for drafting and for reading messy input. It is not a substitute for the person who knows your customers. I have written the longer version of this.
Do I have to move off the software I already use?
Usually not. Most projects connect to what you have rather than replacing it. If a tool you are paying for already does the job and nobody turned the feature on, the right recommendation is to turn it on, and I will say so.
What happens if I want to stop working with you?
That depends on what was built, and it is negotiated rather than boilerplate. A desktop application mostly carries on working on its own. Something with real infrastructure behind it needs a wind-down period so nothing stops without warning. Some deliverables are yours outright from the start. Which of those applies is settled in the proposal, before the work starts, rather than argued about later.
What happens to my data?
It stays yours, and the agreement says so in writing. Where I host an application for you, your data sits on infrastructure I run, and it is never sold and never used to train anything. Where a job can be done without the data reaching me at all, I build it that way: one of my desktop apps handles client records entirely on the user’s own machine, with no server of mine involved at any point.
What kinds of businesses do you work with?
Flagstaff businesses with staff and a process that has outgrown the spreadsheet holding it together: taprooms and restaurants, shops, contractors and trades, clinics and practices, outfitters and tour operators, accountants and law offices. My document automation work has been deepest in real estate, but that pattern, a person retyping facts onto a standard form, turns up in permits, registrations, intake, claims, and quoting just as often.
What is the task you dread?
Bring the one that shows up every week. Thirty minutes, no cost, and no obligation to build anything.