Spec to App
Bring legacy code or specification documents — Airbuild analyzes them, asks the right questions, and builds the full application from an agreed plan.
You rarely start from zero. Most projects begin with something that already exists: a legacy application, a specification document, screenshots of the tool you want to replace. Airbuild takes exactly that as input. The agent analyzes the material, combines it with your prompt, asks clarifying questions where the source is ambiguous — and turns the result into a concrete plan. You approve the plan, Airbuild builds the application.
From legacy code or a spec document to an app
Most software has a predecessor: an old application, a requirements spec, a process description, a screenshot of the tool being replaced. Airbuild takes those as direct input — the agent analyzes them and builds the application from what you already have, on a modern stack: React, FastAPI, PostgreSQL.
How Airbuild gets from source material to plan
Start from what exists
Hand over legacy source code, specification documents, PDFs, screenshots or plain text. The agent reads the material and identifies data models, workflows and business rules.
Analysis + prompt
Your prompt sets the goal, the analysis supplies the detail. The agent merges both into one picture of the application to build — instead of forcing your project into a single chat message.
Clarifying questions
Where the source material is ambiguous or incomplete, the agent asks targeted questions before anything is built — not after. Your answers become part of the plan.
A plan you approve
The result is a concrete build plan: pages, data model, API, integrations. You review and adjust it — then Airbuild builds the application from it: frontend, backend, database and tests.
Plan first, then build
The plan is the contract for the build: which pages exist, how the data is modeled, which integrations are wired. Generation runs against that plan, and the security & quality gate still runs before a publish — with the generated test suite available per project as an additional gate. On the Suite Builder plan the same idea scales up to a full specification workflow — from an evidence pack (PDFs, documents, screenshots) through requirements and domain model to architecture with recorded decisions. Together with the auto-generated documentation, the plan stays a living part of the project.
Frequently asked questions
Can Airbuild build an app from a specification document?
Yes, Airbuild can build an app from a specification document. You hand over the spec as a PDF, as text or as screenshots, with a short prompt alongside it. The agent analyses it, asks about whatever is left open rather than guessing, and proposes a plan. Only after your approval does it build the full application.
Can Airbuild rebuild a legacy application?
Yes, Airbuild can rebuild a legacy application. You provide the old source code or its documentation; the agent analyses data models, workflows and business rules, then rebuilds the application on a modern stack: React on the front end, FastAPI in the backend, PostgreSQL underneath. What it cannot infer with confidence, it asks about.
What does the plan contain?
The plan is the concrete build plan for your application, drawn from the analysis of the spec, your prompt and your answers to the agent's questions: which pages are created, what the data model looks like, which API endpoints exist and which integrations are wired up. You review and correct it before a single line is generated.