ISO teams break on attribution. Two agents call the same merchant. Both claim the file. The shop has one portal login. Operations picks a winner by who yelled last. The loser takes the next lead off-platform. You did not have a culture problem. You had one username.
Loanable issues unique partner links. A serious ISO office gives producers separate partner identities or a documented mapping from code to agent. Applications show up on the dashboard that owns the code. Funded deals pay 50/50 of Loanable profit to that partner of record, Monday ACH, no minimum. How you then split with a W-2 or 1099 agent is your agreement. Loanable is not the lender and is not your payroll vendor.
What to standardize across the team
The application URL pattern. The rule against sending a second funder’s form in the same text thread. The statement checklist. The sentence you use when a merchant asks “are you the lender?” — no, Loanable is a marketplace of 150+ lenders. The timing language: working capital as soon as 24 hours in the best case, not a guarantee. If every agent improvises those lines, you will get advertising and underwriting problems in the same week.
- One code per producer who is allowed to originate
- CRM fields that store the code, not a Slack screenshot
- A house rule on what happens if two codes hit the same EIN
- Monday reconcile by agent, not by office total only
Sub-agents who are actually other shops
If you recruit ISOs who have their own merchants, treat them as partners with their own codes, not as a row on your grid with a borrowed login. Borrowed logins are how you lose both the file and the relationship. Loanable’s program does not require you to be the only brand the merchant sees. It requires the ref code to be correct.
Do not build a fake “API integration” for agents
Teams ask for a push-button LOS. Loanable does not offer a public REST lending API that underwrites and funds inside your homegrown software. Embedded solutions for SaaS companies are branded or co-branded apply flows with partner attribution. For an ISO team, the operational equivalent is a unique link in the CRM and a dashboard. Pretending otherwise in a recruiting deck is how you hire people who will be angry on day three.
Pay attention to product mix across agents. If one producer only sells MCA and another actually asks about equipment, the flat 50/50 split including large facilities up to $50M is your chance to stop punishing the second producer. Train the first one. Do not write a shadow grid that recreates the last shop you left.
Onboarding a producer in one afternoon
Give them a code, a CRM snippet, a statement checklist, and the “we are not the lender” sentence. Watch them send one test click and confirm the dashboard. If you skip the test click, they will paste a homepage for a month. If you skip the sentence, they will advertise like a funder. Loanable’s 150+ lenders and Monday 50/50 ACH will not fix a producer you never trained.
Write the house rule for collision: same EIN, two codes, same week. First complete application wins, or manager review, or split — pick one and put it in the packet. Unwritten collision rules are how teams go to war on a Monday deposit. Unique partner links make the data clear. Policy makes the culture survivable.
Run the team on codes, not on arguments. Apply to Loanable’s ISO program and give each producer a partner link you can see in the dashboard.