For most boutique commercial real estate investment shops of 4 to 20 people, Dealpath and a custom deal-pipeline automation are answering two different questions, and the honest first move is usually neither. Dealpath is a purpose-built deal-management platform designed for collaborative teams of five or more, with white-glove onboarding and a custom quote; it is built for the institutional acquisitions desk, not the four-person shop running deals out of Excel, Outlook, and a shared drive. A custom automation is not “rebuild Dealpath” — it is AI doing analyst work across the stack you already run. This is a decision framework, not a product ranking. It defines the three real routes a boutique shop can take, names where each one breaks, and gives you a short test that maps your firm’s actual situation to one of them before you sign a contract or fund a build.
What Dealpath actually is, and who it is built for
Dealpath is the command center for a real estate deal team: a shared, real-time view of every active acquisition, disposition, development, or debt deal, with pipeline tracking, task and workflow automation for due diligence and investment-committee processes, document management, reporting, AI-assisted data ingestion, and a private listing exchange in Dealpath Connect. The firm reports supporting more than $10 trillion in transactions, with institutions like Blackstone, MetLife, Nuveen, AEW, and Bridge Investment Group on its client roster. It is a serious platform, and for the desk it was built for, it is very good.
The detail that decides most boutique-shop questions is in the fine print: Dealpath plans typically require a minimum of five users, and the product is described as built for collaborative deal teams of five or more. Implementation is white-glove and commonly runs six to eight weeks, with a dedicated customer success manager. That is an institutional posture — a shape that fits a growing acquisitions team with a defined process and several analysts, and fits a four-person shop poorly.
None of this is a knock on the product. It is a statement about fit. The question a boutique shop should ask is not “is Dealpath good” — it plainly is — but “is a five-seat institutional pipeline platform the right tool for a firm my size, or am I buying a coat three sizes too big.”
Three routes, honestly named
The choice is usually framed as two options: buy Dealpath or build your own. It is really three, and naming the middle one changes most boutique-shop decisions.
Route one — a thin AI-assisted workflow on the stack you already run. You keep your pipeline in a spreadsheet or a light CRM, and you use ChatGPT, Claude, or Gemini with saved prompts to do the analyst-grade reading: summarizing an offering memorandum, pulling rent-roll and T-12 figures into your model, drafting the deal-screening memo, triaging the broker emails in your inbox. No platform subscription, no build, no onboarding. Cost is a per-seat model subscription. This is the route the comparison pages never mention, because no one sells it to you.
Route two — a purpose-built platform. You buy Dealpath, or a lighter-weight deal-management or relationship-intelligence tool — Affinity, 4Degrees, DealCloud, Edda, or a brokerage-oriented product like Buildout — that carries the pipeline, the workflow, and the reporting for you. The vendor owns the software, the updates, and the data model. Cost is a subscription, usually per seat, plus onboarding.
Route three — custom deal-pipeline automation. You commission a system that automates the specific analyst work your deals demand, wired into the tools you already use rather than inside a walled platform. Not a Dealpath clone — a set of automations: an inbox layer that reads and routes broker deals, a document layer that abstracts OMs and rent rolls into your model, a screening layer that drafts the first-pass memo. You own the logic and, the part that decides the whole question, the maintenance.
Route two and route three are the two poles people argue about. Route one sits before both, and for a shop doing a handful of deals a month it is very often the honest answer. Every route depends on reading the source documents correctly first, which is the harder-than-it-looks problem covered in our playbook for screening and underwriting more deals with a lean team.
Where Dealpath earns its keep
A platform earns its subscription when the pipeline itself — not any single deal — is the thing that has grown unmanageable. Dealpath and its peers solve four problems a spreadsheet cannot.
One source of truth across a team. When several people touch the same deals, a shared workbook degrades fast: stale versions, overwritten cells, no audit trail. A platform maintains one real-time view of every deal and stage, which is exactly the pain that appears once a shop crosses roughly five active users.
Repeatable process, enforced. Dealpath encodes due-diligence checklists, task assignments, and investment-committee workflow so nothing falls through between stages. For a firm with a defined process and the volume to justify enforcing it, that consistency is the product.
Reporting the principals actually trust. Pipeline dashboards, deal metrics, and committee-ready reports come out of the same system the team works in, so the numbers reconcile. Assembling that by hand from spreadsheets is the tax a platform removes.
Maintenance you never perform. When a feature ships or a data source shifts, the vendor’s team handles it. For a firm with no IT department, that is the quiet core of the value — someone else keeps the machine running. The cost is a five-seat minimum, a custom quote, a multi-week onboarding, and a data model you adopt rather than own. For a growing team, that trade is often right. For a four-person shop, it is frequently a mismatch of scale. How that buy-versus-build line plays out across proptech generally is the subject of our guide to when off-the-shelf proptech is enough.
What custom deal-pipeline automation actually is
The word “custom” scares small firms because they picture rebuilding Dealpath — a multi-year platform project no boutique shop should attempt. That is the wrong picture. For a lean investment shop, custom automation almost never means building a deal-management platform. It means putting AI to work on the analyst tasks that actually eat your week, inside the stack you already run.
Concretely: a layer that reads inbound broker emails and drops structured deals into your existing pipeline; a document layer that abstracts a rent roll, a T-12, and an OM into the exact fields of your underwriting model; a screening step that drafts the first-pass memo against your criteria so a principal reviews rather than writes. The pipeline can stay in your spreadsheet or light CRM. The automation is the analyst you did not hire, not a platform you now have to live inside.
That build is genuinely modest. A competent developer or an agency can ship a first version inside a normal automation budget — in the current market a scoped custom project runs roughly $25,000 to $150,000 depending on how many workflows and how much integration. The build is not the cost. The maintenance tail is the cost, and it is where small firms get hurt. Rent rolls arrive in a dozen formats; a T-12 comes as a clean export one month and a scanned PDF the next; a model that placed every figure correctly in March starts drifting in June as documents shift and the underlying model updates. None of this fails loudly — it fails silently, a wrong occupancy figure in a screening memo, a stale number feeding a go/no-go call — and in a firm with no engineer, no one is watching. The honest total cost of ownership is not the build; it is the standing obligation to keep every automated output accurate, and the person, internal or retained, who owns it after launch.
None of this makes custom wrong. It makes custom a commitment rather than a purchase, and a shop should build only when the payoff clearly justifies carrying that commitment. Which specific analyst tasks are worth automating first is exactly what our review of AI deal-screening tools for small CRE investment firms is built to help you sort.
The five-question decision test
Run your firm through these five questions in order. The first unavoidable answer usually points you to a route; if nothing forces the issue, you belong on one of the two lighter ones.
1. How many people touch the pipeline? Under five, a shared spreadsheet plus a thin AI workflow almost always holds — and Dealpath’s five-seat minimum makes it an awkward fit anyway. At five-plus active users stepping on each other, a purpose-built platform starts earning its keep on the single-source-of-truth problem alone.
2. Is your pain the pipeline, or the deal work? Be precise about what actually hurts. If versions and hand-offs across a team are the mess, that is a platform problem, and Dealpath solves it. If the mess is the hours spent reading OMs, populating models, and writing screening memos, that is analyst work — and a platform does not do it for you. Automation, thin or custom, does.
3. How standard is your process? If your due-diligence flow and underwriting map cleanly onto a vendor’s structure, a platform fits with little friction. If your criteria, model, or asset focus are distinctive enough that you would spend the engagement bending the tool to your shape, targeted automation built to your exact process can beat a constrained product.
4. Who fixes it when it breaks? This is the question that ends most build fantasies. A platform’s vendor is your maintenance team. A custom automation is not — if no one at your firm can diagnose an automation that placed a wrong figure, it will drift and no one will notice. Be honest about whether you have, or will retain, someone to own it.
5. Is fluency in place first? A shop that automates screening before its people can judge an AI-drafted memo has built a machine no one can quality-check. The analyst who signs off on a generated screen needs to know what a good one reads like and where models fabricate. That capability comes before the tooling decision, and it runs through the small-firm playbook for out-operating larger competitors.
If questions one through four all point to a platform and you clear the five-seat threshold, buy the platform. The test is not trying to talk you into a build — only to make sure the route matches the actual pain.
The three routes, side by side
| Dimension | Thin AI workflow | Purpose-built platform | Custom automation |
|---|---|---|---|
| Best for | A few deals/month, lean team | 5+ users, standard process, pipeline chaos | Distinctive process or heavy analyst load |
| Setup cost | A subscription | Subscription + onboarding | Build inside an automation budget |
| Ongoing cost | Per-seat | Per-seat, 5-seat minimum | Compute plus a maintenance owner |
| What it fixes | The reading and drafting | The pipeline and process | The specific analyst tasks |
| Lives where | Your existing stack | Inside the vendor platform | Wired into your existing stack |
| Who keeps it accurate | You, per deal | The vendor | You |
| Breaks silently? | Visible, one deal at a time | Vendor catches it | Only if you are watching |
The pattern is plain. Moving to a platform buys process and a single source of truth, and hands maintenance to the vendor — but it assumes the pipeline is your problem and that you clear the seat minimum. Custom automation attacks the analyst work itself directly and transfers a maintenance burden onto a firm that may have no one to carry it. A thin workflow keeps you cheap and safe but caps how much structure you get. The right seat depends on your answers to the five questions, not on which vendor demos best.
The default for a boutique shop, and what flips it
The honest default for a 4-to-20-person investment shop is start thin — an AI-assisted workflow on the stack you already run — and let real pain, not a sales cycle, pull you toward a platform or a build. Most boutique shops never hit the conditions that make either heavy option pay before they have wrung the easy wins out of the light one, and the ones that buy or build prematurely spend money solving a problem they do not yet have.
Two triggers flip the default toward a purpose-built platform like Dealpath:
- You cross the team threshold. Five or more people are actively working the same pipeline and colliding, and the single-source-of-truth problem is now costing real deals.
- Your process needs enforcing. Volume has grown to where an ad-hoc checklist fails and you need due-diligence and committee workflow the system polices for you.
Two different triggers flip it toward custom automation:
- Analyst load is the bottleneck. The hours are going into reading and drafting, not pipeline hygiene, and a repeating deal type makes the work worth automating once and running many times.
- Your process is distinctive and staffed. Your underwriting or criteria are specific enough that no platform fits well, and you have someone who can own the automation after launch.
Absent a clear trigger, a platform subscription or a build is expensive insurance against a problem you do not have. The boutique-shop edge is speed and low overhead; buying scale you do not need, or a maintenance obligation you cannot staff, quietly erases both.
How to verify before you commit
Whichever route the test points to, prove it on your own deals before you sign or fund anything. The verification is the same shape every time.
Take three or four real, representative deals — ideally messy ones, with a rent roll that is not pristine and an OM that arrived as a scan. Run them through the candidate route: Dealpath’s trial and onboarding conversation, the thin workflow’s prompts, or a small prototype of the automation. Then have someone who knows the deals check the output end to end — every figure that landed in a model, every claim in a drafted memo — against the source. A platform that organizes a beautiful pipeline but still leaves your team hand-keying models has not solved your actual pain; an automation that drafts a fast screen but misplaces the NOI is not ready. This costs a few afternoons and saves a shop from a subscription or a build it will regret.
Frequently asked questions
Is Dealpath a good fit for a small CRE investment firm?
It depends on your team size and what hurts. Dealpath is built for collaborative deal teams of five or more, with a typical five-seat minimum and white-glove onboarding, so a four-person shop is often below its intended scale. It shines when several people work the same pipeline and version chaos or process enforcement is the problem. If your pain is instead the analyst hours spent reading documents and drafting memos, a platform does not do that work for you, and a thin AI workflow or targeted automation is a better first spend.
What does “custom deal-pipeline automation” actually mean for a boutique shop?
For a lean shop it does not mean building your own deal-management platform, which would be a costly mistake. It means putting AI to work on specific analyst tasks inside the stack you already run: reading inbound broker emails into your pipeline, abstracting rent rolls and OMs into your underwriting model, and drafting first-pass screening memos against your criteria. The pipeline can stay in your spreadsheet or light CRM. The automation replaces analyst hours, not the way you track deals.
How much does Dealpath cost versus a custom build?
Dealpath does not publish prices; it quotes each firm based on needs, with plans typically starting at a five-user minimum, so budget a recurring per-seat subscription plus onboarding. A custom automation is a different shape of spend: a scoped build generally runs $25,000 to $150,000 depending on how many workflows and integrations it covers, plus the recurring cost of whoever maintains it. A platform folds maintenance into the subscription; a build hands it to you. The right comparison is total cost over a few years, not the sticker on day one.
Can I just use ChatGPT or Claude to run my deal pipeline?
For the analyst work, yes, at low volume — for the pipeline itself, only loosely. ChatGPT, Claude, or Gemini with saved prompts will summarize an OM, pull figures into a model, and draft a screening memo at the cost of a per-seat subscription. What a chat window will not give you is a shared, real-time pipeline with task workflow and reporting across a team; for that you keep a spreadsheet or light CRM, or you graduate to a platform. Many small shops run exactly this hybrid: a simple pipeline plus AI doing the reading and drafting.
When should a boutique shop build custom instead of buying Dealpath?
When your bottleneck is analyst load rather than pipeline chaos, when a repeating deal type makes automation worth building once and running many times, when your process is distinctive enough that no platform fits well, and when you have someone who can own the automation after launch. If those are not true, and especially if no one can maintain a system that drifts, buying is the right call. Custom is a commitment to maintain, not a one-time purchase.
Does AI get the numbers right when it reads deal documents?
Not reliably on its own, and the numbers are exactly where the risk sits. A model can transpose or invent a rent, an expense, or a cap rate that reads plausibly, so no credible workflow skips human review. The safe pattern on any route is AI as a fast first pass that a person then verifies against the source — occupancy, base rents, expenses, the pro forma — before the figure feeds a decision. A wrong number in a screening memo is a number the investment committee relies on.
Is my confidential deal data safe in Dealpath or a custom tool?
It can be on either, but you have to verify the specific terms. Deal pipelines hold sensitive material — off-market seller identities, tenant financials, underwriting assumptions — that a firm must protect. With a platform, confirm its security posture, access controls, and data handling before you load live deals. With a custom build or a thin workflow, use a business-tier account or API where inputs are not used to train models by default, and set a rule to withhold the most sensitive details until a counterparty is under NDA. Defaults differ and terms change, so read the plan you actually buy.
What is the biggest mistake boutique shops make choosing between Dealpath and custom?
Buying scale, or building a system, before they know which problem they have. A four-person shop that signs a five-seat institutional platform to solve an analyst-hours problem has bought the wrong tool; a shop that commissions a custom automation it cannot maintain has bought a liability that will drift and lose trust. The second mistake is automating before the team is fluent enough to catch the errors any route produces — a fast, tidy screen with a wrong NOI is worse than a slow one that is right.
Where to start
The first question is not Dealpath or custom. It is which of the three routes your firm’s real numbers and real pain point to — and whether your team is fluent enough that any of them is safe yet. A free AI-readiness assessment produces that read: a short working session that maps your team size, deal volume, where the hours actually go, and how distinctive your process is, then returns an honest recommendation for whether a thin workflow, a purpose-built platform, a custom automation, or a month of fundamentals first is the right next move. Book a free AI-readiness assessment before you commit a dollar to either side of the buy-versus-build line.
Arthur Wandzel
