Build
Enabling people, technical and not, to make things with AI: tools, access, model keys, and data, without a ticket queue in the way.
Build is the part of the surface concerned with letting people in your organization make things with AI. It covers the tools they work in, the identity that gets them in, the model credentials they use, the data they can reach, and the path from an idea to something running.
It is the letter almost everyone starts with, usually by buying a coding assistant, and the one most often mistaken for the whole surface. An assistant is one tile on Build. The rest of Build is what happens to the things people make with it.
The claim
If Build is missing, nothing else on the surface gets exercised, because nothing gets made. If Build is the only letter you cover, you have manufactured demand for the other four and no way to meet it: applications with no runtime, keys with no attribution, and a growing pile of useful things nobody can see, steer, or account for.
The two tests that matter:
- How long from a new person’s start date to their first shipped AI change? Measured for an engineer, and measured for someone who is not one.
- If we replaced our primary AI tool next quarter, what would we have to rebuild? If the answer includes identity, keys, data access, or runtime, those things are in the wrong place.
The tension
Build pulls against Secure in the obvious way and against Control in a subtler one. Every guardrail is friction, and friction pushes people toward the unsanctioned path, which has no guardrails at all. The resolution is not to pick a side. It is to make the guarded path faster than the unguarded one, which is a platform problem rather than a policy problem.
Read idea to production first if you only read one page here.
In this part of the surface
- Tooling — The enablement layer beneath IDEs, agent CLIs, notebooks, and chat. How to survive tool churn without re-platforming every year.
- Access — Identity for builders: who gets which AI tools, how they authenticate, and how a new hire is productive on day one.
- Keys and models — Distributing, scoping, rotating, and metering model credentials. BYOK, local models, models through your own cloud, and BAA-covered endpoints.
- Data access — Connecting builders to the data they need without handing out production credentials. Masking, scoping, approvals, and the retrieval plumbing problem.
- Idea to production — Golden paths, templates, and scaffolds. DORA lead time applied to AI work, and what it takes for non-engineers to build like engineers.