01Services
What I build.
I take projects from a rough idea to launch, and I’m happy to keep them running afterwards. Pick one to start a conversation about it.
- Web applications Customer portals, internal dashboards, and full products. Quick to load and obvious to use, for your team and your customers.
- Mobile apps Native iOS in Swift and SwiftUI, or cross-platform when that’s the better call. From first prototype to App Store release.
- Backend & integrations Payments, sign-in, data, and the connections between the tools you already pay for.
- AI & automation AI for the repetitive work that eats your team’s week, tested on your real data before it goes live. If ordinary code does the job better, that’s what you get.
- Cloud infrastructure Hosting on AWS and Cloudflare, set up to grow with you, with a monthly bill you can predict.
- Architecture & consulting A second opinion on what you have, honest build-or-buy advice, and part-time technical leadership. Sometimes the right answer is software you can already buy.
02Approach
How a project runs.
The habits come from Amazon: code review, automated tests, and monitoring from day one. The pace is a small studio’s. You see working software every week and decide what comes next.
Scope it honestly
We agree on the problem, the constraints, and what success looks like before any code is written. You get a written plan and a real price.
Design it to last
A short document covering the approach, the moving parts, and what it will cost to run. Written so you can read it and push back.
Ship every week
Working software from the first week. A demo every week, tests from day one, and nothing hidden from you for months.
Operate or hand off
Launch with monitoring and documentation in place. Keep me on to run it, or hand it to your own team with everything they need.
Every project is different. This is the usual shape.
- Week 1Kickoff: plan and price agreed
- Week 2First demo: real screens to click
- Week 3Your feedback goes in
- Week 4Payments go live
- Week 5The whole flow works end to end
- Week 6Your team tries it with real data
- Week 7Launch, with monitoring in place
- Week 8Keep me on, or take the keys
03About
You’ll talk to the person writing the code.
At a typical agency, your request goes from a sales rep to an account manager to a project manager before an engineer sees it. Here, you talk to the engineer directly.
I spent years as a software engineer at Amazon Web Services, building backend systems and cloud infrastructure where an outage makes the news, and shipping products used by millions of people.
Now I build for businesses directly. A lot of that work involves AI, because it’s genuinely good at some things: reading messy documents, sorting and summarizing, drafting a first pass. It’s also expensive, sometimes confidently wrong, and often not needed. I use it where it pays for itself and say so when it doesn’t.
I don’t have a favorite model or vendor. I pick whatever fits the job, the budget, and how sensitive your data is, and I’ll explain the tradeoff in plain terms.
There’s no account manager and no junior developer learning on your budget. Just me.
Background
- Amazon Web ServicesBackend systems and cloud architecture
- Full-stack product workFrom database to interface
- Native iOSSwift and SwiftUI
- Applied AILLM features, agents, and automation
- Independent consultingArchitecture reviews, audits, and delivery
04Contact
Tell me what you’re building.
A couple of sentences is plenty, no spec needed. I read every message myself and reply within one business day.
Usually the next step is a free 30-minute call. I’ll tell you honestly whether I’m the right fit.