TAPinto® Studio

How the Landing Page Builder Works

What the Studio does

The Studio Builder is your internal control panel for spinning up TAPinto landing pages without touching code. It takes a short, structured brief, asks the agent to generate a page definition, stores that safely in Cloudflare KV, and immediately serves it via the landing worker at /your-slug.

Step 1 · Capture the brief

In the Builder you provide four things:

  • Slug – the URL path, e.g.spring-offer.
  • Primary audience – individual, small business, enterprise, or white label.
  • Offer title & description – one clear paragraph in your own words.
  • Goals – one goal per line (e.g. “Convert 50 early adopters before launch”).

Step 2 · Agent generates the page

When you click Generate & publish, the builder calls the API at /api/generate-landing-page.

The AI agent (or a smart template in early versions) turns your brief into a structured page definition – hero, highlights, sections, persona variants and SEO metadata – and writes it into KV under page:slug.

Step 3 · Worker serves the page

The landing worker checks KV first whenever someone requests /slug. If a KV entry exists, it is converted to the internal content model and rendered with the same components as TAPinto's own marketing pages.

If KV doesn't have a match, the worker falls back to the static definitions in src/content/pages.ts.

Step 4 · Credits & upgrades (soon)

In this preview build, generating pages is free. Ultimately every generation and major edit will:

  • Debit a small amount of TAPinto credits from the account linked to the user.
  • Show a gentle upgrade banner in the Builder when balances are low, with a deep link into the TAPinto billing flow.
  • Record an audit trail so you can see who published which version and when.

Using this with real customers

For launch, we imagine three tiers:

  1. Internal / agency mode – TAPinto team uses the Builder to create pages on behalf of partners.
  2. Guided self-serve – selected partners get access to the Builder with credit packs and approval workflows.
  3. Full self-serve – the Builder is framed as a core TAPinto feature, tightly integrated with user profiles, memberships and communication tools.

This page is meant as a living explainer. As we add versioning, inline editing and credit flows, we can keep this narrative in sync for partners and future team members.