Bernot Software
National platforms. Now, Flagstaff businesses.
My client work has been remote and national for years: payroll, gaming, security, infrastructure. The engineering does not change when the company gets smaller. The access does.
By industry, because the names are not mine to give.
Most of this work sits under other companies’ names and agreements. What I can tell you is the shape of the problem and what I did about it, which is the part that matters to you anyway. What that turns into for a business your size is described under services and pricing.
Gaming & hospitality
Back-end development for a national operator. The kind of system where a slow query is a line of people waiting at a counter.
HR & payroll
Go services and APIs for a platform serving small employers. Moving sensitive records between systems correctly, every time, with no room for a rounding error.
Cybersecurity
Senior back-end and cloud infrastructure work for a security company, where the threat model is part of the design rather than a review at the end.
Health & fitness
A cloud infrastructure stabilisation project for a club management platform. The work was taking something fragile and expensive to run and making it boring again.
Developer platforms
Go development on an infrastructure-as-code product. Tools other engineers depend on, which is a demanding audience to build for.
Higher education
Records systems, live availability boards, and single sign-on services for colleges. Thousands of users, a lot of forms, and zero tolerance for downtime during move-in week.
Real estate
Document automation for an Arizona brokerage: a desktop application that assembles a full packet of standard forms from public records and the brokerage’s own systems, entirely on their machine.
Cloud infrastructure
My day job is engineering on a major cloud platform, on storage and observability systems underneath services used by millions. I also contribute to Kubernetes and have spoken at KubeCon and GopherCon.
One shape, over and over.
Strip the industries away and nearly every project I have done is the same sentence: a person is moving information between two systems that will not talk to each other, by hand, on a schedule.
At a payroll company that looks like a service moving records between providers. At a brokerage it looks like the same eight facts typed onto nine different forms. At a taproom it looks like a stack of distributor invoices and a Tuesday evening.
The cost is identical in all three: someone capable is spending hours on work that has no judgment in it, and every one of those hours is a chance to transpose a digit. If you recognise your own week in that, it is worth half an hour of conversation.
Where this shows up locally
- Invoices and orders re-keyed into accounting
- Intake and registration forms typed twice
- Permits, titles, and applications filled by hand
- Quotes assembled from a price list and a phone call
- Inventory tracked in more than one place
- Reports rebuilt from scratch every month
- Scheduling that lives in one person’s head
Your version of this is probably a spreadsheet.
Bring the process nobody wants to own. Thirty minutes, no cost, and a straight answer about whether it is worth building.