Software
Building software people actually want to use
Adoption is not a feature problem. It is a problem of understanding the day the software is supposed to fit into.
Jonathan Longares · May 9, 2026 · 8 min read
Most software for restaurants and events is built by people who have never worked a Friday night.
It shows in small ways: forms with too many fields, screens that assume a quiet office, reports nobody has time to read.
The useful question is not what features to build. It is: what is this person doing at the moment they open the product, and how fast can they get back to the floor?
When you build against that constraint, the product gets smaller and adoption gets easier.
Go-to-market follows the same rule. If the value takes longer to explain than to experience, build a tool people can try in two minutes and let it do the explaining.