William Loopesko — Fractional CTO, AI-Native Engineering
Your team already knows how your business runs.AI just can’t see it yet.
I help small companies get their knowledge out of inboxes, spreadsheets and people’s heads and into one shared place their team and AI tools can safely work from. Then I teach your people to build the tools they need on top of it, with me as your part-time CTO.
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 owner-led companies, founders, and nonprofits of about 5 to 30 people, with nobody senior owning software, data, or automation.
- Role
- Co-founder & CTO, Aclymate
- Practice
- Shared knowledge first · then your team builds
- Engagements
- Fractional, 1–2 days per week
The problem
AI can’t help with what it can’t see
In most small companies, the way things actually work lives in a dozen places: email threads, shared drives, spreadsheets, the billing system, and the heads of the two or three people who’ve been there longest.
So every AI tool starts from zero. Someone pastes in context, gets a decent answer, and does it all again tomorrow. Nothing builds on anything else.
The fix isn’t a smarter AI tool. It’s giving your team one shared, organized picture of the business that every person and every tool can work from.
How it works
Foundation first, then your team builds
01
Build your shared knowledge base
We find where your company’s knowledge lives today and gather it into one organized place, with a record of every change. We link in the tools you already use, like your billing and customer lists, so it stays up to date. Your people can see everything. Each AI tool sees only what it needs.
02
Teach your team to build on it
I work alongside the people who will own the tools, so they learn a safe way to build, where someone checks each change before it goes live. Because the context is already there, each new tool is faster and safer to build.
03
Stay on as your part-time CTO
Optional. One or two days a week: technical decisions, reviews, and help as your team takes on bigger projects.
You leave the first phase with a working knowledge base and a roadmap for what to build on it next. Not every team needs to start there. If what you need right now is a website or one tool, we start with that.
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
Tell me how your team works today and where your knowledge lives. I’ll tell you honestly whether a shared knowledge base is the right first step, or whether something simpler, like a well-built website and a couple of automations, would do. No pitch.
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.