Where is my money today?
Revenue, orders, average check, margin and receivables by week, month and year — fifteen metrics computed as code, not typed into a slide.
01
Features
Everything in one place — and it tells you what to do.
One system instead of five open tabs. Everything in one place is the easy half. The second half of that sentence is the part nobody does.
- for businesses of 10–70 people
- delivery · retail · services
- hosted in Germany
- from €99/month
02
Six questions an owner asks
Six answers the system gives. Below, each one in detail.
What dropped, and why?
Every hour the numbers are re-read and three detectors run over them. It reports in sentences, and the rules on top are yours.
Where do the numbers come from?
Store, published sheet, CSV or Excel, bank statement, your own webhook, a form on your site. Repeat rows do not double.
Who are my customers?
History, average check, and the rhythm each one buys at — measured from your data rather than from a round number.
What do I do today?
A board with your own stages. Tasks arrive from four places: a person, a rule, an observation you accepted, or a call taken apart into agreements.
And all of it from my phone?
Home screen, no app store. Cards instead of tables. A bot that answers in words and brings a new order into the kitchen chat.
03
In detail
The same six, in the same order — answers this time, not questions. Written from the product's code, not from a drawing of it: where the code says something less impressive than the pitch, the code wins.
- 01SourcesYour store, spreadsheets, bank statements, the site counter, Telegram, the till.
- 02One modelOrders, customers, invoices and tasks in a single shape, with a note of where each came from.
- 03Metrics as codeFifteen metrics computed by code on a schedule. The language model never does the arithmetic.
- 04Workspace and botA role sees its own screen. The analyst explains the numbers it was handed — it does not invent them.
01
money
Fifteen metrics, recomputed every hour
Fifteen metrics are computed as code and materialised every hour: revenue, orders, average check, gross margin, ad spend, ROAS, cost per order, incoming and outgoing money, receivables and overdue, new and repeat customers, delivery time, tasks. Week, month and year sit one control apart.
Comparison against the same period a year ago lives in its own section, and it switches itself on when last year's baseline is entered — a section that would show empty is worse than no section.
- Week, month and year from one control
- Fifteen metrics computed as code — the same definition on screen, in CSV and in an answer
- A recount every hour, and a deep recount of the whole window once a night
- Year-over-year appears when last year's baseline is in — not behind a toggle
02
reasons
Detectors hourly, the deep read on your button
At quarter past every hour the pipeline recomputes your metrics and runs three detectors over them: a jump outside the usual spread, a fall against last week, and any threshold you set in your own words. What it finds goes into the feed and into alerts.
The full walk through the business — the one that comes back with three to seven observations — runs when you press “refresh observations”, not on a timer. That was a deliberate call: an essay written every night at nobody's request is an essay nobody reads.
- Hourly detectors: spread, week-over-week, and your own thresholds
- Rules in your words: if the average check falls below X, say so
- Business health — where the business leaks money and data, one scale, with the price of each hole
- Deep analysis on your button, on the observations page
03
sources
Six ways in, none of them a migration
Six ways in, and none of them is a migration project. A WooCommerce store arrives by webhook in seconds and is pulled again every five minutes in case the webhook did not make it. A published sheet by link is re-read on a schedule. CSV and Excel are parsed with the columns proposed for you, and the mapping is remembered. Bank statements come as camt.053 or CSV. Your own webhook takes rows from Zapier, Make or a script. A form on your site drops straight into the system — the form on this page uses that same door.
Google Ads, Zoho Books and ClickUp are wired and normalised but still run on fixtures: the shape of the data is right, the live connection waits on their OAuth. There is no till integration, and we do not pretend otherwise.
- Store, sheet by link, CSV or Excel, bank statement, webhook, a form on your site
- Repeat rows do not double — deduplication by hash of the canonical row
- Every record keeps a reference to where it came from
- A changed column layout raises a human-readable error instead of silent nonsense
04
customers
Buying rhythm, measured from your own data
Purchase history, average check, and the rhythm each customer buys at. The point at which someone counts as going cold is computed from your own data — the median gap between repeat purchases, then one and a half of it for “cooling” and three for “cold”. Under twelve repeat customers it says plainly that it is falling back on a general rule instead of quietly pretending to know.
Beside the list live the people who reached checkout and stopped, a waiting list that is not a paper note, and reviews asked for after delivery.
- A cooling threshold measured from your data, with the measure shown next to the badge
- Abandoned payments — the people who reached checkout and stopped
- Reviews after delivery: five stars go to your map listing, four and below come to you
- A manager sees their own locations and nobody else's
05
work
A board, a calendar, and four honest origins
A board with your own stages, a calendar of tasks, calls and customer touches, and a feed that records who changed what and when. Tasks arrive from four places, and the record keeps which: entered by a person, raised by a rule, accepted from an observation, or pulled out of a call transcript as an agreement with the quote attached.
What the analyst suggests is a suggestion until somebody presses the button. That is the line the product does not cross.
- A board with your stages, a calendar, and a list that can be sorted and exported
- Four honest origins on every task: person, rule, observation, call
- An event feed — who changed what, and when
- A call transcript turned into drafted tasks, with the quote each came from
06
phone
The phone is the main screen, not a smaller one
Nobody sits down to work in a system. You get a minute standing up with the phone in one hand, so the phone is not a smaller desktop: four sections at the bottom, everything else behind “More”, cards instead of tables, and targets you can hit without aiming.
It installs to the home screen without an app store. A form keeps its draft if the connection drops mid-sentence — and secrets and other people's personal data are kept out of that draft on purpose.
- Installs to the home screen — no store, no download
- Four sections at the bottom, the rest behind “More”
- A dropped connection does not eat what you typed
- The Telegram bot answers in words and drops a new order into the kitchen chat
The workspace itself — real screens, real wording, made-up figures marked as examples — is on the home page.
04
Draw it on paper
Your screen, the way you drew it.
No brief to write and no builder to learn. Take a photo of the sheet and send it to Telegram or e-mail; the rest is our job.
- A4 by handa photo to Telegram
- We write the codemock-up in two working days
- Your screen, livein your workspace within a week
- What you drawA sheet of A4: which figures you want to see, in what order, what is big and what is small. Pen, pencil, a photo of the whiteboard — anything we can look at.
- What you getWithin two working days, a mock-up of your screen in the system's own style. Say yes, and within a week it is live in your workspace on your real data — the way you drew it, not the way a template thought you should have it.
- What it costsThe first screen is part of the start. The next ones come out of the development hour already in every month of the subscription, or out of a package.
Send the photo to @agtsurkan on Telegram or to hello@ovirno.com.
One thing we say before the mock-up
- A figure that is not in your data can be drawn, but not shown. We say so on the first day, before the mock-up — not after it.
05
Your data is yours
One button in Settings, and the whole business is on your disk.
It is a button and not a written request within thirty days, because a promise cannot be pressed. Everything below is in the archive on the day you ask for it.
- tables/*.csvFifty-three tables, row by row. Semicolon-separated with a byte-order mark, so Excel opens them on a double click without mangling anything.
- overview/*.mdThe same business in words and markdown tables — the archive has to be readable by eye, not only by Excel.
- documents/*.md · meetings/*.mdYour documents and call transcripts, one file each, in the markdown they were born in.
- README.mdWhat every file in the archive means.
- MISSING.mdAn honest list of what is NOT in the archive. That file matters more than the first one: “everything” without a list of exceptions is advertising.
The small print, which is also true
- Access keys to your own external systems are not in the archive. They are cut from the export and scrubbed from every cell — an archive lives on a disk for years, and keys have no business being there.
- Column headers in the archive are Russian today. Say the word and that moves up the list; pretending otherwise would be a surprise on the day you open the file.
- Every organisation is isolated at the database level — row-level security, forced — rather than by application logic remembering to filter.
- The system runs in Germany. The company behind it is Kodawari OÜ, Tallinn, Estonia.
06
What it costs
No price per person. Giving the whole team access costs nothing.
the platform, per month — the whole system€99
development hours, per hour, in packages€50–120
a single hour, no package€150
per employee — access for the team€0
One hour of development is already inside the monthly platform fee. There is no per-person line on the invoice and no module configurator — the features are the same for everyone, and the figure moves with scale, not with a checklist.
07
What we don't promise
We are the management layer: where the money is, what dropped, and what to do about it.
- We don't do your bookkeeping and we don't file your reports. We hand your accountant the invoices, payments and orders as CSV for the period they asked for.
- We don't calculate payroll and we don't keep timesheets. Staff rotas are a stub in the code and deliberately not shown as a section.
- We don't take payments for you. The money goes to you directly, through your own provider.
- We don't replace your till and we don't run your kitchen. There is no POS integration.
- There is no support department and no night shift. The person who answers is the person who built it — which is the point, and also the limit.
Everything else stays with the people and the tools that already do it well.
One step
Show me your numbers.
Send one export from your store. In about thirty minutes you are looking at your own business inside the system — not at a demo account with somebody else's data.
Free, and it ends with an honest picture even if we stop there.