I help early-stage founders turn messy ideas into working software.
Not just building to spec—I mean the whole thing: asking hard questions to clarify what actually matters, making architectural decisions that keep things flexible as you learn, and shipping fast without creating a mess you'll regret in 6 months.
If you need technical leadership but can't afford (or don't want) a full-time CTO, we should talk.
Where I Can Help
"We have too many ideas and can't figure out what to build first"
Every conversation with your team generates 5 new features. Your roadmap keeps growing but you're not actually shipping. You need someone to help you prioritize, ask hard questions about what actually moves the business, and turn those ideas into buildable increments.
I'll help you clarify what's core to your product vs. what's noise. We'll use Event Storming and domain modeling to think through your business logic, then build the architecture to support it—modular enough to evolve as you learn from users.
"Our planning is weak and releases keep slipping"
You have a vision but it's not translating into dev tickets your team can actually build. Your PM is overwhelmed or non-existent. Features that should take weeks are taking months because nobody's thinking through the details upfront.
I'll fill that gap. I gather requirements, break down features, make architectural decisions, and translate your vision into clear specs your team can execute on. Projects that would slip 3 months ship in 1 month with strong technical leadership.
"We need to ship fast but can't sacrifice quality"
Speed matters, but so does not painting yourself into a corner. You're still learning what users actually need, so you'll pivot. You need architecture that's flexible without being a mess.
I use Domain-Driven Design to keep architecture modular and adaptable. I use modern AI-assisted development workflows to ship faster without cutting corners. And I write clean, well-documented code from the start—so when you're ready to hire your own team, they can extend what I've built instead of spending months untangling it.
"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 as you add features, and you want a second opinion before you're in too deep.
I'll review what you have and tell you honestly what's working and what needs to change. Then we'll figure out a path forward—whether that's refactoring key parts, starting fresh in specific areas, or continuing with minor adjustments.
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
Based in Wroclaw, Poland