Insights / Company Building · · Updated · 13 min read

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

How to build a useful pre-launch website: explain product status, test interest, limit data collection and prepare for search without promising visibility.

A domain with a logo, the words "coming soon" and an email field gives visitors little context. A more useful pre-launch page explains the intended audience, the problem and what someone can expect after registering interest.

This guide uses phase-zero site to mean a useful public website that exists before a product is ready. The checklist and examples below are recommendations for planning one, not a claim that every Oryvelon company has implemented them.

What a phase-zero site is

A phase-zero site can be the first useful version of a company website. Before the product launches, give it four clear jobs:

  1. Explains the problem in the customer's own language.
  2. Describes the proposed solution, distinguishing available capabilities from plans.
  3. Captures interest through a waitlist, an early-access request or a direct contact form.
  4. Makes public information accessible to readers and permitted crawlers, without promising indexing, rankings or assistant citations.

One substantive landing page can be enough. Add pages when they answer distinct questions or serve different audiences, rather than to reach a page-count target.

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" explanation describing the proposed approach and clearly marking features that are not available.
  • Information for each audience, with separate pages only where useful. A marketplace may need different explanations for buyers and sellers.
  • 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.
  • Ownership and contact information, including any group relationship that can be verified.

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.

Keep collection proportionate to the next step. For a simple email waitlist, consider whether an email address alone is enough. Do not add phone numbers, birthdays or other fields without a clear purpose. Explain the collection and review storage, access and deletion arrangements before enabling the form.

Built properly from day one

Even a small pre-launch site needs deliberate technical choices. Review these foundations against its actual features and risks:

  • Domain security: registered, locked, set to auto-renew, under an account with two-factor authentication.
  • HTTPS and security headers: use HTTPS throughout, test for mixed content and choose headers appropriate to the site.
  • Email authentication: configure and test SPF, DKIM and DMARC for the actual sending service. Authentication helps reduce impersonation and delivery problems; it does not guarantee inbox placement. Check the current Gmail sender guidelines when sending to Gmail.
  • Measurement: define the actions needed for decisions, test event collection, minimise data and document the privacy choices involved.
  • Search structure: clean headings, descriptive titles and meta descriptions, a sitemap, sensible robots rules and structured data describing the organisation.
  • Readable information: put important facts in visible text, use clear headings and keep any structured data consistent with the page.

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

Visitors who have not heard the pitch can reveal confusing language. Ask them to explain the offer in their own words and observe whether they complete the intended action. A sign-up rate provides behavioural evidence, but does not by itself establish understanding or willingness to pay.

It can build an audience early

A waitlist can provide a way to invite interested people to try a first version, within the communications they agreed to receive. Treat registrations as an interest signal. Check whether people reply, accept an invitation or use the product before drawing stronger conclusions.

It allows discovery before product launch

Publishing useful public pages before launch gives search engines an opportunity to discover them. It does not establish a timetable for indexing or rankings. Review actual Search Console reports, including their reporting delay, rather than assuming that an older domain has earned visibility.

For Google's AI search features, Google's optimization guide recommends ordinary SEO foundations and useful, original content; special AI files are not required. Meeting the guidance does not guarantee indexing or inclusion. It also does not establish whether ChatGPT, Claude or Perplexity will cite a page.

It gives the brand a home

A public page gives potential partners, journalists and hires a place to check what a company says about itself. Even a brief status page can help if it names the offer, explains what is available and provides a genuine contact route.

How to measure a phase-zero site

Start with the questions the site should help answer. Combine behavioural reports with direct feedback, and separate completed outcomes from clicks or form attempts. With a small sample, treat differences between pages as observations to investigate, not reliable proof that one message wins.

Question Evidence to examine
Do visitors understand the offer? Visitor explanations and feedback, alongside completed actions
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
Does interest continue beyond a sign-up? Replies to follow-up emails, calls booked, early access accepted
Is search starting to work? Indexed pages, impressions and queries in search tools

Use consistent campaign parameters on controlled external promotional links where useful, and keep staff or test visits separate from audience behaviour. Do not put UTM tags on ordinary internal navigation. A promotional visit, an outbound click, a destination session and a lead are different observations. See UTM standards and outbound clicks, destination sessions and leads.

Content that earns its place

Give the visitor something useful even if they never sign up: a clear answer, a practical comparison or a way to make a better decision. Choose topics because they serve that audience, rather than because a publication quota needs filling.

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 example, a hypothetical relocation service could explain how to find the relevant government guidance and record when each source was checked. An unverified internal rules engine is not evidence that an eligibility claim is correct. A hypothetical store-operations service could explain which operational signals a merchant should investigate; see Shopify operations signals for related reading.

Avoid repetitive pages that add no useful answer. Consolidate overlapping explanations and maintain the strongest page when the underlying information changes.

From phase zero to launch

Plan which parts of the pre-launch site can remain useful when the product becomes available. Possible changes include:

  • 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 are reviewed for accuracy, maintained and linked to the available product where relevant.

Launch still needs a review of forms, account access, payment flows, security, analytics and support arrangements. Some sites can reuse their existing pages; others need migration or development work. A pre-launch site is not evidence that the product is ready.

Phase-zero sites across the group

The Oryvelon Companies page provides group profiles and links to company domains. Those profiles describe the companies in the context of the group. A listed domain is not proof that a product is available or that a working pre-launch site has been published.

Check the actual destination before describing its status. A parked domain, a waitlist and an available product are different states. Keep claims about availability specific to what has been verified.

Common mistakes

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

  • An unexplained "coming soon" page. Visitors may lack enough information to decide whether the offer is relevant.
  • 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 plan. Unchecked event collection leaves gaps in behavioural evidence; interviews and other direct feedback remain useful.
  • Collecting too much. Unnecessary fields add friction and create more data to protect.
  • Forgetting email authentication. Missing or incorrect configuration can create delivery and impersonation risks.
  • Treating it as temporary. A site built to be thrown away rarely gets the care that makes it valuable.

A phase-zero checklist

Use this proposed checklist before publishing a pre-launch site:

  • [ ] 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 intended audience can find a relevant explanation.
  • [ ] At least one useful piece of content beyond the pitch.
  • [ ] A clear action, collecting only necessary data.
  • [ ] Honest status information.
  • [ ] Privacy notice and terms.
  • [ ] Key events tested; external campaigns labelled consistently and staff/test traffic distinguished.
  • [ ] Titles, descriptions, sitemap, robots rules and organisation structured data.
  • [ ] Ownership and any group relationship stated accurately.

Writing the homepage: a practical template

A homepage needs to help a new visitor understand the offer. The following structure is a starting point to adapt and test:

1. One sentence naming the audience and intended outcome. For a hypothetical store-monitoring service, "Daily checks for your Shopify store" is more concrete than "commerce intelligence". Only publish that promise if the planned service can support it, and clearly state when it is not yet available.

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

Plan what happens after a sign-up. Keep updates relevant to the subscription and send them when there is something useful to say. A practical sequence might include:

  • 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: verified progress, a relevant feedback question or an invitation to try an available feature.
  • 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.

Keep the purpose of each list clear. Do not assume interest in one product means permission to send promotions for another. Explain who sends the messages and provide an easy way to unsubscribe. The Gmail subscription guidance also recommends opt-in and easy unsubscribe. See Marketing consent is not product consent for related considerations; these recommendations are not a description of every company's implemented email flow.

When phase zero ends

There is no fixed duration. Set product acceptance criteria and confirm that the team can support real users before changing the site to say the product is available. Until then, keep the status accurate, collect appropriate feedback and monitor any observed discovery or engagement.

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 explains the group, lists its companies and publishes operating notes. Profiles such as MerchNivo, CastLyra and EduRelia provide group context. A profile and a company site under the same ownership are related first-party descriptions, not independent corroboration of product claims.

Use consistent names and ownership descriptions so readers can understand the relationship between a company, its group profile and its founder. Check the underlying facts before repeating them across sites. Consistency alone does not establish authority or guarantee a search or assistant recommendation. See Founder authority sites for related reading.

Phase-zero sites for different kinds of company

The following are hypothetical design examples, not statements about features, forms or data practices currently implemented by Oryvelon companies.

A marketplace may need two routes. Explain the proposition for each side and use distinct calls to action where that helps. Do not suggest there is an active community before that is true. Keep initial interest collection separate from later profile publication and verification.

An education concept needs careful intake design. A pre-launch page could address parents or school staff and ask an adult for a contact address. Avoid collecting children's information merely to measure interest. Review the actual audience, data flows and applicable requirements before a real product launch.

A consumer AI concept should set expectations. If the intended experience is entertainment, describe it that way and avoid promises of reliable predictions or professional advice. Make the availability and limits clear before asking someone to register.

A decision-support concept needs traceable sources. Time-sensitive explanations should identify the relevant authoritative source, jurisdiction and review date. Treat a blog post or internal rules engine as something to verify, not as a substitute for current official guidance.

A commerce concept needs honest availability. A small catalogue could show planned items and offer a notify-me option. Enable purchases only when the business can accurately describe and fulfil the offer. Clearly distinguish stock from previews.

How much to build at phase zero

There is a practical trade-off: a page with too little explanation may leave important questions unanswered, while a large site can consume time before the offer is understood. Choose scope around the questions the intended audience needs answered.

A useful rule of thumb is: build what you can maintain, and leave room to revise what you learn.

Invest in foundations that can be reused, including domain management, email authentication, clear content and proportionate measurement. Recheck them as the product changes. See Domain, DNS and email security for related reading.

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:

  • Choose proportionate measurement. Start with the decisions and outcomes you need to understand. Aggregated reports do not, by themselves, mean the underlying collection is anonymous. Review the actual data flow; see Analytics without surveillance.
  • Plan the name and domain, and plan any later move. A domain change does not automatically erase search visibility. Google recommends URL mapping, appropriate redirects and monitoring; rankings can fluctuate while pages are reprocessed. Follow Google's site-move guidance and keep the old-to-new mapping explicit.
  • Keep pages easy to change. Headlines and offers will be rewritten several times. A simple, well-structured site makes that a small job.

A focused site is easier to keep accurate. Reuse what remains useful at launch, and change the parts that no longer match the product or its requirements.

Summary

A useful pre-launch site explains the proposed offer, states its current limits and gives interested visitors a clear next step. Test the message, minimise unnecessary collection and maintain the answers as the product changes. Its value should be judged by what readers learn and what evidence the team gains, without promises about traffic, rankings or future sales.

Questions and answers

What is a phase-zero site?

A useful public website for a company before its product launches. It explains the proposed offer, states what is available and provides a relevant way to register interest or ask a question.

Why publish a site before a product is ready?

It can help test a message, answer early questions and collect interest. Those signals need follow-up; an early site does not guarantee customers, indexing or search visibility.

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

It can be a single substantive landing page or a small site. The important distinction is useful, accurate information and clear product status, rather than the number of pages.

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