The situation
A materials science organisation deciding that generative AI needed an internal strategy, not a vendor contract. The question was how to put GPTs and agents in the hands of their own teams on their own data, without exposing that data to the public internet.
What we did
Engineers embedded into the client's AI and platform teams, building internal agents function by function. Each one working from the data that function actually uses, not generic public data.
Internal agents · function by function
01
Compliance
Regulatory submissions
02
R&D
Formulation + process data
03
Procurement
Supplier + spec history
04
Commercial
Operations + sales data
Each one working from that function's own data
The search layer tuned to each set of documents, because what works on a legal filing doesn't work on a batch record. A labelled test set behind every agent, so a bad change is caught before deploy, not after. The usual enterprise safety checks: no cross-contamination between teams, no sensitive data leaking into model logs. Every action logged, because an enterprise using AI internally will eventually have to explain to legal or audit what the agent did and why.
Change management alongside the engineering. Training the function teams, collecting feedback, iterating the agents. The engineering is a fraction of the work; adoption is the rest.
The shape of it
A small to medium standing team embedded in the client's AI and platform groups.
The outcome
GPTs and agents in regular use across functions, grounded in the organisation's own data, with the evaluation and audit scaffolding to run them responsibly over time.