Ovirno. Try it on your data
01

The business operating system

Ask at any hour: what dropped, why, and what to do.

Orders, tasks, customers and invoices in one system. You ask out loud and the answer is computed from your own numbers while you wait — in sentences, not charts. Break a rule you set, and it writes first.

  • WooCommerce
  • Spreadsheet
  • Bank
  • Site counter
  • Telegram
  • Till
one core

What slipped this week?

Tuesday lunch — 640 zł against the usual 780.

Aggregator delivery is down: 4 orders instead of 9.

example

How was the week in money?

Revenue 11,130 zł, +12% on last week.

Margin 4,220 zł, +6% — growing slower than revenue.

example

the system wrote first

2,610 zł overdue from customers.

Two invoice tasks are due today.

example
client systems in production3
sources connected and syncing6
observations written by the AI analyst129
data stays in GermanyEU

Counted from the live database on 5 September 2026 — an order came through the system that same day. Client revenue is not published here: that is theirs to share, not ours.

02

Draw your screen

Tick what you want to see every morning — the phone next to it shows how it looks in the workspace. We build exactly that: on your data, no brief, no training.

what to show

Sources are our job: WooCommerce, spreadsheets and Excel, bank statements, the website counter, Telegram, the POS.

Or draw it by hand on a sheet of A4 and send a photo: a mock-up within two working days, the screen in your workspace within a week. The first screen is part of the start; the next ones come out of the subscription's development hours.

Send this screen

your screen · example figures of a coffee shop

9:41example

Wednesday 2 September

Revenue · this weekPLN 11,130 +12%from the POS and WooCommerce
Orders · this week212 +8%from WooCommerce
Website visits · 7 days1,664 +29%from the website counter
Tasks · open today7 −2%from Telegram
  1. A4 by handa photo to Telegram
  2. We write the codemock-up in two working days
  3. Your screen, livein your workspace within a week
No brief, no builder, no template — the screen you drew.
03

How it actually reaches you

Every hour it re-reads the numbers. It writes when a rule breaks, answers whenever you ask, and speaks up on its own once a week.

Tuesday

  1. :15Every hourre-reads the numbers
  2. 13:15Your rule fireslunch below its norm
  3. 13:17Your phone buzzesthe system writes first
  4. 13:18You ask whyby voice or in the browser
  5. 13:20One tapa task with an owner and a date

three minutes

Tuesday 13:17 · your phone buzzes

It noticed before you did.

Every hour, on the quarter, the system goes over the day again and puts each number against its own four-week norm. At 13:15 Tuesday lunch came in under it, and the rule you wrote yourself — if the average check falls below X, tell me — fired while the day could still be changed. Nothing was opened. Nothing was exported.

  • WooCommerce
  • Google Sheets
  • bank statement
  • CSV by link

13:18 · you ask why

You ask out loud. It answers with facts.

A voice message to the bot, or a question in the browser, in your own words. The answer is computed from your own orders while you wait, and it says how it was counted. This is the everyday road to your numbers, and it is open at any hour: you pick the moment, not a schedule.

13:20 · one tap

What the analyst suggests waits for your button.

Tasks
  • Check the Tuesday lunch operator schedulefrom an insight
  • Price check on the lunch setfrom an insight

Two tasks, drafted by the analyst out of what it found. One button on the observation turns a recommendation into a task with an owner and a due date. Dictating to the bot works too, with your hands full — but a dictated task goes on your own list; putting work on somebody else's goes through the web, with a name and a date. Three minutes from the buzz to work in progress — and the record keeps the reason it came from.

Monday morning · it writes first

Once a week, and that is a decision.

A letter that arrives every morning and is almost always the same stops being read — and the morning that mattered goes unread with it. So on its own initiative it speaks once a week, on Monday, while the week can still be changed; the other days, you ask. The same bot drops a card into the kitchen chat when an order lands — and the owner picks which fields it may show, because the whole shift reads that chat.

Ovirnoexample
Bistro Example · 30.08.2026
Выручка: 1 780 (+12% к прошлой неделе)
▂▃▂▄▃▅▄▆▅▄▆▅▇█
Заказы: 34 (+8%)
▁▃▂▄▃▄▅▃▅▄▆▅▆▇

По точкам:
Centrum ████████ 1 080
Podgórze █████░░░ 700

⚠ Просроченных задач: 2

Главное:
⚠️ Podgórze третью неделю ниже Centrum по среднему чеку — сверить обеденное меню точки
ℹ️ Средний чек держится третью неделю

The weekly letter, in the Russian the bot writes in — the shape the product actually sends, not a translation of it. Monday's letter reports on Sunday, with the fortnight behind it.

Ovirno · kitchenexample
🧾 Новый заказ · 13:41
№ 2149
Сумма: 44,20 zł
Состав: Сет дня, Мисо-суп и ещё 2
Город: Kraków
Клиент: повторный — 4-й заказ, до этого на 158 zł

A new order in the kitchen chat. Phone and address are off by default.

The analyst writes in Russian today. The workspace itself reads in English, Ukrainian, German and Russian — the machine's own sentences have not caught up yet.

  1. Voice noteTelegram
  2. Server memoryGermany
  3. TranscriptionMistral · Sweden
  4. Answerfrom your own numbers

the recording is never stored — there is nothing to delete

04

Six questions an owner asks

Everything in one place — and it tells you what to do.

01

Where is my money today?

Revenue, orders, margin and receivables for the week, month and year — against the same period before. Your own set of tiles.

02

What dropped, and why?

Ask, and it answers in sentences instead of charts. Every hour each metric is put against its own four-week norm; the rules on top are yours: if the average check falls below X, say so.

03

Where do the numbers come from?

WooCommerce in minutes, a published sheet on a schedule, CSV and Excel parsed for you, bank statements, your own webhook.

04

Who are my customers?

Purchase history, average check, buying rhythm, and who is going cold — measured from your data, not from a round number.

05

What do I do today?

A board with your own stages, a calendar, a call turned into agreements, and a feed of who changed what.

06

And all of it from my phone?

Installs to the home screen without an app store. Lists are cards, not tables. The bot answers in words.

This is the system those six answers live in.

Four screens open below. The rest of the menu stands as it is — the names, the order and the wording are the product's own, not a drawing of one.

app.ovirno.comexample

Wednesday 2 September

14 orders for PLN 743 · 3 due today · 2 overdue

Configure
Orders
212
+8% over 7 d.
Revenue
PLN 11,130
+12% over 7 d.
Gross margin
PLN 4,220
+6% over 7 d.
Receivables
PLN 2,610
−14% unpaid right now
Recent orders5 fresh
  • 2 Sept, 13:41M. KowalskaWebsiteDeliveredPLN 44.20
  • 2 Sept, 13:12P. WiśniewskiPhoneConfirmedPLN 32.90
  • 2 Sept, 12:38A. ZielińskaAggregatorNewPLN 74.80
  • 2 Sept, 12:05Office lunchB2BDeliveredPLN 129
  • 2 Sept, 11:47E. NowakWebsiteCancelledPLN 41.30
Who to touch today6 awaiting attention
  • A. Zielińskagone cold
  • Office lunchno contact for 41 d.
  • M. Kowalskatime to reach out
Search orders…All channels ▾All locations ▾ApplyExport CSV
DateCustomerLocationChannelStatusTotal
2 Sept, 13:41M. KowalskaCentrumWebsiteDeliveredPLN 44.20
2 Sept, 13:12P. WiśniewskiCentrumPhoneConfirmedPLN 32.90
2 Sept, 12:38A. ZielińskaPodgórzeAggregatorNewPLN 74.80
2 Sept, 12:05Office lunchPodgórzeB2BDeliveredPLN 129
2 Sept, 11:47E. NowakCentrumWebsiteCancelledPLN 41.30
2 Sept, 11:20K. LewandowskiPodgórzeWebsiteDeliveredPLN 26.70
2 Sept, 10:58J. KaczmarekCentrumAggregatorDeliveredPLN 61.50
2 Sept, 10:31M. WoźniakCentrumIn-storeDeliveredPLN 38.90
2 Sept, 10:04T. SzymańskiPodgórzePhoneConfirmedPLN 55.20
2 Sept, 09:38B. DąbrowskaCentrumWebsiteDeliveredPLN 55.90
Rows per page 101–10 of 212BackNext
MineAllDoneWeekBy peopleBoard

7 in progress · 2 overdue · 3 done today

TaskAssigneeOriginDue
Call the supplier about Friday's invoiceMaxmanually2 days overdue
Check the Tuesday lunch operator scheduleMaxfrom an insighttoday
Price check on the lunch setOlafrom an insighttomorrow
Call the twelve regulars who went quietAnnaautomaticallyin 3 days
Что просело на этой неделе и почему?Какая точка тянет вниз за последние 7 дней?Реклама окупается? Покажи ROAS за неделю.
Why did Tuesday lunch dip?

Обед во вторник: 640 zł против нормы четырёх недель 780 zł — разрыв 18%. Заказы с сайта держатся; просела доставка через агрегатор: 4 заказа против обычных 9. Считал по четырём вторникам до этого.

Например: почему в субботу просела выручка?

The analyst writes in Russian today. The workspace itself reads in English, Ukrainian, German and Russian — the machine's own sentences have not caught up yet.

Real screens and real wording; the figures are made up. A client's revenue does not go on a landing page without the client.

The phone is the main screen

Nobody sits down to work in a system. You get a minute standing up, phone in one hand. So the phone is not a smaller desktop: cards, large targets, four sections at the bottom and everything else behind “More”.

All six questions, in detail →

9:41example

Wednesday 2 September

PLN 743

14 orders · 2 overdue

Who to touch todayA. Zielińskagone cold
TasksCheck the Tuesday lunch operator schedulefrom an insight
DashboardOrdersTasksCustomersMore
05

What Ovirno actually is

A platform, an analyst, and the hours of the engineer who builds both.

01

The system of record

Orders, tasks, customers, invoices, calendar, booking page. Fed by your store, your sheets, manual entry. CSV export is a button.

02

The AI analyst

Answers out loud whenever you ask, computed from your data. Watches the numbers hourly and writes when a rule breaks. Goes through the whole business when you press the button. Turns calls into tasks.

03

Development hours

One package of hours, spent wherever the month needs them: a connector, a report, your site, your ads. Balance visible in the system.

  1. 01SourcesYour store, spreadsheets, bank statements, the site counter, Telegram, the till.
  2. 02One modelOrders, customers, invoices and tasks in a single shape, with a note of where each came from.
  3. 03Metrics as codeFifteen metrics computed by code on a schedule. The language model never does the arithmetic.
  4. 04Workspace and botA role sees its own screen. The analyst explains the numbers it was handed — it does not invent them.
Every number remembers the source it came from.

And what it honestly doesn't

Systems in production: 3. One engineer, no sales team.

  1. Nothing goes out that you did not switch on. Mail to your customers — booking confirmations, reminders, review requests — only after you turn that channel on; it is off until you do. What the analyst suggests waits for your button.
  2. It doesn't invent numbers. No sales yesterday means it says there were none.
  3. It doesn't read your papers for you. Documents, mailboxes and chats are searched for supporting passages and quoted back — but the answer is still counted from numbers, not composed from your contracts.
  4. It isn't a company of forty people. One engineer in Tallinn — which is why the person on the audit call builds your system.
06

How it starts

You show us your process. We move it onto the system.

No migration project, no six-month rollout. Phase 0 goes live on your real data in days.

  1. 0130 minutesfree
  2. 02in daysat cost
  3. 03every daysubscription
step 01 · free

Show the process

Thirty minutes: how orders come in, where numbers live, what drives you mad. You leave with an honest picture.

step 02 · at cost

Phase 0

The first working piece on your real data, at cost. You judge a live system, not slides.

step 03 · from €99/mo

Run and grow

The platform runs daily; hours improve it where the business needs them.

What those thirty minutes are

  1. 0–3 minYour organisation is created: name, currency, and the areas you actually work in.
  2. 3–5 minYou get a login and a bot code, and start looking around while we load the file.
  3. 5–12 minYour export is imported. The mapper proposes the columns; money and dates get checked by eye.
  4. 12–15 minMetrics recompute themselves. The dashboard fills up with your numbers.
  5. 15–20 minYou press “refresh observations” and the analyst walks your business, coming back with three to seven of them.
  6. 20–25 minYou link the Telegram bot and ask it something out loud.
  7. 25–30 minWe talk through what it noticed and decide whether there is a next step.

If your file has fewer than fifty rows the observations will be thin. We will say so out loud instead of dressing it up.

Kodawari OÜ is not registered for VAT: nothing is added on top of these figures, and there is no input VAT for you to reclaim.

connects to
  • WooCommerce
  • Google Sheets
  • CSV by link
  • Bank statements
  • Webhooks
  • Telegram

…and anything with an API — that is what the hours are for.

07

Proof, not promises

Businesses run on this today. Names and figures publish after the client signs off on every one of them.

Lithuaniae-commerce

  • WooCommerce
  • Telegram
  • sales sheets
  • AI analyst
  • weekly letter
  • meetings → tasks
  • voice assistant

Polandfood delivery

  • WooCommerce
  • Google Ads
  • Telegram bots
  • online payments
  • checkout fixed
  • a bot per pickup point
  • ads tied to revenue
sources → one core → what runs today

e-commerce · Lithuania

Functional drinks brand

WooCommerce orders in one system, a weekly letter of what changed and why, meeting transcripts turned into assigned tasks, and a voice assistant for a founder who prefers to stay out of dashboards entirely.

  • WooCommerce
  • Telegram
  • sales sheets
  • AI analyst

food delivery · Poland

Sushi delivery, several pickup points

A production store where a silent checkout failure was quietly costing orders. Fixed, then wired: a Telegram bot per pickup point, and ads connected to revenue so spend is judged by returns rather than clicks.

  • WooCommerce
  • Google Ads
  • Telegram bots
  • online payments

See the pilots →

08

Who builds it

One engineer. No handoffs.

Built through Kodawari OÜ, a one-person systems studio in Tallinn. The person on the audit call builds your system. You never re-explain your business to an account manager.

The name is the Ukrainian «О! Вірно!» — “oh, right” — the moment the numbers add up and the next step is obvious.

About the studio →

Oleksandr Tsurkan

Founder · systems engineer

tg
@agtsurkan
web
tsurkan.eu
base
Tallinn · EET

Where everything lives

  1. Tallinnthe engineer · Kodawari OÜ
  2. Germanyour server · your data
  3. Swedenvoice transcription · Mistral · the recording is not stored
  4. Irelandfallback for transcription
  5. Lithuanialive system · e-commerce
  6. Polandlive system · food delivery
All six points are inside the EU.

One step

See it on your own numbers.

Bring one export from your store. The first read of your business is computed from your data, not from a demo. Nothing to sign.

No newsletter, no sales sequence. One reply from the person who builds the system.

Or write on Telegram →
Try it on your data