How we use AI
We use AI to look at every deal in more depth, so our partners can spend more time with founders.
In short
Every deal that reaches us is analysed in full as soon as it arrives. The AI reads the deck and the website, looks into the founders and the market, scores the company against our written criteria, and writes the memo a partner reads.
A partner decides whether a deal proceeds to a discovery call, and the investment committee decides whether we invest. The AI can recommend a pass, but it can’t decline a founder on its own.
How a deal moves
Every deal takes the same path, however it came in. Hover over a step for a summary, or click it for the detail.
Agents
Each agent has one job, and they run in this order, set in code. On re-analysis, fixed rules pick which steps run again. Letting a model choose the order would cost more and make runs less consistent. Open an agent for what it does, the tools it uses and its edge cases.
Doc Intelligence
Reads the deck and the website: problem, product, traction, funding, sector and the competitors the deck names.
Pre-screening gate
Checks the deal against our mandate, from stage and round size to location and business type, and recommends pass or proceed.
Market Trends
Sizes the market independently, with growth and trends, and checks the deck’s number against it.
Synthesis A
Drafts the memo, rates every criterion, pulls the closest past deals, and recommends proceed, pass or more info.
What we score
We score every company against the same criteria. Synthesis A rates every criterion strong, adequate or weak. Code then turns the ratings into a score from 1.0 to 3.0, takes a set amount off for each warning sign the evidence didn’t clear up, and maps the result to proceed, pass or more info.
How they found the problem, whether they know how their buyers actually buy, and what they know about the industry that only comes from working in it.
What edge this founder has on this exact problem, and whether it’s hard to copy or something anyone could have.
How fast they ship, from idea to product to first customer, and how closely customer feedback drives the product.
Whether the technical work is done in-house, what the team has built before, who they’ve convinced to join, and whether they run the company on AI too.
Whether they’ve pushed through hard things before, including moments when quitting would have made sense.
Whether they know what they don’t know, name their biggest risks unprompted, and can point to decisions they changed on advice.
Evidence the pain is real: customers who can describe it, trials that convert to paid, inbound demand and low churn.
A bottom-up count of real customers at realistic contract sizes. For AI companies, the labour spend they can replace, not only existing software spend.
Where buyers sit on the adoption curve, and whether sales conversations sound like “not ready” or “we’ve been looking for this”.
Where the founder thinks the market is heading, why now, and whether that view comes from experience or from reports.
The change it’s taking advantage of, like a new technology, regulation or behaviour, what it believes about the market that most people get wrong, and whether it changes how the category works or competes inside it.
What the product knows after 1,000 customers that a new entrant couldn’t copy, and how deeply it’s built into work the customer can’t afford to get wrong.
Why customers say it’s better, and whether that’s more than price, and whether the innovation is in the data and workflow or only in the model call.
Whether the company can reach customers in a way that doesn’t depend on its AI.
Reliance on any one model provider, how hard it is for customers to leave, and how many tools could copy the core idea within a year.
The barriers it can build as it grows: regulation, distribution lock-in, platform effects, trust, and unit costs that fall with volume.
Revenue, paying customers, gross profit, pipeline, customer concentration, and how much it cost to get there.
Retention, usage, and whether customers sound enthusiastic or just polite.
The measurable results customers report, how fast they arrive, and whether the return on investment holds up when the customer’s finance team checks it.
Whether existing customers spend more over time, and whether pricing grows with their usage.
A specific ideal customer, the first 10 to 20 named targets, acquisition cost against lifetime value, and which channels repeat.
How the company charges, what each new customer costs to serve (AI inference included), and how predictable the revenue is.
Proprietary data that gets better with use and can’t be replicated.
How much the company relies on one foundation model, and whether it survives a model change.
Whether it builds where foundation models won’t go, or competes with what they’re getting better at.
How deeply the product sits in the customer’s work, and what removing it would take.
Whether it stands alone or rides on another platform, and how a first product grows into a platform within 18 months.
The three to five things that must be true for this company to return the fund, and whether the entry price makes sense for its stage and traction.
What our stake looks like after the Series A, the Series B and at exit.
Comparable acquisitions and listings in the space and region, with best, base and downside cases.
Stack
n8n moves data in and out, LangGraph runs the analysis, LangSmith records every run, and OpenRouter connects to the models.
Running the analysis
What takes a deal in, runs the analysis and writes the results out.n8n
Deals reach us through our pitch form, the founder chatbot, the deck inbox, our deal channel in Slack and the Sourcing Signals agent. Each one sends a webhook to n8n, which turns it into one standard record for the analysis. When the analysis finishes, n8n writes the results to Attio and Supabase and posts them to Slack. It holds the logins for those systems, and retries anything that fails. We use n8n because that plumbing, logging in to other systems, retrying and slowing down when a service asks, comes ready-made, and watching a run move step by step through its canvas taught us more about what we’d built than any log. None of the analysis happens there.
LangGraph
Runs the analysis itself, as code. It sets what runs when: Founder Intel and Market Trends run at the same time, and Competitive Intel waits for the market work. It saves progress as it goes, so a run can stop for a partner at the gate and carry on from the same point, and a re-analysis re-runs only the agents the new information affects. n8n can call a model several times in a row, but it can’t keep track of where an analysis is up to or take a different path depending on a result, which is why the analysis lives here.
OpenRouter
One connection to every model provider. Each agent’s model is a setting, so moving an agent to a different model, or a different provider, needs no code change, and every call’s cost is logged against the run. Today every agent runs on Anthropic’s models.
Research
The tools the agents use to look things up beyond the deck. Perplexity and Exa are in an A/B test for market research.Firecrawl
Turns a company’s deck and website, and competitors’ websites, into plain text the agents can read.
Perplexity A/B test
Answers market questions from the live web, with a source for every figure.
Exa A/B test
Finds companies and articles from a plain description, like “export compliance software for seafood”.
Renidly
Pulls each founder’s roles, employers and dates, and their post history, from their public LinkedIn profile.
FullEnrich
Finds founders’ contact details. It checks a series of data providers in turn and stops at the first good answer.
Alexandria Testing
Firecrawl’s library of data sources for AI agents, including professional profiles, research papers and code. We’re testing it as a research source for the agents.
Tracing
Every run is traced, and every change is tested before it ships.LangSmith
Traces every run as one tree under the deal it belongs to: each agent in order, the prompt it used, the tools it called, what came back, how long it took and what it cost. When an output is wrong, we can find the step and the prompt behind it in a couple of clicks. Every agent’s prompt lives here too, versioned, with a production and a testing version, and is loaded when a run starts. Before a change goes live, it runs across our test set of thousands of past deals and is scored side by side with the live version. It doesn’t ship if it does worse on any group of deals, even when the average improves.
Storage
Where the criteria, every analysis and every file are stored.Supabase
Our database. It holds the scoring criteria and screening rules, and every analysis, file and source the AI produces.
pgvector
How we find similar past deals. Each finished analysis is stored as a list of numbers describing the company, and the closest matches become its comparables.
Where the team works
The tools the team works in every day.Attio
Our CRM. Each company’s record, with the AI’s analysis, its score and the decision we made.
Notion
Where partners keep the criteria, screening rules, thesis and mandate. Each deal also gets its own workspace for our notes, assumptions, diligence questions and the investment memo, and those notes feed back into re-analysis.
Slack
Where each finished analysis is posted, and where a partner agrees or disagrees when the gate recommends a pass. Posting a deck in our deal channel starts a run.
Resend
Sends our email: sign-in links for our tools, login codes and notifications to the team.
Models in use
New models come out every few weeks. We run each one against our test sets, past deals where we already know the right answer, and score it on the same checks: whether its claims are supported, how sound its reasoning is, what it pulls out of a deck, and how it applies our mandate. We switch when a model does measurably better.| Model | What it does | Why this model |
|---|---|---|
| Synthesis A drafts the memo and Synthesis B checks it against every source. | The hardest reasoning in a run: long, multi-source analysis, where it has stayed the most consistent on our deals. | |
| Reads the deck, runs the gate and the research agents, writes the memo into Attio, and runs the founder chatbot. | Mostly reading, searching and summarising at volume, where speed and cost matter more than deep reasoning. | |
| Answers the market research questions from the live web. | Every answer comes with its sources, so each market figure can be checked. | |
| Turns each finished analysis into numbers, so similar past deals can be found. | It runs on every deal, and a small embedding model is enough for matching. |
Who does what
The AI’s work all happens before a person forms a view, and it takes about five minutes. The decisions all happen after.
The AI does this
- Reads the deck, the website, the data room and anything that arrives later.
- Screens the deal against our mandate, and can recommend a decline but can’t send one.
- Researches the founders, the market and the competitors.
- Scores the company against our criteria and drafts the memo.
A person does this
- Whether to proceed. A partner reads the memo and decides whether the deal goes to a discovery call.
- Every investment decision. The investment committee makes all of them.
- Every no. When the gate recommends a decline, a partner agrees or overrides it in Slack before it counts.
- The written reason on a no. A partner writes it. If it reads like a model wrote it, tell us. That’s a fair complaint and we’ll fix it.
- Every reference call. A partner is on the phone. Software may transcribe or summarise the notes afterwards.
- The conclusion in the memo. The AI writes the first draft. What the memo concludes is a partner’s call.
What the team sees
The analysis lands in Slack and Attio, where a partner makes every decision. Shown here with Coldline, our made-up test company.
In Slack
Every recommendation posts to #deal-review, our deal channel, where a partner acts on it.
The AI recommends Proceed
The recommendation, what the company does and a summary, linked to the record.
The gate recommends a pass
We removed the round slide, so the only raise in the deck was a future $25M Series A. The gate read that as this round. The partner disagrees, the run carries on, and the error is logged to the test set so the gate doesn’t repeat it.
In Attio
Attio is our CRM. The run fills in Coldline’s record, adds it to the founder pipeline and saves the memo as a note beside the founder’s enquiry.
Click a highlight to read it in full, or a note to open it.
After the first meeting
New material, like a call transcript or a data room file, re-runs only the agents it affects. The memo says where each new number came from, such as “Tess, on the call”.
Click the note to open the updated memo.
What it learns from
The AI keeps no memory of its own. What makes it better over time sits in our databases, and survives every rebuild of the code.
Scoring criteria
Built from years of accelerator cohorts and portfolio companies we followed from application form to outcome.
Past deals
Every finished analysis is saved, and new deals are matched against the most similar ones. Our accelerator cohorts and earlier write-ups went in before the first live deal, so there were past deals to compare with from day one.
Outcomes
Each deal is logged as a win, a loss or a pass. As bets resolve, we recalibrate the scoring against what happened, and when a partner overrides the AI we record who turned out to be right.
The criteria had years of history from the start. Outcome tracking is newer, and improves as more deals resolve.
Roadmap
Everything above runs on every deal today. None of these runs on deals yet.
Founder chatbot In progress
Founders can apply by talking it through instead of filling in a form. The conversation goes into the same analysis as every other deal.
Sourcing Signals v2 In progress
Finds founders before they apply or announce anything, from new company and domain registrations, GitHub activity, patents and research grants, people leaving scale-ups, and accelerator cohorts. Firecrawl Alexandria’s profile and code data is one of the planned sources.
Deal tracking In progress
Keeps watching deals we passed on or put on watch, and flags one for another look when something happens that could change our view.
Technical due diligence Scoping
Checks on the technology, for deals that get past a first meeting.
Financial due diligence Scoping
Checks on the financials, for deals that get past a first meeting.
Changelog
| Date | Type | Change |
|---|---|---|
| 5 Oct 2026 | Improved | Pre-screening calibration. Revised the pre-screening prompt against deals the team flagged, so fewer clear mismatches come back as More Info. |
| 5 Oct 2026 | Bug fixes | Geography pass reason. Deals that met our location rule were sometimes given International as their pass reason anyway. That reason now only goes on deals that actually fail the location rule. |
| 5 Oct 2026 | Improved | Report language. Simplified the language in re-analysis notes and investment recommendation reports, and now check them with our Humanizer agent. |