01 / 04
Capabilities · Engagements
What I build, and how I build it.
Most of my work falls into three areas. For each one, here’s what the projects look like, the tools I reach for, and the kinds of problems it fits. I use AI tooling heavily throughout, which is how one engineer covers this much ground.
Recently shippedSquadUp and YardPaint, two iOS apps I designed, built, and launched myself. Both are live on the App Store.
See the studio →Pillar / 01 of 03
01
Full-stack applications
New apps and rebuilds, from first commit to launch.
Customer portals, internal tools, operational dashboards, and customer-facing products, on the web and on iOS. On new projects I default to TypeScript and Postgres, which are well understood and hold up for years. On rebuilds or additions to an existing system, I work in whatever you already run. Either way, I write the code myself.
Spec
- Default stack
- Next.js · TypeScript · Postgres · Tailwind
- Comfortable in
- React · Vue · Python · Go · Rails · MySQL · MSSQL · MongoDB
- Native
- Swift / SwiftUI when iOS is in scope
- Hosting / runtime
- Cloudflare · Vercel · Fly.io · AWS · Azure · GCP · Docker · Kubernetes
- Typical scope
- Days for a fix · 6–14 weeks for a full build
- Pricing
- Fixed price or time and materials
- Team size
- 1 engineer (me)
Problems that fit
- Member portals and customer accounts that need to handle real volume
- Internal tools replacing the spreadsheet-and-Zapier sprawl
- Billing, admin, and audit consoles wired to Stripe or your ERP
Pillar / 02 of 03
02
Cloud, pipelines & automation
The infrastructure and pipelines that move your data from systems to decisions.
Cloud infrastructure and CI/CD that’s containerized, observable, and easy to reproduce. Data pipelines that turn scattered operational data into live dashboards and reports, and from there into automated decisions, with AI where it pays off. This is the plumbing that sits under any AI layer and keeps it honest.
Spec
- Cloud
- AWS · Azure · GCP · Cloudflare
- Containers / orchestration
- Docker · Kubernetes
- CI/CD
- GitHub Actions · pipelines · infrastructure as code
- Data / pipelines
- Python · SQL · Airflow · Temporal · scheduled jobs
- Surfacing
- Dashboards · reports · alerts → decision automation
- Typical scope
- Days for a fix · 3–8 weeks for a build
Problems that fit
- Standing up cloud infra and CI/CD that a small team can run day to day
- Turning scattered operational data into dashboards and reports people trust
- Replacing brittle manual steps with observable, recoverable automated pipelines
Pillar / 03 of 03
03
AI systems & agents
AI systems that do real operational work and can be trusted to run on their own.
Production agents and pipelines built on Claude, the Claude Agent SDK, and MCP, or OpenClaw when an open-source framework suits the deployment better. What separates a production agent from a demo is observability, audit trails, and a way to roll back when it gets a step wrong. I build the version you can leave running.
Spec
- Models
- Claude (Opus, Sonnet) · OpenAI when warranted
- Frameworks
- Claude Agent SDK · OpenClaw · MCP servers · custom tool harnesses
- Runtime
- Cloud Run · Workers · Kubernetes · Docker · self-hosted runners
- Observability
- Langfuse · OpenTelemetry · custom
- Pipelines
- AI evaluation in CI · prompt regression suites · model deployment
- Typical scope
- 4–10 weeks · fixed price
Problems that fit
- Bug-to-PR engineering agents that take a flagged exception, reproduce it, and open a draft pull request with passing tests
- Computer-use agents that drive workflows locked behind legacy UIs without APIs — the operational work that’s been too brittle to automate before
- Multi-agent pipelines that own a multi-step operational process end to end, with audit, rollback, and human-approval gates where they matter
Not just big builds
Plenty of good work doesn’t look like a three-month project. These are welcome too.
- Quick fixes and small jobsA bug that won’t go away, a deploy that keeps failing, a feature that’s 80% done. Small jobs are fine.
- Ongoing help with your teamPart-time or longer-term work alongside your engineers, for as long as it’s useful.
- Joining a project in progressOther contractors or vendors already involved? I can take a piece of it and work alongside them.
- Not sure what you need yetDescribe the problem on a call and we’ll work out what kind of help makes sense.
Next step