Founder, Fuelo · CTO, Extratzis / Greece
I'm building Fuelo, the fuel-price app for Greece, and leading engineering as CTO at Extratzis, a marketplace for short-term work. Python and full-stack by trade, Claude Code as my daily driver. I own the whole stack, from the Postgres schema to the thing you tap on your phone.
I'm Giorgos Moustakas. I'm the founder of Fuelo, a fuel-price app for Greece, and the CTO and Lead Engineer at Extratzis, a Greek platform for short-term and on-demand work. I write Python and TypeScript for a living and use Claude Code daily. Before this I led a team at Datawise that built Python environments for training and evaluating AI models, and before that came e-commerce backends, satellite internet troubleshooting, and a lot of late-night customer calls about DNS.
Now: I'm building Fuelo, a fuel-price app for Greece, and leading engineering as CTO at Extratzis, a marketplace for short-term work.
Previously: I led a team at Datawise (Atlanta, working from Greece) that built Python tasks used to evaluate and benchmark AI models, until the role ended in July 2026. Containers, eval harnesses, and a lot of "why did the model do that" debugging.
Before that: e-commerce backends at Brdy., satellite internet support at Bigblu, and an internal Flask tool at Nova that cut hardware-replacement time in half.
I use Claude Code as a daily driver across the full build cycle: planning, implementation, review. Not as a shortcut but as a force multiplier for getting the hard parts done faster. It is also one of the models I evaluated at Datawise, so I know where it is strong and where it needs a second pair of eyes.
Stack I reach for daily:
Fuelo started as an itch and became a product: official Greek fuel-price data, turned into alerts, route costs and a fuel log people actually open. I take ideas from zero to shipped.
CTO and Lead Engineer at Extratzis. Architecture, hiring bar, delivery cadence, and the unglamorous decisions that keep a two-sided marketplace shippable.
Next.js, Python, PostgreSQL and the glue between them. Services that survive bad networks, ugly inputs and Monday-morning load spikes. Tested, logged, observable.
Claude Code across the full build cycle, plus LLM pipelines, eval harnesses and agentic automation. I evaluated and benchmarked models at Datawise, so I know where they help and where they don't.
I write the migration myself. Indexes where queries hit. No surprise N+1s six months later.
Not just JWTs and HTTPS. RBAC, secrets handling, threat modeling - the stuff that bites when you don't.
Profile first, then fix. Most slow code is slow for one reason you can find in an hour.
Stripe to Postgres to the email job that fires at 9am. The integrations that make a product feel like one thing.
Tcpdump if I have to. The bug usually lives in the boundary you didn't think to check.
Built for the next 10x, not the next 1000x. Premature scale costs more than late refactoring.
Claude Code is part of my daily build cycle. I evaluated and benchmarked AI models at Datawise, so I know what these tools actually do. That combination means I use them where they help and skip them where they don't.
You send what you have - a doc, a deck, a Slack thread, even just a rough idea. We get on a 30-min call.
Within a week you get a written scope: what gets built, what doesn't, a timeline, and a fixed price. You decide.
Weekly Loom updates, the staging URL from day one, real code in your repo from week one. No black boxes.
Production deploy + 30 days of free fixes if anything breaks. You own everything, end of story.
Two things. I'm the founder of Fuelo, a fuel-price app for Greece (fuelo.gr), and I'm CTO and Lead Engineer at Extratzis (extratzis.gr), a platform that connects people with short-term and on-demand jobs.
Selectively. My time goes to Fuelo and Extratzis first, so I take on advisory work and the occasional well-scoped build. Tell me what you have and I'll give you a straight yes or no, usually with a fixed quote.
It depends on my current load. If it's a fit I'll tell you the earliest start date in my first reply. If something is on fire, say so in your message.
Always. I'm based in northern Greece, EET (UTC+2). I overlap with most of EU and the Americas East Coast for live calls. Async-first for everything else.
Standard. I sign mutual NDAs before we discuss anything proprietary. Your code stays yours, your data stays yours, no portfolio entry without your written OK.
Yes - I do a lot of work as the extra hands inside small teams. I write in your style, follow your conventions, leave the codebase better than I found it.
Got a question that isn't here? Just ask.
Services I rely on and recommend. Sign up through these links to get started, and I may earn a small credit at no extra cost to you.
Partnerships, advisory, or a selective build: tell me what you're working on. I'll reply within a day with whether I can help, and what it would take.
