Agent

Dealflow analysis

Dealflow analysis turns the decks arriving in your inbound mailbox into a consistent screening note. It reads each deck, sets it against the thesis your partnership has written down, and pulls out the handful of facts that decide whether a name is worth a conversation. The associate on rota still makes that call, but the reading is already done.

How it runs

Step by step

01

Collect the inbound decks

Decks arriving in the shared mailbox or dropped into the inbound folder are picked up and logged as they land.

02

Extract the deciding facts

The agent pulls the model, the traction claims, the raise and the team from the deck, and notes what has been left out.

03

Test against the written thesis

Each name is set against the sector, stage and cheque range the partnership has agreed, and against the exclusions.

04

Check the names already seen

It looks for the company, the founders and close comparables in your existing files so a second look is never mistaken for a first.

05

Write the screening note

A short note sets out the read, the gaps and the reason to pass or talk, with each fact cited to a slide or a file.

06

Associate confirms before the record updates

Nothing changes in the pipeline tracker until the associate on rota has read the note and agreed the outcome.

The harness

Exactly what this agent can see, touch and change

The same five controls sit behind every Askollo agent. These are this one's settings — visible before you build it, not buried in an admin screen afterwards.

Context

What reaches the model

Funds taking more inbound than the team can read properly, where the first read still has to be as good on Friday as it was on Monday.

Escalation

When it asks a person

The associate on rota confirms the screening note before the pipeline record is updated

Applications & Rights

Which tools it uses, and what it may do in each
GmailRead only
Google DriveRead only
DropboxRead only
NotionReadWrites newCreates new records or documents. Never edits, moves or deletes anything that was already there.

Verification

How you know it’s right

Every claim links to the document it came from. A statement the agent cannot cite does not make it into the output — which is what makes the result reviewable in minutes rather than re-read end to end.

Who it’s for

Funds taking more inbound than the team can read properly, where the first read still has to be as good on Friday as it was on Monday.

What you’ll need

  • Inbound mailbox connected
  • Written investment thesis
  • Pipeline tracker fields agreed
  • Associate rota for approvals

What you get

  • A cited screening note per deck
  • A suggested pass or call with reasons
  • A tagged view of thesis matches

What it doesn’t do

It reads what a deck claims and says where the claim is unverified. It does not diligence the numbers, contact the founder, or pass on a company by itself.

How you get it

We build the first one with you

Not a template you configure alone. We sit with your team, build it on real data, and hand over the controls.

01

Scope

One session with the people who actually do the work. We agree what the agent reads, what it may write, and who approves.

02

Co-build

Built on your own data, not a sandbox. You watch it being made, so you know why it behaves the way it does.

03

Handover

You own the controls. Change the context, tighten the rights, move the approval gate — without coming back to us.

What it replaces

Parts of the work currently spread across the categories below. It does not replace any of those products outright.

Manual deck triageInbox-as-pipeline trackingRepeated thesis-fit questions
Estimated savingNot setNo figure ships until someone at ollo owns it and the method behind it.

Frequently asked

Does it ever reply to founders?

No. Nothing it produces leaves the fund. The screening note sits in your tracker for the associate on rota, and any reply to a founder is written and sent by a person.

What happens to a good company that sits outside the thesis?

It is marked as outside thesis and kept, with the reason it caught attention recorded. Those names collect in one view so a partner can scan them the next time the thesis is revisited, rather than disappearing into an archived mailbox.

How does it handle a deck with almost nothing in it?

It says so. A thin deck produces a short note listing what is missing instead of a padded summary. That list is usually the quickest way for an associate to decide what to ask the founder for.

Can we change what it screens for?

Yes, and that is the point of the handover. The thesis, the exclusions and the cheque range sit in the agent's configuration where your team edits them directly. A change of focus does not need us.

Let's Build

AI is a capability you build. Let's build it together.

30 minutes with our team and you'll leave with a real plan — not a sales pitch.