Skip to content
The Build More logo and the Robaws logo side by side with a neon green x, on a dark navy background

Robaws x Build More: our clients and what we are working on now

Over the past year we built up a lot of experience with Robaws. Several clients, trial and error, and quite a few solutions built. Frankly, we are Robaws experts by now. Below: our current clients, and what we are working on right now.

Our current clients

ZET Wonen builds in wood: timber frame construction, CLT, roofing, cladding. How many hours a site would take lived in a single Excel file, with an estimated number of hours per measurement code that someone had once filled in by gut feeling. Nobody could trace where those figures came from, while the hours actually worked had long been sitting in the Robaws work orders.

We built a web tool that plugs straight into Robaws: projects, hours and work orders come from there, and the tool writes data back too. From every closed site, the tool pulls the measured values per measurement code and builds its own average from them, which feeds the post-calculation. The planning per crew and van lives in the same tool, with work orders that go straight to Robaws. Twelve weeks after the first commit, the first working version was live. See the ZET Wonen case.

K&C Marine Contractors carries out diving and underwater inspections on quay walls, locks and jetties. Reporting was done on paper, later retyped into a Word template, each diver in their own way: half a day's work per inspection.

We built a native iOS and Android app that lets divers fill in their report on the spot; the admin approves it and delivers a PDF in the K&C house style with one click. The Robaws integration syncs projects and clients automatically, so there is no double administration. ("Top product," according to Kevin De Clercq, Managing Director Europe at K&C.) See the K&C case.

What we are working on now

We are currently building for new clients, including Cedric Sels Dakwerken, Renolux and Stefdec, again on top of Robaws: quote automation, post-calculation, a stock management system, and further automations with MCP. We will say more about those soon, once the projects are mature enough to show.

We also built something that works for every Robaws company, not just one client: an MCP server (Model Context Protocol, the open standard that both ChatGPT and Claude use for external integrations) that exposes the Robaws API to your AI assistant. You paste one URL into ChatGPT or Claude, and ask your Robaws something in plain language: "Who are my five biggest clients this year?", "Which invoices have been open for more than 60 days?"

robaws-mcp runs live, multi-tenant, with 1,086 Robaws endpoints covered, read-only by default (writing can be added later, via a separate account with confirmation and an audit log). See /robaws-ai/ for the full explanation and the questions you can already ask today.

Why not every Robaws question gets a Robaws answer

At Railforce, which plans railway works, we deliberately looked at standard packages such as Robaws and Timeking, and they did not fit how Railforce really works. There we built something fully bespoke. That is the nuance we always keep in mind: Robaws is strong for those who use it, but not an automatic answer to every planning question (when to choose a standard package and when custom software).

Do you work with Robaws and are you running into something, from post-calculation to an AI question that no report answers? Get in touch and we will look at what is possible together.