More feedback cycles, better product decisions for LAUTEC WindGIS with Claude Code

Project teams keep all their GIS data in one place, with granular access right management for individual users down to a single dataset, and work with vector and raster layers, 3D terrain and nautical charts in the browser, save and share themed map views, link survey reports and documents to the map, and print or download maps and data in shapefile and other formats. AIS vessel tracking, the FiDU uploader for contractors' field data and live progress maps from LAUTEC's Daily Progress Reporting tool all feed into the same viewer, which also works with the major desktop GIS software tools.

The platform runs in production in four regions, and LAUTEC's clients use it for project development, construction and operations across Europe, Asia, North and South America, and Australia and Oceania.

Before April 2026, a typical WindGIS ticket took a median of 21 days from first work to production and a story or epic took 40, while the slowest stories took almost four months.

Any AI in the workflow had to operate within LAUTEC's own repositories and rules, maintain LAUTEC's code ownership, and leave every change subject to human review before it reached the main branch.

We get more functionality/value without giving up control. We ship twice as many releases at the same quality. The code and the rules stay ours, and a person approves every change. We now say “yes” to more of what our clients ask for - and we deliver it while it still matters on their project.

Henrik Søgaard Iversen

Managing Partner, Head of IT, LAUTEC

RebelDot has been LAUTEC's technical partner for the past ten years, handling new technology and innovation development, and introduced Claude Code on WindGIS as part of that work.

An engineer clarifies the request and scopes the work, often with a written spec, before Claude Code implements it, and every change passes a first-pass AI review and a human approval before it merges. LAUTEC owns the codebase and the harness configuration, and changes to the harness rules undergo the same review as changes to the code. Since April 2026, 492 commits across the WindGIS repositories have Claude as co-author.

Shorter cycles give LAUTEC and its users more opportunities to see work early and steer the next iteration, so the team can address what wind farm teams need, better.

RebelDot built and runs a harness around Claude Code across the three WindGIS repositories:

Technology: Claude Code, CLAUDE.md rulebooks, custom skills and subagents, pre- and post-edit hooks, MCP servers for Atlassian (Jira) and Context7 (documentation lookup), GitHub through the GitHub CLI

With RebelDot's Claude Code setup in place, the WindGIS team ships twice as many feature releases and typical work reaches production about a third sooner, while the share of tickets sent back from QA has held at 3 to 4%.

Agentic engineering puts our work in front of real users sooner. Each release becomes a chance to learn, and that is how we widen the surface on which the product can succeed.

Vadim Fintinari

Chief AI Officer, RebelDot