The tier follows the task, not the size of the company.
Three products. Choose by what is breaking.
Request intake, an app for work away from the desk, an operations system. Each one has a price, a scope and a timeline.
- Request intake One place where requests from the website, from a phone call and from a message all land — with one status, one owner and one notification.€800
- Mobile app For people who do not work at a desk: the task is opened and closed on site, and the office sees it immediately.€2,500
- Operations system When a process no longer fits in one person’s head: the process itself is rebuilt, not just request intake.from €6,000
Three products. Choose by what is breaking.
The tier follows the task, not the size of the company.
€800
Request intake
One place where requests from the website, from a phone call and from a message all land — with one status, one owner and one notification.
First release from 7 working days
What is included and what is billed separately€2,500
Mobile app
For people who do not work at a desk: the task is opened and closed on site, and the office sees it immediately.
Timeline by scope
How it worksfrom €6,000
Operations system
When a process no longer fits in one person’s head: the process itself is rebuilt, not just request intake.
Timeline by scope
What this tier covers
WHICH ONE
Which of the three is yours
-
Requests arrive from the website, by phone and over WhatsApp — and sit in three different places. Everything else works.
Request intake, €800. Nothing else has to be rebuilt. -
Your people do not work at a desk. What has been done, you find out in the evening or the next day.
Mobile app, first module €2,500. Data reaches the system at the moment of work. -
You are the only person who knows how the whole process works. When you are away for two days, work piles up.
Operations system, from €6,000. The process itself is rebuilt. -
Your process cannot be read over the phone, but it does not need several days of observation either: one working day is enough to see the full cycle.
On-site review — one day, €1,200. A day at your site and a written document that is credited towards the project. -
None of the four points describes your situation precisely.
Take the self-check on the site: it runs automatically, and at the end you can describe in your own words what is not working.
IS THIS YOU?
Is this you?
Four situations. Each one states what we built next to it — and what it does not cover.
Trades — plumbing, electrical, roofing, construction
- The request lives in your head until the evening, until you write it into the spreadsheet. Some evenings never come.
- The customer called a second time because nobody called back the first time.
- What was done on site and when comes up half a year later, when a warranty claim arrives.
- Weather moves the schedule, and the crews are re-planned from scratch, on paper.
- Material is ordered from memory. Sometimes twice.
What we built next to this
One list that everything lands in: the request from the website, the phone call and the message — with one button. An employee app with the day plan and a checklist. Working-time records that cannot be rewritten after the fact without a trace. A service record for completed work, signed on site, with time and date — the entry is assembled from the employee’s actual time and the planned work. Vehicle repair history with documents and prices, control of TÜV and insurance dates.
What this does not cover — plainly
- Material calculation and a price calculator are not included in the €800: that is separate work based on your formula.
- Weather-driven re-planning of crews we have not built for anyone. If that is your main pain, say so in the first conversation and we will tell you whether we take it on.
- We have no trades case study on this site: the closest thing you can look at is the operations system of a mobile care service.
Look at first: mobile care service case — fleet, employee app, signed service recordsStart with: request intake, €800
Hospitality — restaurant, café, bakery, small chain
- Purchase prices changed three times this year. The menu was recalculated once, by eye.
- You do not know which dish makes money and which one is on the menu out of habit.
- Reservations run through an external service that takes a commission and knows nothing about the till.
- Catering orders, cakes for a date and ordinary orders sit mixed together in one WhatsApp, and deadlines get confused.
- Each location has its own till and its own shift records, and reconciliation happens once a month, by hand, across three spreadsheets.
What of this we have already built — and you can open it
kartulirest.de — a restaurant in Germany; the platform was built in 3 months: till and open bills, kitchen tasks, cook statistics, menu, recipes and semi-finished products, dish costing and break-even point, delivery zones with geocoding, reservations and tables, working-time records, payroll with an audit log, financial postings and recognition of financial documents, campaigns, customer balance, mobile app. The working-time module is also in use in other restaurants.
What this does not cover — plainly
- Nothing is ordered automatically: stock is tracked and written off against the stored recipes, and once minimum levels are reached the system compiles the purchase list and derives a recommended selling price from the same costing. Ordering and pricing are decided by an administrator.
- A shared online overview of several locations on one screen is not something we offer as a ready module. The kartulirest.de platform is one location; end-to-end analytics across several businesses exists for us only in a closed project we can speak about in general terms only.
- If you have three locations, that is a conversation about design work, not about a ready-made button.
kartulirest.de — you can open itLook at first: case studyStart with: one location — operations system, from €6,000
Ambulatory care and mobile services
- Tours are assembled by hand in the morning. One sick note — and everything is re-planned on paper.
- What was done at the patient’s home reaches the office a day or two later.
- Reporting to the payer is compiled by hand, because the data arrives late.
- The industry software covers documentation — and does not cover everything else.
- Practice appointments and the field schedule are kept separately, and every two weeks they collide.
What of this we have already built
The system calculates the route and the travel time between patients itself, from map data, and then corrects it against actual data from the employee app. The patient signs the delivered service on a tablet at the moment of delivery; the record is assembled from the employee’s actual time with the patient and the service foreseen in the plan. The patient record is linked to the payer — Pflegekasse, Krankenkasse or Sozialamt — with the stated number of billable hours and a check against that limit during planning. A patient appointment calendar instead of a paper diary. Employee app: day plan, checklist. Fleet: before, a dedicated person transferred odometer readings from WhatsApp photos into a spreadsheet; now the odometer photo is taken in the app, readings are entered automatically, mileage is reconciled against plan and fuel use, with repair history including documents and control of TÜV and insurance dates.
What we do not claim — plainly
- We do not claim that our system performs the Abrechnung with the payer, or that a digital Leistungsnachweis is accepted by a particular Kasse, by the Sozialamt or by an inspecting authority. We built the signature for a delivered service and the link to the payer; recognition of the document by a third party is not our claim.
- The time stamp at the start and at the end of a task is described separately and in full on the app page. The legal basis for introducing it remains yours.
- We have not built a system in which practice appointments and the field schedule live in one calendar: consulting-room appointments and home visits we implemented in different projects. Joining those two flows is design work, not a ready module.
- Separating GKV and PKV and the document flow under Heilmittelverordnung we have not done.
Look at first: mobile care service caseStart with: process review — formats, prices and limits
Manufacturing — made-to-order and small batch
- There is no single place showing which stage each order is at: drawing, material ordered, in production, done.
- The shop floor stands still because material for a specific order was ordered late.
- Every order arrives with its own file, and file and price approval runs by email, separately from production.
- Shift planning and load are not connected to the actual order volume.
- It has to work on a tablet on the shop floor, not like an office program.
What of this we have already built
Made-to-order manufacturing, US, anonymised. Before: requests by email, tasks on paper, long approval cycles between order and production. Built: a chat with 3D file viewing and approval of file and price; automatic distribution of orders by metal type and shape; automatic assembly of the product tree; integration with the 3D printer — casting moulds are ready before the shift arrives. First response to an incoming order: 1 day → 15 minutes. Headcount over the period 7 → 13. Employee app with day plan and checklist. Time records that cannot be rewritten after the fact without a trace.
What this does not cover — plainly
- This is jewellery manufacturing, not Metallbau and not food production. What transfers is the mechanics — routing an order by material and shape, approving file and price inside the system, visibility of the stage — not the industry experience. We do not claim to know your production.
- Purchasing material for a specific order we have not automated for anyone.
- Batch accounting and traceability — which raw batch went into which batch of finished product — we have not built. HACCP document flow we have not built. We hold no certifications in the food industry. If that is your task, we are not a fit for you today, and we say so before the conversation, not after.
- Line load planning against order volume we have not built. The closest thing we have is working-time records with holidays and day statuses, and planning from actual app data on routes. That is not the same thing, and we do not present it as the same thing.
Look at first: made-to-order manufacturing caseStart with: process review — formats, prices and limits
No block claims industry expertise: each one describes mechanics you can check in the case study.
When you do not need us
- The task can be solved with an off-the-shelf tool you have not tried yet. We will say so directly and will not take your money.
- You need an online shop: that is a different specialisation, and we do not work in it.
- You need only design, or only text, without a system behind it.
- Your procurement rules require a commercial register extract and a USt-IdNr. Today we can provide professional liability insurance, readiness to sign an AV-Vertrag, and handover of the source code. A register extract and a USt-IdNr. we do not have.