Grow Brave Studios

A place people arrive

Websites & Interfaces.

Sites people read, and interfaces people move through and use. Built around what a business actually does, not a template with a logo dropped into it.

What it covers

Anything someone lands on and uses.

Websites and landing pages

A full site, or a single page built to do one job properly. Written, designed and built together rather than passed between three people.

Rebuilds and refreshes

A site that has drifted away from the business it describes, brought back into line. Content worth keeping gets kept.

Interfaces and web tools

Something people do a task in rather than read. A calculator, a configurator, a small internal tool, a browser extension.

Templates other people can use

A single file someone else can fill in and deploy themselves, with no build step and nothing to maintain.

What it is for

The sentences people actually arrive with.

The site does not sound like us.

Usually because the words came last, after the template was chosen. Here the copy and the structure get decided together, so the page is shaped around what is being said rather than the other way round.

It was built years ago and nobody can edit it.

Sites get abandoned when changing them requires the person who built them. Static, plain-text pages with no build step can be edited by anyone who can open a file, including an AI assistant working for you.

People land and leave without understanding what we do.

Almost always a structure problem rather than a design problem. What a visitor needs first is rarely what a business most wants to say first, and fixing that order fixes most of it.

We need it live this month, not in six.

A one-person studio with AI capacity has no handover cost, which is where most of the time in a small web project goes. Scope still decides the timeline, but nothing waits in a queue behind someone else's work.

The work

Built solo, start to finish.

Each with the human decisions and the AI role set out, and the authorship credited.

Single-page site · Cape Town

Cape Town Washing Line

A small domestic problem solved properly. Global forecast data read down to one useful answer: the best day to hang your washing.

Read the case study
What existed before
Weather forecasts full of numbers that answer a hundred questions, none of them the one actually being asked.
What it needed to become
One answer. Which day this week should you do the washing.
What the studio decided
That wind, humidity and rain probability matter more than temperature for drying, and that the site should give a verdict rather than a dashboard.
Where AI expanded capacity
Turning the forecast model into a drying score, and the site build.
What was made
zawashingline.date, live and free.
Credits
Concept, direction and build through Grow Brave Studios. Forecast data from public meteorological sources.
Visit the site

Web template · Resume

Your Intelligence File

A CV as a declassified dossier. One HTML file, no build step, light and dark, filled in by handing an AI your LinkedIn PDF.

Read the case study
What existed before
The same two-column PDF CV everyone has, indistinguishable from every other one in the pile.
What it needed to become
Something memorable that still reads as a serious professional document, and that anyone could fill in without a designer or a build step.
What the studio decided
The declassified dossier conceit, and the constraint that it be a single HTML file. One file means anyone can host it anywhere, forever, with no toolchain to maintain.
Where AI expanded capacity
The build, and the pipeline that turns a LinkedIn PDF into the filled-in file.
What was made
An open-source single-file template, deployed on Cloudflare Pages.
Credits
Concept, direction and build through Grow Brave Studios.
View on GitHub

Artist site · Weekly releases

frequenXYZ

A site designed to absorb a weekly release without being rebuilt each time, so adding music is a data entry rather than a redesign.

Read the case study
What existed before
Songs written by Aloha Jacqueline, a release schedule, and no site that could keep up with it.
What it needed to become
A home for the music that could take a new release every week without a developer touching the layout.
What the studio decided
The site architecture, so a release is a record in a data file rather than a page someone has to design. Art direction and identity alongside it.
Where AI expanded capacity
The site build, and visual generation for release artwork.
What was made
frequenxyz.com, and a release pipeline one person can run weekly.
Credits
Words and songwriting by Aloha Jacqueline. Site and identity built through Grow Brave Studios. Released through Grow Brave Records.
Visit frequenxyz.com

AI drafts.
A human decides.

How AI is used here

On a website the useful AI work is unglamorous. First-pass markup. Layout variations to react to. Repetitive build tasks that would otherwise eat a day. Draft copy that gives something to argue with instead of a blank page.

What stays human is the part that decides whether the thing is any good. Structure, order, what gets cut, and every word that carries the meaning of the business. A page that arrives generated and unread is how sites end up sounding like every other site.

No autonomous agents produce client work while nobody is looking. Nothing is handed over that a human has not made a decision about.

Questions

The ones that actually get asked.

Do you work on existing websites, or only new builds?

Both. A rebuild of a site that has drifted out of date is as common as a new build. If an existing site has content worth keeping, it gets kept rather than thrown away.

What are the sites built on?

Most of this work is fast static pages deployed on a service like Cloudflare Pages, which keeps hosting cheap and avoids platform lock-in. Where a site genuinely needs a content management system or a database, that gets decided in the conversation rather than assumed up front.

Does AI write the copy on my website?

AI drafts, a human decides. Nothing ships unread, and the words that carry the meaning of a business are written and edited deliberately rather than generated and pasted.

Who owns the finished website?

You do, outright. Files, code, domain and hosting accounts are handed over in your name. There is no lock-in and no retainer unless you ask for one.

Start here

Bring the thing you wish existed.

A site that needs rebuilding, a page that is not landing, or an interface that does not exist yet. Describe it in a couple of lines and the conversation starts there.

Bring the thing you wish existed