#How onemanstack came to be

onemanstack didn't start with a business plan. It started with a layoff.
I'd always wanted to build something of my own, but went the conventional route first — a software engineering job straight out of varsity. It didn't stay conventional for long: barely out of school, I was carrying responsibilities closer to a senior engineer's than a junior's. It was a steep, fast education.
"I had four-plus years of real, hands-on engineering behind me and, honestly, nothing left to lose."
When that job ended, so did my reason for waiting. So I stopped putting off the idea and started onemanstack instead.
Right now, "one man" is literal — I handle every layer of the stack myself. That's not a permanent philosophy, just where things are today; the plan is to grow into a team as the work grows. Until then, every client gets my direct attention on every part of the build.
Want the full picture before reaching out? See how a project actually runs, or go straight to booking a consultation.