Five steps. One complete build package.

Every client project starts with a pile of unstructured material — a Zoom transcript, a back-and-forth email thread, a rough SOW draft, a Notion doc full of half-formed ideas. Agency Engine doesn't ask you to clean any of it up first. Paste your raw intake material and submit. The pipeline reads across all of it — reconciling contradictions, extracting requirements, and establishing scope before anything gets built. You can also attach brand assets during intake — logo files, brand guidelines, inspiration screenshots, or screenshots of an existing site. Each asset takes a short context note. Those files are passed as vision inputs and influence design system generation and other relevant plan files.

After sitemap approval, Agency Engine writes copy for every page and every section defined in the sitemap. Each block is scoped to its purpose: a hero gets a headline, subheading, and CTA label. A feature section gets a heading, descriptor prose, and individual feature copy. The copy is generated with the client's business context in mind — pulled from the intake material — so it reflects what was actually said in the kickoff.

Once the plan package is complete, Agency Engine generates a scaffold — a setup script that initializes your project directory, drops in the plan documents, and configures the project for immediate use with Claude Code. You can download the setup script and run it locally, or authorize a direct push to a GitHub repository. From the scaffold page you can also provision services directly: Agency Engine creates a Sanity project with dataset and tokens, provisions a Resend API key, and sets up a Vercel project — linking the GitHub repo, injecting environment variables, and triggering the initial deployment. All provisioned credentials are automatically written into the Claude Code starter prompt.