Is Your Prototype Ready for Real Users?
One week. Fixed price. A written report telling you what you have, what is missing before strangers can use it, whether you actually own your own software, and what the build will cost. Written for founders who do not read code. If you go ahead with the build, the fee comes off the price.
Production Readiness Review
One week. A written report plus a call. Credited in full against the build if you engage us within 90 days.
What the Report Contains
The same six sections every time. The price is fixed, so the shape is fixed. Nothing to report in a section is itself a finding, and it gets written down.
What you have
A plain-language inventory of the system as it actually is, not as it was described to you. What it does today, what it is built from, which parts are yours and which are bought services, and where the AI-specific pieces sit. Written for someone who does not read code.
What is missing before real users touch it
Ranked by risk, worst first. For each one: what breaks, what a user would experience, and what fixing it involves in days. Not a list of everything imperfect. The things that fail when a stranger uses your product.
Whether you own your own software
A twelve point audit of the repository, cloud account, domain, API keys and third party services, plus the AI-specific assets that standard contracts miss entirely: your prompts and their history, your evaluation set, fine-tuned models and their training data, and your vector store. Most founders find at least one item is not in their name.
What technical due diligence would find
If you are raising, this is the section that matters. What an investor's technical advisor will ask for, what they would find in your code today, and which findings would actually slow a round rather than merely raise an eyebrow.
What the build costs and how long
A scoped plan rather than a number, so you can push back on scope instead of on price. Options where options genuinely exist, what each excludes, and an honest note on the single unknown most likely to move the estimate.
A proposed first milestone
If you go ahead: what gets delivered, by when, and how both sides will know it is done, with a number attached wherever quality is a threshold rather than a yes or no.
Why This Exists
You have something that works. Now it needs to become a product that strangers can use, that does not fall over, and that an investor's technical advisor can open without wincing. So you are about to hire someone, and you cannot evaluate the people you are choosing between. Everyone has a portfolio, a confident manner, and good ratings.
Committing tens of thousands of dollars to that decision on a first conversation is a bad way to spend money. A week and a fixed fee is a better one. At the end of it you know what you have, what it will take, and what you are exposed to. You can act on that with us, with your existing developer, or with somebody else entirely.
The ownership section is usually the surprise. Founders assume a contract saying they own the code settles the question. Then the repository turns out to sit in someone else's organisation, the servers run on someone else's cloud account, and the API keys are registered to an email address they do not control. That is cheap to fix in week one and expensive to fix later.
What We Need From You
Four things, all of them on day one. The week starts when the last of them arrives, not when you sign, because chasing access halfway through is what makes a one week promise slip.
- Read-only access to your code repositories
- A 45 minute walkthrough call, where you drive and we watch
- Access to the product running, or a recording of it running
- Your written answer to: what does this need to do, for whom, and by when
Questions
Start With a Call
Twenty minutes, no charge. We look at what you have, tell you whether the review is worth your money right now, and say so plainly if it is not.
Or Send Us the Details
Tell us what you have built and where you are stuck. We reply within 24 hours.





