Phase-zero sites: launching a brand before the product exists

There is a familiar sight on the internet: a domain with a logo, the words "coming soon" and an email field. It tells visitors almost nothing, gives search engines nothing to index and teaches the founders nothing about whether their message works.

At Oryvelon we do something different. Every company gets a phase-zero site — a real website with real content — before its product is finished. It is step eight of our new-company protocol, and in our experience it is one of the highest-leverage things a new company can do.

What a phase-zero site is

A phase-zero site is the first real version of a company's website. It exists before the product launches, and it does four jobs:

Explains the problem in the customer's own language.
Describes the solution clearly enough that the right person recognises it is for them.
Captures interest through a waitlist, an early-access request or a direct contact form.
Starts earning discoverability in search engines and AI assistants.

It is not a placeholder. It is not a single landing page with a headline and a form. It is a small, well-built site with enough substance to be useful — and to be worth indexing.

What it must contain

The exact pages vary by company, but a phase-zero site usually includes:

A clear homepage that states who the product is for, what problem it solves and what makes it different.
A "how it works" page describing the approach, even if some parts are still being built.
Pages for each audience, where there is more than one — a marketplace needs to speak to both sides; an education product may need separate messages for families and schools.
Answers to real questions, often as an FAQ built from early customer conversations.
A way to act: join a waitlist, request early access, book a call or get in touch.
Honest status information so visitors know what is available now and what is coming.
Legal basics: privacy notice and terms appropriate to what the site collects.
The group relationship, stated naturally — usually a small "An Oryvelon company" in the footer and a line on the about page.

What it must not do

A phase-zero site must never pretend the product is finished when it is not, promise features the team is not confident about, or publish invented testimonials, metrics or customer logos. Credibility is the whole point of the exercise, and it is easy to destroy.

It also must not collect more data than it needs. A waitlist needs an email address; it probably does not need a phone number, a birthday or a company size. The same minimum-collection rule that applies to products applies here.

Built properly from day one

Because the phase-zero site is the company's public face, it is built on the same foundations as a live product:

Domain security: registered, locked, set to auto-renew, under an account with two-factor authentication.
HTTPS and security headers: the same standards as every Oryvelon site.
Email authentication: SPF, DKIM and DMARC on the domain, so waitlist confirmations arrive and nobody can easily spoof the brand.
Measurement: analytics that respects visitors, with events for the actions that matter — sign-ups, replies, requests.
Search structure: clean headings, descriptive titles and meta descriptions, a sitemap, sensible robots rules and structured data describing the organisation.
AI readability: clear, factual content that assistants can understand and quote, plus machine-readable summaries where appropriate.

We cover the discoverability side in Search and AI-assistant visibility and Structured data and llms.txt.

Why launch the site before the product?

It tests the message with strangers

Founders explain their idea to friends, colleagues and investors, who usually understand it because they know the context. Strangers do not. A phase-zero site shows whether someone arriving cold understands the offer well enough to act. If they do not, it is far cheaper to change a headline than a product.

It builds an audience early

Every person who joins a waitlist before launch is someone who can be invited to try the first version, give feedback and become an early customer. Launching to a list of interested people is very different from launching to silence.

It starts search visibility months ahead

Search engines take time to discover, index and trust a new site. A company that launches its website on the same day as its product starts that clock late. A company whose phase-zero site has been live and useful for months arrives at launch with pages already indexed and, often, early rankings for relevant questions.

The same applies to AI assistants. When people ask an assistant about a problem, assistants draw on content they can find and trust. A clear, factual phase-zero site is part of how a new company becomes something an assistant can mention.

It gives the brand a home

Partners, journalists and potential hires will look a company up. A proper site answers their questions and signals seriousness. A "coming soon" page signals the opposite.

How we measure a phase-zero site

We measure a phase-zero site against the questions validation is trying to answer, not against vanity numbers.

Question	What we look at
Do visitors understand the offer?	Share of relevant visitors who take a meaningful action
Which message works best?	Action rates across headline and page variants
Who is interested?	Answers to one or two optional questions at sign-up
Where do interested people come from?	Sources and campaigns of visitors who act, not all visitors
Is interest real?	Replies to follow-up emails, calls booked, early access accepted
Is search starting to work?	Indexed pages, impressions and queries in search tools

Traffic from the group's own channels — oryvelon.com, founder sites, sister brands — is tagged with consistent UTM parameters so it can be separated from organic interest. A spike of visits from our own audience is encouraging, but it is not validation. See UTM standards for measuring traffic between sister brands.

Content that earns its place

The content on a phase-zero site should be useful even to a visitor who never signs up. That is what makes it worth indexing and worth citing.

Good phase-zero content often comes straight from validation conversations:

Explanations of the problem in the words customers use.
Guides that help people with part of the problem today, before the product exists.
Honest comparisons of the ways people currently handle the problem.
FAQs built from real questions asked in conversations and sign-up forms.

For a relocation product like KeşifAtlası, that might mean clear explanations of how eligibility generally works and what documents people usually need to think about — carefully written, with the product's rules engine as the source for anything specific. For a store-operations product like MerchNivo, it might mean practical guides on the signals a Shopify store should watch every day. See The operational signals every Shopify store should watch.

What we avoid is thin content written only to rank. It does not help visitors, it weakens the brand and it is exactly the kind of content search engines are designed to ignore.

From phase zero to launch

A phase-zero site is not thrown away at launch. It evolves.

The waitlist form becomes a sign-up or trial flow.
The "how it works" page gains real screenshots and details.
The FAQ grows with questions from real users.
Status notes are updated as features arrive.
Content pages keep earning traffic and become part of the company's long-term marketing.

Because the site was built on the group's standards from the start — security, measurement, search structure — there is no migration or rebuild at launch. The company simply turns the product on.

Phase-zero sites across the group

Each Oryvelon company has a public home on its own domain, and each is listed on the Companies page with a profile describing what it does. The profiles on oryvelon.com complement the companies' own sites: they explain each company in the context of the group, while the company site speaks directly to its customers.

The stage of each site varies. Some are fully live products; some are earlier in their journey. The standard is the same: real content, honest status, proper foundations.

Common mistakes

A few mistakes come up often when teams build pre-launch sites:

Only a "coming soon" page. It wastes months of potential search visibility and teaches nothing.
Over-promising. Listing features that are not certain creates disappointment and support work later.
Invented social proof. Fake testimonials or logos destroy trust instantly when discovered.
No measurement. Without events on the actions that matter, the site cannot validate anything.
Collecting too much. Long sign-up forms reduce sign-ups and create data you must protect.
Forgetting email authentication. Waitlist emails land in spam, and the domain becomes easier to spoof.
Treating it as temporary. A site built to be thrown away rarely gets the care that makes it valuable.

A phase-zero checklist

Before a phase-zero site goes live at Oryvelon, we check:

[ ] Domain locked, auto-renewing, under a 2FA-protected account.
[ ] HTTPS, security headers and email authentication in place.
[ ] Homepage states the audience, problem and solution clearly.
[ ] Each audience has a page that speaks to it.
[ ] At least one useful piece of content beyond the pitch.
[ ] A clear action, collecting only necessary data.
[ ] Honest status information.
[ ] Privacy notice and terms.
[ ] Analytics with events for key actions; internal traffic tagged.
[ ] Titles, descriptions, sitemap, robots rules and organisation structured data.
[ ] "An Oryvelon company" mentioned naturally, not as a logo.

Writing the homepage: a practical template

The homepage carries most of the weight on a phase-zero site. We use a simple structure that works for very different companies.

1. One sentence that names the person and the outcome. Not the technology, not the company's ambition — the person and what changes for them. "Your Shopify store, watched every day" says more than "AI-powered commerce intelligence".

2. The problem, described the way customers describe it. Two or three short paragraphs using phrases from real conversations. Visitors should recognise their own situation.

3. How the product helps. Three or four concrete capabilities, each tied to part of the problem. If a capability is not ready yet, say so.

4. Who it is for — and who it is not for. Being explicit about fit saves everyone time and makes the right visitors more confident.

5. What happens next. A single clear action and a sentence about what the visitor will receive: an invitation, an early-access email, a call.

6. Trust signals that are true. The team behind the product, the group it belongs to, how data is handled. No invented logos or quotes.

7. Answers to the questions people actually ask. Pulled from conversations, not imagined.

This structure is deliberately plain. The design can be distinctive; the message should be unmistakable.

Waitlist emails that people read

A waitlist is only useful if the relationship continues after the sign-up. We keep waitlist communication short, honest and infrequent.

Confirmation: sent immediately, from the company's own domain with proper authentication, confirming what the person signed up for and what to expect.
Occasional updates: real progress, not filler — a feature that now works, a question we want their opinion on, an invitation to try something.
The invitation: when early access opens, a clear message with a single action.
An easy exit: every email makes it simple to leave the list.

Each company sends its own emails to its own list. A waitlist for one Oryvelon company is never used to promote another. See Marketing consent is not product consent.

When phase zero ends

There is no fixed duration. A phase-zero site moves into launch when the product meets its written MVP acceptance criteria and the team is ready to support real users. Before that point, the site keeps doing its job: learning which messages work, building the list, and accumulating search visibility.

Occasionally the phase-zero site reveals that the idea needs to change — a different audience responds, or a secondary feature turns out to be the main attraction. That is a success, not a setback. It is exactly the kind of lesson that is cheap to learn at phase zero and expensive to learn after launch.

Phase-zero sites and the Oryvelon website

Oryvelon.com itself follows the same idea at group level. It explains what the group is, lists the companies, describes how we build and publishes notes like this one. Each company profile on oryvelon.com — for example MerchNivo, CastLyra or EduRelia — acts as a second, independent explanation of that company, written in the context of the group. Together with each company's own site, that gives search engines and AI assistants two consistent, factual sources describing what the company does and who stands behind it.

That consistency matters. When a company's own site, its profile on oryvelon.com and its founders' authority sites all describe it in the same terms, it becomes much easier for search engines and assistants to understand the company as a real entity — and to recommend it when someone asks the right question. See Founder authority sites and how they relate to a company group.

Phase-zero sites for different kinds of company

The template above works across the group, but each type of company has its own emphasis, and its own traps.

A marketplace needs two front doors. A site for CastLyra has to speak to talent and to businesses, with separate pages, separate calls to action and separate sign-up forms. Mixing them confuses both. It also must not imply activity that does not yet exist: no talk of a thriving community before there is one. Registration forms ask only for what verification will later need, and nothing is published about any person without their consent.

An education product speaks to adults. For EduRelia, the phase-zero site addresses families and schools, and the waitlist collects contact details from adults only. There is no reason to collect anything about a child before the product exists, so the site does not.

A consumer AI product sets expectations early. A site for ZodiVela states plainly that readings are for reflection and entertainment, not prediction or advice. Setting that framing at phase zero is far easier than correcting it after launch.

A decision-support product is careful with specifics. A relocation site can explain in general terms how eligibility tends to work, but specific answers belong to the product's verified rules, not to a blog post that may go out of date. Where rules change, the content says when it was last reviewed.

A commerce brand can sell from day one. For a direct-to-consumer brand, phase zero may simply be a small catalogue with honest stock information and a notify-me option for items not yet available. The same principles apply: true claims, minimal data, proper measurement.

How much to build at phase zero

There is a real trade-off here. Build too little and the site teaches nothing and ranks for nothing. Build too much and you have spent product time on a website for an offer that may still change.

The rule we use: build what you would keep, and nothing you would have to undo.

That means the foundations are done properly — domain, DNS and email authentication (see Domain, DNS and email security), measurement, search structure — because they carry straight into launch. It also means content that answers real questions, since it keeps earning after launch.

It usually does not mean user accounts, complex content management, a design system built out for every future screen, or pages for features that are still uncertain. Those can wait until the product exists and the message has been tested.

A few specific choices follow from that rule:

Measure actions, not people. Phase zero needs to know how many visitors joined, from which source and after reading which page. It does not need to follow individuals around. See Analytics without surveillance.
Settle the name and domain first. Rebranding after months of indexing throws away the search visibility the site was built to earn. See Naming, domains and brand architecture.
Keep pages easy to change. Headlines and offers will be rewritten several times. A simple, well-structured site makes that a small job.

A good phase-zero site is modest in scope and high in quality. That combination is what lets it turn into the launch site without a rebuild.

Summary

A phase-zero site is the first real product a company ships: a clear, honest, well-built website that tests the message, builds an audience and starts earning discoverability before the product is ready. It costs little, teaches a lot and keeps paying back long after launch. That is why every Oryvelon company starts with one.

Questions and answers

What is a phase-zero site?

A proper website for a company that exists before its product is finished. It explains the problem and solution, invites people to register interest and is built to be found in search.

Why does Oryvelon launch sites before products?

To test the message with real visitors, build an audience early, and start earning search visibility months before launch.

Is a phase-zero site the same as a landing page?

It goes further. A landing page usually has one message and one form; a phase-zero site has enough useful content to be valuable and discoverable on its own.

Published by Oryvelon, a digital company builder · About the group · Our companies · More in Company Building

NextContinue, stop or scale: how we make portfolio decisions at 30, 60 and 90 days →