Architecture before the landing page

A pretty landing page is easy to want early. It is also a good way to lock in the wrong product.

For ConsentBloom, the order of work matters: decide what the product is, then dress the front door.

The temptation

Marketing wants a sharp headline and a clean hero. That is fair. Solo US lash, brow, and wax artists will judge the site in a few seconds.

The trap is writing that page before the product has a spine. You invent a category you do not mean to own. You promise a booking app you already refused to be. You sell a form builder when the job is send → chase → find.

A landing that lies about the product is worse than a quiet domain.

What had to be true first

A few decisions had to land before the marketing copy could be honest:

• Sit beside Square and Booksy, not instead of them.
• Refuse the form-builder category. Fixed templates, not a blank canvas.
• Start email-first. SMS is a compliance product of its own, so it waits.
• Keep appointments manual for version one. Integrations are not a prerequisite.

Those choices are the architecture. They are also the only honest brief for a landing page.

Architecture here is product shape

I do not mean “draw more boxes.” I mean the shape the customer actually feels: invite, remind, find the signed copy later. The form is an ingredient. The chase is the product.

When that loop is clear, the homepage can say one true sentence. Until then, every hero paragraph is a guess you will regret editing under pressure.

Honesty about what is not live

This post is not a launch. It is not a claim that the marketing site is finished, that every channel is live, or that we are a law firm. It is the sequencing decision: product truth before marketing polish.

Writing in public about that order is part of the work. The blog is where those decisions show up. The landing follows when the copy can match what we actually ship.

The short answer

If someone asks why ConsentBloom did not lead with a polished landing, the short answer is that the product decisions had to come first. Architecture before the landing page means we can advertise something we mean.

The blog will have more of this. There's RSS if you want it in a reader.