CTO INBOX
Startup Technical Review · $1,000 · 2 weeks

The technical review you'd get from a CTO, before you can afford a CTO.

Seven areas, one written review, $1,000. Architecture, IP ownership, security, spend, hiring, delivery, and how all of it will read to an investor. Two weeks. For early-stage startups only — the rules are below and we hold to them.

Check eligibility and book — $1,000See the seven areas

You're technical enough to be dangerous, or not technical at all. Both are hard.

You have a product, or the beginnings of one. It was built by a technical cofounder, a first engineer, an agency, a freelancer you found somewhere, or you, learning as you went. It works, mostly.

What you don't know is whether any of it holds up. Whether the architecture survives your next twenty customers or falls over. Whether you actually own the code — a surprising number of founders don't, and find out during diligence. Whether the thing that would embarrass you in an investor's technical review is something you could fix in a week for nothing, or something structural.

Nobody around you can tell you. Your engineer built it and can't be objective about it. Your investors aren't technical, or won't say. Every agency you ask concludes you should rebuild it with them.

So it stays an open question, and open questions at this stage tend to get expensive exactly when you can least afford them.

We publish the rules and we check them.

A discount that everyone claims isn't a discount, it's just a lower price — and it would undercut every other number on this site. So this one is gated, and the gate is real.

All six must be true on the day you book:

1For-profit, with a place of business in the United States.
2Incorporated or formed within the last 5 years.
3Fewer than 50 full-time employees, counting affiliates.
4Under $5 million in trailing-twelve-month revenue.
5Independent — more than 50% owned and controlled by individuals or other qualifying small businesses. Not majority-owned by a corporate parent, holding company, private equity firm, or family office.
6Raised under $10 million in total funding, and not past a Series B. Bootstrapped counts.

Where these come from

There's no single legal definition of "startup," so we've built the gate out of the tests that established programs actually use, tightened to the stage we're serving:

  • For-profit, US-based, >50% individually owned and controlled, employee cap including affiliates — these are the SBIR/STTR small business concern eligibility rules. SBIR's cap is 500 employees; we use 50, because a 400-person company is not who this is for.
  • Independence and size testing — mirrors the EU's SME definition (under 250 staff, with independence from larger parents), again tightened.
  • Revenue and funding ceilings — set well under the Section 1202 qualified small business asset threshold, which sits at $75 million for stock acquired after 4 July 2025. That's the ceiling for "small" in the tax code; we're nowhere near it, on purpose.
  • The 5-year age limit — the most common line across European startup programmes and US accelerator eligibility.

How we verify

You self-certify on the intake form, along with three things we check before the session: your formation date, a current headcount, and a one-line ownership summary. No cap table forensics, no bureaucracy — but if the certification turns out to be wrong, we'll move you to the correct product at its listed price or refund you in full. Your choice, no argument.

One per company, once. This is a starting point, not a standing rate.

Seven areas. Each one gets a plain-English verdict and a priority.

01

Architecture and technical direction

Does what you've built survive the next twelve months of growth, or does it need to change before it does? What breaks first, at roughly what scale, and how much warning will you get.

02

Code and delivery health

Whether a new engineer could productively join next month. Test coverage, documentation, deployment process, and how long it currently takes to ship a change — the number that quietly determines how fast you can respond to customers.

03

IP ownership and contracts

Do you own your code, unambiguously, in writing? Contractor agreements, IP assignment, open-source licence obligations, and anything an acquirer or investor would flag. This is the most commonly broken thing we see at this stage, and the most expensive to fix late.

04

Security and data handling

The basics that block your first enterprise customer: credential handling, access control, data exposure, and what you'd need for a SOC 2 conversation later. Not an audit — an honest read of what's exposed and what's urgent.

05

Technology spend

What you're paying for infrastructure, tools, and people against what you should be. Early-stage companies routinely overspend on infrastructure by multiples and underspend on the things that actually slow them down.

06

Team and hiring

Whether the people you have match the work in front of you, what the next hire should be, and what to pay for it. If you're relying on one person who knows everything, what that risk actually looks like and how to reduce it.

07

Investor and diligence readiness

How your technology will read to a technical diligence reviewer in your next round — what they'll ask, what they'll find, and what to fix before they look. Written so you can use it as a prep document.

What you get

  1. 01A short intake form, plus read-only access to whatever you're willing to share — repository, infrastructure, contracts
  2. 02A matched CTO within one business day, from your sector, whose background you see before you pay
  3. 03A 90-minute working session with you and your technical lead, if you have one
  4. 04A 5–7 page written review within two weeks — each of the seven areas with a verdict, the reasoning, and a priority: fix now, fix before your next raise, or fine, leave it alone
  5. 05A prioritised action list, shortest path first, with a realistic sense of what each item costs
  6. 06One round of follow-up questions by email

The document is written for a non-technical reader and built to be forwarded — to a cofounder, an investor, or the engineer who has to act on it.

Why $1,000

Because at this stage the alternative isn't a cheaper review. It's no review, and a rebuild in eighteen months.

We're not pretending this is charity. Companies that use this well tend to come back when they're bigger, and that's the whole business case — we'd rather be the people who told you the truth early than the ones who sold you diligence prep after it was too late to change anything.

What it isn't is a discounted Proposal Review. Those are different jobs. If you have a $200,000 development contract on your desk right now, the $2,500 Proposal Review is the product you want — startup or not — because it goes line by line through that document in a way this one doesn't.

$1,000 is credited in full toward any extended engagement started within 60 days.

What this isn't

  • A code audit. We read enough to form a judgment, not enough to certify anything.
  • A security certification. We'll tell you what's exposed. We won't hand you a SOC 2.
  • A rebuild pitch. Nobody on this bench builds software. "This is fine, stop worrying about it, go sell something" is a real and frequent outcome.
  • A valuation or an investment opinion. We assess the technology, not the business or the raise.
  • A vendor referral. We don't take referral fees. If we name a tool it's because we'd use it.

Questions

We're pre-revenue and pre-funding. Do we qualify?

Yes. Bootstrapped and pre-revenue companies qualify — the ceilings are maximums, not minimums. This product is arguably most useful before you've raised, because everything is still cheap to change.

We're a startup but we're at Series C / we have 80 people. Any options?

You're past this one, but extended engagements covers you — and honestly, at that size the deeper products will serve you better anyway.

We're outside the US.

This product is US-only, because the eligibility rules it's built on are. Tell us what you're facing and we'll quote the work directly.

Is our sector covered?

The bench is deepest in banking, fintech, insurance, manufacturing, and consumer products. Early-stage reviews lean less on sector knowledge than a due diligence engagement does, so we take startups outside those five — we'll just tell you up front if your situation is one where the sector gap would matter.

Do we need to give you access to our code?

It makes the review substantially better, but no. We'll work from what you're comfortable sharing and we'll be explicit in the document about anything we couldn't verify.

What if we don't have a technical person to bring to the session?

That's common and it's fine. It changes the questions, not the product.

Will this tell us if our developer is any good?

It will tell you whether the work holds up, specifically and with reasoning. We assess the code and the process, not the person — but founders generally find that answers the question they were actually asking.

How many do you take?

A limited number each month, because the price doesn't support unlimited capacity. If the month is full you'll be told a date, not put on a vague list.

Seven areas, one written review, two weeks.

Check eligibility and book — $1,000