Cloud architecture & integration
Landing zones, migrations, and the integration work that connects new services to the systems you already depend on.
- AWS, Azure, and GCP
- Infrastructure as code from day one
- Cost and security reviewed in writing
cloud · genai · training
I help businesses and teams adopt public cloud and generative AI — from architecture and integration through a production pilot, then hands-on training so your people can run it without me.
Plain scope, plain verbs. Everything I do fits one of three shapes — and most engagements use all three, in order.
Landing zones, migrations, and the integration work that connects new services to the systems you already depend on.
Retrieval, agents, and model integration built on your data, with evaluation and guardrails from the first commit.
Workshops and recorded courses built from the same work I ship for clients. No theory you can't use on Monday.
Every engagement starts with a one-page plan you can read in two minutes. It names the phases, the weeks, the deliverables, and the sentence that means we're finished.
// engagement.yaml client: acme-co goal: "support assistant, in production" assess: 2 weeks → readiness report build: 6 weeks → pilot on your account teach: 2 weeks → 4 workshops, runbooks done_when: "your team ships the next feature" "without me"
Assess, build, teach — in that order. Pick where you're starting and see what the plan looks like.
Map the current stack, data, and readiness. Name the real blockers and the first thing worth building.
Three ways to work together. Every one ends with a written handover.
A second set of eyes on a plan, a platform, or a proposal before you commit budget to it.
Assess, build a production pilot on your account, then teach the team that will run it.
A hands-on workshop series for one team, on your stack, ending with something deployed.