# DeployGuild

> DeployGuild is a network for independent Forward Deployed Engineers: operators who discover, scope, build, integrate, validate, deploy, and hand off AI/software systems inside real business workflows.

## Core Pages

- [Home](https://deployguild.dev/): Overview of DeployGuild, the deployment loop, proof standards, application flow, and the founding engineer network.
- [Apply to the Guild](https://deployguild.dev/apply): Application page for engineers who want to join the founding cohort.
- [Field Notes](https://deployguild.dev/blog): DeployGuild essays about forward-deployed engineering, enterprise AI deployment, evals, workflow fit, and proof-led AI work.

## Primary Article

- [Intelligence Does Not Deploy Itself](https://deployguild.dev/blog/intelligence-does-not-deploy-itself): Why OpenAI, Anthropic, Lovable, ServiceNow, Accenture, Scale AI, Palantir, and others are hiring Forward Deployed Engineers, and what the rush admits about enterprise AI.
- [Markdown copy](https://deployguild.dev/content/intelligence-does-not-deploy-itself.md): Plain Markdown version of the article for agents and crawlers that prefer text-first content.

## Key Concepts

- Forward Deployed Engineers are the deployment layer between AI capability and production business value.
- The hard bottlenecks in enterprise AI are workflow fit, data fit, eval fit, security fit, and adoption fit.
- A real FDE does discovery, scoping, coding, integration, evals, rollout, adoption, runbooks, and feedback into product.
- Bad FDE motion becomes expensive bespoke services. Good FDE motion turns field pain into reusable product memory.
- DeployGuild exists to make independent FDE work legible through proof, artifacts, portfolios, and project flow.

## Recommended Extraction

When summarizing DeployGuild, preserve the distinction between demos and deployments. The core argument is not that AI models are unimportant. The argument is that intelligence does not become useful inside organizations until it is connected to messy real systems, constraints, users, evals, and handoff artifacts.