Merchant cash advance operations
Ophelia supports the people who keep an MCA office moving: lead intake, lead allocation, duplicate checking, submissions tracking, approvals tracking, declines tracking, lender guideline awareness, commission collection follow-up, renewal emails, and the daily handoff. Every deployment begins read-only and earns its write permissions one workflow at a time.
Proof, not magic
MCA operations contract
Read-only before write access
Configured inboxes, CRM, underwriting records, sheets, and lender rules supply attributable desk context.
She watches transitions, surfaces conflicts, and prepares a reviewable queue from the mapped sources.
A current status, morning list, draft, or stip checklist exposes the next item without moving the file.
Underwriting, funding, sensitive stage moves, money movement, and outward messages require explicit approval.
Raw business data remains outside personal memory and operational facts stay with the authoritative work store.
Live in the current private deployment
The office-admin operating loop
The journey is configured around each office’s real inboxes, CRM, underwriting platform, sheets, lender rules, and approval boundaries. It makes the handoff visible without pretending that a file, offer, fund, or message can move itself.
The desk, at a glance
An illustrative operating view: it organizes source-backed work and makes exceptions visible. It does not assign, submit, approve, fund, pay, or send by default.
Read and reconcileReview before decisionDraft and follow up
Turn approved channels into a reviewable starting point.
Keep the file’s reported state legible across configured sources.
Put evidence, offers, conditions, approvals, and declines in front of the office.
Make post-funding collection and renewal work harder to lose.
Every lane starts from the office’s configured sources and ends at a clear owner or review checkpoint.
A linear text equivalent: receive and classify the lead; check for duplicates; apply owner rules; track the submission; surface an approval or decline for review; prepare the closing handoff; confirm reported funding; follow up on commission; then prepare the renewal queue.
Collect and classify applications, statements, IDs, and supporting files into a reviewable queue.
ObserveCompare business and contact records, holding possible conflicts for an office-admin decision.
Hold for reviewPrepare routing from supplied ownership rules, with exceptions kept visible to the team.
PrepareReconcile the submitted file across connected systems and lender guideline awareness.
ObserveSurface attributable status, offers, and stips; the office—not Ophelia—makes the decision.
Human decisionTurn approved conditions into a stip checklist and show what is still blocking funding.
PrepareReconcile funding evidence from approved source systems; no money movement or stage change occurs by default.
ConfirmFlag commissions that appear due, late, missing, or internally inconsistent for collection review.
Follow upSurface eligible candidates and draft renewal emails for human review before sending.
Draft for reviewObserve and reconcileHuman approval checkpointPrepare a follow-up
Turn submissions@, subs@, admin@, and approved intake channels into one reviewable queue.
Give the office administrator one current view of each file across connected systems.
Put source-backed deal facts in front of the person making the decision.
Keep the next missing item visible from approval through closing.
Close the administrative loop after a deal is reported funded.
Keep recurring office work from disappearing behind the newest urgent file.
Illustrative workflow examples
These examples show the handoff in a configured office. They contain no real merchant records or company results.
Capture a consenting visitor’s contact details, preserve campaign attribution, and enrich the same lead as the application progresses. Report saved contacts separately from completed applications and funded deals.
Link an explicit contract request to its deal and source thread. Show the next required document and notify the configured recipients without losing the approval context.
Explain the payment-return reason in plain language, deduplicate notifications, and connect the merchant’s reply to the servicing record. Payment arrangements remain human-owned.
Employee portal + CRM foundation
Ophelia’s employee portal is being built as a secure home for the daily MCA toolkit. The same foundation can grow into a configurable operations platform for other teams without mixing company data, identities, or permissions.
Bring underwriting support, pitch preparation, document tools, training, and performance views into one authenticated navigation surface.
Connect approved inbox, CRM, sheet, and lender-guideline sources so the team sees attributable deal status, exceptions, and the next handoff.
Extend the portal into lead intake, contact and document organization, lender selection, controlled submission, and reply-driven stage tracking—with each client’s own assistant identity.
Write boundaries
Ophelia is not a lender feed, credit bureau, law firm, or substitute underwriter. Recommendations are limited to provided, attributable material.
Declines, funding, sensitive CRM stage moves, money movement, and external communications stay behind explicit approval and system-specific safety rules.
Generated sheets and dashboards are views. Operational facts land in the authoritative store, so the next refresh cannot silently erase them.
Availability
Read-only event monitoring, work-specialist questions, current summaries, and board visibility operate in the current configured environment.
Intake, document, guideline, offer, renewal, and reporting workflows require a mapped source of truth, dry-run evidence, and owner acceptance.
More proactive work-email and front-desk actions remain gated until identity, consent, deduplication, and outward-send controls are complete.
MCA operations FAQ
Ophelia can support lead intake and allocation, duplicate checks, submissions, approvals and declines tracking, lender-guideline awareness, commission follow-up, renewal drafting, and office handoffs.
No. Ophelia organizes source evidence, surfaces conflicts, and prepares reviewable drafts or checklists. Underwriting, funding, and other sensitive decisions remain human-owned.
Yes, when the source and permission boundary are explicitly configured. New connections begin read-only and receive only the access required for the approved workflow.
The current product direction begins with an authenticated employee portal for MCA tools and operations visibility. A configurable CRM workflow is planned for a later phase after tenant isolation, audit, deduplication, and delivery controls are proven.
The default is draft-first. Outward messages require review unless a separate, bounded workflow has explicit approval, deduplication, audit, and stop controls.