You know the business. I'll make the software hold up.
Your domain knowledge and your drive are what a business is built on. Maybe you turned them into a first version with AI tools and now real customers depend on it. Maybe you run an app that has carried the business for years and is starting to creak. Either way, what it needs now is the engineering underneath: a sound data model, tests, safe deploys, speed under load, sensible costs, and documentation good enough that any developer after me can pick it straight up.
I am a senior engineer. I spent seven years on a multi-tenant B2B platform while it grew from about $4M to $13M in annual revenue, ran its terabyte-scale Postgres database, and cut its cloud bill by six figures a year. Each page below covers one kind of engagement, a business shaped like yours, and what I need from you. If one sounds like your situation, write to me.
How I can help
Each one starts small and fixed-price, ends with written documentation, and leaves you owning everything: the code, the accounts and the know-how.
You took an idea, an AI tool and a lot of late nights and turned them into something people use. That's the hard part, and it's done. What it needs now is the engineering underneath: a real data model, tests, safe deploys, speed under load, and documentation good enough that any developer after me can pick it straight up.
Vibe-coded app to production →The same bug keeps coming back. Every fix breaks something else. You've lost days on a problem the AI tool says it has solved five times. An experienced engineer usually finds the real cause in an hour or two, fixes it, adds tests so it stays fixed, and leaves your AI tools better instructions for next time.
When AI can't fix your app →You know your customers, your market and what the product has to do. What you need beside you is someone senior who owns the technical side: the architecture, security, vendors, hiring and reviewing developers, and a roadmap you can trust. Part time, ongoing, and written down so the knowledge stays with your company.
Technical partner for founders →Your ops leads, analysts and product people know the work better than anyone, and with AI tools they're now shipping internal tools and features themselves. Instead of cleaning up afterwards, I set up the guardrails at the start: a shared repo, review on every change, automated tests, a staging copy, sensible permissions, and a weekly review where your builders get better each time.
Engineer in the loop for AI-built software →Duplicate customers, statuses typed as free text, reports that disagree with each other, and no record of who changed what. I put the rules into the database, clean and reconcile the existing data without taking the app down, add an audit trail, and prove the backups actually restore.
Data integrity and data-model repair →Your app has settled down: the features are built, the customers are steady, and the work is mostly maintenance. But the hosting bill still looks like it did during the big growth push, or bigger. I measure where the money goes, cut the waste without risking stability, and write down every saving so you can see it month by month.
Cut what a mature app costs to run →Your developers already know your codebase, your customers and your edge cases better than anyone. What they often lack is a shared way of working with coding agents. I work inside the team for a few months, build those habits alongside them, and leave when they no longer need me.
AI coding enablement for engineering teams →A system that has run for five or ten years holds a lot of hard-won decisions. The trouble is that most of them live in the heads of people who have moved on. I recover the spec from the code itself, put tests around what it actually does, and leave documentation any developer can pick up.
Documentation and handoff for an app nobody fully understands →Slowness is usually a sign of success: more customers, more data, more traffic than the app was first built for. Your team knows the product. I bring the measuring tools and the database depth to find what's actually slow, fix it, and write down the numbers before and after.
Slow Rails app performance →Your team started the upgrade, then customer work came first, as it should. Now the branch is months stale and the version gap keeps growing. I take it from there in small, safe steps behind tests, and leave a written process your team can repeat for the next version.
Rails upgrades, finished →Your team knows the product, the customers and the codebase. What's short is senior capacity: someone to take whole pieces of work and finish them. I join your repo and your process, keep you posted in writing, and leave the work documented so your team owns it.
Senior Rails contractor for your team →Three steps, starting small
Write to me
Use the form below. Tell me what you have and what is going wrong. I reply within a business day with questions and an honest opinion on whether I am the right person.
A small first piece
Usually a fixed-price assessment: a written, honest read of your app and what to do first. You see how I work before deciding anything bigger.
Built to be handed over
Work happens in your repository and accounts, with written updates. It ends with documentation any developer can pick up from.
Questions I get asked
Who is this for?
Founders who built a first version themselves, often with AI tools, and now have customers depending on it. Companies running an existing Ruby on Rails and Postgres app that matters to the business. Engineering teams that are overloaded, lost a senior developer, or want to get better at working with coding assistants.
Do I need to be technical?
No. You need to know your business and your customers, which is the part I cannot supply. I explain every decision in plain language and write it down, so you understand what was built and why.
What does it cost?
Most work starts with a small fixed-price assessment or a single scoped piece, so you see the quality of the work before committing to anything bigger. After that, work is scoped and quoted in writing. No retainer you cannot leave.
Will I be stuck with you?
No, and that is deliberate. Every engagement ends with written documentation: a system overview, runbooks, decision notes, performance numbers and instructions for AI assistants, so any competent developer or freelancer can pick up where I stopped. You own the code, the accounts and the documents.
Where are you, and do you work remotely?
Seattle, and yes. I work remotely with clients across the US, in your repository, your accounts and your review process.
Tell me about your app
One or two sentences is plenty. What do you have, what is going wrong, and what would good look like?