Sales Intelligence, for sales and business unit leaders at large services firms

An intelligence layer built from what your pursuit teams learned on every large deal

We interview the pursuit team after every large deal, send you an intelligence brief, and build a memory bank your team queries from Copilot, with the answers ready to import into your CRM and your RFP library.

See the six-week pilot   How it works

Why did we lose the banking bid?

From your memory bank, in Copilot: The bank had hired a new CISO shortly before the RFP, and the evaluators asked us two security questions during the process. The team expected the evaluators to choose on price, and the evaluators chose on security. Next time, give the security expert more time in the finalist meeting. Source: the debrief with the account lead and the solution lead. (Illustrative example.)

How it works

One person from each team spends 20 minutes with us, and we do everything else.

We interview one person from each team

Within two weeks of the decision, we talk to the account lead, the solution lead, the bid manager, the pricing lead and the marketing lead for 20 minutes each. Nobody has to write anything. People say in conversation what they never type into a CRM.

You get an intelligence brief

Once a month, we send you a document with your team's distilled insights: what surprised them, suggestions on what to do differently next time, how to make these ideas more actionable. We also file a five-line summary in your CRM for every deal.

Your team queries the memory bank

Every insight goes into a memory bank your team queries from Copilot. A bid writer can ask "what's the best way to engage the CIO" or "what has resonated with telecom clients?"

What we find

The reasons people write down after a loss are too vague to act on, but in an interview the same people explain what happened and what to do about it next time.

What gets written in the CRM

What the team told us

What we put in the brief

"Pricing was a factor."

→

The evaluators compared first-year prices, because nobody showed them the cost over the full contract.

→

Change the conversation to Total Cost of Ownership, and ask the CFO's office to compare bids on that basis.

"The relationship could have been stronger."

→

Nobody had met the executive who owned the budget.

→

Ask a partner that already works with the client to co-host a lunch with that executive.

"Resourcing was tight."

→

The delivery lead we named was committed to another client.

→

Name a backup delivery lead, and have both managers confirm their time in writing.

15%

of loss reasons recorded in CRM systems matched what buyers said in interviews.

Clozd

85%

of employees said they had felt unable to raise an important issue with their boss.

Milliken, Morrison and Hewlin, 2003

9

people contribute to each RFP response on average, and each of them hears different things from the client.

Loopio, 2026

The examples are composites of pursuits people described to us.

The memory bank

Turn your tools from generic interns to insightful colleagues, supercharged with your team's intelligence.

We put every insight and every expert answer we capture into the memory bank, each with its source and date. We deliver it as a document you store in SharePoint, where Copilot can read it, or we connect it through an MCP connector, and we deliver the expert answers in your RFP library's import format.

At pursuit kickoff

"What have we learned on banking bids in the last two years?" The pursuit lead gets a one-page brief: why the last four were won or lost, which competitor showed up, and what procurement benchmarked price against.

While writing the response

"Who has delivered a phased S/4 cutover around a client's peak season?" The bid writer gets the solution lead's answer from a previous deal, with the name and date, instead of chasing an expert for three days.

Before orals

"What did evaluators in this sector ask twice?" The team prepares answers to the questions the evaluators weighed most in the last bid.

When nobody has answered a question yet, we ask the right expert and add the answer, so your team has more answers every month.

Confidentiality

Your firm receives the findings, and nobody receives the recordings.

We write every finding in our own words, with no names and no quotes. Each person approves their own points before we use them.

The pilot

In six weeks, we debrief the last three deals one business unit responded to, and you decide whether to run it every month.

WeeksWhat happens
1We agree the setup with your business unit leader: who we interview and where the outputs land (Copilot, your CRM, your RFP library). You pick the last three deals the unit responded to.
2 to 4We interview five people per deal, 15 conversations in all.
5We deliver the intelligence brief, the CRM summaries and the memory bank for Copilot.
6We present the findings to your leadership, next to what the team recorded in the CRM for the same three deals.

What you get

Intelligence brief

You receive a written brief on the three deals: why the team won or lost each one, what they would do differently next time, and a five-line summary per deal ready for your CRM.

Memory bank for your AI tools

You receive one file with every finding, each with its source and date, for Copilot to read from SharePoint or through an MCP connector.

Insights presentation

We present the findings and the actions for the next pursuits to your leadership in a debrief session.

$25K

We run the first pilots at half price, $12,500, under one statement of work. After the pilot, we run the program every month for one business unit at $150K to $300K a year, sized to your deal volume.

Next step

Pick one business unit and its last three deals, and we will show you what the team knew and nobody recorded.