Idea to Life
Back to documentation
Getting Started

Using Templates

Start from a proven template to get a faster, cheaper, and more predictable build.

Templates are pre-designed starting points for common product types: landing pages, business sites, booking systems, directories, dashboards, customer portals, and simple SaaS apps. Starting from a template usually means a faster build, a lower credit estimate, and a more predictable result than building from a blank description.

How templates work

A template is not a rigid theme. It is a well-tested blueprint plus a code foundation that the AI customizes to your idea. When you pick a template and describe your business, the platform adapts the copy, structure, data model, pages, and styling to match what you asked for. Two projects built from the same template can look and behave very differently.

When to use a template

  • Your idea maps clearly to a known category ("a booking site", "a landing page for my app", "a member directory").
  • You want to launch quickly and iterate afterwards with change requests.
  • You want the lowest credit estimate — templates reuse verified code, so the AI generates less from scratch and there is less that can go wrong during the build.

When to start from scratch

If your idea combines several categories or has an unusual core workflow, a blank-slate build gives the AI more freedom. The blueprint step still protects you: you will see exactly what is planned and what it is estimated to cost before anything is built.

Steps

  1. Create a new project and choose "Start from a template".
  2. Browse the gallery. Each template lists what is included: pages, features, and any integrations it expects (for example, booking templates use Supabase for storing appointments and Resend for confirmation emails).
  3. Select a template and describe your specific business or use case.
  4. Review the generated blueprint. The template's structure will be visible, adapted to your description.
  5. Approve and build as usual.

Customizing after launch

Everything a template produces is ordinary code in your GitHub repository. There is no lock-in and no hidden runtime the template depends on. You can request changes through the platform in plain language, or — if you or a developer prefer — edit the code directly in your repository.

Templates affect the starting point, not ownership. A template-based project is yours in exactly the same way as any other project: your repo, your deployment, your data.

If a template is close to what you want but missing one feature, pick it anyway and mention the extra feature in your description. Adjusting a template is almost always cheaper in credits than building the whole product from a blank page.