Complex logic, operated by the people who own the work.
We build software for work that is too complicated to be simple and too important to hand to whoever can write code.
The idea
Every tool that automates expert work eventually hits the same wall. The simple cases are easy to make no-code — filling a blank, picking from a list — and most tools already do them.
The wall arrives with real logic. This clause only for these clients. This section repeated once for each party. This language in one state, a different exception in another. At that point the tools stop being visual and hand the problem back to whoever can write the syntax.
The expertise was never really written down. It was written in a language the people who own it do not speak.
We think that trade costs more than it appears to. A rule only one person can read is a rule nobody can check. When it needs changing and that person has moved on, the safest thing anyone can do is not touch it — so nobody does, and the reasoning that went into it is gone.
That is the problem we build against, and it is not specific to any one profession. It shows up wherever expert work gets encoded into a tool: the people who understand the work cannot operate the system that holds it, and the people who can operate the system do not understand the work.
Where we apply it
We start with legal documents, because that is where the cost of the trade is most visible. A firm’s templates are its accumulated judgment, and when that judgment becomes unreadable the firm loses something it cannot easily rebuild.
Formixa is a document platform for law firms. An attorney takes a Word document the firm already uses, marks the parts that change and sets the rules — by clicking, not by writing code. From then on, anyone on the team can fill in the form.
That is a narrow thing to do, and we do it deliberately narrowly. It is also the hardest part of this category to build.
The principle is not narrow, though, and it does not end at documents. Documents are the first place we apply it, not the last.
Complex logic, operated by the people who own the work
One company, one principle, and products that are instances of it rather than a portfolio.
What we’re working toward
A template tells you what a document does. It does not tell you why it is that way — which clause was chosen over which alternative, and on what grounds. That reasoning lives in the partner’s head, and when the partner leaves, it leaves.
Because Formixa captures rules rather than prose, it already knows more than it currently shows. Every generated document could carry its own account of itself: the question, the answer, the rule that fired, the date. We want a firm to be able to open a document it did not build and understand why it says what it says.
Very little of that exists yet, and we would rather say so than imply otherwise. It is what we are building toward, and it is the reason we built the visible-logic layer first — you cannot record the reasoning behind logic nobody can see.
What a firm chooses to do with that record later is the firm’s business, not ours.
Show if state == "CA" and seller_note_amount > 0Venue shall lie exclusively in County Client County, California.
- AskedWhich state governs this agreement?
- AnsweredCalifornia — 3 March 2026
- RuleShow if · State is CA · seller note present
- Set byTemplate v4, published 11 Jan 2024
- Not usedTexas venue clause · condition not met
The same record that answers this question is the firm’s to export. It is not ours to learn from.
Illustration of intent, not a shipping feature.
How we work
The work stays yours. Your text is yours, and your decisions are yours too. The record of how a document was built — what was asked, what was answered, which rule applied — is what we are building toward. When it exists, it will belong to the firm that made it.
Logic only one person can read is logic nobody can check.
Build conditions from plain-language choices — pick a question, pick an answer. No code to write. Legibility is what makes logic checkable.The cost: it is far harder to build.
The interesting part of expert work is the decision, not the output.
Anyone can produce a document. What matters is the judgment that shaped it.The cost: designing for decisions is slower than designing for output, and pays off later.
Depth before breadth.
One practice area at a time. A tool shallow across twenty practice areas is useful in none of them.The cost: a slower path to a bigger market, chosen deliberately.
The work belongs to whoever made it — including the record of how it was made.
Not just the templates and clauses, but the decisions behind them. We are building that record for the firm to hold, not for us to mine.The cost: it forecloses the easiest version of the data business, on purpose.
Where we are
Formixa is early, and there is a great deal still to build. We would rather say that plainly than dress it up. The firms we want to work with can tell the difference, and they are choosing a platform they intend to be using in five years.
Questions? Email hello@formixa.io.