FRACTIONAL CTO & AI CODING
AI coding the pragmatic way — software craftsmanship, not chaos
I help startups and software houses ship faster with AI-assisted development, without paying it back as tech debt. Fractional CTO leadership and in-house team workshops.
Jarosław Michalik — Fractional CTO, Google Developer Expert, founder @ Impl
Book a 15-min call
Worked with
Problems we solve for dev teams
Teams adopt AI coding tools. Few adopt the process. The result: chaos, tech debt, or both. We fix that.
Fractional CTO
CTO-level leadership without a full-time hire. Clear priorities, architecture decisions, and 30/60/90 execution plans that improve delivery.
See service detailsAI Coding Workshops
In-house, 1 day. Your team gets one shared AI coding standard, practical Randori training, and a 30-day rollout plan.
See workshop detailsTech Due Diligence
For investors and founders. What's under the hood: architecture, tech debt, scalability. Honest assessment.
Book a callMVP Architecture
Build fast without building a mess. Modular design, critical path tests, documented decisions from day one.
Book a callAI Process Audit
Your team uses Cursor. But does everyone follow the same rules? We align standards and cut the chaos.
Book a callTeam Standards
One language for the whole team. How you use AI, how you review code, how you ship. No more "everyone figures it out solo."
See workshop detailsWhen AI helps vs when it creates debt
AI speeds up coding. It also speeds up mistakes. The difference is process.
Software craftsmanship, not prompt spaghetti
- •Patterns that work and patterns that break code reviews
- •Shared standards so everyone speaks the same language
- •Context-first, not prompt-first — what high-performing teams do differently
- •When to let AI run, when to keep humans in the loop
What founders and CTOs say
“[Quote 1]”— [Role], [Company/context]
“[Quote 2]”— [Role], [Company/context]
“[Quote 3]”— [Role], [Company/context]
About me
Jarosław Michalik
I'm Jarek — Fractional CTO and founder of Impl. I build products and teams, not slide decks.
10+ years in software. Kotlin, Android, Flutter, Firebase. I've shipped MVPs, scaled teams, and done tech due diligence for investors.
I help dev teams adopt AI-assisted development without the mess. Architecture, standards, code review — the stuff that keeps AI from turning into tech debt. Software craftsmanship, not prompt spaghetti.
Google Developer Expert. Speaker at Droidcon, DevFest, SFI IT Academic Festival. Based in Kraków, working with startups and software houses across Europe, UAE and US.
LinkedInLatest from the blog
Insights and best practices for AI-assisted development
"We don't have tech debt." Come on, I know you're lying.
Technical debt is not just old libraries. It is also fading system understanding, undocumented decisions, and AI-accelerated entropy that teams do not see until delivery slows down.
Does AI Understand Your Codebase?
For sure not in the same way carbon-based lifeforms understand it. Here's how to use the agent to build the map before you change the territory.
New kind of technical debt we're not talking about
Coding agents introduce a new kind of technical debt no one is really considering. The real danger isn't messy code — it's intent debt, context debt, dependency debt, and confidence debt.
Your dev "productivity" metrics are broken (and here's the proof)
Everyone wants to show progress. We track numbers, build dashboards, and celebrate achievements. But what if the very metrics you're relying on are misleading you?
Do you really need a CTO?
So, do you need a CTO? Yes. But... you must hire for the stage you're in, not the stage you dream of.
Scale your team without scaling the chaos
More devs + more AI tools = more potential for mess. Unless you set standards first.
Align first, then scale
- •Shared approach to AI-assisted development
- •Code review that actually catches AI-generated debt
- •Documentation of decisions (ADR) so context doesn't live in one person's head
- •One workshop, one day — your team speaks one language
How we help (anonymized)
Real projects. No names. Lessons you can use.
MVP before funding round
Startup needed architecture review before investor due diligence. We identified tech debt, documented risks, and gave a clear path to fix.
Book a callAI chaos in a 12-person dev team
Everyone used Cursor. Nobody agreed on standards. One in-house workshop later: shared rules, Randori practice, less "who broke this?"
See workshop detailsHow we work
Different needs, different engagement. One goal: your team ships better.
Fractional CTO
Ongoing leadership for founders and engineering teams. I work on architecture, delivery priorities, and quality standards with your team, not on the sidelines.
Book a callAI Coding Workshop
One day, in-house, on your context. We align team rules for AI coding, run hands-on exercises, and leave you with a playbook you can use next sprint.
See workshop detailsAudit & Consulting
One-off. Tech due diligence, architecture review, or "what's wrong with our AI process?" Honest assessment, clear recommendations.
Book a callWorth a 15-min chat?
See if this fits your team. No pitch, no slides. We'll figure out if Fractional CTO, a workshop, or something else makes sense.
Book a 15-min call