---
title: "Method: how we build SalexHub"
description: "The rules we hold ourselves to: the work ends in a finished thing, people decide, one organization, the Agent never holds more than its person."
url: "https://salexhub.com/method"
---

# How we build SalexHub

The rules we hold ourselves to, in the product and on this site.

## What we hold to

- **The work ends in a finished thing**: A job is done when something exists that was not there before: a sent quote, an issued invoice, a received delivery, an approved leave request. Not an answer in a chat. Every use case on this site names the thing it ends in. [See the use cases](https://salexhub.com/use-cases)
- **People decide**: The Agent prepares; a person says yes where it matters. By default each change waits as a card. Only the Owner can let the Agent act on its own, and sharing, roles and exports wait for a person in every mode. [How you stay in control](https://salexhub.com/solutions/stay-in-control)
- **One organization, one record**: Customers, quotes, invoices, orders, stock and people live in one place, and every way in, the App, the Chat, a Mini or the API, works on the same records. Nothing is copied from one tool into another. [All features](https://salexhub.com/product)
- **The Agent never holds more than its person**: It works with the rights of the person it works for, and what it does is in the same audit log as what people do. [Control & audit](https://salexhub.com/product/control)
- **We say only what is built**: This site shows what the product does today. Anything planned carries Coming soon, and only when an approved plan names it. Every change ships with its date in the changelog. [How we keep this site true](https://salexhub.com/blog/how-this-site-stays-true)
- **Plain words**: Quote, invoice, purchase order, leave: the names you already use. We do not invent a term where a common one exists.

---

The same page for people: https://salexhub.com/method. Index of this site for agents: https://salexhub.com/llms.txt