Independent software company
Software for what happens in more than one place.
NineToNever LLC builds and operates its own products. Each one takes something scattered across many locations, channels, or people and puts it in a single place where somebody can actually act on it.
What we do
Three products, owned end to end.
Two of our products are business software, sold to companies that have outgrown a single site — where the hard problems stop being the work itself and start being coordination. What differs between locations. Which things are running and which quietly stopped. What arrived while nobody was looking. The third is a consumer application in the same shape: information that exists in thousands of separate places, assembled into something a person can check before they commit to a decision.
We design, engineer, host, and support all three ourselves — the API, the web client, the native mobile applications, the servers they run on, and the mailbox the support requests arrive in. That is a deliberate constraint. It means we take on few products, and it means there is nobody else to hand a defect to.
We are a small, self-funded team, which lets us decide what to build and what to collect on the merits rather than on what an advertising model would prefer.
- Entity
- NineToNever LLC, a Texas limited liability company
- Platforms
- Web, iOS, Android
How we build
The same standards on every release.
These are conditions we hold a release to, not intentions for a later version.
Built for more than one site
Our data models assume several locations from the start: what is shared, what is overridden locally, and who is allowed to change which. Retrofitting that into a product built for one site is close to a rewrite.
Failures announce themselves
Anything that runs unattended reports that it is still running, and tells the people responsible when it stops — by name, once, without waiting for someone to notice or a customer to complain.
A person stays in the loop
Where software drafts or collects something on a person’s behalf, a human reviews it before anyone else sees it. Automation gets to prepare the work; it does not get to send it.
Collect the minimum
We store less than we could. Where a feature can work without an account it works without one, and where a record does not need a person attached to it, none is.
Accessible by default
Interfaces target WCAG 2.1 AA: measured colour contrast, labelled controls, live regions for status changes, and layouts that survive the largest system text size.
We run what we ship
We operate our own infrastructure and answer our own support mail. There is no vendor between a defect and the people who can fix it.