I partner with early-stage founders who need to move fast without creating technical debt. If you need a product from zero to market, and can't afford to rebuild in 6 months - we should talk.
Problems I Solve
"We need an MVP but don't have a technical co-founder"
You've validated the market. You have the vision. You need someone who can translate that into a working product with solid architecture. Not a dev shop that churns out code - someone who thinks like a technical co-founder.
What you get: Strategic technical thinking, rapid domain discovery, architecture designed for your specific business model, and a product built to evolve as you learn from users.
"We're not sure what's technically possible"
You have ideas but don't know what's realistic in 8 weeks vs. 8 months. You need someone to help prioritize what actually moves the needle vs. what's just nice to have.
What you get: Honest technical advice on what to build first, what to defer, and what's going to bite you later. I've seen the patterns - what works and what becomes expensive regret.
"We need to ship fast but can't sacrifice quality"
Speed matters, but so does not painting yourself into a corner. You need modular architecture that lets you pivot, scale, and hand off to a team you hire later.
What you get: Clean, well-documented code with good practices from day one. When you're ready to hire junior devs, they can extend what I've built - not spend 6 months understanding spaghetti.
"We started building but worried we're going the wrong direction"
You have some code but it feels fragile. You're not sure if the architecture will hold up. You need a second opinion before you're in too deep.
What you get: Technical audit of what you have, clear assessment of what's working and what needs to change, and a roadmap for getting back on track without starting over.
How I Work
Discovery First
I start by understanding your domain, users, and business model. What's the core value? What can wait? What's going to be painful to change later? This phase shapes everything.
Iterative Building
I ship working features regularly so you can test with real users and we can adjust as we learn. The goal is momentum + quality, not perfection.
Clean Handoff
When we're done, you get documentation, architecture decisions explained, and recommendations for what to do next - whether that's hiring a team or continuing with me.
Strategic Thinking Throughout
You don't just get code. You get someone thinking about your business constraints, technical trade-offs, and what actually matters for your stage.
You're Probably a Good Fit If:
- You need something built from scratch (or close to it)
- Timeline matters (you need it in weeks/months, not someday)
- You value architecture that doesn't become technical debt
- You're willing to be collaborative (I ask questions, you have answers)
You're Probably NOT a Good Fit If:
- You need ongoing maintenance of existing systems
- You want the absolute cheapest option
- You're enterprise-scale with complex procurement
- You need a full team (I'm one person who moves fast, not a dev shop)
Let's Talk
If this resonates, email me at szwajkajakub@gmail.com with:
- What you're building (2-3 sentences)
- Where you are now (idea stage? some code? prototype?)
- What timeline you're thinking
Kuba Szwajka
0-to-1 Software Architect
Based in Wroclaw, Poland