One engineer, in your timezone, who ships the whole thing and is still there when it needs to change.
I'm Nathan Patterson, a software engineer in Salt Lake City. I build full-stack systems on TypeScript, Next.js and AWS, and I was most recently the only engineer on a homebuilder's entire platform. Every system, one person.
Full-stack product builds
The whole thing, end to end, by the person who will still be there in month three.
Next.js and TypeScript on AWS, PostgreSQL underneath, deployed on infrastructure that costs what it should. Most recently a full rebuild for a Salt Lake City event production company: a public site plus a multi-tenant client portal with row-level security, shipped and running.
A fit when
You have a product idea and no engineering team yet.
You have a site that works and a portal that does not.
You need one person accountable rather than four people coordinating.
AWS and Next.js, off the rails
For teams already on the stack who have hit the part nobody blogs about.
Self-hosting Next.js on AWS instead of Vercel, SST and CloudFront, cold starts, cache behaviour, the bill. I run this exact setup in production and can tell you what it actually costs, because I pay it.
A fit when
Your Vercel bill grew faster than your traffic.
You need to leave a managed platform and keep the app working.
Something in the serverless path is slow and nobody can say why.
AI agents that run unattended
Agents on a schedule, with guardrails, that you can trust with a real database.
I run autonomous agents against real markets with real money, on the same stack. The interesting work is never the model. It is the catalog that stands between a language model and a service-role credential, and the evaluation that can actually fail.
A fit when
You want an agent doing real work, not a chat box.
You have an LLM near production data and it worries you.
Your agent works in a demo and not on a Tuesday.
How it goes
01You writeTell me the problem in your own words. No form fields, no discovery questionnaire.
02We talk onceThirty minutes. If I am not the right person, I will say so on that call and tell you what I would look for instead.
03Scope, in writingWhat gets built, in what order, and what it will cost. You approve it before anything starts.
04Ship in weeksWorking software you can look at, early and often, rather than a reveal at the end.
The details
Where
Salt Lake City, Utah. Remote, working US hours. Happy to be on site for Wasatch Front work.
Engagements
Fixed-scope projects, or ongoing contract work by the week. Both start with a written scope.
Cost
Quoted per project once I understand it, in writing, before anything starts. Ask and I will tell you fast.
Marketing sites a template would do better, anything that needs a team of five, and work I would not put my name on.
The proof is on this site rather than in a pitch: what I have built, the system I run on the same stack, and the log, which is mostly about things I got wrong and measured.
Availability last updated
Build something that runs withoutyou.
Type it here — it lands on my dashboard and pages my phone.
⌘↩
TypeScript✦JavaScript✦SQL✦Python✦Java✦C/C++✦Next.js✦React✦React Server Components✦Tailwind CSS✦shadcn/ui✦Radix✦Node.js✦PostgreSQL✦Row-level security✦Supabase✦Zod✦REST✦Webhooks✦Event-driven architecture✦AWS Lambda✦CloudFront✦EventBridge✦AWS CDK✦SST✦GitHub Actions✦Anthropic Claude SDK✦Agentic tool use✦LLM extraction pipelines✦TypeScript✦JavaScript✦SQL✦Python✦Java✦C/C++✦Next.js✦React✦React Server Components✦Tailwind CSS✦shadcn/ui✦Radix✦Node.js✦PostgreSQL✦Row-level security✦Supabase✦Zod✦REST✦Webhooks✦Event-driven architecture✦AWS Lambda✦CloudFront✦EventBridge✦AWS CDK✦SST✦GitHub Actions✦Anthropic Claude SDK✦Agentic tool use✦LLM extraction pipelines✦
