CodFleet Oy · Helsinki · Building since 2025

Every service business
runs on a number
nobody ever checked.

How much to prep. Who to put on the floor. What it costs when the answer is wrong. CodFleet builds the intelligence layer underneath those decisions — starting in restaurant kitchens, where being wrong is measured in kilos and hours, every single day.

See what we're building How the loop works

The gap / 01

Nobody is short of effort.
They're short of the number
that would have changed the decision.

Operators

The forecast is a feeling

On Tuesday you prep for Friday. Nobody wrote down what happened last Tuesday, so you prep for the Friday you remember — the busy one. Then you throw away the difference and call it the cost of business.

A quiet day with a full roster and a full prep list costs more than an empty room.

Workers

Finding work is harder than spending it

Spending money takes one tap. Getting paid for a skill takes a CV, a portal, a form, an interview, and three weeks of silence. The friction sits entirely on the side that can least afford it.

Meanwhile the shift that needed filling went unfilled at 17:00.

Customers

You pay twice for the same table

An intermediary charges the customer to find the business, and the business to be found. Neither side chose it. The price goes up, the margin goes down, and the connection was never the hard part.

The hard part was knowing there'd be a table free at 19:30.

The loop / 02

One signal. Three products.
It closes on itself.

Most companies would build three businesses here. We build one system with three surfaces, because each one produces the data the next one needs. Here is a single Tuesday, moving through it.

ONE SYSTEM Orbis DECIDES Fleet STAFFS Go SELLS

Tuesday · one kitchen · one signal

Orbis
Reads the last four Tuesdays against weather, bookings and the till. Forecast: 196 covers, not the 240 the owner remembers.
Orbis
Rewrites the prep list and the roster. 14 kg of protein instead of 20. Three on the floor instead of five.
Fleet
17:00 opens up when someone calls in. The shift goes to a verified sole trader already working in the zone — no agency, no markup.
Go
Tables and pre-orders come in direct. The customer pays the menu price. The kitchen keeps the commission it would have lost.
Orbis
Service closes at 201 covers. Waste, hours and margin land back in the model, and Tuesday is a little less of a guess next week.

Each surface earns its place by producing the data the next one needs. That is the whole reason there are three, and the reason there will never be a fourth that doesn't.

First market / 03

Orbis is being built
inside working kitchens.
Not in front of them.

We didn't survey restaurant owners. We worked the pass. Orbis connects front of house to the kitchen to inventory, so that what was prepped, what sold and what got thrown away are finally the same conversation — and next week's roster is written from it.

ORBIS · SERVICE VIEW · TUE 14:20 MODEL SYNCED

Covers

Last 6 Tuesdays · forecast today

188
203
176
211
194
199
196

Owner's instinct said 240. Six Tuesdays of till data say 196. The gap is four hours of labour and a full tray of prep.

Prep & waste

Prepped vs sold vs dumped

Protein14.0 kg −6.0
Mise, cold9 trays −2
Bread60 pcs +8
Yesterday's waste€96 −41%

Waste isn't estimated. It's what's left when you subtract sold from prepped — so it finally has a number attached to it.

Shift plan

Written from demand, not habit

Kitchen 1
Kitchen 2
Floor 1
Floor 2
Late cover

Roster cost today: €1,284. Same service, planned by memory last Tuesday: €1,610.

Interface in development · figures shown are illustrative of the model, not customer data

The fleet / 04

Three products.
Built in the order
the data allows.

We ship them one at a time, and we say plainly where each one stands. A roadmap you can check is worth more than a roadmap you can admire.

In build · design partners confirmed

Orbis

Operational intelligence

One system that runs the floor, the kitchen and the stock room off the same numbers — and plans next week from what actually happened this one.

  • Front of house, kitchen and inventory on one connection
  • Waste derived from prep versus sales, not guessed
  • Shifts and payroll planned from demand history
  • Hygiene, temperature and prep compliance logged as you work
Partner on the beta →

Specified · build follows Orbis

Fleet

Workforce intelligence

The shift Orbis says is missing, filled by a verified independent professional already working in that zone — with the contracting, invoicing and compliance handled underneath.

  • Verified Y-tunnus professionals, routed by zone
  • Built to the EU Platform Work Directive, not retrofitted to it
  • Bookings, clients and invoices in one place
  • Uusimaa mapped as four operating zones for launch
In development

Registered · consumer build in progress

Go

Demand, direct

Where the customer books the table, the cleaner or the delivery — without a commission layer deciding what it costs and who gets seen first.

  • Tables, pre-orders and home services in one app
  • Menu price to the customer, margin to the business
  • Demand feeds straight back into the Orbis forecast
  • Live company entity registered in Finland
In development

Where we actually are / 05

No market-size slide.
Our own numbers instead.

3

Helsinki restaurants building Orbis with us — where the founder has worked the kitchen himself.

7,847

Pages of Finnish and EU legal guidance read into the compliance framework the products are built on.

30

People building across Helsinki and India — engineering, data, QA and design.

4

Operating zones mapped across Uusimaa, the launch region before the Nordics and Baltics.

Why it's built this way / 06

Vyūha

Sanskrit
Arrangement · formation
One entity, many forms

The name for the idea that one thing can take several forms without becoming several things. Each form is complete on its own. Each one serves the whole.

That's the test every product has to pass here. Orbis, Fleet and Go are not a portfolio — they're one system seen from three sides: the business making the decision, the person doing the work, the customer who shows up. Anything that doesn't feed the loop doesn't get built.

We're not raising.
We're instrumenting
kitchens.

If you run a restaurant in Helsinki and you're tired of finding out on Sunday what Tuesday cost you — that's the conversation we want. Design partners get the beta early, and get to shape what it does before it hardens.