I open the repository behind the pitch deck and tell you, in writing, whether there is a company underneath it. Six risk vectors, one score, five working days.
Large funds keep a technologist on the bench for exactly one reason. Somebody has to open the repository, not to be impressed by it, but to establish whether the thing described in the deck exists in the form described.
You are making the same decisions without that person in the room. Not because you cannot judge a business, a founder or a market. You judge those better than most funds do.
It is that AI is the first category where the entire claim can live in a layer nobody at the table can read, and where the gap between a real system and a convincing one is three weeks of work.
That layer is the only thing I look at. I have no view on your thesis and no opinion on the founder. I tell you what is built.
Every engagement runs the same six vectors in the same order. Select one to see what the evidence actually looks like.
A repository keeps an honest diary. Commit cadence, authorship spread and the ratio of new code to rewritten code tell me whether a company was built over two years or assembled over one quarter to be shown to you.
The demo serves twelve people beautifully. I model the point at which it stops, which component gives way first, and what it costs to fix. Most architectures do not fail gradually. They fail at a specific number.
One dependency with the wrong licence can place the intellectual property you are buying outside the company that is selling it to you. I walk the full dependency graph, including the parts the founders did not know they had.
AI margins invert quietly. A company can grow revenue and lose more money on every new customer, and the deck will not show it because the deck prices tokens at last year’s rate and this year’s volume. Move the inputs and watch where their model actually sits.
Where the training data came from, whether they had the right to use it, and what leaves the building. Two of the last nine companies I looked at were training on customer data their own contracts prohibited them from touching.
Fine tuned, or a system prompt in a trench coat. There is a test for this and it is not the demo. I compare what the deck claims is proprietary against what the repository can actually be shown to contain.
The Luminaq Index scores the six vectors from zero to one hundred and resolves to one of three verdicts. The same instrument runs on every deal, which is the only reason deals can be compared to each other.
A real audit, redacted to protect the investor and the company. Nothing here is a template. Read it before you decide whether I am worth a call.
Prepared for , at the request of , in connection with a proposed seed investment in .
Luminaq Index 31 / 100. Two critical findings materially change what is being sold. Detail at sections 4 and 6.
| Engagement | LQ-0231 |
| Instructed | 11 FEB 2026 |
| Delivered | 17 FEB 2026 |
| Repository access | READ ONLY, 4 DAYS |
| Author | S. R. SINGH |
Each vector is scored independently against the same rubric. No vector is weighted higher than another. A single critical finding caps the overall index at 40 regardless of performance elsewhere.
| Vector | Score | Flags |
|---|---|---|
| 1. Codebase integrity | 22 | 1 high |
| 2. Architecture scalability | 38 | 1 high |
| 3. Licence and IP | 9 | 1 crit |
| 4. Inference economics | 27 | 1 high |
| 5. Data lineage | 14 | 1 crit |
| 6. Model moat | 31 | 1 high |
Composite: 31 / 100. The company presents as a research led AI business. The evidence supports an interface business with a competent front end team and no defensible technical position.
Observation. The production lockfile resolves version 2.1.4 at dependency depth four, reached through the segmentation path in . The package is licensed GPL-3.0.
Why it matters. The module is linked into the inference binary the company distributes to on premise customers. On the plain reading of the licence, the copyleft obligation extends to the surrounding work. The company describes that surrounding work to investors as proprietary.
What the founders said. When asked, the CTO was not aware the package was present. It arrived transitively through a vision utility added in .
Remediation. Replace with an Apache-2.0 equivalent, or purchase a commercial licence from the author. Engineering estimate two to four weeks. The prior distribution history is a legal question and is outside my scope.
Effect on index. Vector 3 scored 9. Composite capped at 40.
The deck models blended inference at USD 1.80 per million tokens. Billing exports for the trailing three months show an actual blended rate of USD 4.10, driven by retry volume and an uncached system prompt resent on every call.
| Per seat, monthly | Deck | Observed |
|---|---|---|
| Tokens consumed | 0.4M | 1.4M |
| Inference cost | $0.72 | $5.74 |
| Price charged | $29.00 | $29.00 |
| Gross margin | 97% | 80% |
| Heavy decile margin | not modelled | -98% |
The blended figure is survivable. The distribution is not. The heaviest ten percent of users consume 61 percent of tokens and are the cohort the sales team is actively targeting.
Note. Caching the system prompt is a two day fix and recovers roughly 30 percent. I have flagged it to the founders regardless of the outcome of this engagement.
Put these to the founders directly. The wording matters. Each one is answerable in a sentence by a team that has done the work, and produces a long answer from a team that has not.
You are not testing their intelligence. You are testing whether the artefacts exist.
Answer for a deal you are actually looking at. Ninety seconds, no email, no download. It will not replace an audit and it will tell you whether you need one.
Founders can charm a generalist. They cannot hide a commit history from someone who has written one.
I am Satish Rohit Singh. I have spent fifteen years building the systems I am now asked to examine, which is the only qualification that matters here. I was the first hire on a product team and co built that product from an empty repository. I have stood up data science functions inside companies that had none. I have shipped generative AI into production, with the cost reports and the incident reviews to go with it.
That history is why this works. I know what a real training run costs, what a rushed architecture looks like six months in, and which corners get cut when a raise is three weeks out. I have cut some of them myself.
I do not take equity, carry, or a finder’s fee, in your fund or in anything I audit. I have no relationship to protect on either side of the table. The only thing I am selling you is an accurate answer, including the ones that cost me repeat work.
Anyone can tell you no. What you are buying is the ability to say yes quickly, for a stated reason, and sleep afterwards.
He found three things in four days that we had missed in six weeks. Two were fixable. One was not.
Diligence should cost a fraction of what it protects. The audit scales with the size of the decision behind it, so a small deal never subsidises a large one. You get the number before the work starts, never after.
A first pass before you commit to full diligence. Enough to know whether the deal deserves the next four days of anyone’s time, including yours.
The complete instrument. Six vectors, scored, every finding evidenced and every claim in the deck tested against what the repository actually contains.
For investors seeing deals continuously. You stop deciding whether a deal is worth diligence, because diligence is already retained.
Fifteen minutes, no obligation, and I will tell you on the call whether it is worth auditing at all. Sometimes the answer is that it is not, and that is free.