Workflow Core
Durable loan-file state machine, agent orchestration, retries, SLAs, escalations, and idempotent actions.
Private proposal summary
A regulated workflow automation platform for mortgage processing teams, covering LOS and vendor integrations, document ingestion, human approval gates, compliance guardrails, and immutable audit trails.
Scope basis
This estimate is based on the supplied technical specification for a mortgage processing AI agent system. The scope is closer to a compliance-sensitive workflow platform than a lightweight chatbot.
Durable loan-file state machine, agent orchestration, retries, SLAs, escalations, and idempotent actions.
One primary LOS, vendor APIs, email/DMS connectors, normalized adapter schemas, and document routing.
GLBA, RESPA, HVCC/AIR, UAD, NMLS, PII tokenization, encryption, approval gates, and audit retention.
HITL dashboard, Slack/email notifications, processor review queues, metrics, shadow mode, and rollout support.
Investment context
Production-grade regulated AI systems with multiple integrations typically land in the high six figures to low seven figures before ongoing support and third-party compliance costs.
Pricing rationale
The proposed pricing is based on the combination of regulated workflow engineering, AI/document extraction, third-party integrations, security controls, human review tooling, and production rollout support.
At senior AI, backend, integration, security, and product rates, this quickly lands in the high-six to low-seven-figure range before external security review, SOC 2 work, cloud spend, and API usage.
Public 2026 buyer guides place regulated fintech/healthtech-style platforms around $500k-$1.2M+.
FWC app development guideEnterprise AI platform ranges commonly run from roughly $250k to $1M+ or $2M+ depending on scope.
Uvik AI cost guideEnterprise modernization and AI integration rates are commonly benchmarked around $150-$350+/hr.
Modernization Intel rate guideSOC 2 and penetration testing are separate cost centers that can add tens of thousands before rollout.
Proposed commercial structure
To align incentives while still covering delivery risk, we can reduce the upfront build fee in exchange for a defined share of gross product revenue after launch.
$750k upfront
Plus 50% of gross revenue until $1.5M has been paid through the share.
$45k
Creditable toward the build fee if the production engagement moves forward.
First-dollar gross
Monthly reporting, audit rights, launch deadline, and change-of-control payout.
Delivery timing
If the client provides LOS access, vendor credentials, historical files, sample documents, and compliance approvals early, the MVP can move quickly. Integration delays are the main schedule risk.
2-3 weeks
Integration audit, final MVP definition, compliance matrix, data flow, and delivery plan.12-16 weeks from start
One LOS, 2-3 vendor workflows, document extraction, HITL dashboard, audit log, and shadow mode.Additional 12-16 weeks
Supervised mode, hardening, monitoring, security review, training, rollout, and rollback plan.9-12+ months total
Additional LOS platforms, vendor breadth, portal fallbacks, mature evals, and broader operations.Implementation path
Support model
This product will need active support because mortgage workflows, vendor APIs, documents, and compliance requirements shift over time. Support should begin during supervised rollout, not after issues accumulate.
Suggested contract: 6-month minimum after launch, then month-to-month. Emergency support outside agreed SLAs, new integrations, and major feature expansion are scoped separately.
Client inputs needed
These items determine how firm the quote and schedule can be. The more complete this handoff is, the faster the MVP can begin producing useful results.
Primary LOS, vendor list, sandbox credentials, API documentation, DMS preference, and email environment.
90 days of anonymized historical loans, sample appraisal/UAD, HOI, flood, VOE, transcript, and title docs.
HITL approval matrix, PII policy, retention requirements, approved AMC rules, and compliance owner availability.
Gross revenue definition, revenue share cap, reporting cadence, launch deadline, IP ownership, and payout triggers.
Target customers, expected loan volume, sales responsibility, pilot cohort, processor availability, and rollout dates.
Cloud preference, security review scope, SOC 2 expectations, SLA targets, support hours, and budget for pass-through costs.