Building scalable software that grows with your business

Hi there! I'm Petar, a Senior Product Engineer and technical partner. I'm here to help you build or evolve your SaaS product end-to-end — one that solves the right problem, feels effortless to use, and can grow from user #1 to user #1,000,000.

I've spent the last 7+ years building products across startups and large enterprise environments, including platforms for Fortune Global 500 companies, spanning fintech, ed-tech, social networking, and e-commerce.

That experience has taught me that the best software comes from understanding the problem before writing the solution. Before thinking about implementation, I want to understand the problem we're actually trying to solve. Who is using the product? Why do they need this feature? Is there a simpler way to achieve the same outcome? And will the decisions we make today still make sense as the product grows?

That's the mindset I bring to every project.

I especially enjoy the challenges that come with growing SaaS products. What starts as a simple application naturally becomes more complex as customers, features, and requirements accumulate. Patterns that worked at the beginning stop scaling. Development slows down. Small changes start affecting unexpected parts of the product.

I enjoy stepping into that complexity, understanding what's causing it, and finding ways to make the product easier to build, maintain, and evolve.

That mindset shaped some of the work I'm most proud of. Most recently, at Paayed, a UK-based B2B fintech SaaS platform, I saw that an inconsistent UI and duplicated frontend patterns were becoming increasingly difficult to maintain as the platform grew. I built a shared component library and design system that was adopted across the product, giving the team a stronger foundation for developing new features and evolving the platform.

I'm also someone who cares about the small details. Whether it's an interaction that doesn't quite feel right, an unnecessarily complicated piece of code, or an architectural decision that could create problems later, I find it difficult to simply say, "good enough." I want to finish something and genuinely be proud of what I've built.

AI has made building software faster than ever, and I use it extensively in my own development process. But I think that makes engineering judgment even more important. The interesting question is increasingly not "Can we build this?" but "Should we build this — and what's the simplest way to solve the actual problem?"

Outside of client and product work, I'm building What Is The Output, my own experiment in making developer education more personalized. Building something of my own has given me another perspective on software — thinking not only about architecture and code, but also about users, validation, priorities, and whether an idea actually creates enough value to deserve being built.

And when I'm away from the keyboard, you'll usually find me playing music, reading, or spending time with my family.

So if you're building a SaaS product and looking for an engineer who will understand the bigger picture, care about the details, contribute ideas, and take ownership beyond the code itself — we'll probably have a lot to talk about.