How Gewerkton Used AI Agents To Make A Fast, Full-Scale Relaunch

🔍 Read the full analysis: How Gewerkton Used AI Agents To Make A Fast, Full-Scale Relaunch on ThorstenMeyerAI.com

Prime Big Deal Days · Oct 6–7Offer from Amazon

Get the latest gadgets delivered free — and shop member deals

• Fast, free delivery on millions of items
• Access to Prime Big Deal Days deals on October 6–7
• Prime Video, Amazon Music and more included

Start your free Prime trial →Free trial for eligible customers · Cancel anytime

As an affiliate, we earn on qualifying purchases.Hide

Gewerkton, a construction-site documentation tool built in Iffeldorf, Bavaria, says it replaced the design across its web app, iPhone and Android apps, Studio, 26 icons and 529-page website on Oct. 2 and 3, 2026, as detailed in the original analysis. Its publisher’s account says AI coding agents carried out the implementation from plans approved by founder Thorsten Meyer, who reviewed and released each part; the company also reports problems that required human checks and fixes.

The new design is called HORIZON. Gewerkton says the web app’s 281 hard-coded colour values were moved to design tokens, with 11 exceptions retained, and 47 cards were restyled. The phone apps moved to the new look in version 0.5.0, while Studio received light and dark versions. The 26 icons were re-rendered using Blender, in cobalt and navy.

The website comprises 529 pages in 40 languages. The company says it added a new opening section featuring real product screens and uploaded 1,583 files without errors. It also ran 228 AI-generated film jobs for five regions, including 222 regional versions, and produced eight help videos. Gewerkton says 76 film jobs failed and were not billed; production paused after the ninth round, when 208 of the 228 runs were complete and 38% of jobs were failing.

The “two days” describes execution from an approved plan to the live website, not the full design process: an interim design draft dated Sept. 26 was used. Meyer directed a fleet of Codex and Claude coding agents, according to the publisher’s account. Agents worked on a separate code branch, and Meyer approved plans, checked results and authorized releases. Certain film reruns required his explicit approval, while Apple’s developer agreement had to be accepted by Meyer before the iPhone build could proceed.

Human Checks in an Agent-Led Relaunch

The account offers a specific example of how a small software publisher used AI agents for a broad, coordinated product release while keeping approval and release authority with a human. Gewerkton describes agents implementing written plans across multiple products, but not independently deciding the design, approving paid reruns or publishing each part. That distinction matters to readers evaluating claims that agents can manage software work end to end.

The reported problems also show why passing automated tests did not settle whether the redesign was ready. A dark-mode icon issue was caught by Meyer’s visual inspection, while film recolouring errors escaped an automated mask. The company says its checks included extensive automated tests and visual reviews, but the experience it describes suggests that human inspection remained part of quality control, especially for visual output and region-specific media.

These are results reported by the product’s own publisher, not an independent assessment of agent productivity or reliability. The account does not provide a comparison with the time, staffing or cost of completing the work without agents. It therefore documents one deployment and its workflow, rather than establishing that similar projects will take two days or produce comparable results.

From Approved Plan to Live Site

The relaunch began with a plan listing unresolved decisions, alternatives and recommendations. Meyer says he approved the recommendations before the agents worked in a separate copy of the code. Each part remained unmerged and undelivered until he released it. When implementation departed from the plan, the deviation was recorded and the more conservative option was used.

One such decision involved the brand’s cobalt colour. Gewerkton says the original shade reached a 4.38:1 contrast ratio against a light background, below the company’s working standard of 4.5:1 under WCAG 2.1 AA. The shade was darkened to reach 4.80:1 rather than released as first planned.

The company reports that the web app was checked across 200 views, four languages, three screen widths and light and dark modes. Its phone app passed 853 of 853 tests, and Studio passed 2,158 of 2,158. The website passed seven test suites and was checked in five regions at three widths. Gewerkton also reports eight failing web-app tests across seven files: six files failed the same way on the main branch, and one test passed when run alone, so the publisher says the redesign did not cause those failures but did not fix them.

“The agents worked in a separate copy of the code on their own branch.”

— Thorsten Meyer, Gewerkton founder, in the publisher’s account

Costs and Follow-Up Still Open

The supplied account gives only a partial financial picture. It says the film work cost about $134 in actual, but the figure is cut off before the full amount or unit is stated. It also does not quantify the time Meyer spent planning, reviewing or correcting the work, or provide a like-for-like comparison with a conventional relaunch.

Some implementation issues remain in progress. Gewerkton says five major findings from a Pixel 10a Android test were not blockers and were scheduled for version 0.5.1; one involved buttons wrapping text, including the German word for “cancel.” The account does not say whether that version has since shipped. It also does not independently verify the company’s reported test results, upload totals or film-job figures.

For regional films, the company says 10 versions with leftover red were temporarily switched to the European cut after review. Nine were later reshot with Meyer’s approval and passed visual checks. The account does not state the eventual status of the remaining version.

Android Fixes and Film Rechecks

Gewerkton’s stated next software step is version 0.5.1, which is scheduled to address the five findings from the Android camera-screen test. The publisher’s account does not give a release date, so it is not clear when users will receive the fixes.

The company also describes continued review of generated films: nine regional versions were reshot and checked, while the remaining temporary European-cut substitution is not accounted for in the supplied details. The next useful update would clarify the Android release, the final status of regional film versions and a complete cost figure for the work.

Key Questions

What changed in Gewerkton’s relaunch?

Gewerkton says it applied the HORIZON design to its web app, iPhone and Android apps, Studio, 26 icons and a 529-page website in 40 languages. The website also received 228 film-generation runs for five regions and eight help videos.

What did the AI agents do?

According to the publisher’s account, Codex and Claude agents implemented work from written plans on a separate code branch. Founder Thorsten Meyer approved the plans, reviewed results and released each part; some approvals and Apple account steps required his direct action.

Was the whole redesign completed from scratch in two days?

No. Gewerkton says an interim design draft dated Sept. 26 was already available. The two-day period refers to execution from the approved plan through the live website on Oct. 2-3, 2026.

What problems did the team report?

The company says white icon tiles obscured dark-mode labels, automated film recolouring missed some red details, and film jobs had a high failure rate during one production round. It also reports five non-blocking findings in an Android test, scheduled for version 0.5.1.

How much did the relaunch cost?

The supplied source gives an incomplete figure of about $134 for the film work; it is cut off before specifying the full amount or unit. It does not state the total cost of the relaunch or provide a comparison with a non-agent workflow.

Source: ThorstenMeyerAI.com