April 13, 2026
Thinking about selling your small SaaS company in Illinois?
Good. If your ARR is clean, churn makes sense, and the code is actually yours, buyers will pay attention fast.
The software matters, sure, the revenue matters more. Buyers like small B2B SaaS companies because recurring revenue is a beautiful thing. High gross margins. Repeat customers. Delivery that can grow without adding trucks, crews, or warehouses. That's the fun part.
But buyers aren't just buying your dashboard and a Stripe report. They're asking one big question: will this revenue still be here after you leave?
If you're in Chicagoland, DuPage County, Kane County, or anywhere else in Illinois, you can make that answer a strong YES with the right prep. Tangent Brokerage helps owners get this stuff organized before buyers start poking around, because that's when you still have time to clean up the file and tell the story right.
ARR is the start
Annual recurring revenue is usually the headline number. Everybody wants to know ARR.
But don't stop there. Buyers want to know what kind of ARR it is. Month-to-month customers who can cancel tomorrow are not the same as multi-year enterprise contracts. Setup fees aren't the same as subscriptions. Custom development isn't the same as recurring software revenue. Usage spikes, hardware, consulting, pass-through services, support fees, one-time implementation work, it all needs to be sorted.
Break revenue into clean buckets:
- Subscription revenue
- Implementation fees
- Support revenue
- Custom development
- Usage-based revenue
- Hardware or pass-through items
- Other one-time revenue
Then match those buckets back to your accounting records. If your revenue schedule says one thing and your profit and loss statement says another, that's a red flag. Even if the business is doing great! Messy numbers make buyers nervous, clean numbers make them move.
Pro tip: build the monthly revenue schedule before you go to market. Not after a buyer asks for it at 10:00 p.m. on a Thursday.
Churn needs a real story
Churn is not automatically bad. Let me say that again, because owners get too worked up about this. Churn isn't automatically bad.
Buyers will look at logo churn, revenue churn, gross retention, and net retention. If you don't track those today, start now. You need to know who left, when they left, what they paid, and why they left.
Did small low-dollar customers cancel while bigger accounts expanded? That's usually easy to explain. Did one major account downgrade and take a big chunk of revenue with it? Different story. Still fixable, but you need to own it.
Was the churn tied to a discontinued product? A bad onboarding process you already fixed? One customer segment that never really fit? Say that. Plain English wins.
What buyers really want is proof that you understand your customer base. They don't expect perfection. They do expect you to know your own numbers.
Contracts matter a lot
In a SaaS sale, customer contracts can add value fast. Or they can slow things down. Usually it's not because the contract terms are awful, it's because nobody has them organized.
Buyers will check whether contracts are assignable. They want to know if customer consent is needed in a change of control. They want to see renewal terms, cancellation rights, pricing rules, and service promises. If you've got old order forms, email approvals, and click-through terms that changed three times over the years, fine. Just inventory it.
Get a simple contract summary together with:
- Term: month-to-month, annual, multi-year, auto-renewal, or manual renewal.
- Cancellation: termination for convenience, cure periods, and notice rules.
- Pricing: fixed, seat-based, usage-based, annual increases, discounts, and legacy pricing.
- Assignment: whether it transfers in an asset sale or stock sale.
- Service terms: uptime, support response times, data handling, and service credits.
If several customers need consent, that's not the end of the world. It just goes into the deal plan. The timing matters. The wording matters. You don't want to spook customers or employees because someone got sloppy with outreach.
Do you own the code?
This one is big.
Buyers will ask who wrote the software. Founder? Employee? Contractor? Offshore developer? Freelance shop from five years ago? They will also ask whether invention assignment agreements are signed and whether the company owns the work product.
If you paid a developer but never got signed ownership language, fix that before the sale if you can. Don't wait for a buyer's attorney to find it. That's when it becomes a negotiating point, and not the fun kind.
Buyers may also look at open-source components and licensing concerns. They may ask for a code review, architecture review, security review, cloud infrastructure review, and a look at deployment practices. Sounds like a lot. It is, but it's manageable when the basics are documented.
You don't need a 40-person engineering department. Most small SaaS companies don't have that. You do need to show the product can be maintained after closing.
Helpful items include:
- System documentation
- Issue tracking
- Release notes
- Backup procedures
- Cloud vendor details
- Deployment process notes
- A current product roadmap
Simple beats fancy. Every time.
Security and compliance files should be ready
Even a small SaaS company can hold sensitive data. Buyers are going to ask about cybersecurity policies, penetration tests, SOC 2 status, HIPAA exposure, PCI responsibilities, data retention, and incident history.
Do you need every compliance badge on earth? No. But you do need to explain what data you collect, where it's stored, who can access it, and what happens if something goes wrong.
If your customers are healthcare providers, financial firms, schools, manufacturers, or government contractors, expect more questions. That's normal. Pull together privacy policies, data processing agreements, cyber insurance records, vendor agreements, and security questionnaires you've completed for customers.
A clean compliance file keeps the deal moving. It also keeps the conversation focused on growth, not guessing.
Add-backs need to be believable
SaaS buyers love revenue multiples, until they don't. In many smaller private company deals, the conversation still comes back to adjusted EBITDA and cash flow.
Founder compensation may be an add-back. One-time development projects may be. Unusual legal costs, travel, personal expenses, non-recurring contractor costs, those can count too.
But don't get cute. If the expense is needed to run the business, buyers won't give you credit for removing it. They shouldn't.
Be especially careful with development costs. If you've been starving engineering to make earnings look better, a buyer will see it. They may lower the price to account for deferred product work. Better move? Show real profit, real product investment, and a realistic cost structure going forward. That's a much stronger story.
Founder transition is part of the deal
A lot of Illinois SaaS companies are founder-led. You do the demos. You handle pricing exceptions. You know the big customers. You make product calls. You jump in when support gets ugly.
That doesn't make the company unsellable. Not even close. It just means the transition plan matters.
Buyers may ask for a transition period, consulting agreement, earnout, seller note, or employment arrangement. That's not an insult. That's how they protect continuity, and it's also how you can help the business keep winning after closing.
Before buyers ask, decide what can move off your plate. Train employees. Write playbooks. Bring in outside vendors where it makes sense. If you're the only person who can close enterprise deals or manage the product roadmap, buyers will price that risk. If your team can carry more of it, value goes up. Pretty simple.
What to prepare first
You don't need to dump 200 files on a buyer on day one. Please don't do that. But once a qualified buyer signs an NDA, you want the backup ready.
For a SaaS company, prepare:
- Monthly recurring revenue reports
- Cohort data
- Customer contract summaries
- Churn analysis
- Product documentation
- Financial statements
- Tax returns
- Employee agreements
- Contractor agreements
- Cloud vendor details
- Pipeline report
This is where Tangent Brokerage spends a lot of time with owners. Not making things look better than they are. Making the real value easier for buyers to understand.
FAQs
Can I sell my SaaS company if churn is higher than I want?
Yes, if you can explain it clearly. Buyers care about the reason, the trend, and whether stronger customers are staying or expanding.
Do buyers prefer asset sales or stock sales for SaaS companies?
It depends on contracts, tax issues, liabilities, and transfer rules. Assignment language and customer consent requirements often push that discussion.
What if contractors wrote part of my platform?
That's common. The key is having signed agreements showing the company owns the work product, including code written by freelance or offshore developers.
Do I need SOC 2 before selling?
Not always. But buyers will want to understand your security practices, customer requirements, and whether SOC 2 is becoming necessary for growth.
How long should I stay after closing?
That depends on how involved you are today. Some owners stay a few weeks, others stay under a consulting agreement or employment arrangement for several months.
Your SaaS company has a story buyers want
You built recurring revenue. You built software customers rely on. That's real. Now the job is to package it so buyers can see the strength without tripping over loose contracts, unclear churn, or missing code paperwork.
Get those pieces lined up and the sale process gets a lot more exciting. Cleaner files. Better buyer confidence. Stronger terms.
If you're planning to sell an Illinois SaaS company, contact Tangent Brokerage at 630-862-5234 or request a free valuation. Let's find out what you've built and what the right exit could look like.