Copperlane Penny vs. Floify: Document Collection Compared

TL;DR

Floify is a borrower-facing portal. It gives borrowers a clean checklist and a place to upload documents, then waits for them to log in and act.

Penny is an outbound agent. It chases missing documents across SMS, voice, and email, reaching borrowers wherever they already are.

The core difference is simple. Floify waits. Penny acts.

Both tools deploy as overlays. Neither replaces your LOS, and they can run side by side.

What Each Tool Is

Floify is a borrower-facing document portal, and it does that job well. Borrowers log in to a white-labeled checklist that carries the loan officer's branding, then upload tax returns, pay stubs, and bank statements at their own pace. The portal syncs documents into Encompass through eFolder, so processors see uploads without manual filing. Loan officers get a clean self-service experience to hand borrowers, and the upload flow feels modern. Floify's strength is the interface borrowers touch and the branding lenders control.

The limit is structural. Floify waits. A borrower has to log in before anything happens, and a missing document sits as a quiet line item on a checklist until someone notices.

Penny works from the other direction. It is an outbound collection agent that initiates contact the moment a document is missing or a condition is open, reaching borrowers by SMS, voice, and email without requiring a portal login. When a document arrives, Penny validates it at upload for legibility, type match, and completeness, so a blurry pay stub gets flagged before it lands on a processor's desk. Penny also maps each request to specific open conditions in your LOS, which means collection follows what underwriting actually needs rather than a generic checklist.

Penny is not underwriting software and it does not close loans. It handles the chase and the intake. Where Floify hands borrowers a place to upload and waits for them to act, Penny reaches out, confirms the document is usable, and writes it back against the open condition. Floify waits. Penny acts. That contrast runs through every dimension below, and it is the reason the two tools solve different parts of the same problem.

Head-to-Head: Six Dimensions

The two tools split along one axis. Floify hands the borrower a checklist and waits for action. Penny initiates the work itself, then validates and routes what comes back. The six dimensions below show where that difference shows up, from the first document request through how each tool writes back to your LOS.

Document Request Initiation

Floify gives the borrower a static checklist. The borrower has to log into the portal to see what's missing and decide when to act. Nothing happens until they do.

Penny fires an outbound request the moment a document is missing or a condition opens. The borrower hears from Penny before they think to log in anywhere.

• Floify is reactive. The portal sits until the borrower visits.
• Penny is proactive. Each gap triggers an outreach instead of waiting.
• Floify waits, Penny acts.

Channel Coverage

Floify operates inside the portal. A borrower responds to a request by logging in and uploading. The login step is the friction point.

Penny reaches borrowers over SMS, voice, and email. The borrower replies in the channel they already use. No portal login is required to respond.

• Floify needs the borrower to come to it.
• Penny meets the borrower where they already are.
• Removing the login step cuts the most common stall in doc collection.

Upload-Time Validation

Floify accepts whatever the borrower uploads and stores it in the file. No quality check runs at the moment of upload, so a blurry W-2 or the wrong tax year sits in the portal until a processor opens it. That delay is where back-and-forth cycles start.

Penny validates each document as it lands. The agent checks legibility, confirms the document type matches what was requested, and flags missing pages before the file reaches your ops team.

• Floify stores uploads without a real-time review
• Penny rejects bad scans at the source, not three days later
• Fewer reupload requests means fewer touchpoints per condition

Condition Awareness

Floify tracks documents against a checklist the lender builds. That checklist has no native link to the open PTD and PTC conditions sitting in your LOS, so someone has to reconcile the two by hand.

Penny maps each document request to a specific open condition. Collection runs off the actual condition set, not a static list someone configured weeks ago.

• Floify chases a checklist that drifts from the live condition file
• Penny pulls open conditions and requests exactly what clears them
• Condition-driven collection keeps PTD and PTC items from going stale

The contrast holds again here. Floify waits for the borrower and the processor to close the loop. Penny acts the moment a condition opens.

LOS Integration

Floify syncs documents into the LOS eFolder, with Encompass as its primary supported system. Once a borrower uploads through the portal, the file lands in Encompass without a processor manually moving it. Penny writes back to the LOS through an adapter layer, pushing collected documents and status updates against the loan record.

The practical difference shows up in what gets written. Floify moves files into the eFolder. Penny moves files and updates the open conditions tied to them.

• Floify: eFolder sync, Encompass-first
• Penny: adapter-based write-back across supported LOS platforms
• For Penny's current LOS coverage, contact the vendor rather than assuming parity

Deployment Model

Both tools deploy as overlays, so neither forces you to rip out or replace your LOS. You keep Encompass or whatever core system runs your pipeline, and either tool sits on top of it.

The overlay model also means Floify and Penny can stack. Penny runs on top of Floify for shops already committed to the portal, adding the outbound chase layer without disturbing the upload interface borrowers already use.

• Floify: overlay portal, no LOS replacement
• Penny: overlay agent, no LOS replacement
• Penny can deploy directly over an existing Floify setup

Comparison Table

The table below maps both tools across the dimensions IMB ops teams actually weigh during evaluation. Where a capability is unknown, the entry points you to the vendor rather than inventing a spec.

Dimension	Floify	Penny
Document initiation	✅ Borrower-driven portal checklist	✅ Agent-initiated outbound chase
Channel coverage	⚠️ Portal login only	✅ SMS, voice, email
Upload-time validation	❌ No real-time check	✅ Validates at upload
Condition awareness	❌ No condition mapping	✅ Maps to open LOS conditions
LOS integration	✅ eFolder sync (Encompass)	✅ Adapter-based write-back
Overlay deployment	✅ Yes	✅ Yes, can run on Floify
Best for	Portal UX + LO branding	Proactive doc chase + condition-linked collection

Floify waits for the borrower to act. Penny opens the conversation, validates what comes back, and ties each request to an open condition.

When to Choose Floify

Choose Floify when your loan officers already own borrower follow-up. If your LOs chase documents manually or through a CRM workflow, Floify gives borrowers a clean place to upload. You already have the outreach. You need the portal.

Floify's white-labeled borrower experience is genuinely strong. The portal carries your LO's branding, the upload checklist is intuitive, and borrowers can self-serve without hand-holding. Shops that compete on borrower experience get real value from that polish.

Encompass eFolder sync is the other reason to pick Floify outright. If your only hard requirement is documents landing in eFolder without manual filing, Floify handles that cleanly. You don't need condition-linked collection, and you don't need outbound multi-channel chasing.

Floify is the right call when the portal itself is the job. You want a borrower-facing upload experience with LO branding and proven UX, and your team already covers initiation somewhere else. Floify waits for the borrower to act, and if your process is built around that, the wait isn't a problem. It's the design.

When to Choose Penny

Choose Penny when manual doc-chasing is eating your processors' days. Floify waits for borrowers to log in and upload. Penny acts the moment a document goes missing or a condition opens.

Pick Penny when borrower non-response drives your cycle times. Penny reaches out over SMS, voice, and email without forcing the borrower back into a portal. Most borrowers answer a text faster than they remember a login.

Pick Penny when conditions go stale waiting on docs. Penny maps each request to a specific open PTD or PTC condition, so collection follows underwriting priorities instead of a flat checklist.

Pick Penny when you want multi-channel outreach without building it yourself. Your team gets proactive doc chase, upload validation, and condition-linked collection in one agent. You stop stitching together a CRM, a reminder cadence, and a portal to do what one tool handles.

Can You Use Both?

Yes. Penny runs as an overlay on top of Floify, so you do not have to pick one or rip anything out. Lenders who already committed to Floify's portal keep the upload interface their borrowers know.

Floify handles the front door. Borrowers log in, see their checklist, and upload through the white-labeled experience your loan officers branded. Penny sits behind that and runs the active layer.

Penny initiates the outreach when a document is missing, reaches the borrower over SMS, voice, or email, and validates each file at upload before it lands in your processor's queue. Floify waits for the borrower. Penny goes and gets them.

Neither tool requires an LOS replacement. Penny writes back through its adapter while Floify keeps its eFolder sync to Encompass. You get Floify's portal UX and Penny's proactive chase running together, with no separate outreach workflow to build and maintain.

Pilot Penny

Watch Penny run a live doc-chase against your actual pipeline before you commit to anything.

• See Penny initiate outbound contact on a stalled file across SMS, voice, and email
• Watch upload-time validation flag bad documents before they reach your processors
• Track condition-linked collection against your open PTD and PTC items

Every condition that sits stale waiting on a borrower is processor time you're paying for. Penny chases the docs your team would otherwise call about by hand.

Request a Penny pilot

Frequently Asked Questions

Does Floify send automated reminders to borrowers?

• Floify sends portal-based notifications, not outbound SMS or voice
• Borrower must have logged in or opted into alerts first
• Penny initiates outreach regardless of prior portal activity

Which LOS does each tool support?

• Floify integrates primarily through Encompass eFolder sync
• Penny writes back via adapters; contact the vendor for the LOS list
• Both deploy as overlays; neither replaces the LOS

Can Penny replace Floify entirely?

• Penny is an outreach and collection agent, not a portal
• Floify's upload UX and LO branding are distinct strengths
• The practical path is running Penny on top of Floify

How does Penny validate documents at upload?

• Penny checks legibility, document type, and completeness at upload
• Bad uploads are flagged before they reach the ops team
• Fewer back-and-forth cycles run between borrower and processor

What does proactive doc collection do for cycle time?

• Fewer stalled conditions clear PTD and PTC faster
• Cutting manual follow-up days compresses per-loan cost directly