Habr AI showed how to build a brand platform for a startup in 8 hours without a designer

On Habr AI, a detailed breakdown was published on why a brand platform can be useful for a startup even before a full MVP. The author demonstrates how to assemble a system of textual constraints in eight hours, from which a landing page, app screens, and advertising creatives can then be derived without constantly returning to a vague "make it look nice."

Why Brand Before MVP

The main thesis of the piece — a brand at an early stage is needed not as a logo and not as a decorative shell. It works as a system of constraints: it sets the product's voice, the type of visual solutions, permissible promises, and the way to communicate with the audience. Without this system, each new artifact — from a banner to a social media card — has to be generated from scratch.

As a result, the model repeatedly arrives at an averaged "expensive" design that looks convincing but doesn't fit the specific user well. The article illustrates this with a test case of a PWA for off-road travelers across Russia, Mongolia, and China. A quick landing page assembled in five minutes got a dark theme, invented metrics, two CTAs, and fake social proof.

The version made through the pipeline in eight hours turned out calmer, but more honest: one CTA, real use cases, visual emphasis on location and audience language. For the author, what matters more is not instant wow-effect, but the ability to scale the same approach to new screens and creatives.

"20 artifacts in 5 minutes — that's 20 lotteries. 8 hours once —

that's a system."

What the Pipeline Consists Of

The author suggests starting not with Figma and not with generating a "beautiful landing page," but with the product ontology: what exactly does it change in a person's relationship with the environment, what's its archetype, where's the boundary between usefulness and false promises. From this level, a brand platform is assembled, then visual semantics rules, identity system, tokens, and only then — specific artifacts. In such a chain, every decision can be explained in words and checked against the overall logic.

• Product ontology and JTBD
• Brand platform with invariants
• Principles of visual semantics
• Visual identity, tokens, and components
• Screens, landing page, and creative specification

The key idea is that prompts stop being a collection of taste preferences. Instead of the word "beautiful," they contain specific constraints: why no dark theme is needed, why one CTA, how to show data recency, when people in the frame are acceptable and when they're not. This approach is closer not to free generation, but to constraint-driven production: first the specification is set, then interfaces, illustrations, and marketing materials are sequentially derived from it. The more artifacts a product needs, the more profitable this preparatory layer becomes.

Where AI Gets Wrong

One of the most telling moments in the breakdown — an error by the model itself within a carefully constructed pipeline. At one stage, AI decided that visuals shouldn't include people: the territory was supposedly supposed to remain the main subject of the frame, and the interface should work from a first-person perspective. Formally, the explanation looked logical, but contradicted audience knowledge.

For overlanders, trust in data is tied to its source, which means people in the frame are sometimes essential: the person showing the way, discussing a river crossing by the car, or sharing an observation is part of the product. The author needs this episode not to criticize models, but to draw a more harsh conclusion: prompt engineering works as a multiplier, but doesn't create substantive knowledge from thin air. The pipeline helps to fix decisions, check them for consistency, and see where AI convincingly made a mistake.

But the final check is always made by a person who understands the market, audience, and context of use. That's why the brand platform in the article is described not as a replacement for a designer or product manager, but as a way to bring professional intuition into text and make it reproducible.

What It Means

For solo founders and small teams, the conclusion is simple: before landing pages and banners, it's worth spending a few hours on a one-page constraint file with principles, anti-examples, and brand voice. This won't replace hypothesis testing on the market, but it will reduce chaos in generations and help assemble a cohesive system faster instead of a set of random images.