Moat vs Head Start: How I Filter Product Features

Building O9X for my business, I ask: functional need or UI polish? Arc Browser taught me the difference.

As someone with multiple Google accounts, I lived in “account hell.” Switching meant signing out and back in across browsers. Arc’s Spaces fixed this—isolated sessions in one window. I recommended it to many of my friends.

Even as I recommended it to everyone, I knew I wouldn’t pay for it. The problem was annoying, not expensive. Safari copied Profiles in six months. Zen Browser shipped vertical tabs as open source. Arc’s moat was UI—a head start, not a moat. As they transitioned to Dia - which I never liked - I quit Arc and moved to Zen.

Applying This to O9X

O9X is an ERP I’m developing for my business—Security and Manpower Services. Phase 1’s goal: single source of truth.

My business runs on Payroll Software, Zoho Books, Excel sheets, and unread emails. Guard attendance in one place, client complaints scattered across email inboxes and WhatsApp groups. Nobody knows which version is current.

When my team requests features, I run three questions:

1. Is this something the team does regularly?
2. Will this increase output?
3. Behavioral change: net positive or negative?

Three recent decisions:

Small form: Internet drops kill unsaved data. I built a quick-capture form—basic info first, details later. Regular work. Prevents loss.

Excel migration: They wanted to import their sheets. That’s the entire point of O9X. Built it.

Custom reports: 1-2 customers ask once a quarter. Deferred to Phase 2. Not regular work. Phase 1 is production testing.

O9X is internal, but my time isn’t unlimited. Every feature delays launch.

What I’m Watching For

Most Phase 1 features are done. Testing starts in March with live operations.

Three-month test. I don’t know if skipping custom reports will force my team back to Excel, or if “good enough” UI will actually hold.

Here’s the filter I’m using. Test it yourself. Let me know what breaks.