I'm RB, Cloud Architect and CEO of RB Consulting. I help companies bring their infrastructure under control by treating it as code β and increasingly, with AI as a force multiplier at every layer of the stack.
- ποΈ IaC: Terraform, OpenTofu
- βοΈ AWS: multi-account architectures, FinOps
- βοΈ Platform Engineering: Kubernetes, GitOps, internal developer platforms
- π€ AI-Native Engineering: autonomous AI agents, Claude Code, internal prompt libraries, LLM-powered workflows
- π Security: policy enforcement, compliance automation, zero-trust
- π§βπΌ Leadership: project management, team building, client advisory
"If you touched it twice, it should be code."
I've gone deep on making AI a core part of how engineering teams operate β not just as a productivity hack, but as a fundamental shift in how work gets done.
What that looks like in practice:
- Claude Code & agentic workflows β using Claude Code for autonomous coding tasks, code review, and infrastructure generation end-to-end
- Claude Skills β building custom Claude Skills that plug domain-specific knowledge and tooling directly into developer workflows
- Internal prompt libraries β building versioned, reusable prompt libraries that encode your team's standards and patterns so every engineer benefits from collective knowledge
- Autonomous AI agents β designing multi-agent pipelines that handle repetitive ops tasks, security audits, and compliance checks without human-in-the-loop for every step
- AI-native team transformation β helping engineering orgs move from "AI as a tool" to "AI as a team member": workflows, guardrails, evaluation loops, and culture
- LLM-powered platform tooling β embedding LLMs into internal developer platforms to reduce toil and accelerate onboarding
If you're thinking about how to actually operationalize AI in your engineering org β not just add a chatbot β let's talk.
Dealing with messy infrastructure, security gaps, AI transformation, or just need to go faster? Reach out.







