Memory before motion
The system starts with the record: email, meetings, decisions, and the sources that make each fact credible. Work does not begin from a blank prompt.
Company
Run the business. Not the software.
The operating layer for small companies that need more work carried, not more software operated.
one:ton is being built around a simple shift: software should carry more of the work it records. It keeps the context around a customer, a decision, or a process attached to the action that follows. You stay responsible for direction and judgment. The system carries authorized work, shows what it did, and returns when the boundary matters.
- What we are building
- An operating layer, not another department’s tool. It keeps context attached to the work that follows, moves what you authorize, and returns only the decisions that need judgment.
- Why now
- Headcount is no longer the unit of scale. The constraint on a small company is how much of it you can hold at once. That’s a software problem, not a hiring problem.
- Where we are
- Not open yet. one:ton opens when it is whole, not in pieces, and this site describes what it is being built to be.
- What we will not do
- Send on your behalf without an explicit approval. That’s architectural, not a setting, and no authority level widens it.
The operating model
A lighter company starts with a record that moves.
Authority before autonomy
You decide what can happen without you. Each level widens the system's room to act, but nothing it can do changes the boundary around the company.
Relief without surrender
The point is not to hand over the company. It is to remove the carrying work so your attention returns where judgment changes the outcome.
Relief without surrender.