Agent

Company research

Company research gives an investment team a first read on a business before anyone books time with the founders. The agent works across the sources your firm has agreed to use, sets what it finds against the comps and precedents already sitting in your files, and returns a one-pager where every line points back to where it came from. An analyst reviews and files it, so nobody starts from a blank page.

How it runs

Step by step

01

Set the research brief

You tell the agent the company, the sector lens and the questions your partnership always asks. That brief becomes its standing instruction and your team edits it later.

02

Work the approved sources

It searches only the public and licensed sources agreed during the co-build. Anything outside that list is left alone.

03

Match against your own files

Findings are compared with the comps, prior deals and precedents held in Drive, Dropbox, SharePoint or Notion, under your existing permissions.

04

Flag what it cannot verify

Thin, contradictory or unsourced claims are marked as open questions rather than smoothed into the prose.

05

Draft the house one-pager

The agent structures the findings into your own one-pager format, with a citation on each statement and the open questions at the top.

06

Analyst approves before filing

The draft lands for review. An analyst edits and approves it before anything is written to the deal folder.

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

Associates and analysts covering a wide top of funnel, and partners who want the same first read on every name that reaches the Monday meeting.

Escalation

When it asks a person

An analyst approves the one-pager before it is filed to the deal folder

Applications & Rights

Which tools it uses, and what it may do in each
DropboxRead only
SharePointRead only
NotionRead only
Google DriveReadWrites 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

Associates and analysts covering a wide top of funnel, and partners who want the same first read on every name that reaches the Monday meeting.

What you’ll need

  • Deal folders connected
  • Approved source list agreed
  • House one-pager format supplied
  • Named analyst to approve

What you get

  • A cited company one-pager
  • A list of open questions
  • Links to matching internal precedents

What it doesn’t do

It reports what the sources say and where they disagree. It does not price a round, score a company against your thesis, or take a view on whether to proceed.

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 desk researchAd-hoc comps huntingHand-assembled one-pagers
Estimated savingNot setNo figure ships until someone at ollo owns it and the method behind it.

Frequently asked

Where does the research actually come from?

Only from the sources you approve in the co-build: the public and licensed feeds your firm already pays for, plus your own deal files. If a source is not on that list, the agent does not use it. Every line in the one-pager carries a link back to what it was drawn from.

What happens when two sources disagree?

It shows both readings and marks the point unresolved instead of picking a winner. Disagreements are collected in the open-questions block at the top of the one-pager, which is usually the part the analyst reads first.

Does our internal comp data leave our systems?

No. Internal comps stay in your Drive, Dropbox or SharePoint and the agent reads them under the same permissions your team already has. The finished one-pager is written back into your own deal folder.

Who changes the brief when our focus moves?

You do. The sector lens, the standing questions and the source list live in the agent's controls, which we hand over at the end of the co-build. Changing the brief for a new fund or a new sector is a job for your team, not a support ticket.

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.