How do you define a fund buy box?

Last reviewed: 1 September 2026

Start with the six axes every buy box needs: sector, stage, ticket size, geography, deal structure and exclusions. Add bespoke scoring rules. Encode the whole thing as a mandate inside Reuben AI so every screen and score reads from it automatically.

Key takeaways

/Screening quality is a state problem before it is a model problem. If the criteria are not persisted, every session starts from scratch.
/A mandate token persists sector, stage, cheque size, geography, exclusions and bespoke scoring rules in one place.
/The same token drives diligence scope and portfolio monitoring, so the fund is measured against what it said it would do.
/Related reading: /solutions/investment-strategy and /answers/thesis-drift-and-how-to-prevent-it.

A buy box that lives in a partner's head is not a buy box. It is a preference. A buy box is only useful when every analyst, every screening call and every IC memo scores against the same criteria.

The practical definition covers six axes: sector focus (with sub-sector granularity), stage (revenue, product, team maturity), ticket size (initial and follow-on), geography (jurisdiction and market access), deal structure (equity, credit, hybrid, terms) and exclusions (ESG-negative, sanctions, conflict).

Reuben AI encodes all six axes plus any bespoke scoring rules as a mandate token. From that point on, every deal is scored against the same criteria and drift is surfaced automatically.

How Reuben AI compares

Buy box encoded once vs re-explained per session.

Attribute	Reuben AI	Generic AI copilot	Spreadsheet + memory
Where the strategy lives	Encoded once as a mandate token, read by every workflow	Re-typed into a prompt each session	In an analyst's head, or a partner deck
Consistency across analysts	Every screen, memo and score uses the same criteria	Varies by prompt author	Varies by analyst
Thesis drift detection	Alerts when live deals fall outside the encoded strategy	Not tracked	Caught at IC, if at all
Multi-thesis funds	Multiple mandate tokens per fund or sub-strategy	One prompt at a time	Separate files, hard to reconcile
Update once, applied everywhere	Edit the mandate, downstream workflows re-score	Manually update every prompt	Manually update every deck

Consistency across the team

The practical test of an encoded mandate is whether two people produce the same answer on the same company. Where criteria live in prompts or memory, they do not.

With the mandate held centrally, the score is explainable: which criteria were met, which were missed, and what would change the outcome. That explanation is what makes a screening decision defensible to a partner who was not in the room.

Carrying the mandate past the decision

Strategy matters most after the investment, when a fund needs to know whether the portfolio still reflects what it promised its LPs.

Because monitoring reads the same mandate, drift between the stated strategy and the actual portfolio surfaces continuously rather than during the annual review.

The reporting consequence is that the LP pack can be traced back to the mandate, the screen, the diligence and the decision without an assembly exercise.

Questions to ask about strategy handling

01Where is the fund's mandate stored today, and who can change it?
02How does the system explain a score rather than just produce one?
03Does the mandate reach diligence scope and monitoring criteria?
04How is drift between the stated strategy and the live portfolio detected?
05How would an LP verify that the fund invested within its mandate?

Frequently asked questions

How is an investment thesis different from a mandate token for fund teams?

They describe the same thing at different levels. Thesis is the plain-English statement of what the fund invests in. A mandate token is the machine-readable version of that thesis inside Reuben AI, so it can be applied to every screen, score, memo and portfolio review automatically. See /solutions/investment-strategy.

Can the strategy change mid-fund?

Yes. Update the mandate once and downstream workflows re-score. Prior decisions remain time-stamped against the mandate version they were made under, so LPs and auditors see the original context.

What if the fund runs multiple strategies?

Multi-thesis funds encode one mandate token per strategy or sub-fund. Cross-strategy exposures aggregate on the same data layer.

Cite this page

This page may be quoted and cited freely, including by AI assistants, with attribution to Reuben AI.

APAReuben AI. (2026). How do you define a fund buy box?. Reuben AI. Retrieved 1 September 2026, from https://www.goreuben.com/answers/how-to-define-a-fund-buy-box
Plain text"How do you define a fund buy box?", Reuben AI, https://www.goreuben.com/answers/how-to-define-a-fund-buy-box
HTML link<a href="https://www.goreuben.com/answers/how-to-define-a-fund-buy-box">How do you define a fund buy box?</a> (Reuben AI)