The Ormi Manifesto
Everything we build at Ormi follows from those two ideas. This page is the long version — what we believe, what we won't do, and who we're building for.
The platforms trades run on today were built for very different businesses. They priced per seat because their customers had knowledge-work org charts. They billed in 3-year contracts because their customers had procurement cycles. They bolted on features to win enterprise RFPs, not to help a tech close a call at 4:47pm on a Friday.
Then that same software got sold, feature-for-feature, to the 12-tech HVAC shop down the street — at the same price per seat. Shops paid $3,000/month for 90% of a product built for someone else, and negotiated dispatch around the 10% that was broken.
Ormi exists because field service teams deserve software built for field service teams. That's not a positioning line — it's the whole thesis. Everything below is just what that thesis looks like when you take it seriously.
The best field service software is the kind nobody ever has to talk about. If a dispatcher is thinking about the tool, we've already failed.
02 · What we believe
Decisions about features, pricing, and hiring all trace back to one of these. If a choice isn't consistent with the list, we either change the choice or change the list.
01
The best field service tools are invisible. A dispatcher shouldn't have to think about the software — just the job. A tech shouldn't need training to close a call. We measure success in how few taps it takes to get work done.
02
Per-seat pricing punishes growth. The day you hire a tech is the day your bill goes up — before that tech closes a single job. We charge per completed job. We only win when you win. The incentives shouldn't need a translator.
03
We don't build toward a Gartner quadrant or an analyst's feature list. We ride along on installs, sit in on dispatch calls, and read every support ticket. If a feature didn't come from a real job site, we didn't build it on purpose.
04
Every feature has a cost — cognitive load, maintenance, a new edge case. Complexity compounds. Simplicity doesn't. Competitors with thousand-feature catalogs built themselves a ceiling. We'd rather ship 50 things that matter than 500 that mostly don't.
05
We release to production every week. Decisions happen in days, not quarters. If a tech flags a bug on Tuesday, it should be in production by Friday. The calendar isn't the product — the product is.
06
Export your data any time — customers, jobs, invoices, photos. One click, full CSV. We don't believe in lock-in as a retention strategy; if we can't earn the renewal, we shouldn't keep you through contract friction.
03 · What we won't do
These are the moves competitors make that we've decided against — on purpose. If we ever break one of these, hold us to it.
Charge by seat
So every dispatcher, tech, and office manager can log in without costing you another line item.
Hide prices behind "contact sales"
Our number is public. A sales rep shouldn't be a gatekeeper to what you'd pay.
Bolt on AI for AI’s sake
If a feature uses an LLM, it's because it actually helps — not because the deck needed a slide.
Hold your data hostage
One-click full export, any time. Lock-in as a retention strategy is a tell that the product isn't winning on merit.
Chase the enterprise checkbox
We build for shops that run the work, not procurement departments that audit the vendor. If a feature request is really a compliance blocker, we'll say so.
Pad the roadmap with marketing
What we're shipping is on the changelog. What we're planning is in customer conversations. We won't announce vaporware to win a bake-off.
04 · Who this is for
For
Not for
The Ormi team
McKinney, TX · April 2026
A manifesto is cheap. Software isn't. The only way to know if this reads true is to actually use Ormi — or come build it with us.
