how i work

A one-person shop still needs a process.

Working with one person instead of a team doesn't mean less structure — it means fewer handoffs where things get lost. Every project moves through the same four stages, whether it's a two-week build or a multi-month one.

~/onemanstack/process.log
01Discovery

// We talk through what the application needs to do, who it's for, and what "done" looks like — before any code gets written.

02Build

// Development happens in visible stages, not one long silence. You see progress as it's made, not just at the end.

03Deploy

// The application goes live on proper cloud infrastructure, configured to actually stay up.

04Support

// Launch isn't the finish line. I stay reachable for fixes, changes, and the next phase of the build.

In practice: expect a short call or written brief up front, regular check-ins while it's being built (not just a reveal at the end), and a direct line to me — not a support ticket — once you're live.