Peak Pages / SaaS

The feature is almost done.The waitlist should already be.

Software teams need waitlists, demo pages and webinar sign-ups without developers building the marketing site. With Peak Pages the page comes from a template, is embedded via embed.js inline or as a popup in your product site, and can be read, edited and published via API and MCP with a personal key.

Your goal for the next step

Put the goal into words. Add perspectives and timing right below.

Local draft · no product activation

Create a waitlist

Local example · nothing is published, no lead is stored.

One page. Embedded. Reachable via API.

Waitlist / Embed / Automation

01Waitlist02Embed03Automation

Example / Release funnel

A release in three building blocks.

Waitlist: The “App waitlist” template with form and thank-you page.
Embed: embed.js inline or as a popup, allowed hosts per site.
Automation: API and MCP with pages:read, pages:write, pages:publish.

Example with fictional data · not the product interface

For SaaS teamsWaitlist → Embed → Automation

Your release in the example

What's coming next for you?

Set release, embed and automation. The preview shows the structure and stores nothing.

Local working example · nothing is saved or sent. Please don't enter personal data.

Peak Pages / Start noteLOCAL DRAFT

02 / Your start noteLocal preview

Three answers. One release funnel.

Draft · not yet put together

Waitlist: Still open
Embed: Still open
Automation: Still open

Your input appears here right away. With “View the start note” you check the three details locally.

Two typical release moments

What's on the roadmap?

Pick the moment. Page, embed and measurement follow from it.

New feature before launch

A beta is starting and you want to know who wants to test it.

The action: The “App waitlist” template as a popup in the help centre; one question about team size helps with selection.
The intent: A list of interested users with context, in Peak CRM.

Working example / Beta waitlist

The beta list

Template: App waitlist (example)
Embed: Popup in the help centre
Then: Webhook to your product tool

Editorial structure sketch · not a customer reference

The example shows the structure. In Peak Pages you set up page, embed and API key yourself.

To the next step

Is this for you?

A clear job. Clear limits.

A SaaS team that
wants to treat pages like code.

This is where the example helps.

You need waitlists and demo pages without developer time.
Pages should be embedded in your product site.
You want to keep pages current via API or agent.

Local previewPeak Pages

Nothing goes live

What this preview doesn't do.

This preview publishes no page and collects no enquiries.
Deleting, domains and brand settings are not reachable via API.
Peak Pages measures no usage in your app, only page visits.

From the example to a real waitlist

Start with “App waitlist”.

In Peak Pages, set up the waitlist, allow your product site's hosts and add embed.js. You create a personal API key in the settings under API & MCP.

Start with Peak Pages

Peak Pages / Your next step

The page is ready before the feature is.

Start with the release that's next on your roadmap.

Create a waitlist

Local working example

For software teams with a release plan.

API and MCP with pages:read, pages:write, pages:publish.

Frequently asked questions

Can I embed a funnel in my website?

Yes, with embed.js: inline with automatic height or as a popup. You set the allowed websites per site.

Is there an API?

Yes. Through API and MCP with the scopes pages:read, pages:write and pages:publish.

Which templates fit SaaS?

App waitlist, B2B demo and live webinar.