About

We're operators first

Acorn Works came out of running multi-location businesses, not out of a consulting practice. The systems on this site were built for companies we own or operate — entertainment venues across four states, a vending and amusement route operation, a vehicle storage yard. We shipped them, used them daily, found what was wrong with them, and rebuilt them properly.

That's a different relationship to the work than a vendor has. When a rollout goes badly, we're the ones who have to explain it to our own staff on Monday. It makes us conservative about scope and stubborn about the details that only matter later.

How we build

We ship in phases, and we're specific about what a phase does and doesn't include. The first thing we build is usually a clickable version on sample data, so you can walk a stakeholder through a familiar flow before anyone commits to the real thing. It's much cheaper to be wrong at that stage.

We build for the person actually holding the device. Large tap targets when it's used on a floor, a short PIN when the device is shared, bigger type when the user isn't twenty-five. These sound like small decisions. They're the difference between a system people use and a system people route around.

We treat permissions, audit trails, and data privacy as part of the build, not as a phase two. Row-level security, soft deletes, opt-in records, and secrets that live in a vault and never in a bundle.

What we won't do

We won't sell you a platform you have to grow into. We won't put an AI feature in front of a problem that a query would solve. And we'll tell you when the answer is to change the process rather than buy software, which happens more than you'd think.