Product leadership that speaks engineer.
I'm Dimi — 20 years in tech, 10 of them as Head of Product. I embed with your team as a fractional product leader: setting direction, unblocking delivery, and getting real software in front of real users.
Sound familiar?
You have engineers. You have a roadmap of sorts. What you don't have is someone senior owning the space between them.
It worked at ten people. At thirty it's the bottleneck, and the roadmap is whatever was discussed most recently.
Velocity looks fine. Six months of output, and the metric you actually care about hasn't moved.
A permanent Head of Product is a six-month search and a six-figure commitment. You need someone useful in week one.
Three ways I work with teams
I embed in your team as the senior product person. Roadmap ownership, discovery, prioritisation, stakeholder alignment, and coaching your existing PMs so you're stronger when I leave than when I arrived.
Best for: scale-ups with engineers but no product function, or a product team without a leader.
End-to-end delivery: discovery, requirements, prototype, and a working MVP in front of users. I bring the product thinking and can bring the build capacity with it. I've done this twice in the last year alone.
Best for: validating a new product line, or an idea that's been stuck in a deck for six months.
I use AI throughout the path from idea to implementation — prototyping concepts in hours instead of sprints, and compressing the loop between "what if" and something testable. I'll do it on your project, or show your team how.
Best for: teams who suspect AI should be speeding them up and can't work out where it actually fits.
Track record
A decade of product leadership across fintech, SaaS, and consumer platforms.
Brought in to lead a product team and drive a stalled project to a market-ready MVP, now entering commercialisation. Took on a second product line in parallel and brought that to MVP as well. Used AI-assisted prototyping to compress the path from concept to working implementation.
Two products from concept to MVP inside twelve months.
Accounting and invoicing SaaS. Joined as a backend developer, left as Head of Product having built and led multiple product and development teams.
- —Led integration of finAPI and Kontomatik, giving 80,000 customers access to 2,300 European banks
- —Mentored and managed 15 product owners and UX/UI designers
- —Internationalised the product into Switzerland, Austria, Greece, and Spain — market research through to local sales support
- —Grew ARPA by double-digit percentages through an add-on and revenue-share strategy
- —Co-owned the 1&1 / IONOS partnership
- —Delivered GDPR compliance under legislative deadline
Data-science performance diagnostics for endurance athletes.
- —Assembled and led a team of seven engineers, designers, and data scientists from scratch
- —Took a niche product to successful go-live with 5,000 active users
- —Secured €800,000 in regional government funding with a two-year scaleup plan presented to decision-makers
- —Shipped Garmin and Polar API integrations enriching athlete physiological data
- —Contributed as a backend developer alongside the team
All-in-one SEO software platform.
- —Led a full product redesign and re-architecture for scalability
- —Balanced technical feasibility against business goals across a complex refactor
- —Introduced user feedback tooling and analytics to make decisions on evidence rather than opinion
References from former CEOs, CTOs, and engineering leads available on request.
I build my own products, too
The fastest way to stay honest about how software actually gets built is to keep building it.
A platform for short-term rental hosts, hotels, and property managers to create customisable, QR-accessible guest guides — everything a guest needs about the property in a single scan, with no app to install.
I designed, built, and run it solo. It's deliberately small, and it's where I test the AI-assisted delivery methods I bring into client work before I recommend them to anyone.
How engagements work
Every team is different, but engagements usually take one of three shapes. We'll work out which fits on the call.
| Embedded | Focused sprint | Build engagement | |
|---|---|---|---|
| Shape | 1–3 days/week, ongoing | Fixed scope, 4–8 weeks | Fixed scope, 8–16 weeks |
| You get | A senior product leader in the team | Discovery, strategy, and a roadmap you can act on | A working MVP in front of users |
| Good when | You need continuity and coaching | You need clarity fast | You need something shipped |
| Commitment | Rolling monthly, 30 days' notice | One-off | Milestone-based |
All engagements are remote-first from Germany, with onsite time where it matters. Working in English or German.
The first two weeks are diagnosis, not a reorganisation.
Decisions, rationale, requirements — so the team isn't dependent on me being in the room.
The goal is that you need me less over time, not more.
I can read your codebase, review a schema, and argue about architecture. That's the point.
About
I've spent twenty years in software and the last ten leading product.
I started in IT and ERP engineering, moved into backend development, and worked my way up through lead developer to Head of Product at sevDesk — where I built and mentored a team of fifteen product managers and designers, took the product into four countries, and connected 80,000 customers to European banking infrastructure.
Since then I've built a product team from scratch at an endurance-sports startup, secured €800,000 in public funding for it, and led a platform re-architecture at an SEO software company. In June 2025 I went independent. My first client is a UK open banking provider, where I've taken two products from concept to MVP. Alongside client work I build and run Hostory, a digital guest guide platform — small on purpose, and the place I test new ways of working before I recommend them to anyone.
What I bring that most product people can't: I've been the engineer. I can read your code, challenge your architecture, and translate between the people building the thing and the people funding it — because I've been both.
I'm based in Baden-Württemberg, Germany, hold a B.Sc. in Computer Science from the University of Freiburg, and work in English and German.
Questions you're probably asking
How quickly can you start?+
Usually within two to three weeks. Get in touch and I'll tell you honestly what my availability looks like.
Do you work with our existing team, or replace people?+
Work with them. Most teams I join have capable people who lack direction or air cover, not people who need replacing.
What does it cost?+
Depends on shape and commitment. I'll give you a clear figure after our first call, once I understand what you actually need — no packages, no surprises.
Can you actually build, or just advise?+
Both. I came up as a developer and still work hands-on. For larger builds I bring in trusted engineering capacity.
Are you only working with fintech companies?+
No. I have deep experience in fintech and regulated domains, but I've led product in SEO software, accounting SaaS, and consumer sports. The common thread is B2B software with real technical complexity.
You have your own product — will you actually be focused on us?+
Yes. Hostory is a small side product I keep deliberately small, and it exists to keep me hands-on with the tools and methods I bring to client work. Client engagements come first, and I'll tell you upfront exactly how much capacity I have.
Where are you based, and do you travel?+
Germany, working remote-first across European time zones. Happy to be onsite for kickoffs, workshops, and the moments that need a room.
Let's work out if I'm the right fit.
Thirty minutes, no pitch. Tell me what you're building and where it's stuck, and I'll tell you straight whether I can help — and if I can't, who might.
Prefer email? dimitrios.stamou@leon-tech.com