What is the difference between Obsidian Deal Ops and a broker CRM?
The short answer: they do different things. A CRM tracks your pipeline and relationships. Obsidian structures the deal pack itself — the documents, the DD gaps, the submission quality. They sit at different points in the deal process, and a broker might reasonably use both.
The confusion comes from the fact that both tools touch the same deals. But they touch different parts of those deals. A CRM tells you where a deal is in your pipeline. Obsidian tells you whether the deal is actually ready for the next stage.
This is not a replacement question. It is a “what does each tool do well” question.
What does a broker CRM do well?
CRMs are built for pipeline management and relationship tracking. The good ones do this very well.
Pipeline visibility. A CRM shows you how many deals are at each stage — enquiry, submitted, in legals, completed. It gives the principal broker a dashboard view of the firm’s activity. For a brokerage running 20 to 40 live deals, this visibility is valuable. You can see which deals are stalling, which are moving, and where your revenue is likely to come from next month.
Contact and relationship management. CRMs store borrower details, lender contacts, solicitor information, and introducer relationships. They track communication history — who emailed whom, when the last call was, what was discussed. For a broker who relies on repeat business and referrals, this relationship data is an asset.
Activity tracking and reporting. CRMs log activities — calls made, emails sent, tasks completed. For a firm with multiple brokers, this gives the principal visibility into team activity. It answers the question: is everyone doing the work?
Workflow automation. Modern CRMs can trigger reminders, send templated emails, and move deals between stages based on rules. This reduces the admin burden and ensures nothing sits untouched for too long.
These are genuine strengths. A brokerage without any pipeline visibility is flying blind. CRMs solve that problem.
What does a CRM not do?
A CRM does not structure the deal pack. This is the gap that most brokers feel but struggle to articulate.
CRMs do not track document completeness at the deal level. A CRM might have a file upload field or a notes section where you can record what documents have been received. But it does not know what documents are required for a bridging deal versus a development finance deal. It does not generate a DD gap list. It does not tell you that the valuation is three months old and the lender will require a refreshed one.
CRMs do not check consistency between documents. If the deal summary says 65% LTV but the valuation implies 72%, the CRM does not flag it. Consistency checking is a packaging function, not a pipeline function.
CRMs do not structure the submission itself. When you are ready to submit to a lender, the CRM can tell you the deal is at the “ready to submit” stage. But it does not organise the documents into the structure the lender expects, ensure the deal summary matches the supporting evidence, or produce the pack in a format that a credit committee can work through efficiently.
CRMs do not capture lender-specific requirements at the deal level. A CRM might store general lender criteria. But it does not cross-reference those criteria against the specific deal to identify gaps before submission.
This is not a criticism of CRMs. They were never designed to do this. Pipeline management and deal packaging are different disciplines.
Where does Obsidian Deal Ops fit?
Obsidian sits between the pipeline and the lender. It is the layer that takes a deal from “I have the instruction” to “I have a lender-ready pack.”
Deal pack structure. Obsidian organises the deal by document category — property, borrower, legal, financial — and tracks what has been collected, what is outstanding, and what is not applicable. The structure adapts to the deal type. A bridging deal has a different document set from a development finance deal, and the system reflects that.
DD gap tracking. For every deal, Obsidian maintains a due diligence gap list that shows the current state of documentation. This is the tool that prevents incomplete submissions and reduces lender follow-up questions. When a gap is closed, the deal record updates. When a gap remains, it is visible to anyone working the deal.
Submission readiness. Obsidian tells you whether a deal is genuinely ready to submit — not based on which pipeline stage you dragged it to, but based on whether the required documents are complete, consistent, and matched to the target lender’s requirements.
Deal state visibility for the team. When a junior broker picks up a deal, they can see the current state of the pack without reading through email chains or asking the senior broker. The document tracker, the gap list, and the lender notes are all in one place. This is the operational layer that makes handovers seamless rather than chaotic.
Lender matching at the pack level. Obsidian helps match the deal to lenders based on what the pack actually contains — not just the headline parameters. A deal might fit a lender’s criteria on paper, but if the pack is missing documentation that lender requires pre-submission, that match is premature.
Can I use both a CRM and Obsidian?
Yes, and many brokerages will. They serve different purposes.
Use your CRM to manage the pipeline: track which deals are active, which borrowers need follow-up, which introducers are sending you work, and what your completion pipeline looks like for the quarter.
Use Obsidian to manage the pack: structure the documents, track DD gaps, ensure submission quality, and give your team visibility into deal state at the document level.
The CRM answers: “How is my business performing?” Obsidian answers: “Is this deal ready to submit?”
A brokerage that has strong pipeline visibility but submits incomplete packs will win instructions and lose deals. A brokerage that packages perfectly but has no pipeline visibility will close what they have but miss opportunities. The two tools address different problems.
Why is this not a replacement question?
Because the failure mode they prevent is different.
The failure mode without a CRM: you lose track of deals, miss follow-ups, and have no visibility into your pipeline. Deals fall through the cracks because nobody was watching.
The failure mode without deal packaging discipline: you submit incomplete packs, trigger multiple rounds of lender questions, and lose deals to slow processing. The deals do not fall through cracks — they get stuck in the lender’s queue because the pack was not ready.
Both failure modes cost you deals. They just cost you deals in different ways.
If you are choosing where to start, ask yourself which problem is costing you more deals right now. If you are missing follow-ups and losing track of opportunities, start with a CRM. If you are submitting and getting rounds of questions back, or if your team cannot pick up each other’s deals without starting from scratch, start with the packaging layer.
Most brokerages that have grown past two or three people need both. The question is not which one to choose. It is understanding what each one does so you use the right tool for the right problem.