I build Fikst, software for installation companies, and work as an SAP consultant. With AI, every day.
A selection of what is running, not the full list.
fikst. ◇ the planning board
The planning board from the Noordkoel demo: per day the crews, who is still free and which job sits where. You drag a job to another day or crew. And because Fikst is built agent-native, an agent can do the same through that MCP layer. More at fikst.app.
beforeThe planning on a whiteboard and in someone's head.
nowEvery crew and every job on one board.
fikst. ◇ the quote
The customer gets a link, reads the quote online, chooses and signs. With your own logo and photos, and the amounts come from the same system as the planning and the invoice.
beforeA PDF in the mail and waiting for a signature.
nowRead, chosen and signed online.
customer portal ◇ the dashboard
The next appointment with reschedule and cancel buttons, the latest documents and three big actions: book maintenance, report a fault, ask a question. No manual required, including for customers who rarely touch a computer.
beforeA folder of emails, a folder of invoices, and calls for the rest.
nowEverything on one screen, after hours too.
customer portal ◇ fault reporting
The customer picks what is going on, adds a short description and photos. The portal asks the follow-up questions an engineer would ask, and the report lands with the planners right away.
beforeA queue, a phone menu, and telling the story twice.
nowReported with photos, straight to the planners.
customer portal ◇ my appointments
Planned maintenance visits come with reschedule and cancel buttons, up to 48 hours ahead. Every new proposal respects the engineer's route, so the planning stays sound.
beforeRescheduling took two phone calls.
nowRescheduling takes two clicks.
Tico really got us out of a bind. He professionalized our IT landscape and made it a lot more robust, on his own and fast. Whenever something comes up, he's there, morning or evening. And he trains us to handle maintenance ourselves, so we depend on him less.
Why that works
Whoever thinks your processes through with you also builds them. Nobody in between who has to retell the story to IT.
I know lead-to-cash from the inside. Fourteen enterprise implementations taught me how a sales, service and billing process really works, where it breaks, and what a system has to do to move a business forward.
That's how I build Fikst: on my own, with AI agents and a fixed way of working, and a security check on every release. Elite Klimaat Groep runs entirely on it.
A business runs as well as the systems underneath it.
Founder
I build Fikst: CRM and ERP for air-conditioning, heat pump and installation companies. Customers, articles, inventory, purchasing, quotes, scheduling and maintenance share one system, with apps for engineers, sales advisers and customers. Elite Klimaat Groep uses it with 22 people. You deal directly with me as the builder.
S/4HANA, CX and integration
I set up SAP Sales Cloud and Service Cloud and connect them to S/4HANA, with custom ABAP and integrations in SAP Integration Suite. Fourteen full-cycle CRM projects, lead consultant on most.
Building with AI
I build Fikst with AI agents every day, and that's how I build for others too: agents and MCP servers working on a real system, with hard limits on them. A cost cap, for instance. I forgot one once on a test against Google Maps. Got a bill for a thousand euros.
On your own work
Practical AI training for teams, on tasks from their own week. Your team goes home with automation that already runs.
Enterprise CX
Fourteen full-cycle implementations of Sales and Service Cloud, as Lead Consultant on most. End-to-end customer journeys with integrations to ERP and custom portals, including hypercare after go-live.
Elite Klimaat Groep
Elite Klimaat Groep runs Fikst with 22 people: 6 in the office and 16 field engineers. Six separate packages were retired. The company was fully live within two months. Its existing customer portal is connected: a maintenance booking becomes a work order. The Fikst case explains what changed and where the figures come from.
view the caseWhy I do this
From nothing to something. A black screen becomes something that works.
That's the feeling I'm after on every project: an empty screen that ends up keeping your work running.
Whatever I take on gets
fixed
I stay until it runs, and after that I'm simply reachable.
Enough about me; where are you stuck?
I reply within 24 hours.