15 step-by-step guides covering exactly what aiKit does today — from starting a project to publishing it live. No filler, no unbuilt features described as available.
Every aiKit project begins at /start, before you've created an account and before you've committed to anything. This guide covers the very first choice you make, the progress tracker that stays with you the whole way, and how the two intake formats relate to each other.
Chat mode is the conversational way to start a project — one clean question at a time, not a stack of labeled fields. Here's exactly how it flows, including the two toggles that change how many questions you're asked.
Form mode lays out the exact same intake as Chat mode, but as a structured form with three expandable sections — useful if you'd rather see and jump between every field at once instead of moving through them one at a time.
The guided interview is an optional but recommended step, available from both Chat mode and Form mode, that sharpens your first draft by asking a short round of specific, grounded questions instead of leaving aiKit to guess at the gaps in what you've told it.
aiKit offers eleven distinct visual style directions for your project, and each one changes more than color — it changes how your copy is actually written. This guide covers what your options are, the full-screen Style Explorer where you compare them, and how to change your mind later.
Once you have a project, a persistent toolbar sits above the real mockup of your site in the right-hand column, on screen throughout building and refining — not just on one tab. This guide walks through every control in it, including which pieces are real and which are honestly marked as not built yet.
Once your first draft exists, it opens into a workspace with four tabs, plus the persistent live mockup and toolbar beside it. This guide walks through what each one actually shows and what it's for.
A first draft is meant to be a starting point, not a finished product — aiKit gives you several distinct ways to refine it depending on how big or small the change is.
While you're inside /start actively building, a sidebar lets you jump to another project or start a new one without losing your place — this is the only place your projects live; see "Finding and switching between your projects" for searching a long list and Test runs.
Publishing always requires an account — a live site needs a real owner. This guide covers what that gate actually requires, the pre-publish checklist, and exactly what changes the moment you go live.
aiKit's free tier is what lets you draft, refine, and publish a project without paying anything. This guide is a plain explanation of how that actually works today, including the parts that are policy rather than something enforced by the product yet.
Once a project is live, aiKit gives visitors a direct way to react to it, gives whoever submitted feedback a real page to track its status, and gives you a full dashboard to decide how fast changes happen and work through every request across every project.
Every project on your account lives in the projects rail inside /start — there's no separate standalone projects page. This guide covers finding one among many, the Test runs section, and getting to a project's Feedback or Client Hub from there. See "The projects sidebar" for the rail's core mechanics (opening it, the Current section, switching projects).
The Client Hub is a private, password-protected page for one project's client — separate from the public feedback widget every visitor sees. Your client answers questions, reviews the live preview, pins comments right on it, and approves each round, all in the app instead of over email.
Alongside building a project, aiKit can turn any goal — a business target, learning a skill, a student's exam, or a personal practice — into a real, dated plan. This guide covers how it works from the moment you set a goal to the ongoing coaching relationship afterward.
Looking for a quick, specific answer instead? Check the FAQ.