There are two ways to start with us, and which one fits depends on whether you have a system already, or whether you have a workflow that should be one.
The Assessment — for when you already have something
The Assessment is free. It's also our best lead-generation activity, and I'll explain why later in this post.
What we actually do
We point a set of AI tools at your codebase, your infrastructure, and any documentation you have. The tools were built for this specific job — they read every file, map the architecture, identify dependencies, surface security gaps, evaluate test coverage, examine how releases get deployed, check what monitoring is in place, and assess operational maturity across eight categories. They don't get tired or bored, and they don't miss things humans miss when they're skimming.
The output of the tools is then reviewed and augmented by a senior software architect — somebody with 15 to 20 years of experience building software-as-a-service products and large-company platforms — who reads what the tools found, applies judgment, and writes the actual report.
The combination matters. The AI tools cover ground a human couldn't cover in a reasonable amount of time. The architect filters for what actually matters, surfaces patterns the tools can't see, and translates the findings into an operating plan in plain English. Tools without the architect produce a noisy report. Architect without the tools takes three weeks instead of two and misses things.
What you get
Regardless of whether you ever work with us again, you walk out of the assessment with a plain-English risk summary covering the eight assessment categories, a specific list of what would break first and why, a roadmap of what needs to happen to harden the system into something operable, and a fixed quote for hardening plus ongoing managed operations.
That roadmap is yours. You can take it to us. You can take it to your in-house team. You can take it to a lower-cost outfit and have them execute it. We're transparent about the fact that this is a real risk we're taking — we put real expert time and real AI tooling into the assessment, and you might walk away with the document and have somebody else execute it. That's a bet we make consciously.
We're comfortable with the bet. We think most operators who see what's in the report, and what we're proposing alongside it, will conclude that the value of our framework, our pricing, and our accountability is worth more than the savings of executing it elsewhere. Some won't. That's fine.
Why this is our best lead gen
Honestly? Because it's where buyers see what we actually do. Most service firms in our category sell on a sales call — slides, talking points, case studies, the whole performance. We sell on a deliverable. The Assessment is the first piece of real work we do for a client, and it's the moment they figure out whether we're the kind of partner they want or not. If we're not the right partner, the assessment makes that clear quickly, and nobody loses much. If we are, the assessment makes that even clearer, and the quote on the last page tends to be the easiest yes the buyer has signed in a while.
The Discovery — for when you don't have a system yet
If you have a workflow problem but no system to assess, the Assessment isn't the right entry point. The Discovery is.
It costs $3,000, credited in full against the build if you have us build the system.
Why we charge for it
We used to do these for free. We don't anymore.
Discovery work is real work — two or three working sessions, a written specification, design of how data will be structured, sketches of every screen, a map of every external system the application will need to talk to, and a fixed build quote at the end. It takes our team meaningful time and a senior architect's attention. When we did it for free, we were essentially funding the early-stage thinking of buyers who in many cases weren't going to commit, and the math on that didn't work.
So we charge. And to be straight with you: we know that some buyers will take the Discovery deliverable and go build it themselves, or hand it to a $25/hr team off Upwork to execute. That happens. We're at peace with it. What we produce is genuinely portable, agent-readable, and complete enough that someone else can pick it up and run with it. We think we'll do a better, faster job than most alternatives. We credit the $3,000 against the build if you have us build it. But you're under no obligation, and the deliverable is yours to take wherever you want.
What you actually get
A written specification good enough to take to any AI agent or competent developer and have them build the system. Specifically: the data model (what entities exist, how they relate, what constraints apply), the workflow flows (every screen, every state transition, every decision point), wireframes of every screen, a map of every external system you'll need to integrate with, and a fixed build quote from us with a scoped handoff into managed operations attached.
That's it. No mystery, no vapor, no "let's discover what's possible." We'll know what's possible by the end of the second session. The deliverable is a thing you can act on — by Friday, if you want to.
Which one fits
If you have a system running and want to know whether it can be operated responsibly: the Assessment, free. If you have a workflow that should be a system but isn't yet: the Discovery, $3,000, credited if you build with us. Either way, you walk out with a real answer. That's the deal.