Designing Pipeline Stages That Match How Deals Really Fund
A pipeline is a set of promises about where a deal is. Here is how to define stages with exit criteria your whole floor applies the same way.
Open the pipeline view at most funding shops and you will see stages like Hot, Warm, Working, Pending, Follow Up and Almost There. Each broker has a private theory about what they mean. The manager sees forty deals in Working and has no idea whether that means forty merchants waiting on an offer or forty voicemails left last month.
A pipeline is only useful if a deal's stage tells you a fact about it. That requires stages tied to real events in the funding process, written exit criteria for moving forward, and rules for what happens to deals that stop moving. This guide lays out a stage design built around how business-funding deals actually progress, and the common mistakes that make pipelines lie.
Pre-flight summary
- Each stage should describe an event two people would agree on.
- Write an exit criterion for every stage.
- Use fields, tasks and notes for nuance instead of extra stages.
- Close lost deals with a reason from a short fixed list.
- Give every stage a time limit and an automatic consequence.
Leg 01Stages should be events, not feelings
The test for any stage is simple: could two different people look at the same deal and agree, without discussion, whether it belongs there? Hot fails that test. Application Signed passes it. Statements Received passes it. Submitted to Lenders passes it.
Event-based stages also make your reporting honest. When stages are feelings, conversion between them is meaningless. When they are events, you can see exactly where deals stall, such as plenty of signed applications that never produce statements, and fix that specific step.
Leg 02A stage set built around the funding process
This is a reasonable starting design for a broker or ISO. Your own may differ, especially if you are a direct funder, but notice that each stage has a clear exit criterion: the thing that must be true before the deal moves on.
- New Lead: exits when a real two-way conversation has happened
- Qualified: exits when time in business, approximate deposits, industry and use of funds are confirmed and fit at least one lender
- Application Signed: exits when a signed application is on file
- Documents Complete: exits when the required statements, ID and supporting documents are received and reviewed
- Submitted: exits when at least one lender has returned an offer or a decline on every submission
- Offer Presented: exits when the merchant accepts an offer or declines all of them
- Contracts Out: exits when signed contracts and stipulations are complete
- Funded: closed won, with the funded amount and lender recorded
Leg 03Why more stages usually makes things worse
It is tempting to add a stage for every nuance: Statements Requested, Statements Partially Received, Waiting on Landlord Letter, Submitted Round Two. Each one feels useful when it is added. Together they create a pipeline where brokers spend time moving cards instead of calling merchants, and where small differences in how people use the stages destroy your conversion data.
Keep stages for milestones and use fields, tasks and notes for nuance. A missing landlord letter is a task on a deal in Documents Complete, not a stage of its own. Round two submissions are additional lender submissions threaded onto the same deal, not a new stage.
A good rule of thumb: if a stage would never be the place where a manager intervenes differently, it probably should not exist.
Stages are for milestones. Fields, tasks and notes are for nuance.
Leg 04Lost reasons are part of the design
Every deal that does not fund should leave the pipeline with a reason picked from a short, fixed list. Free-text loss reasons become unreadable within a month.
Say your loss reasons show that a large share of qualified merchants are lost at Documents Complete with the reason Never Sent Statements. That tells you the problem is collection, not lenders, and a simpler upload path or a better follow-up cadence might help more than adding lenders to your panel.
- Declined by all lenders
- Merchant chose another provider
- Merchant no longer needs funding
- Never sent documents
- Did not qualify after review
- Unreachable
Leg 05Stale-deal rules that keep the pipeline honest
Every stage needs a time limit. When a deal passes it, something should happen automatically: it shows up on the manager's exception list, the owner gets a task, or a follow-up sequence starts. The specific numbers depend on your floor, but the principle is that no deal should sit silently.
For example, you might decide that a deal in Application Signed with no statements after two business days triggers a text and email reminder to the merchant and a task for the broker. After a longer window with no response, the deal is closed with the reason Never Sent Documents and moved into a reactivation campaign. That is not giving up; it is being honest about where the deal really is.
FundPilot lets you set custom stages and connect them to campaigns that respect the merchant's local time and stop as soon as they reply, so a stale-deal rule can trigger a polite follow-up without a broker having to remember it.
Leg 06Rolling out a new stage design
Changing stages on a live floor needs care. Map every old stage to a new one before you switch, migrate open deals in one sitting, and spend a huddle walking through the exit criteria with real examples from your current pipeline.
Expect two weeks of brokers asking where a particular deal belongs. Answer every question in team chat so everyone sees the ruling, and adjust a definition if the same question keeps coming up. After a month, compare stage-to-stage conversion with what you expected. In FundPilot, the AI assistant can pull those numbers from live CRM data in plain English, which makes the first review quicker. A walkthrough is a good way to see how your current stages would translate.
Questions from the floor
How many pipeline stages should a funding shop have?
Most broker and ISO floors work well with roughly six to nine stages between first contact and funded. Fewer than that and you lose visibility into where deals stall. Many more and brokers spend effort moving cards and interpret stages inconsistently. Start lean, run it for a month, and add a stage only if managers genuinely need to act differently at that point.
Should renewals use the same pipeline?
Usually a separate pipeline or a clearly tagged deal type works better. Renewals start from a different place: you already have the merchant's history, payment performance and contact details, and the first stage is often an eligibility check rather than a cold qualification call. Keeping them separate also stops renewal volume from distorting conversion rates for new business.
What should happen to a deal that goes stale?
It should trigger something visible: an exception-list entry, a task for the owner, or an automatic follow-up. If it stays stale past a longer limit, close it with an honest loss reason and move the merchant into a respectful reactivation sequence. Leaving dead deals open inflates the pipeline and hides the real problems from your reporting.
Can brokers skip stages?
They can when the facts allow it, such as a merchant who sends a signed application and statements in the same email. The exit criteria still apply; the deal just satisfies several at once. What should not happen is skipping a stage because its requirement was ignored, such as submitting to lenders before documents have actually been reviewed.
General information only — not legal, tax or financial advice. Rules for telemarketing, texting, recording, disclosures and data retention vary and change; confirm current requirements with qualified counsel.
Connecting flights