AI systems design
A system you cannot score is a demo. Evals come before features.
- Claude API
- MCP servers
- Agent orchestration
- Evals
- Spec contracts
- Observability
Gozzy Nwogbo AI Systems Builder & Transformation Partner
I come at it from business, not computer science, and that is what makes it useful. Based in Toronto.
Every item in the fit demo maps to something I have built. Drawn from 483 automations and the systems on this site.
Now · Jul '26
Building
Atomos
A governed AI knowledge layer where every output traces back to the rule that allowed it.
Reading
Rewired
McKinsey's AI playbook.
Listening
Icon
Brent Faiyaz.
Last shipped
A hands-off agent that reads new federal tenders and emits a weekly can-bid / can't-bid digest.
I came at AI from business, not computer science. Business school taught me how to take a messy organization apart on paper: what it sells, where the margin lives, which problems are worth solving and for whom. That training runs underneath every system I build.
Two years ago these tools stopped being toys and became amplifiers, so I went deep while the frontier was still forming. Since then I have built daily: knowledge systems, agents, automation pipelines, real deliverables for real organizations. The systems I rely on every day were built the same way, which is why I can show them instead of describing them.
That combination is rare in one person, and it is the whole point. I sit between what AI can do and how organizations actually work, and I close that gap myself instead of handing off a requirements document and hoping.
At a glance
Worked with
Built with
Consulting projects at Ivey academic program work
Selected for research on incentive design. The root of a lasting interest in why people actually do things, which still runs through the persuasion and content work.
Built workflow-optimization features on a cross-functional team. The year business questions turned into schemas and shipping discipline.
Co-founded a health-tech venture and ran enterprise engagements for Bupa Global, the NHS, and Boston Medical Center. Built the AI orchestration layer behind the platform.
AI and digital-transformation strategy for CIBC and national nonprofits. Each strategy deck shipped with a working system behind it, not just slides.
Building daily: knowledge systems, agents, and automation that run inside real businesses.
483 workflows spanning contract review, freight invoice auditing, finance operations, real estate, logistics, and tax. Each carries evals and a preferred trigger and storage pattern per use case, so a new build starts from a proven shape instead of a blank canvas.
11,000+ knowledge entries across 59 domains, kept as plain text and cross-linked Karpathy-style so context crosses fields: a persuasion principle can inform an ad pipeline, a maintenance philosophy can shape an agent design. 107 session logs record how the system actually gets used, day after day.
The corpus holds distilled working methods from 50+ MasterClass instructors, broken down and cross-linked so their frameworks surface in the middle of real work instead of staying trapped in a lecture.
A complete priced tender package for a six-country infrastructure group, delivered in 3 days against a 4 to 6 week team baseline. The speed is the same knowledge and automation base as everything else on this page, pointed at one deadline.
Counts are live file counts from the working system, not estimates.
AI is only as useful as what you can put in front of it.
A working personal knowledge OS: an MCP server with semantic search over pgvector, daily capture, processing, and digest pipelines, holding 11,000+ entries across 59 knowledge domains. It runs my daily practice.
Read the case study
And the rest of the bench, each ending in an outcome.
Six working disciplines. Every tool below is in live use; none of it is aspirational.
A system you cannot score is a demo. Evals come before features.
Answers should come from knowledge you own and can trace, not model memory.
An agent gets the minimum context and authority the task needs, scoped before it runs.
Measure in time saved first, then convert to money. Technology that cannot answer that is a hobby.
What it sells, where the margin lives, which problems are worth solving and for whom.
The numbers get rebuilt, not accepted.
Open to founding and greenfield AI roles, forward-deployed and solutions engineering, and AI transformation work. Based in Toronto, remote works fine. Say what you are working on and you will get a straight answer.
¶ Correspondence
Three channels