Over 25 years of code, working for your product.
A developer of more than twenty-five years, with time served as Tech Lead and CTO. I help startups, mid-size companies and agencies decide what to build, how to build it and who with — and bring AI into their development and business processes, where it produces measurable results instead of announcements.
- Experience
- 25+ years building software
- Roles
- Developer · Tech Lead · CTO
- Engagement
- Fractional, per project or per sprint
- Contact
- Direct, no middlemen
Three ways to work together
Fractional CTO
A CTO for the fraction of time you actually need: technical roadmap, architecture and stack decisions, priorities, vendor and investor conversations.
One to three days a week · ongoingSoftware development
Applications, APIs and integrations — from first prototype to a system that holds under load. Also embedded work with an existing team.
By project or by sprint · solo or with your teamAI in the process
Putting AI where it pays: into processes that burn hours of repetitive work, and into the software development cycle.
Assessment, pilot, adoption · tailoredI wrote code long before I wrote strategy
I started more than twenty-five years ago as a developer and never stopped. Along the way I led teams as Tech Lead and owned a company’s technical decisions as CTO — and learned that the problem is almost never the technology.
I step in where credible technical leadership is missing, stay as long as needed, and leave behind a team that can carry on without me.
Full CV →AI isn’t a product you buy: it’s a process you redesign.
I use AI tools daily to write and review software, and I’ve seen what happens when they arrive in a company without guidance: enthusiasm, then distrust. The value shows up when you pick a few points in the process, measure before and after, and set clear rules about data and accountability.
Coding assistants used well: generation, tests, code review, documentation and migrations. More speed on the repetitive parts, without giving up control of architecture and quality.
Documents, customer requests, data scattered across systems: we find where intelligent automation removes hours of manual work, starting from a measurable pilot.
Which data leaves the company and which doesn’t, what stays a human decision, how a result gets verified. The rules are written before adoption.
Tell me what you need to build
A couple of lines is enough. I reply personally within one working day, and the first half-hour call is free.
I’ll reply within one working day. In the meantime, feel free to browse the blog.