with Public Safety Workforce Management Software · Public Safety Workforce Management Software
LenderHawk analysis. Not affiliated with or endorsed by Acquisitions Anonymous.
The business is marketed as sticky public-safety software with recurring monthly revenue and low churn, but the panel doubts the growth story because it has existed since 2005 and still produces only modest revenue. The likely financing path depends on whether the product is truly SaaS, whether the buyer has relevant domain experience, and whether a lender can underwrite the niche customer base at all.
A business can have recurring revenue and still be unfinanceable if it is too small for the lender’s credit box.
Old SaaS listings warrant extra diligence on whether the product is truly cloud-native or just legacy software dressed up as SaaS.
Customer stickiness alone does not solve weak scale; a 16-year-old software company with sub-$600k revenue raises questions about growth ceiling and product relevance.
For niche software or services businesses, buyer operating experience can materially improve financing odds.
SBA lenders care about practical recourse, so a seller note often matters more than theoretical lawsuit rights after closing.
A seller note can be structured to amortize rather than sit on full standby under current SBA practice, depending on the lender’s credit policy.
For MSPs, low margins, hidden hardware/warehouse needs, and customer concentration can make the deal look much riskier than the teaser suggests.
Broker funding examples often overstate simplicity by assuming idealized debt terms and ignoring qualitative underwriting concerns.
Heather divides SBA lenders into those who underwrite mainly to collateral and those who underwrite mainly to debt coverage and recurring cash flow. SaaS and other asset-light acquisition targets usually fit the cash-flow lender model better.
When to use: Use this when evaluating whether an SBA lender is likely to support an asset-light acquisition.
She describes a structure where a buyer can put as little as 5% equity if the seller carries the other 5% on full standby for the life of the SBA loan. She says her bank only uses it in limited cases such as key-manager buyouts with low transition risk.
When to use: Use this when a deal is capital-constrained and the lender is considering an unusually low equity injection.
Instead of a prohibited earnout, a seller note can be tied to customer retention or EBITDA maintenance and partially forgiven or amortized only if performance holds up. Heather frames this as a workaround for concentration issues in SBA structures.
When to use: Use this when a deal has a big customer concentration problem but the buyer still wants performance-linked downside protection.
The SaaS listing was priced at $1,025,000 on $256,000 of income, implying a 3.9x multiple.
Bill read the teaser economics for the public-safety software business.
The software company reported about $49,000 in monthly recurring revenue across 244 customers.
The listing teaser was used to show the subscription base and customer count.
Heather said many lenders view enterprise values under $1 million as too risky for acquisition loans.
She explained why the software deal sat near the lower edge of SBA bankability.
Typical SBA acquisition structure discussed was 75% senior debt, 15% seller note, and 10% equity.
Heather laid out the standard acquisition capital stack from a lender perspective.
The SBA guarantee covers 75% of the loan, leaving the bank exposed to 25% of a defaulted loan.
Heather compared how risk is split between the bank and the SBA on a $1 million loan.
Live Oak’s conventional acquisition program starts at about $1.75 million of EBITDA.
Heather contrasted SBA lending with conventional acquisition financing thresholds.
The SBA loan maximum is $5 million per personal guarantor, and Live Oak can pair that with up to $3 million of companion debt for a total of $8 million.
Heather described Live Oak’s larger-deal financing product.
For many MSPs, customer concentration above 20% is a key underwriting problem.
The panel discussed how lenders model concentration risk in recurring-revenue service businesses.
Confirm whether a SaaS listing is truly cloud-native before underwriting it as recurring software.
Why: Legacy on-prem software repackaged as SaaS often has very different economics and exit value.
Ask for customer acquisition cost and pipeline detail before getting excited about small, niche software businesses.
Why: A sticky customer base does not mean the business can grow fast enough to justify the valuation.
Keep investors below 20% economic ownership if they do not want to sign personal guarantees.
Why: Heather said SBA personal guarantee rules turn on 20% economic benefit, not just direct equity.
Use seller notes as practical recourse, not just legal theory.
Why: If the seller misrepresented the business, stopping note payments is often more effective than suing to recover cash.
Do not rely on broker funding illustrations without checking the underwriting assumptions.
Why: The teaser math can ignore replacement salary, maintenance capex, or the qualitative risk that kills the deal.
For MSP deals, back out any customer above 20% of revenue and test whether the company still covers debt.
Why: A single large client can make the loan fragile even if the headline margins look acceptable.
The panel noticed that a software company launched in 2005 still only generated roughly $577k of revenue, which made them question whether the product was truly growing or whether the market itself was tiny and slow-moving. Bill suggested that the business might be a legacy application rebranded as SaaS rather than a modern cloud platform.
Lesson: Age alone does not create value; the real question is whether the product model and market can still scale.
The second listing looked like a managed IT provider with recurring revenue, but the numbers revealed thin margins, lots of hardware handling, and a surprisingly large warehouse footprint. The hosts concluded that the teaser looked better for a strategic buyer who could strip out redundancies than for a standalone acquisition.
Lesson: In service businesses, hidden infrastructure and low margins can make a deal much weaker than the headline revenue suggests.
Heather explained that a seller note can become the buyer’s most practical remedy if diligence later uncovers misrepresentation, because the buyer can simply stop paying the note and force the seller to respond. The discussion contrasted that with the difficulty of recovering cash through litigation or escrow fights.
Lesson: In small-business acquisitions, the structure of the seller note can matter more than legal remedies on paper.