Where technical rigor meets creative vision.
Launch strategy, AI-use guidelines, and technical architecture advisory for founders and teams ready to move.
Begin the conversationBuilding it was never the hard part.
When Flushiest launched, I assumed the hard work was behind me — the app was built, it worked, people needed it. Then I tried to actually get it in front of people, and found out how much I didn't know. You can't just print flyers and hand them out on the street in Amsterdam — there are real legal constraints on how and where you can distribute physical marketing material, and I only found that out after I'd already ordered the print run.
That's the gap almost nobody talks about. Vibe-coding and AI tools mean anyone can build something real in a weekend now. Almost nobody's prepared for what comes after — how to launch it, distribute it, and do it in ways that are actually legal and actually work. That's what I do.
This works best if you've already got momentum.
I'm not the right call for a first idea on a napkin. I'm the right call once you've got something real — a product, a working team, a direction you believe in — and you need someone who can think and move as fast as you can, without a six-week onboarding process first.
If you're the kind of founder or team that makes decisions in days, not committees, we'll get along fine.
Your team just shipped something, and now what?
You've built it. It works. Nobody knows it exists yet, and you're not sure what's actually legal to do about that. I help you figure out how to get in front of the right people — fast, and without the mistakes I already made once.
Everyone's using AI tools, nobody agreed on how.
Half your team is vibe-coding features, the other half doesn't trust any of it, and there's no shared standard for what's safe to ship. I help you write the guidelines that let your team move fast without it becoming a liability later.
You need a technical decision-maker, not another meeting.
Architecture, stack, build-vs-buy — someone has to own that call, and it shouldn't be whoever's loudest in the room. I step in as the technical authority for as long as you need one, then step back out.
Your brand guidelines exist. Nobody's checking anyone follows them.
You don't need someone to design a new brand system. You need someone glancing over what's actually going out the door and catching it before it drifts. I do that check so you don't have to.
I built Flushiest, then found out I had no idea how to get it in front of anyone. Everything on this page is what that taught me — Paolo
Vision ESG CTO
Brought in as CTO to design the platform from scratch. The call that mattered most wasn't the tech stack — it was deciding what not to build in version one, so the thing could actually ship.
Rising Collective CTO
Same role, same kind of call: design the system, then build it myself rather than hand it off and hope. Some decisions you only get right if you're also the one holding the code.
Flushiest Founder, built & launched
Built, launched, and got it picked up by four news outlets and radio, on a marketing budget that was basically zero. The lesson that shaped everything on this page came from this project.
There's no menu here, because advisory work doesn't scope the way a website build does. A first conversation is just that — we talk through what's actually going on, and I tell you honestly whether I'm the right person for it. If it makes sense, we figure out together whether this is a short, focused engagement or something more ongoing. No proposal deck, no forced tier.