/ SOURCES
Every Book Finance Keeps
Cost sheets, ledger exports, budgets and invoices, uploaded as files or synced from the database behind them on a schedule you set. norami only ever reads them.
/ solutions / Finance & Accounting
Cost sheets, the ERP ledger and sales invoices, joined. See where margin moved and which cost line moved it — with the file and the exact query behind every figure.


Put cost per kilo, budget variance, supplier costs and customer margin on one model of your books — so finance, operations and sales argue about decisions, not about whose spreadsheet is right.
Join sales invoices to the month's cost file and ask where margin was made or lost, then check the rows behind each figure.
[ IN THEIR WORDS ]
“At Seajoy we compare, pond by pond, what an extra week of growth is worth against what it costs to wait. By hand that’s half a day of work for a single pond, which is why it never got done. Now it runs every week.”
[ YOUR FIRST ANSWER ]
Pick one — the variance nobody can explain, the cost per kilo that moved after the close, or the customer who looks profitable until freight is counted. We'll show how norami connects your cost sheets, ledger and invoices and traces the answer back to its source.
Bring one decision your finance team is working through, from a variance to a customer's true margin.
We identify the cost sheets, ledger exports, invoices, or databases that hold the relevant records.
See the answer alongside its source and the exact query, so your team can verify the numbers.
[ THE PLATFORM ]
Three layers, one workspace: your cost sheets and ledger in, one model in the middle, answers the whole team can check.
/ SOURCES
Cost sheets, ledger exports, budgets and invoices, uploaded as files or synced from the database behind them on a schedule you set. norami only ever reads them.
/ WORKSPACE
Revenue, cost lines and margin mapped once, and a finance assistant that can only query the datasets linked to it.
/ ANSWERS
When the corrected close file lands, saved questions keep working on the new numbers — and you can see what changed, with the rows behind it.
[ SECURITY ]
What protects your orders, prices and customers today — each control described on our security page, in plain terms.
Each customer's data is scoped to its own workspace, with Row-Level Security switched on for every table.
norami never writes to your ERP or database. Sessions are read-only, and queries are single SELECT statements with row caps and timeouts.
Each team reaches its own assistant, and an assistant can only query the datasets linked to it — checked on the server for every query.
Sign-ins, access changes, uploads, connections and exports go to an append-only, hash-chained log.
No. norami reads the ledger exports, cost sheets and invoices you already have and answers across them. Your ERP stays the system of record, and norami never writes to it.
It can put them side by side when both are in your workspace: ask where actuals differ from budget and every answer shows the rows it used from each. Deciding what the variance means stays with your team.
Drop it in, or let the connected database sync on its schedule. Saved questions keep working on the new numbers, and a refresh that looks wrong — rows vanishing, columns changing shape — is held for review before it reaches anyone.
Everyone you invite, with a role that matches their job. Assistants are grouped by department, so finance reaches the finance assistant and the datasets linked to it.
No. Ask in plain language, typed or by voice. The exact query is there for anyone who wants to check it.
[ Get started ]
Tell us about your data and we'll get in touch to arrange a walkthrough. Prefer to explore on your own? Create your workspace and bring your data in minutes.