1. How many systems have to agree. Every integration is a project inside the project: authentication, field mapping, sync direction, deduplication, retries, and what happens when the other side is down. One integration adds $8,000–$20,000. A connector framework that makes the fourth integration cheaper than the first is worth it once you pass three; we built one for Fundz that carries signals into Gmail, HubSpot and Salesforce from the same code.
2. How much of the work is documents. If intake arrives as PDFs, scans or handwriting, you are paying for OCR, document classification, field extraction and a human review step for the exceptions. Done well, this is where AI earns its place: a model reads the application, a person checks only what the model flagged. Budget $20,000–$50,000 for a document-AI intake pipeline with the review queue, more if the document types vary widely.
3. Compliance and auditability. Lending, healthcare and anything touching PII needs an audit trail on every status change, field-level permissions, retention rules and sometimes third-party due-diligence calls that must be traceable later. For Samson Funding’s working-capital lending platform, the due-diligence API calls were built for retries and traceability from day one, because a funded loan has to show why it was approved. This adds 15–30% to a build and is the worst thing to retrofit.
4. Reporting and the data model under it. Dashboards are cheap; the data model that makes them true is not. Hoopes Vision had years of surgical data in spreadsheets; the cost was in normalising it into one database with ingestion, transformation and reporting kept separate, so a new data source never breaks an existing report. Expect $15,000–$40,000 for a reporting layer with a clean model, less if your data is already structured.
5. Who has to use it. An internal tool for twelve staff needs less polish than a client-facing portal. nCred’s credentialing portal shows live progress pulled from Salesforce and lets clients upload documents themselves so files stop arriving by email. Client-facing adds design, onboarding, self-serve flows and support tooling, roughly 30–50% on top of the internal version.