Shape
A services, contracting or engineering business
Work arrives as jobs, gets estimated, gets delivered by a team, and gets invoiced. That is the loop the whole product is built around.
Fit6 signals
A straight answer beats a demo you did not need.
YumaOS is a per-client implementation, so a poor fit costs both sides real time. These are the conditions under which it works well, and the four things worth raising before anybody schedules anything.
Use cases
Six signals that this is the right shape.
Most of these are about how your business already runs, not about what you want software to do.
Size
Small enough that a few people hold several authorities each
The permission model expects the operations lead, the approver and the commercial lead to be two or three humans today, and separate people later.
Systems
Already running Xero, and tracking time somewhere
Invoices and payments mirror in from Xero, contacts import from it, and hours come in from whatever tracker you already run rather than being re-entered.
Posture
You want the data in your own database
One deployment, one organisation, on infrastructure you control. If your buying decision turns on where the data physically sits, this is the shape that answers it.
Appetite
You want agents doing work, not summarising it
The reason this exists is agents that move cards, draft quotes and prepare campaigns. If a read-only assistant is all you need, a general chat tool is cheaper.
Rhythm
Somebody will actually answer the queue
The approval queue drains in order and stops at the first unanswered row. That is a feature when a person checks it daily, and a bottleneck when nobody does.
Four things to raise in the first conversation.
None of these is a dealbreaker on its own. All of them are cheaper to discuss now than to discover during a procurement review.
Change control
Schema changes are applied as a push rather than as reviewable migration files, with a verified backup taken first. If your change control needs reversible migrations, say so in discovery so it is priced in.
Hosting
The scripted deployment targets your own hardware or a private server. Who runs that host, and who is on call for it, is worth settling before anything is installed.
Scale
One application and one database per organisation. No published throughput or concurrency figure exists, so if you are sizing for hundreds of concurrent users, that is a load test during discovery rather than a number we will quote.
Certification
The control surface a questionnaire asks about is there and demonstrable. Formal certification is not. If procurement requires an attestation on paper, raise it first.
Still unsure which side of the line you are on?
The FAQ answers the specific product questions directly, including what YumaOS deliberately does not do. Discovery is the other way to find out, and it comes before scope and price for exactly this reason.