Company records
the spineA couple of thousand of them, searchable, deduplicated, and owned by a rep, so two people working the same market see the same truth.
An M&A firm with its own CRM.
BishopKnight brings buyers and sellers of private companies together — relationship-heavy, document-heavy work. We built a standalone CRM on the firm's own hosting and shaped it round by round with the team using it daily.
A couple of thousand
Company records, each owned by a rep
Own infrastructure
The firm's own hosting, not a shared install
Within the week
Change requests shipped item by item
Client · BishopKnight — M&A firm, California
The starting point
Months-long conversations and paperwork on every one, spread across spreadsheets and inboxes.
The client
BishopKnight is an M&A firm — the people who bring buyers and sellers of private companies together. A couple of thousand companies to track, conversations that run for months, and paperwork attached to every one.
The problem
All of it lived in spreadsheets and email threads. Two reps working the same market had no shared view, records drifted between copies, and finding the last conversation with a company meant searching an inbox. The firm was also sharing an install with another business, which made every change a negotiation.
What we built
One system, built round by round
Shaped by the person using it all day, not by a specification written up front.
Pipeline stages
deal positionA deal's position is a fact in the system rather than something a rep has to remember.
Activity timeline
per companyCalls, notes and emails in one chronological view, so the last conversation is a click away instead of an inbox search.
Document handling
paperworkThe paperwork sits with the company it belongs to instead of in a folder somebody has to find.
Sector-benchmark valuations
deal toolingA defensible first number to open a conversation with a seller, calculated from sector benchmarks.
Mail that actually arrives
deliverabilityMoved onto authenticated SMTP from the firm's own domain after password-reset mail was silently disappearing, with a DMARC policy on the domain.
How it gets changed
Short numbered lists, shipped live, answered item by item.
Change requests come from the person using the CRM all day. They ship live and get answered one item at a time, usually within the week. That loop — rather than a big specification up front — is why the system fits the way this firm actually works.
The outcome
The companies, the pipeline, the paperwork and the mail, in one place.
What changed for the reps
One shared view of every company and deal, with the last conversation and the documents attached to the record instead of scattered across inboxes.
What changed for the firm
The system runs on their own infrastructure, on their own schedule, and the requests coming back are refinements rather than workarounds.
Similar problem?
Deal flow spread across spreadsheets?
Book a discovery call. We'll scope what it takes to get your pipeline into one system your team will actually use.
Book a discovery callNo slides, no obligation.