Multi-agent orchestration
Several agents, each with one responsibility, coordinated with Pydantic AI and wired into the systems and infrastructure the company already runs.
I build systems where several agents each own one job — and I keep them running. Ask the orchestrator below.
At Game Strategies I’m building a new product around a set of agents with separate responsibilities, coordinated with Pydantic AI and connected to the infrastructure the company already runs.
Several agents, each with one responsibility, coordinated with Pydantic AI and wired into the systems and infrastructure the company already runs.
Text, image, video and 3D models combined into a single workflow, plus the backend and frontend around it.
Claude Code and Codex daily, from first prototype to the code that ships, against delivery dates agreed with the business.
These run inside a company, so the repositories stay closed. What follows is the shape of each system and what I owned in it — happy to walk through the architecture in a call.
Inference API that turns a single image into a 3D model, running TRELLIS.2 on H100 GPUs. Synchronous calls for small jobs, a queue for everything else.
Android app for streaming live sports: camera control from the phone and real-time overlays drawn on top of the video feed.
Catalogue of web motion and layout patterns that composes a chosen pattern into a precise prompt for a coding agent.
Each bar is a role placed on the same timeline. Read it top to bottom and you get the short version: test automation, then the platform underneath it, then the agents on top.
I’m most useful where agents have to touch real systems and stay up afterwards. Send me the problem and I’ll tell you straight whether agents are the right tool for it.