Let me in early

Early access · opening soon

Let them try it first.

AI customers explore your app before real ones do. See where a workflow breaks, with the evidence and a fix prompt for your coding agent.

We’ll only email you about access. No newsletters.

Maya, Theo, Ruth and Sam are illustrative AI guests, not real people.

You built it in a weekend. Nobody’s used it like a customer yet.

AI makes building fast. Walking every flow as a customer, again after each change, still takes hours. So the first person to find a broken step is often a real customer.

Meet your first customers.

They’re not real. That’s the point. Each one uses your app their own way, so each one finds different snags.

  • Maya Curious

    Clicks everything, opens every menu, finds the button you forgot about.

    Finds dead ends and buttons that do nothing.

    “What does this one do?”

  • Theo Coming back

    Leaves, returns days later, and expects his work to still be there.

    Finds changes that don’t stick.

    “Where did my due date go?”

  • Ruth In a hurry

    On a slow phone, on a train, skipping every step she can.

    Finds slow screens and flows that are too long.

    “Six steps to invite someone? I left.”

  • Sam First time

    Has never seen your app before and reads every word.

    Finds jargon and steps nobody explained.

    “What’s a ‘workspace’?”

How it works.

A preview of the Soft Launch experience.

  1. Share your app.

    Send a link to your web app. Live, or not quite.

  2. The guests explore.

    Each guest goes their own way: clicking around, rushing, leaving and coming back.

  3. Read the guestbook.

    What broke, the exact steps, screenshots, and a suggested fix prompt for your coding agent.

  4. They check again.

    After your change, the same guest walks the same path to make sure it holds.

Not a dashboard. A guestbook.

Example guestbook entry · fictional app.

Theo · Coming back

Snag Tidelist · task due date

I moved the launch to Tuesday. It said Saved. When I came back, it was Friday again.

Evidence

Step 3 · after Save, the due date reads Tue 4 Nov. Step 5 · after coming back, it reads Fri 31 Oct, not the date Theo saved.

How Theo got stuck

  1. Open the task “Launch website”
  2. Change the due date: Fri 31 Oct → Tue 4 Nov
  3. Press Save. The app shows “Saved”
  4. Open Inbox, then come back to the task
  5. The due date shows Fri 31 Oct again

Suggested fix prompt

In Tidelist, a task’s due date reverts after saving. Steps: open the task “Launch website”, change the due date from Fri 31 Oct to Tue 4 Nov, press Save (the app shows “Saved”), open Inbox, then reopen the task. Expected: Tue 4 Nov. Actual: Fri 31 Oct. Find where the new due date is lost between the save request and the stored task, fix the cause, and add a test that saves a due date and reads it back.

A starting point for your coding agent, not a verified fix.

The doors open soon.

We’re letting builders in a few at a time. Leave your email and we’ll save you a spot.

We’ll only email you about access.