Questions, answered plainly

aiKit is a platform where you describe a business or project in your own words and it drafts a real site or app plan for you — a working outline of pages, copy, and (for internal tools and apps) actual screens, not just a mockup image. You can then refine that draft in plain conversation and publish it to a real, live link. It's built for people who don't want to hire a developer or wrestle with a website builder just to get something real up and running.

Go to /start and describe what you're building — a business, an app idea, a tool you wish you had. You choose between Chat mode (a back-and-forth conversation) or Form mode (a structured form with expandable sections), tell it as much or as little as you know, and aiKit generates a full first draft: sections, copy, a suggested visual style, and feature ideas. You don't need an account to see this draft — your first project is free and account-free the whole way through building and refining it.

No. Everything in aiKit is driven by describing what you want in plain language and then adjusting it the same way — typing (or dictating with your voice) what you'd like changed, checking or unchecking feature ideas, picking a visual style from a gallery. There's no code editor, no config file, and nothing to install.

No. aiKit is deliberately value-first: you can describe your project, go through the guided questions, and see and refine a complete first draft entirely without an account. Your first project (and, separately, your first goal in the Goals workspace) is free that way. aiKit asks you to create a free account at three points after that: when you start a second project or goal, when you open the Projects or Goals list to see everything you've made, and when you publish a project to a live link — publishing needs an account because a live site needs a real owner. The order is deliberate: you see real, concrete value before you're asked to sign up for anything.

Chat mode is a conversational intake — aiKit asks you one question at a time in a chat interface, the way you'd describe your business to a person. Form mode is the same intake as a structured form, organized into three expandable sections ('The basics', 'Vision & audience', and 'Look & feel'), so you can see and jump between every field at once instead of moving through it turn by turn — Form mode's sections also carry a wider range of optional depth fields (real numbers, what you've already tried, what's driving the project now, behind-the-scenes needs) plus a free-text notes box per section for anything else. Both modes feed the exact same underlying project data and both let you turn on the guided interview — pick whichever fits how you think.

Yes. Chat mode and Form mode stay in sync with each other — anything you've already filled in (your project name, description, audience, goal, style choices, and Form mode's extra depth fields and section notes) carries over automatically when you switch, so changing your mind about which format you'd rather use doesn't cost you any of the answers you've already given.

Yes. Each of Form mode's three sections — 'The basics,' 'Vision & audience,' and 'Look & feel' — has its own open-ended, optional notes textarea at the bottom for anything specific to that section that doesn't fit the structured fields above it: competitive context under Vision & audience, a past attempt you don't want to repeat under Look & feel, whatever's relevant. These notes are folded into the same first-draft-writing prompt as your main description, at the same weight — not treated as an afterthought — so nothing you add there gets silently dropped.

No. Both Chat mode and Form mode fill in the description with the same builder by default: you add it one paragraph at a time — type or dictate a paragraph, press Enter or 'Add,' and it appears as its own compact, editable card above the input, with a running 'N things added' count. After each paragraph, a short nudge suggests what's still worth covering (a real number, a tool you use today, what triggered this now, a past attempt that didn't work, the internal/operational side), and 'Use this description →' moves you on once you're satisfied. If you'd rather write or paste it all as one block instead — the way some people already have it typed up elsewhere — a 'Prefer to paste one big block instead? →' link switches to a single open textarea, and you can switch back at any point without losing anything. Either way, it becomes the exact same single description on your project.

Just a project name and a short description of what you're building — that's the only real requirement. Everything else in the intake (who it's for, your #1 goal, an existing website to reference, a style inspiration, the guided interview, and Form mode's extra depth fields — what's driving the project right now, what you've already tried, specific numbers, behind-the-scenes operational needs, and a free-text notes box on each section) is optional, and aiKit is built to work with partial information, filling in clearly-flagged placeholder content around any gaps rather than blocking you until every field is complete. More detail produces a sharper first draft, but a bare-minimum description is enough to see a real one.

It does both. For every section of your draft — and the hero image at the top — aiKit picks a targeted, concrete photo search (always two specific, photographable words, like 'bakery storefront' or 'electrician panel,' never a vague word like 'quality' or 'trust') so the images that show up actually match what that section is about, instead of generic stock photography that could belong to any business.

Yes. The second project is the point where aiKit asks you to create a free account — the first one is free and account-free, and starting another shows a signup card right where you are, without losing what you've already typed. Once you have an account, every project you've started lives in the projects rail inside your workspace, with a 'New project' link to add another, and there's no limit on how many you can have.

The guided interview is an optional, recommended toggle ('Interview me for a stronger, more complete plan') that has aiKit ask you a short round of multiple-choice questions — with a 'Something else' option any time none of the choices fit — specifically shaped around what you've already told it. It runs in up to three rounds, and each later round is generated based on what you actually answered in the round before, not a fixed generic questionnaire. Turning it on generally produces a sharper, more specific first draft, because the AI is working from real answers instead of guessing at the gaps.

The guided interview runs in short rounds — up to three rounds total, each its own small batch of multiple-choice questions, with a visible 'Round X of 3 — Question Y of Z' progress indicator so you always know where you are. You're never forced to finish all three rounds: there's a bail-out button ('I'm done — build it now →') available at any point during the interview that builds your draft immediately from whatever you've answered so far.

Yes. The guided interview is opt-in, and even once you've started it you can stop at any point — Chat mode and Form mode both have a clear 'I'm done — build it' path that generates your draft immediately from whatever information you've given so far. aiKit never blocks you from getting a first draft; more detail just tends to produce a sharper one.

Yes. Both Form mode and Chat mode have an optional 'Already have a website?' field. If you add a URL, aiKit does a quick read of that page so the questions it asks and the plan it drafts reflect your actual business instead of generic guesses — useful if you're rebuilding an existing site or want your new plan to stay consistent with what's already live.

Yes, for essentially every text field in the intake flow — your project description, audience, goal, Form mode's extra depth fields (what's driving the project, what you've already tried, specific numbers, behind-the-scenes needs), each section's notes box, and free-text answers during the interview — there's a microphone/dictate button next to the field so you can speak your answer instead of typing it.

Every field in Form mode and every question in the interview is optional or skippable — aiKit is built to work with partial information and fill reasonable, clearly-flagged placeholder content around the gaps rather than blocking you until every field is complete. You can always come back later, in the Plan tab, and adjust or replace any section once you know more.

It adapts. Round 1's questions are generated fresh from what you've already described — not a fixed generic form — and mix real business-goal questions with concrete functionality questions. If you continue past round 1, every later round's questions are generated from the actual transcript of how you answered before, specifically digging into whatever came back thin or vague, and aiKit itself judges when there's already enough real depth to stop asking rather than always running the full three rounds.

Two different kinds, deliberately mixed together. Some surface business bottlenecks or opportunities you may not have thought to ask for — after-hours availability, following up on leads before they go cold, automatic reviews or referrals. Others are concrete functionality questions about what the platform should actually let people do — create an account and log in, pay online, book or schedule something, browse a catalog, message you directly, or see a private staff-only area. Every question is grounded in the specific business you described, not a generic template — a landscaping crew and a therapist get genuinely different questions.

That's actually the point of it, not a side effect. Each multiple-choice answer option is written to name a real, concrete capability rather than a vague 'Yes'/'No' — for example an option might read 'Let people book and pay at 2am' or 'Auto-remind past customers every season' — so reading the choices itself surfaces things you may not have realized a website or app could do for your business, even before you pick one.

Yes. When you start a project you pick one or more project types — Website, Landing Page, Client Portal, Internal Tool, App, Admin System, or Something Else — and for the operational types (Internal Tool, Admin System, Client Portal, App) aiKit drafts actual product screens, not just marketing pages: real screen names, the specific role who'd use each one (e.g. 'Office/Dispatch' vs. 'Field Crew'), and concrete interface details like table columns, statuses, and buttons, grounded in the workflow you described — not a generic dashboard.

These are the project types you pick from when starting: a Website is a full multi-section public site, a Landing Page is a single-purpose page built around one goal (like capturing leads), and Internal Tool / Admin System / Client Portal / App are operational software aimed at people who work inside your business or your customers logging in — for those, aiKit drafts real screens and workflows in addition to any public-facing pages, rather than treating the whole project as one marketing site. You can select more than one type for the same project if it genuinely needs both a public face and internal software behind it.

No — aiKit isn't built around fixed industry templates. You describe your actual business or idea in your own words, and the plan it drafts is grounded in that description rather than a pre-built template for 'restaurants' or 'contractors.' It tends to do well with service businesses, local businesses, and small operational tools in particular, because those benefit most from the operational-screen and feature-suggestion parts of a draft, but the intake itself doesn't assume any specific industry.

aiKit suggests one of eleven visual style directions — ranging from spare and minimal to bold and saturated to quiet luxury to playful and colorful — based on what you've described. Each style isn't just a different color palette: it also changes the actual voice of the writing (for example, 'Luxury & Understated' is written in restrained, no-exclamation-point language, while 'Playful & Fun' is written with more energy and personality), so the whole draft feels consistent, not just recolored.

Yes. On the Live Preview tab there's a 'See another direction' button that cycles your draft through aiKit's other style options, and the full style gallery is browsable any time you want to deliberately pick a specific one instead of cycling.

aiKit writes real, specific copy grounded in what you actually told it — not generic template filler. Where it has to invent something you haven't provided yet (a customer testimonial is the clearest example, since nobody has a real quote yet on day one), that section is explicitly marked with a visible 'Sample' flag so it's obvious what's placeholder and what's real, and that flag only goes away once you replace it with the genuine thing.

It's a genuine mix, and which screens are which is worth knowing. For Internal Tool, Admin System, Client Portal, or App projects, aiKit drafts a real, detailed spec for each screen: the screen's actual name, the specific role who uses it, and concrete interface content — real field names, table columns, statuses, and buttons grounded in the workflow you described, not a generic 'dashboard.' For table and record-detail screens specifically, that's now backed by real, working storage, not just a picture of one: you can add a row or record, edit one, and delete one, and it's genuinely saved — reload the page and it's still there, exactly like a real app's database. Kanban boards, dashboards, calendars, and activity feeds are still display-only previews of what those screens would contain (real editing on those is on the roadmap, not built yet). None of it is a finished custom application with its own working login system for your end customers — the editing that exists is for you and your project's members, not a public account system.

There's no fixed per-industry template it fills in. Every draft is grounded specifically in what you actually said — your description, your interview answers, and a scrape of your existing website if you gave one — and the writing system is explicitly instructed never to invent a fact, claim, or detail you didn't provide. Even your assigned visual style reshapes the actual writing voice, not just the color palette, so two businesses with the same style pick still read differently based on what they each told it.

Adding an item from the Kit — any of the roughly 260 items across categories like e-commerce, booking, reviews, or local SEO — writes real, on-brand content into your site describing that feature right away, the same as everything else aiKit writes: it's grounded in your project, not filler. What it doesn't do yet, for most items, is build the actual working system behind the description — a 'Booking & Scheduling' section describes an online booking widget, but doesn't wire up a real calendar backend a customer could book through today. The exception is the operational screens covered above (table and record-detail screens for Internal Tool/Admin System/App/Portal projects), which genuinely save and load real data. Building real, working functionality behind more of the Kit's items — not just the content describing them — is an active part of the roadmap.

Yes — service and trade businesses like landscaping, cleaning, or electrical work are exactly the kind aiKit's feature-planning is built around: describe your crew and how jobs actually flow through your business, and aiKit's plan draws on patterns that genuinely fit that kind of work, like local SEO, a before/after job-photo gallery, quote-to-invoice tooling, and a dispatch/scheduling view — grounded in what you actually told it, not invented industry facts.

Yes. Describe your food or hospitality business — your menu style, hours, what makes you different — and aiKit drafts a plan grounded in that description, the same flexible intake as any other business rather than a fixed 'restaurant template.' Keep in mind aiKit drafts the site's plan and copy, not a live online-ordering or point-of-sale system — that's outside what it builds today.

Yes — Client Portal is one of the project types you can pick, and for it aiKit drafts real portal screens grounded in how you actually manage clients: things like a private status/phase view per client, a place for files you've shared, and your own admin view across every client at once, built from the actual workflow you describe rather than a generic client-list template.

Yes — there's no fixed industry template that limits it, so describe your actual practice (your services, your clients, how people currently book or reach you) and aiKit grounds the plan in that. Health and personal-care businesses tend to benefit especially from the same local-service-business patterns aiKit's feature planning already favors, like online booking-style features and automatic follow-ups.

Yes — this is one of the clearest cases for aiKit's Internal Tool / Admin System project types. Describe how jobs move through your business today and aiKit drafts a real dispatch-style screen spec: table columns like customer, address, assigned crew, and job status, grouped by the actual role that uses it (office/dispatch vs. field crew), grounded specifically in the workflow you described rather than a generic dashboard.

It can draft a plan for a retail or product-based business too — product-focused sections, a catalog-style structure, feature ideas suited to selling physical goods — grounded in what you describe. One honest limit: aiKit drafts the plan, copy, and structure, not a live shopping cart or payment-processing system itself, the same way it drafts booking or scheduling ideas as a feature concept rather than already-wired backend software.

Yes — describe your organization, your mission, and how members or attendees actually interact with you, and aiKit grounds the plan in that description. There's no dedicated nonprofit template, but the same flexible intake that works for any business works here too, including an Internal Tool or Admin System project type if you also need an internal way to track members or events.

Yes — professional and education-focused businesses fall well within the range aiKit is built for. Describe what you teach or coach and who it's for, and aiKit drafts a plan grounded in that, with the option to add an Internal Tool or Client Portal project type if you also want a private area for students or clients.

Yes — a Website or Landing Page project type fits a creative portfolio well, and this is a place where aiKit's style directions genuinely matter: styles like 'Creative & Artistic' or 'Warm & Personal' change the actual writing voice, not just the color scheme, so a creative business's plan can sound distinctive rather than corporate.

Yes — this is a combination aiKit's drafting pipeline handles deliberately, not as an afterthought. When you pick both a consumer-facing type (Website or Landing Page) and an operational type (Internal Tool, Admin System, Client Portal, or App) for the same project, aiKit writes real content for both audiences — genuine public-facing marketing sections for customers, and a genuine screen-by-screen spec for your own team — rather than treating the whole thing as one marketing site with an admin login mentioned in passing.

Yes — aiKit is built to work from a short description with no existing content at all. Every field beyond your project name and description is optional, and where there's a real gap (like not having a customer testimonial yet, since nobody does on day one) aiKit fills it with clearly-flagged placeholder content you can replace once you have the real thing, rather than blocking you until your business has a track record to draw on.

A general chat assistant gives you back a wall of text you'd still have to structure, design, and host yourself. aiKit runs a purpose-built pipeline on top of a top-tier AI model: it interviews you with rounds of grounded, specific questions, writes several independent versions of your first draft in parallel and has a separate pass judge and pick the strongest one, structures the result into real sections/features/screens instead of one blob of prose, applies honesty guardrails (like flagging invented content instead of quietly presenting it as real), and turns the result into an actual hosted, shareable, live web page — not just an answer in a chat window.

aiKit is powered by Claude, Anthropic's AI models, with different models doing different jobs: your first draft is written independently three separate times by a top-tier model, then a separate pass compares all three versions and picks the strongest one before you ever see it. After that, when you're revising and refining your draft, a faster model handles those edits — refinements need to come back quickly, not take as long as the original careful draft.

Your first draft is the moment that matters most for quality, so aiKit spends more on it: it generates three independently-written versions in parallel and has a separate judging pass pick the best one, using aiKit's most capable model. Once you have a draft, revisions switch to a faster, lighter model, because at that point you're making a specific, targeted change rather than needing a from-scratch creative pass — so edits come back noticeably quicker than your first draft did.

'Sample' is aiKit's honesty flag for content it had to invent because you hadn't provided the real version yet — most commonly a customer testimonial, since no new project has a genuine customer quote on day one. It's a visible, deliberate label rather than aiKit quietly passing off invented content as real. The flag clears automatically once you replace that section with your own actual content.

There are a few ways, depending on how big the change is. Each individual section in the Plan tab has its own 'Adjust or remove this section' control where you type or dictate exactly what you want changed and only that section updates. The Features tab lets you check or uncheck any suggested feature, expand one for more detail, or delete it outright. And for a broader rewrite, 'Make it yours' opens a chat-style revision panel where you describe what you want different and aiKit updates the draft accordingly.

aiKit writes three full, independent drafts of your first plan in parallel — each with a different guiding thesis for how to open and structure it (one leads with trust and credibility, one leads with the core mechanism of what you offer, one leads with the specific problem being solved) — then a separate AI judging pass compares all three against each other and picks the strongest one. That judged winner is the draft you actually see; you're never asked to pick between three yourself.

It rewrites the actual writing voice, not just the color palette. Each of aiKit's eleven style directions carries its own voice instruction — for example 'Luxury & Understated' is written in restrained language with no exclamation points, while 'Playful & Fun' carries more energy and personality — and that voice genuinely shapes sentence rhythm and word choice in the generated copy, so switching styles changes how your draft reads, not just how it looks.

You have several ways to change it without starting over. Each section in the Plan tab has its own 'Adjust or remove this section' control for a targeted rewrite of just that part, the Features tab lets you check, uncheck, or delete any suggested feature, 'Make it yours' opens a broader chat-style revision panel for bigger changes, and 'See another direction' on the Live Preview tab cycles your whole draft through a different visual style and voice. None of these require regenerating your project from scratch.

Yes. When you ask aiKit to revise your draft, it's explicitly instructed not to invent specific values for legal or compliance text, license or certification numbers, or real prices shown to customers. Instead of guessing a plausible-sounding number, it leaves that value clearly blank (or applies the rest of your request and leaves just the risky specific out) and tells you in plain language what it didn't guess and what you need to confirm yourself.

Those are do-it-yourself builders — you still choose and arrange blocks, write your own copy, and make your own layout decisions inside their editor. aiKit writes the actual first draft for you: real copy grounded in what you described, structured into genuine sections (and, for internal tools or apps, actual product screens with real fields and statuses), produced from three independently-written drafts that a separate AI pass judges and picks the best of. You start from a real, specific plan instead of a blank block-based canvas.

For getting a genuine first draft — real written copy, a real structure, a matched visual style, and for internal tools a real screen-by-screen spec — no, that's exactly the gap aiKit is built to close for people who don't want to hire someone just to get something real started. It writes and structures the plan itself rather than handing you a blank page to fill in.

A template there is the same layout and placeholder text for every buyer — you're the one who has to replace the placeholder copy with your own words. aiKit writes real, specific copy grounded in your actual business from the start, and its eleven style directions change the actual writing voice, not just the visual theme, so what you get isn't a generic layout waiting to be filled in.

A no-code builder gives you components and logic you assemble yourself inside their tool — you're still doing the building. aiKit interviews you first (through rounds of grounded, adaptive questions) and writes the actual plan before you touch anything: real section copy for public-facing pages, and for internal tools or apps, real screen names, roles, and concrete interface content like table columns and statuses — a finished draft to react to and refine, not an empty builder canvas to learn.

You can, but you'd be doing by hand everything aiKit's pipeline does for you: turning one description into a structured set of real sections (or operational screens) with headings, nav labels, and photo direction; running that draft three independent times with different angles and having a judging pass pick the strongest one; flagging what's invented placeholder content versus real; and then actually hosting it at a live, shareable link with a feedback widget. A chat window gives you a wall of text you'd still have to structure, style, and host yourself.

For the part most small businesses actually get stuck on — turning a rough idea into a genuine, specific first draft of real copy, structure, and visual style (and for internal tools, a real screen-by-screen spec) — yes, that's exactly what aiKit does, at no cost and without needing to brief and wait on a freelancer. It's built around a plan-generation-and-refinement pipeline, so if what you need goes beyond that into custom development, that's outside what aiKit does today.

It behaves more like a consultant that also hands you a real draft. The guided interview is deliberately built to ask the way a sharp consultant would — surfacing bottlenecks and options you might not have considered (after-hours booking, automatic follow-ups, a private staff area) — rather than just collecting form fields, and the plan it hands back afterward includes concrete, checkable feature ideas mixing website-, admin-, and app-level capabilities, not just page layout choices.

Yes, in the sense that matters most: you can describe your project, go through the full guided intake, see a complete first draft, refine it, and publish it to a real live link — all without paying anything or entering a credit card. aiKit's model is a 90-day free live preview window for every published project before any paid yearly hosting applies, and right now every published project stays live and free, since the paid hosting step isn't turned on yet.

aiKit's plan is a 90-day free live preview window for a published project, after which continued hosting moves to a paid yearly plan. That paid hosting step is still being built and isn't live yet, so right now every published project simply stays up on the free tier — nothing currently gets taken down or paywalled after 90 days.

From your side, no — editing and refining your draft during the free preview doesn't feel limited or metered. There's no visible edit counter, running total, or paywall interrupting you while you revise your plan.

No. You don't need a credit card to build a draft, and you don't need one to publish it, either — creating a free account is the only step required before your project goes live.

It's a small badge and link that appears at the bottom of every free-tier published site, reading 'Built with aiKit ∞' and linking back to aiKit. It's part of how free hosting works — it's what funds giving projects a real live link and hosting at no cost during the free preview window.

Not right now. The badge is part of every free-tier published project today, and there's no paid, badge-free tier live yet to switch to. That's a planned direction, not something available currently.

aiKit's model is a 90-day free live preview window for every published project, with paid yearly hosting planned to apply after that. That paid step isn't built or turned on yet, so right now, every published project simply stays live and free with no cutoff — but the honest long-term plan is a free preview period followed by paid hosting, not free forever by design.

The catch, such as it is, is visible rather than hidden: every free-tier published site carries a small 'Built with aiKit ∞' badge at the bottom that links back to aiKit, and that badge is part of how the free hosting gets funded. Beyond that, the plan is a 90-day free preview followed eventually by paid yearly hosting — that paid step just isn't live yet, so today there's no hidden fee or bait-and-switch, just the badge and the future paid-hosting plan.

No. Publishing itself is free — you create a free account (no credit card needed) and your project goes live immediately at a real link. There's no paid plan to pick or upgrade to at publish time; paid yearly hosting is a planned step for after the 90-day free preview window, and it isn't built or enforced yet.

Once you've refined your draft to where you're happy with it, you create a free account — a live site needs a real owner — and confirm publishing. If you already made an account earlier (starting a second project, or opening your Projects list), this step is skipped and you go straight to publishing. Publishing sets your project live immediately at a real address on aiKit's platform — there's no waiting on DNS or a manual approval step.

You get a real, working link at aikit.ai/s/your-project-name that's reachable the instant you publish, with your project's own sections, style, and (if you selected any) a feature/what's-included band, plus a live feedback widget visitors can use. A custom subdomain of your own is on aiKit's roadmap but isn't available yet — today, every published project lives at that shared aikit.ai address.

Your draft lives in the Plan workspace (Live Preview, Plan, Features, and Summary tabs) while you're working on it, and the Summary tab is built to be viewed or downloaded to share with someone directly. A project only gets a real public link once you actually publish it — before that, it isn't reachable at a public URL.

Every published aiKit site includes a feedback widget that visitors can use right on the live page to leave a comment or flag something — no separate account or tool required on their end.

Feedback submitted through your published site's widget lands in your account's Feedback dashboard, where each item is tied to the specific project it came from and threaded so you can see the conversation around it, not just a flat list of disconnected comments.

Your project's draft and details are tied to your account and session, not exposed publicly, until you choose to publish. Before you create an account, an in-progress draft is scoped to your current browser session rather than being publicly listed or searchable. Once you publish, the content you've included on that page becomes public by design — that's the point of publishing — so review your draft before that step the same way you would before making any page public.

When there's no real customer quote yet — which is true for every brand-new project — aiKit does invent a plausible-sounding testimonial so the section isn't empty, but it's never presented as real: that section gets a visible 'Sample' badge in the interface that only clears once you replace it with an actual quote. The invented quote text itself still reads as normal, finished prose rather than announcing its own fakeness (no '— placeholder quote' inside the quote), because the honesty signal is the visible Sample flag, not broken-looking text a real visitor would find confusing.

Honesty is built into several separate mechanisms, not just a policy statement. Every section aiKit had to invent (most commonly a testimonial) gets a visible 'Sample' flag until you replace it with the real thing. The writing system is explicitly instructed never to invent a fact, claim, or detail you didn't actually provide. And when you ask for a revision that would require inventing something risky — legal text, a license number, an exact price — aiKit declines to guess and tells you plainly what it left out instead.

No — the system that writes your draft is explicitly instructed never to invent facts, claims, or details you didn't actually give it. Where it has to fill a gap because you haven't provided the real content yet (a testimonial is the clearest example), that content is clearly marked with a visible 'Sample' flag rather than presented as something you said, and your tagline and business description specifically stay general rather than guessing a narrower business model than what you actually described.

Yes. Your draft lives in a Live Preview tab that shows the real rendered page — not a text summary — while you're still refining it, well before you create an account or publish anything. Nothing about your project is reachable at a public URL until you actually choose to publish, so you get a full look at the real thing first.

The public feedback widget on a published site is for anyone visiting the page. The Client Hub is a separate, password-protected page for one specific client — a place to ask them questions directly (with optional multiple-choice answers), log what they say, and keep it out of email entirely. You open a project's Client Hub from the small '💬' button next to it in your projects rail, set a password, and share the link with your client.

No. Your client only needs the link you give them and the password you set — no signup, no login of their own. They enter the password once and their browser stays signed in after that.

The moment your client answers a question, it's logged and shows up in your project's Client Hub manager immediately — no polling, no separate export step. An answered question moves to your client's own 'Answered' history too, so they can see what they've already told you.

In their Client Hub, on the 'Review & Approve' tab, your client sees your real live page in an embedded preview with a Desktop/Mobile toggle, can click anywhere on it to pin a specific comment (which lands in your Feedback dashboard like any other request), and clicks '✓ Approve this round' when they're satisfied. You start the next round from your side once that one's approved — round history (v1, v2, and so on) stays visible to both of you the whole time.

Yes — the Client Hub's 'Requests' tab is for exactly that: anything not tied to a specific pin, like 'add a testimonials section' or general feedback. It shows a live count by status (Requested, In Progress, Done, Verified) and every request your client has filed, pinned or not, so they always have one place to see what's outstanding and what's shipped.

It's a third way to start on aiKit, alongside creating a product: instead of describing a website or app, you describe an outcome you want — a business target, learning a new skill, a student's exam, or a personal practice — and aiKit builds a real plan around it: a short strategy, dated milestones worked out from your deadline, concrete tasks, and an ongoing coach you can update as you go.

Yes, and they get identical treatment — same intake, same AI, same quality of plan. Categories include Business, Learning, Student & Study, Skill, Personal & Wellness, Creative, and Financial. The category changes your coach's tone (direct and numbers-forward for business, gentle and non-clinical for personal/wellness goals) but never the quality or depth of the plan itself.

aiKit writes a blueprint — a short overview of the real path to your goal, a few strategic pillars, and a First Win (one specific thing doable in under 20 minutes, today) — plus 4-7 dated milestones, worked out backwards from your target date if you set one. Each milestone comes with a couple of concrete tasks and, where useful, specific how-to tips.

Yes, fully. Every milestone has quick actions to make it easier, split it into two, push its date (with a choice to compress later milestones or move your whole finish line), or delete it. You can add a new milestone just by typing a plain sentence describing what you want — aiKit drafts it, you approve it before it's added.

It's an ongoing update thread tied to your goal — post a win, a struggle, or a question any time, and aiKit replies specifically to what you said and may add a few genuinely relevant new tasks. A Coach intensity setting (Gentle, Steady, or Push me) controls how direct that coaching is, and you can change it any time.

When it would genuinely help, aiKit proposes one bespoke tool built specifically for your goal — like a daily practice quiz for a language goal — using the same real generation pipeline as any aiKit project. You see the proposed description before anything is built, can edit it, and can skip it entirely; a goal never requires one.

They're real, named outside resources — an app, a book, a course, or a practice — that aiKit thinks would genuinely help a specific milestone. These are always real, existing things, never invented products, and aiKit will point you to the best real option even when it isn't anything aiKit builds itself.

A genuinely in-depth, on-demand lesson — generated only when you ask, not automatically for every task. Each one opens with the specific misconception people usually get wrong about that topic, a real detailed walkthrough, a self-test question with its answer, and a pointer to a related topic worth learning next. It's written once and saved, so revisiting it doesn't regenerate it.

No. Choosing a Personal & Wellness goal shows this plainly before you continue: it's a practice companion that can help you build a gentle habit and notice your own progress, not therapy or medical care. For anything serious, it also points you toward a real person — a counselor, a doctor, or someone you trust.