How ForGrit builds your app

You start by writing what you want to build in plain English — no technical spec, no exact wording required. A worked example: someone building a startup landing page might write something as simple as “Build a conversion-optimized startup landing page with a hero, feature sections, testimonials, a pricing table, FAQ, and a newsletter signup.” ForGrit turns a brief like that into a plan.

The same brief-first approach works whether you’re describing a one-page marketing site or a multi-role SaaS product. ForGrit doesn’t need you to name your stack, your database schema, or your component structure — it infers structure from intent, then shows you what it inferred before building anything.

ForGrit turns your brief into a plan you check before anything is built — the features, the screens, and the assumptions it made, all in plain language. Nothing is generated until you review and approve this plan.

Alongside the plan, you see a cost estimate. The honest range is wide, because complexity varies a lot: a startup landing page runs about 40–60 credits, while an ai chat application (medium complexity) runs closer to 160–220 credits, and a full saas analytics dashboard runs about 240–300 credits. Across ForGrit’s example builds, that spans roughly 40–300+ credits — the number scales with what you’re actually asking for, not a flat per-app fee.

Before committing to a full build, you see a representative visual preview of the app — a real look at layout and design, not a text description of one. This is the last checkpoint before credits are used.

If the preview or the estimate isn’t right, you adjust the brief and review again. Credits are used only after you approve the cost — there’s no build running silently in the background while you’re still deciding.

Once you approve, ForGrit generates the app and runs quality checks against it. Build time scales with complexity, not with a fixed timer: a simple-complexity build like startup landing page finishes in about 2 min, a medium-complexity build like ai chat application takes about 3 min, and a complex-complexity build like saas analytics dashboard takes about 4 min — roughly a 2–5 minute range across ForGrit’s examples.

If a paid generation step fails, credits for that step return to your balance — you’re not charged for ForGrit’s own failures.

The generated app is stored in a private GitLab repository linked to your project, with version history you can review — private by default, version history. From there you put it online, or download and export it when you’re ready.

This is the same launch step every ForGrit build goes through, regardless of what you built. Your code is never used for model training, and it’s only listed or transferred on the marketplace if you explicitly approve that workflow.