William Loopesko — Fractional CTO, AI-Native Engineering
I teach your team to use AI to build the system it needs.Not hand them something finished and walk away.
Most companies buying outside help end up with a consultant they can never fire. I do the opposite. First, I help you figure out how things actually work today and what’s worth automating: an internal tool, a website, a governed AI agent, sometimes nothing more than a better process. Then I build what it needs to get started, and where training is part of the engagement, I work alongside whoever will own it from day one, so the capability is theirs, not something they’re handed and left to figure out alone.
I’m a co-founder and the CTO of Aclymate, a climate accounting software company. Everything below is something I built and operated there or alongside it. Not a framework I read about.
This tends to fit best for small teams, founders, and nonprofits: real work worth automating, and nobody in-house yet to own it.
- Role
- Co-founder & CTO, Aclymate
- Practice
- Building and teaching · AI-native delivery
- Engagements
- Fractional, 1–2 days per week
Selected work
Three things I have actually done
This same method took Aclymate from dabbling in AI to fully AI-native in a couple of months. Here’s what that actually looked like, plus proof it isn’t specific to my own company.
The internal tools that replaced our SaaS stack
Aclymate · 5-person climate accounting SaaS
A non-engineer running his own production tooling independently, and a repeatable way to teach anyone else to do the same.
From zero coding background to org technology lead
Nonprofit · one staffer, no prior engineering experience
A shipped production site, and an apprentice who teaches the workflow forward without me.
A custom agent platform, built with real guardrails
Aclymate · production, live on company operations
AI agents that monitor company operations and flag issues for a human to approve. Reliable enough to run continuously. Not yet trusted to act fully on their own.
Where to start
A free conversation, first
Every engagement opens with a short, unpaid call. No pitch, and no assumption that a platform is the right answer. Often it isn’t: a well-built website and a couple of well-scoped automations covers it, and I’ll tell you that directly rather than upsell past it.
Either way, we start with a first phase built together with whoever will own it, priced to fit the shape of the work, plus a roadmap for what comes next, so you have something concrete regardless of scope.