Batibig runs a fast-growing construction group. Stratos rebuilt the core of its business software, planning, client management and invoicing, in four months, using Claude across design, specification, code, testing and documentation.
Batibig was founded by two operators who bought a first construction company and brought modern management to a traditional trade, then rolled up more companies into a group now worth around €350M and heading toward €1B in revenue.
The group had outgrown its software. The system at the heart of the business, planning, client management and invoicing, still ran on a very old platform that no longer matched how the company worked. Batibig wanted to modernize that core, without a multi-year replacement project.
.webp)
Rather than a long specification-then-build cycle, we ran the project with Claude at each stage, from validating concepts with the client to writing the code, the tests and the documentation. The result was a full rebuild of the core system in four months.
Three stages, each accelerated by Claude, with senior engineers keeping quality and architecture under control.
We created the mockups and the design system with Claude Design, so we could validate concepts, designs and ideas with the client quickly. Putting real interfaces in front of Batibig early meant decisions were made on something concrete, not on documents.
Once the mockups were validated, we had Claude write the specifications directly from them. The specs stayed tied to what the client had already approved, instead of drifting into a separate document.
Senior developers set up the project on solid engineering practices, then we built with Claude Code on the Max plan, using a set of Skills, some from the market and some we built ourselves, fed by the developer specs prepared earlier. End-to-end tests and demo videos of the application were produced with Claude and Playwright, and reused, for example, to build the FAQ. All the technical documentation and the FAQ were written with Claude.
Because the full technical documentation and the FAQ were produced with Claude, they form a clean base for the next step: an assistant grounded in the complete documentation and FAQ, so Batibig's teams can get answers directly instead of searching.
An assistant that answers from the complete documentation and FAQ built during the project, giving the client's teams a single, reliable place to ask.
A custom ERP with this level of sector-specific depth (building maintenance, multi-subsidiary, complex tax rules) normally forces a trade-off between three variables: functional scope, quality of business fit, and timeline. Compressing one of the three to hold the other two is the norm in classic ERP integration.
Here, the production velocity enabled by Claude Code meant that trade-off didn't have to be made: scope stayed broad (8 modules, not a stripped-down MVP with 2-3 functions), business fit stayed precise (real sector-specific rules, not generic approximations), and the timeline held (4 months, both release milestones met).