Technical leadership, with a platform behind it.
For seed and Series A teams looking to supplement their technical leadership. You get a fractional CTO for a bounded engagement, and polis doing the heavy lifting behind them. Think airCFO, for your technology.
Built for us, delivered for you.
Every service started as something we needed to build Metropolis. Take one, or all of them, and go as far as you want: advice, a build, or a system we run for you.
We turn a problem or an opportunity into a plan, build it inside your own codebase, and release it. If you want, we keep running and maintaining it. You get a project plan, working software, and someone to run it.
We map your systems, model the threats, and check whether you are ready to operate at the next stage. You get architecture maps, a threat model, a readiness review, and a ranked list of fixes.
We show you what you spend on Claude, Codex and other models, and which work it pays for. You get a usage dashboard and recommendations, once or on a recurring basis.
Software delivery and its governance carry the most operating history behind them: it is how Metropolis builds polis every day. The other services are newer, and we are building them out through our first engagements.
About six weeks, and a person accountable throughout.
AI does the work. A person makes the consequential calls, and reviews every document before you see it.
We learn the problem and your requirements, review what you have today, document the architecture and security picture, and agree on a plan.
The work gets built, tested and released inside your own repository, under your review.
We measure the results, update the documentation, and either hand everything over or keep running it for you.
Why not just use Lovable?
Tools like Lovable, Base44 and Perplexity are great for trying an idea quickly and cheaply, and we would tell you to start there. They are tools you drive yourself, built for starting new apps on their own stack. We work inside the system you already have, and a person is accountable for the result. Start on a tool. Come to us when you want to own and grow what you have built.
What's yours stays yours.
Every engagement runs in its own isolated polis deployment, on a dedicated server, never shared with another client. Access is scoped to the engagement and revoked at the end. Nothing leaves your environment without our approval, and what we carry forward to other work is method, how a kind of problem gets solved, never your code, data, or strategy. An NDA spells all of this out before we start.
What are you trying to build?
Tell us what you're working on and what's in the way. We'll get back to you with how we'd approach it.