Build vs Buy: Should Your Transition Consulting Firm Build Its Own Tech?
Build vs Buy: Should Your Transition Consulting Firm Build Its Own Tech?
A boutique transition consulting firm running 30-50 transitions per year should almost always buy rather than build. The breakeven for building custom transition technology is roughly $1.2M in year-one investment, $400K in annual maintenance, and a 24-month payback that requires the firm to grow past 100 transitions per year before the math turns positive. The exceptions are firms with proprietary IP they cannot expose to a vendor, firms with deep engineering benches already on payroll, or firms whose service model genuinely diverges from market-standard workflows.
The Real Cost of Building
The intuition behind building is appealing: own the IP, own the workflow, no per-seat fees, no vendor risk. The math behind building is less appealing.
A minimum viable transition platform that handles ACATS form generation, NIGO triage, custodian integrations, audit trails, and document storage requires:
| Component | Year-1 Build Cost | Annual Maintenance |
|---|---|---|
| Senior engineering (2 FTE, full year) | $480,000 | $480,000 |
| Product management (0.5 FTE) | $90,000 | $90,000 |
| Compliance and security review | $80,000 | $40,000 |
| Custodian integration build (Schwab + Fidelity + Pershing) | $180,000 | $60,000 |
| Cloud infrastructure and tooling | $40,000 | $50,000 |
| Initial security audit and SOC 2 prep | $90,000 | $40,000 (continuous compliance) |
| Internal training and documentation | $30,000 | $20,000 |
| Total | ~$990,000 | ~$780,000 |
That excludes the cost of the inevitable post-launch rebuild after the first wave of users surfaces requirements the original spec missed (typically 30-50% additional investment in year two).
Compare to buying an enterprise transition platform: $80K-$150K per year for a consulting firm running 30-50 transitions, all-in, including custodian integrations the vendor already built and amortizes across many customers.
When Building Actually Pays Off
There are three scenarios where the build math turns positive:
Scenario 1: Volume past 100 transitions/year, growing. At 100+ transitions, per-seat or per-transaction vendor pricing crosses the $200K-$300K mark. Building a custom platform amortizes across enough transactions that year-three economics turn favorable, assuming the firm can hold a 2-FTE engineering team without distraction from core consulting work.
Scenario 2: Proprietary IP the firm cannot expose. Some consulting firms have developed unique workflow methodologies that constitute their commercial differentiation. Embedding that IP in a third-party platform creates vendor exposure (the vendor could productize it and sell to competitors). In this case, building is a defensive moat decision, not an economic decision.
Scenario 3: Genuine workflow divergence. A firm whose service model differs substantively from market-standard transition workflows — for example, a firm specializing in cross-border transitions, captive insurance carve-outs, or alternative-heavy books — may find that off-the-shelf platforms force unworkable compromises. Building is the only path to a workflow match.
If none of those three apply, buying is the cleaner answer.
The Build Path That Most Firms Choose (And Regret)
The most common build pattern is "we'll start with a custom internal tool and extend it as we grow." This pattern almost always fails for three reasons:
The MVP underestimates compliance. Audit trails, retention requirements, encryption-at-rest, and FINRA examination support are not edge cases — they are core requirements that take 30-40% of the engineering investment. Founders often discover this only when a client requests their SOC 2 report.
Custodian integrations are not "wrapping APIs." Schwab, Fidelity, and Pershing have integration patterns that include sandbox environments, certification requirements, security reviews, and ongoing version migrations. A serious custodian integration is a 6-month project per custodian, not a sprint.
The engineers leave. A 2-person engineering team at a consulting firm has no career path. Senior engineers leave for tech companies offering equity and a product team. The platform becomes "the thing only Joel knows how to fix," and then Joel takes a Stripe job and the firm has a $1M technical debt problem.
A Cleaner Decision Framework
Skip the build-vs-buy spreadsheet and answer four questions:
- Is your firm running 100+ transitions per year and growing 30%+ annually? If no, buy.
- Is there workflow IP that genuinely differentiates you commercially and would be exposed by using a third-party platform? If no, buy.
- Do you already employ 2+ senior software engineers as part of your core team? If no, buy.
- Are you willing to accept a 6-9 month delay on launching new transition capacity while the build happens? If no, buy.
If all four answers are yes, building may make sense. In practice, fewer than 5% of transition consulting firms have all four conditions true.
The Hybrid Path That Often Works
A middle path that many firms ultimately land on: buy the platform for core workflows (document generation, ACATS, NIGO triage, custodian integrations) and build thin custom layers on top for the firm's unique workflows. This pattern works because the expensive, compliance-heavy core is amortized across the vendor's customer base, while the firm preserves its workflow IP in a layer that is much smaller and cheaper to maintain.
A typical hybrid stack:
- Core platform (buy): Document automation, ACATS, NIGO triage, audit trails, custodian connectors, advisory agreement generation
- Custom layer (build): Firm-specific intake forms, proprietary scoring or prioritization logic, client communication templates that reflect the firm's voice, dashboards that aggregate across the firm's portfolio
- CRM integration (configure): Salesforce or HubSpot, with the firm's process structured as workflows in the CRM rather than custom code
The hybrid stack typically costs $120K-$200K in year one (platform + integration consulting) and $80K-$150K in maintenance, versus the ~$1M of a full custom build.
The Vendor Lock-In Question
The most common objection to buying is vendor lock-in. The honest answer is that lock-in risk is real but smaller than the build-cost risk for most firms. Mitigations:
- Negotiate data portability into the MSA. Complete data export in machine-readable format within 10 business days of request, at no charge.
- Pick vendors with multi-tenant architecture, not single-tenant. Multi-tenant vendors have stronger incentives to maintain pricing discipline because customer churn is more visible.
- Avoid vendor-proprietary data formats where alternatives exist. Store underlying client data in formats that other systems can ingest.
With those mitigations, the practical lock-in risk is roughly the cost of one quarter of operational disruption during a vendor switch — which is far less than the $1M+ year-one build investment.
FAQ
At what transition volume does building make economic sense? Roughly 100+ transitions per year with sustained 30%+ growth, given current per-seat vendor pricing. Below that, the engineering and compliance overhead of building eats the savings.
Can we build incrementally and avoid the big upfront cost? The "incremental MVP" pattern almost always fails because compliance, security, and custodian integration are not incrementally extensible — they are foundational. Firms that try to build incrementally often spend $300K-$500K on an MVP that cannot pass FINRA examination scrutiny, then start over.
What about using low-code platforms like Retool or Airtable? Useful for internal workflows and project tracking. Inadequate for production-grade ACATS submission, custodian integration, or audit trail retention. Most firms that adopt low-code platforms for transition workflows hit a wall at 15-25 concurrent transitions.
How long does a serious build actually take? 9-18 months from green-light to first production transition. Anyone promising less than 9 months has not built one before.
What's the cleanest hybrid model? Buy the core platform for compliance-heavy and custodian-integrated workflows. Build a thin custom layer for firm-specific intake, prioritization, and client communication. Use a configured CRM (Salesforce or HubSpot) for relationship management. Total cost: $120K-$200K year one, $80K-$150K annually.
Related: Meeting Assistant · Advisor Transitions Platform
