BusyIncorporated
BUSY.Schedule an intro

Roster / AMES.0801

Ames has already worked
the deals nobody opened.

Ames is a deal sourcing associate with a real computer, real logins and one continuous memory. Every CIM that lands is read and screened against the thesis the day it arrives, the CRM stays current without anyone typing into it, and the memo, the deck and the first-pass model are drafted in the firm's own format. Outreach is drafted, then waits for a yes.

Own email + machineWorks in the firm's CRMEvery figure sourcedApproval-gated outreach
BUSY, INC.AMES.0801
Ames
AmesDeal Sourcing Associateames@busy.inc
ACTIVE

The work

What is on the desk
before the team opens the deal.

Five artifacts, each on its own cadence, in the firm's own format.

  1. 01The screened one-pagerDay the CIM landsEvery teaser and CIM read the day it arrives, scored against the thesis and summarized to a page with the company researched from the open web. Deals stop going unopened because the week was full.
  2. 02The IC memo, draftedFirst draftIn the firm's format and voice, built from the documents and the model, every figure traced to where it came from. Review becomes checking rather than hunting for the source of a number.
  3. 03The diligence deckPer dealLaid out the way the firm lays them out, with tables and charts generated from the actual data. A last-minute change lands in hours instead of costing an evening.
  4. 04The first-pass modelPer dealSources and uses, debt schedule, returns — real Excel on Ames's own machine, tied out and stress-tested, with the least certain assumptions flagged at the top.
  5. 05The CRM, currentDailyCalls, emails and meetings written in as they happen, contacts added, duplicates merged, stages and next steps kept honest. What has gone quiet gets chased before it goes cold.

The job

Five jobs.
Ames runs all of them.

The associate work between a deal arriving and a decision — logged, screened, drafted and modeled, at the volume the pipeline actually arrives in.

  1. 01CRM input & administrationDailyCalls, emails and meetings written into the CRM without anyone typing them in. New firms, brokers and contacts added as they appear, duplicates merged, and stages, owners and next steps kept current — Ames chases what has gone quiet.
  2. 02Deal intelligenceEvery new dealNew CIMs read the day they land, scored against the thesis and summarized to a page. The company researched from the open web — market, competitors, owners, history — with every claim sourced.
  3. 03Investor memo draftingFirst draftIC memos in the firm's format and voice, built from the documents and the model. Every figure traced back to its source, so the partner reading it can verify a number in one step. Rewritten on notes, as many rounds as it takes.
  4. 04Diligence slide deck creationPer dealDiligence and IC decks laid out the way the firm lays them out, with tables and charts generated from the actual data. Overnight and last-minute changes turned around in hours.
  5. 05Deal modelingFirst passSources and uses, debt schedule, returns — leverage, coverage, ROIC and IRR, built in Excel on Ames's own machine. Tied out and stress-tested, with the least certain assumptions flagged at the top.

MCPs / DealSift MCP

Ames is the operator. DealSift MCP is the corpus behind the sourcing.

It gathers public broker listings, resolves the same business posted under three brokers into one canonical deal, searches by meaning, and checks the corpus against the firm's standing thesis. Ames brings back the match, the source listing behind it and a drafted approach — so the partner's time goes to the call rather than the search.

Explore DealSift MCP →
DealSift MCP / working viewSource-backed
01SignalNew listing matching the thesis
02EvidenceCanonical deal + source listings
03ArtifactOne-page screen against the buy box
04DecisionOutreach drafted, waiting for a yes
Ames brings the deal back to the teamNothing goes out without approval

Control

Outreach goes out
after the firm says yes.

Two questions decide whether an associate role can be handed over: whether the work stands up to a partner's review, and what reaches an owner or a broker when it does not. Sourced figures answer the first. The approval gate answers the second.

Every outbound draft arrives with

  • The deal or contact it concerns
  • What Ames found, and where it came from
  • The draft itself, ready to send or edit
  • What happens next if it goes out

Approve it and it goes out from Ames's own address, with replies routed back. Ignore it and nothing is sent. Nobody outside the firm hears from Ames without a person reading the words first.

What Ames may do without asking

  • Read CIMs, teasers and the data roomAlways
  • Log calls, emails and meetings in the CRMAlways
  • Draft memos, models and decksAlways
  • Email an owner, broker or sellerAsk every time
  • Start an outbound sequenceAsk every time
  • Commit the firm to anythingNever

Access

A real computer,
with real access.

Ames works in the firm's tools and comes back with deliverables. Systems with a direct connection are read and written without a person in the middle. Anything without one, Ames opens in Chrome and works by hand — signing in, clicking through, handling SMS-based 2FA — which is how the deal room and the broker portal stay worked rather than skipped.

  • Word, Excel, PowerPoint and PDF — real files on a real desktop
  • Signs in and works web tools by hand in Chrome
  • Gets through captchas, 2FA and one-time passwords
  • An isolated machine, so the firm's data stays on it

Where Ames works

  • The firm's CRMPipeline logged, updated and pulled from
  • ExcelModels built, edited and sent as real .xlsx files
  • Word + PowerPointMemos and decks in the firm's template
  • QuickBooksFinancials pulled, read only
  • ChromeEverything without a direct connection, worked by hand

Most tools a firm already uses connect directly. Access levels are set at the user level.

Memory

Ames gets better
every week.

One continuous memory across email, texts and meetings. Ames remembers what the team says and learns how the firm works — through verbal feedback, never by anyone writing code.

  • Wk 2Learns how the firm structures a CRM update
  • Wk 4Knows which deals are worth the partners' time
  • Wk 6Pre-drafts IC memos before the team opens the deal
  • Wk 8Presents first-draft LBO models for review
  • Wk 12Project-manages diligence end to end

The same curve every Busy teammate runs: the work compounds because the memory does.

Getting started

White-glove setup,
then weekly coaching.

First week

White-glove setup

Email, machine, logins and access — set up the same way a new hire would be.

First month

Company context

The thesis, the people and the history collected, then the first use cases run closely supervised.

First quarter

Weekly training

Thirty minutes a week of guided feedback that sharpens the work.

First year

A digital teammate

Fully integrated. Ames carries the busywork so the team spends its hours on deals and relationships.

No RFP, no migration, no new tool for anyone to learn. Ames works inside what the firm already uses.

Fit

Worth a conversation
if this sounds like your pipeline.

A good fit

  • More deals arrive each month than the team has hours to screen properly
  • The thesis is written down clearly enough to score a company against it
  • A partner will read a memo draft and mark it up

Probably too early

  • Deal flow is thin enough that every teaser already gets a careful read
  • The firm has associates with the bandwidth to work the whole pipeline
  • You want outreach leaving the building without a person reading it

Put Ames on the pipeline.

One email starts it. Setup is white-glove, the first use cases run supervised, and nothing external happens without approval.

Email Ames

ames@busy.inc