Why this is built the way it is

Ask a language model for a gross margin and it will give you one. It will be formatted correctly, phrased confidently, and occasionally wrong in a way that is invisible until someone reconciles it. The failure is not that models are unreliable at arithmetic — it is that the output carries no trace of how it was produced, so a reviewer has no way to tell a right answer from a wrong one without redoing the work.

So the model does not do the arithmetic here. It reads the question, decides which deterministic calculation answers it, and explains the result. The calculation is ordinary code operating on your ledger, returning a value with its inputs, its assumptions, and its steps. The division of labour is deliberate: models are good at understanding what was asked, and unnecessary for computing a ratio.

The same reasoning drives the rest of the architecture. Tenant isolation is enforced by the database rather than by application code remembering to filter, because “we always remember” is not a security control. A query that forgets its tenant context raises an error rather than returning nothing, because a silent empty result would ship. Money is exact decimal rather than floating point, because a ledger that is occasionally off by a cent is a ledger nobody trusts.

None of that is novel. It is the ordinary discipline of financial systems, applied to a category of software that has largely skipped it.

We will not present a model-generated figure as a verified fact. Answers distinguish between what was retrieved, what was calculated, what was assumed, and what is interpretation.

We will not claim a certification we do not hold. The security page states plainly what is implemented and what is not.

We will not list an integration as available before it works. The integrations page separates what runs today from what is designed.

MazeCFO provides analytical support. It is not a substitute for licensed financial, legal, tax, audit, or investment advice, and no output from it should be treated as one.

Registered entity details, team, and location are not published here yet. For procurement, vendor review, or due-diligence purposes, request them via the contact page and we will provide them directly.