Overview {#overview}

This case study is not a toy AI demo.

It is a practical look at a real internal operating model:

We connected OpenClaw directly to the private GitHub repo for the AutomateThis! website and used it to analyze, rewrite, restructure, and ship real changes in the live project context.

The goal was not simply to “let AI write copy.” The goal was to:

• read the website critically,
• identify positioning contradictions,
• make decisions in-context,
• and implement the changes directly in the repo.

The starting point

The website had a familiar problem set for a growing agency site:

• a stronger homepage than supporting pages
• older offer/funnel language from previous phases
• legacy blog content heavily shaped by older Mautic / marketing automation framing
• footer, contact, and conversion layers still carrying SaaS/product signals
• an unclear relationship between AutomateThis! and hartmut.io

In short:

There were strong pieces, but the overall message was inconsistent.

What we actually did {#what-we-built}

We used OpenClaw not just as a writing assistant, but as an operational execution layer.

The workflow looked like this:

1. Read the live website

The first step was to read the public site and evaluate it through the lens of positioning, ICP, offer structure, and conversion logic.

2. Clarify the real customer and offer

We then extracted the implied target customer and tightened the positioning.

That led to a clearer split:

• AutomateThis! as the systems engineering / integration partner
• hartmut.io as the specialized branch for managed stack operations

3. Connect to the private GitHub repo

Using a GitHub token, the private repo was cloned into the workspace.

That meant changes could be implemented for real — not just suggested.

4. Edit the actual Astro codebase

The work happened in the live Astro project.

Among other things, we:

• rewrote positioning pages
• aligned German and English offer pages
• cleaned footer and contact pages
• removed fake scarcity and stale trial/product-language
• reframed legacy blog content strategically
• clarified the brand boundary between AutomateThis! and hartmut.io
• fixed HTML entity rendering issues centrally in the blog layout

5. Commit and push in the loop

Changes were committed continuously and pushed to main after approval.

Deployment then happened automatically via GitHub → Coolify.

Why this mattered

The interesting part was not “AI writes text.”

It was the combination of:

• analysis
• strategy
• direct file edits
• git-based execution
• human review and steering in the same loop

That is a different operating mode from generic copywriting or chatbot use.

Key benefits {#key-benefits}

1. Less handoff loss between thinking and shipping

Instead of the usual chain of strategy → brief → copy → dev → review → rework, much of the friction was compressed.

2. Decisions happened inside the real system

Not in an abstract doc, but inside the repo, page structure, and actual content architecture.

3. Visible iteration

This did not stop at recommendations. The changes were actually written, committed, and deployed.

4. Strong sparring-partner behavior

OpenClaw was not used as a cheerleader. It was used to ask better questions:

• Who is the real ICP?
• Which pages damage positioning?
• What is legacy vs. strategically important?
• Which content should stay, be reframed, or be removed?

5. Better balance between speed and judgment

The agent accelerated execution. The human kept strategic control.

What this means for clients

For clients, the relevant point is not that “AI” is involved in the background.

The relevant point is:

• faster iteration on website and content systems
• less handoff loss between strategy, copy, and implementation
• clearer decisions inside the real system, not in abstract docs
• less delay caused by recommendations that never get shipped
• a workflow that can move from analysis to commit in one loop

That is especially useful for teams with grown websites, legacy content, and contradictory positioning.

Technology stack {#technology-stack}

The operating stack in this workflow included:

• OpenClaw as the agentic execution layer
• GitHub as source of truth for code
• Astro as the website framework
• Coolify as deployment target
• Leantime for project organization
• direct chat-based approval and iteration

Where this workflow is especially strong

This kind of setup is particularly useful for:

• live website iteration
• content refactoring across larger existing sites
• positioning work with direct implementation
• repo-native tasks where analysis + edits + commits belong together
• ongoing improvements instead of monolithic relaunches

What it does not replace

It does not replace:

• human judgment
• strategic accountability
• real business decisions
• prioritization by the owner or team lead

But it dramatically reduces the distance between idea and implementation.

Summary {#summary}

This case study shows how OpenClaw + GitHub can be used not merely as a writing assistant, but as a practical execution layer for real website and content operations.

Not for AI noise. But for making website systems faster to improve, easier to align, and more consistent over time.

If you want to explore what a similar workflow could look like for your website, content system, or internal operations:

• Request the Decision Memo