Fleet, tickets with deadlines and invoicing in one system: the dispatcher sees the office, the technician sees the day's route on their phone.
Tickets with deadlinesFleet and routesInvoice from the work orderDemo available
Track 01 · Platforms and ERP
Fleet, tickets, timesheets and invoicing,first module in 60 days
Fleet, tickets with SLAs, timesheets, invoicing, stock — built around your workflow, not around a template. The first module goes live in 60 days or less.
What runs on this track
5 projects
A transparent proxy in front of MCP servers that records every tool call and puts a cost on it, per model and per team.
My own productCost per callRecurring billing
From lead to signed quote, contract, work order and an invoice filed with the tax authority — in a single flow.
ANAF e-invoicinge-TransportStock and receivingDemo available
Trips, drivers and site work sheets, from which timesheets and payroll are calculated.
Trips and mileageTimesheets and payrollFinancial dashboard
Support for addiction, with an account without a name, saved conversations and a daily usage budget.
Conversation without a nameSubscriptionTools for cravings
How we work
3 steps01
We map the current workflow
A day with the people who do the work, not with the org chart. What comes out is a list of modules, ordered by how much each one hurts.
02
We deliver module by module
The first module goes into production and gets used. The rest settles on top of it, instead of arriving in one big bang at the end.
03
We keep it running
Hardening, backups and monitoring are part of the delivery. They are not sold separately.
Twenty minutes and you know
You describe the workflow, I tell you whether it is doable, what price range it sits in and how long it takes. If I am not the right person, you find that out too.