The CTO
A senior partner in your decisions.
Architecture, hiring, what to build next, what not to build. Wojciech is in the room when those calls get made.
Most fractional CTOs hand you a roadmap and a hiring problem. This engagement embeds CTO-level judgment in your company, with the senior team that ships what gets decided. Monthly retainer plus scope, long-running by default. Closer to a co-founder than a vendor.
The default agency model assumes a known scope and a clean handoff.
Domain-expert founders rarely have either.
The CTO
Architecture, hiring, what to build next, what not to build. Wojciech is in the room when those calls get made.
The team
Three more senior developers behind the CTO, working to the same standards. Real capacity to ship two workstreams in parallel.
The pricing
You're paying fees for ongoing technical judgment, and the cap table stays yours. Scope shifts as you learn. The model is built for that.
The horizon
We stay long enough to ship, then long enough to maintain what we shipped. Most engagements run multiple years. And when you're ready to hire in-house, we help you make those hires and hand over a codebase they'll thank you for. That's the point of yet.
Political finance, regulated industry
A non-technical political-finance operator brought us a decade of regulated-industry expertise and a problem nobody had solved well. We took it on as our own. Wojciech is a co-founder. Our deepest engagement to date.
Architecture from scratch. Co-founder-grade equity stake. Long-running engagement, still active.
Satellite data platform
Two founders with deep space-domain expertise and, when we met, very little software between them. Mid-build and stuck on the architecture for a satellite data platform. We advised, then we built it. In production since 2026.
Started as advisory. Converted to a partnership engagement once the technical answer was clear. Founders kept ownership. We kept technical judgment.
How we work
It writes a good deal of our code. What it has never done is decide what to build, or notice that the thing being built was the wrong thing. The structural argument for why that holds is on the stack page.
We write the design before we write the code, AI or otherwise. The spec is what we review, argue about, and change. Implementation is downstream of judgment.
Every change is read by a senior engineer before it ships. AI implementation doesn't get a free pass. It raises the bar on review.
TanStack Start + Supabase generates types from your database to the frontend. AI hallucinations break the build before they reach production.
When the engagement ends, and it might not, you're left with code another senior team can read. Maintenance is a design constraint we hold from the first commit.
Tell us what you’re building and what you know about your field that nobody else does. We read every message and usually reply within a day.