Open-source business software
Seven Three keeps your customers, work and money in one place. It answers questions with the working shown, checks every quote against the policies you wrote, and waits for your approval before anything goes out.
In development. We are building it on our own install-and-service business first.
One system for the whole business
Every part of the business goes through the same three moves: understand it from your data, decide with your policies, act through your tools. The system carries the rules; the model handles the language.
The product
What most small businesses keep in spreadsheets, chat threads and memory, kept together and checked.
Enquiries, quotes, jobs, contracts, tickets and invoices, linked to the customer they belong to. Bring them in from a file or add them as you go. Every change is logged.
Every answer shows the definition it used and the query that produced it, read straight from your records, so a number can be checked before anyone relies on it.
-- the query behind it SELECT severity, name, due_at FROM job WHERE kind = 'ticket' AND status = 'open' AND due_at <= now() + INTERVAL 36 HOUR
Write policies the way you already would, as numbered clauses. They become rules that quote your exact words, are tested before you approve them, and then check each quote as it is built, with no model in the decision.
2.2Installation is priced as a share of the hardware.
2.3A quote below the minimum gross margin is not sent without the owner's approval.
3.1Discounts above the owner's limit are refused.
margin_pct >= @setting:min_margin_pct
Seven Three drafts the routine steps: reminders, follow-ups, visits, quotes. Anything that reaches a customer or involves money waits for your approval, and every decision is kept with its reason.
The customer journey
Seven stages, the same for an installer, a shop, a subscription or a consultancy. Seven Three places each customer in a stage from their records, with the owner's question beside it.
How it works
What your numbers mean, what your policies allow and who may do what are reviewed definitions that run as ordinary code. A language model handles only the steps where language is the job.
"Which tickets are close to their deadline?"
Matches the words to the business's own terms.
"Open ticket" means status = open, reviewed once.
On your records, within your permissions and a cost limit.
In plain words, from the rows that came back.
The answer, the definition and the query, together.
Solid steps are the system; the gradient marks the model.
Every figure opens to its definition and query. Every policy finding cites its clause.
Most steps make no model call. Those that do run under a daily spending limit you set.
None where none is needed, a small one on your own hardware, or a hosted one on your own account.
Open, and where it stands
Open sourceThe code is published with the first release.
Runs where your data isYour own computer or server. Your records are not sent to us.
Fits the tools you haveDesigned to read from your CRM and accounts system. Other AI tools can use it over MCP, and none of them can approve anything.
Plain files you can reviewDefinitions, policies and permissions live in readable files, changed like code.
Everything marked working is in development, running our own install-and-service business first. It opens to others when it runs ours day to day.
Seven Three Labs is building it in the open. The source and documentation are published with the first release.