What running our own product taught us
We built anon.li, then had to run it. Operating a product every day changed how we build for clients.
When you run what you ship, every shortcut you take sends you a bill within the week.
You ship it, you run it
When you operate the business behind an app, visual approval is not the finish line. The product still has to explain itself to a distracted visitor, load reliably, accept changes, and stay understandable months later.
That perspective carries into client work. We pay attention to the handover, the editing experience, and the small operational details because we know someone will depend on them after the project team has moved on. Usually that someone is us.
Simplicity compounds
A clear navigation label, a reusable content pattern, or one less dependency can seem like a small decision. Repeated across years of updates and thousands of visits, it becomes an operating advantage.
Complexity is sometimes necessary, but it always creates a cost. We ask whether a new interaction improves understanding enough to justify the extra testing, maintenance, and attention it will require.
“The most durable design decisions keep working when no designer is in the room.”
Real users give better feedback than taste
Operating a product creates a steady stream of useful evidence: the questions people ask before upgrading, the search terms that bring visitors, and the points where a task is abandoned.
- Listen for repeated confusion in enquiries and support messages.
- Compare what visitors search for with the language the product uses.
- Watch the complete journey, not only page-level traffic.
- Prioritise changes that remove a real obstacle over changes that merely look new.
Why this matters to clients
Clients get the after-launch perspective for free: maintainable code, honest estimates of what a feature will cost to keep, and a builder who has personally answered support email.
“Running your own product is the fastest cure for clever ideas.”
Frequently asked questions
- What does owner-operated mean at ENGR?
- ENGR does more than build apps for clients. It also owns and runs its own products, taking responsibility for their web experience, content, performance, and ongoing improvement.
- How does operating a product benefit a client?
- It brings an after-launch perspective into the project. Decisions are considered not only for presentation, but also for conversion, editing, maintenance, speed, and future changes.
- Does ENGR plan to run more products?
- Owning products is part of the model, but there are no numbers to announce. When there are, this blog will say so first.