Gardens, not bouquets

A bouquet is a finished thing. Someone cut the flowers, arranged them, wrapped them, and handed them over. It looks wonderful on the day. It was never going to last, and nobody expected it to. That was the deal.

Most websites are bouquets. An agency arranges one, hands it over at launch, and moves on. The brand posts the announcement, the team celebrates, and then the site starts the only journey a bouquet can take. Six months later a product page is out of date, the new campaign doesn’t fit the template, and someone is quietly opening a ticket titled “redesign.”

For a long time this was fine, because bouquets were expensive. Building a competent storefront took months of skilled work, so a launch felt like an achievement, and the slow decline afterward felt like the natural cost of owning a website.

That’s over. A competent storefront can be generated in an afternoon now. The mockups, the copy, the code, the whole arrangement. AI made bouquets close to free, and when something is free, having one stops meaning anything.

The instinct is to answer this with more beauty. If everyone can make a decent site, make a gorgeous one. We understand the instinct and we don’t think it holds. Beauty is getting cheaper too, and a gorgeous site that nobody touches after launch is still a bouquet. It just cost more.

The distinction that survives is different. It isn’t beautiful versus ugly. It’s tended versus abandoned.

Look at any storefront you admire and ask how it got that way. Almost never in one launch. It got that way because somebody kept showing up. They noticed the product page where people hesitated and fixed it. They watched the checkout, the search, the email after the first order. They shipped a small change most weeks for years, and the changes stacked into something no single launch could produce.

That’s a garden. Nobody hands you a garden. A garden is time, attention, and the willingness to come back on a Tuesday when nothing is on fire.

We hear the word slop a lot now, usually about how something looks. We think that misses what makes it slop. Plenty of ugly things are loved and cared for. Plenty of beautiful things are orphans.

Slop is what happens when an artifact is made and then abandoned. It exists, it is technically complete, and no one is responsible for it. The web is filling up with these: sites generated, launched, and left. They aren’t wrong, exactly. They’re unattended.

The problem with an unattended storefront isn’t aesthetic. It’s that customers change, catalogs change, platforms change, and the site doesn’t. Every month it drifts a little further from the business it was built for. The redesign ticket is the moment somebody finally notices how far.

This changes what a launch is for. In the bouquet model, launch is the finish line, so everything has to be perfect by then, which means it never is, which means launch slips. We’ve watched brands lose a quarter to a launch that wanted to be flawless.

In the garden model, launch is day one. You ship something good and true, and then the real work starts: watching real customers use it and making it better with the evidence in hand. The not-perfect launch isn’t a compromise. It’s the only honest way to start, because you don’t know what perfect is until people show up.

Every storefront we keep got better after it shipped. Not one of them launched finished. That is the point.

There’s a reason the person who runs a shop is called a shopkeeper, and the person who tends bees is a beekeeper. The work was never the opening. It was the keeping. Showing up, noticing, adjusting, staying.

We think that’s the job now. Not making the arrangement. Anyone can make the arrangement. The job is being the people who come back, who know the store’s history, who remember why that section is the way it is and what happened the last time it changed.

So when we say we build gardens, not bouquets, we don’t mean our launches are prettier. We mean we’re still there in year three, and the site is better than it was in year one, and we can show you the dates. A kept-since date is the only credential that can’t be generated.