01 — Track record

Business stories, not a portfolio.

Every project below is told the same way: the context, my exact role, the numbers, and what it taught me. No screenshots of login pages. And at the end — the graveyard, because listing only survivors would be survivor bias.

2016 — today · bootstrapped · profitable

Backpack for Laravel

Creator, maintainer, business owner

The context. Working in an agency, I kept rebuilding the same admin panels, project after project. So I built a tool to make that stop. The first prototypes were Cornel and Viorel — named after Romanian uncles — and then Dick, named for how it looked in the terminal. Funny at the command line; harder to pitch to corporate clients. The fourth attempt got a sensible name and a business model.

What I did. Everything a software business needs: the code, the docs, the pricing, the licensing, the support, the community, the marketing. Open-core model — a genuinely great free core, paid add-ons for the pro conveniences. No funding, no ads, no growth hacks; ten years of word of mouth in the Laravel community.

Where it is now. On autopilot — a design decision, made after it blew up and I learned first-hand what thousands of users and zero systems feels like. Contributors and a small team handle the day-to-day; I steer. It takes a couple of my hours per week — the rest runs on process, documentation and a community that has skin in the game. Also: ten years is a long time to own anything. If you're the kind of company that acquires developer tools with a decade of profit behind them, my inbox is open.

What it taught me

Distribution first, monetization second: open-source works as a business when the free thing is genuinely excellent. And a product can be designed to run without its founder — that's not neglect, that's architecture.

2023 — today · startup · launching

POV Tickets

Co-founder & Head of Product

The context. Live events in Romania sell tickets through platforms nobody loves. My co-founder knows the events market cold; I knew we could build something better than what venues and promoters were tolerating.

What I did. The entire platform, zero to one: ticketing, payments, refunds, invoicing, compliance, venue and promoter tools. Built lean, on boring technology, to survive real traffic on real event nights. My co-founder owns go-to-market; I own the product.

What it taught me

We spent two years building before the public could buy a single ticket. If I did it again, I'd flip that — the next thing I take 0→1 will have paying customers by month three. That's exactly the scar tissue you're paying for.

2011 — today · agency · board member

UPDIVISION

Employee #3 · junior dev → managing partner → board member

The context. Two friends — Andrei Iordache and Eugen Tudorache — had a tiny web shop in Bucharest. It became my first real job; I joined when the whole company fit around one desk.

What I did. Grew from junior dev to senior dev to managing partner, and helped move it from "digital agency" to a proper software product house: the processes, the hiring, the Laravel practice, and the Creative Tim partnership that shipped 30+ products. Today I'm a board member — I bring in clients, advise, and otherwise stay out of the team's way.

What it taught me

Agencies teach you scope, deadlines, and respect for other people's money. Two hundred shipped projects means two hundred first-hand lessons in how software actually gets finished.

2026 — today · in the lab · alpha

TicketList

Founder — currently in customer discovery

The idea. "Your playlist for real life." Every upcoming event in Romania — concerts, theatre, festivals, conferences — pulled from 16 sources, de-duplicated and polished into one live picture of the country's event market. Browse, follow venues, build your list, actually go.

Where it stands. Phase one asked: can you even aggregate a whole country's events? Answer: yes — 10,000+ raw events processed into the cleanest dataset of the Romanian market. Phase two is the real test, happening now: customer interviews to find what's actually missing for event-goers — how going out could make their lives better — and which of those needs people would pay to solve. I'm a heavy event-goer myself, but I refuse to assume everyone shares my problems. Monetization will likely come from organizers or ticketing vendors — we are not becoming another ticketing platform. Piloting in Romania; built to go global fast, if it earns it.

Full disclosure. I wrote code before the problem was clear as day — my own rule, bent again. The interviews are how I pay that debt. It might graduate; it might join the graveyard below. That's the process working, either way.

Products are experiments. Some fail. Here's the tuition I paid — so the projects above didn't have to.

There were more — I've honestly forgotten some of them. Which might be the truest lesson on this page: you take more shots than you remember, and you only need one to land.

The next story on this page could be yours.

I'm choosing one big thing to build next. If you have a real problem and real distribution, read what gets a yes.

What I'm looking for →