Contact
Describe the system. I'll send back a read.
Write it the way you'd say it out loud. What the software is, what it's doing that it shouldn't, and what has to be true in three months. You get a written technical read on it: scope, risks and how I'd start, before anyone talks about money.
Availability
Taking on one new engagement from September.
Based in Türkiye (UTC+3), working internationally. Any European or UK hours work, and so do United States hours across every time zone.
01
You send the brief
Any length. Screenshots, a repo link or a Loom all help, none are required.
02
I reply within the same day
A written read on what I think is actually going on, what I'd do first, and whether I'm the right person at all. If I'm not, I'll say so and point you somewhere better.
03
A call, if it still makes sense
Forty-five minutes, technical, no deck. We come out of it with a scope and a start date or a clean no.
Direct
GitHub
Interactive portfolio
What to include
The six lines that make a good brief.
What the software is
Product, internal tool, platform. Who uses it and how often.
The stack, roughly
Framework, backend, where it's hosted. Version numbers if you know them, 'React 16' tells me more than a paragraph.
What isn't working
The symptom is enough. Slow releases, breakage, a team that can't move. I'll find the cause.
Who's on it now
Team size, seniority, whether anyone who built it is still there.
The deadline behind the deadline
A funding round, a client launch, a contract ending. It changes what I'd recommend.
What you've already tried
Saves us both the first two suggestions.
Questions
Asked often enough to answer here.
How fast do you reply?
Within the same day, always with something substantive. If I'm mid-engagement and can't take work on, I'll tell you that instead of going quiet.
Do you take short engagements?
Yes. A review or an architecture assessment can be a week. Build work is usually longer. The engagement models are set out on the Services page.
Do you work through agencies?
Yes, if I get direct access to the people making technical decisions. I don't work through a layer that relays requirements.
Can you join our team's tooling?
Your repo, your board, your CI, your standup. I work inside how you already run, not alongside it.
Remote, or on site?
Remote by default, from Türkiye. On site in Ankara whenever it helps, and kickoffs or workshops elsewhere where it's worth the travel.
Not ready to write it all out?
Send two sentences.
A short message is a fine start. I'll ask the rest.