B2B Job Processing Software Provider, 22-Year Austin Niche Vendor

$1.1M

Revenue

$575K

SDE

Subscribe Free

Read the full deal writeup

Get Free Access

Already a member? Sign in

Full Editorial Writeup

This is a 22-year-old niche B2B software vendor based in Austin that provides job processing software under a license-plus-support model. The company runs three core product offerings and generates roughly $1.1M in revenue with about $575K in cash flow, implying strong margins in the low-to-mid 50 percent range. Roughly 95 percent of revenue is recurring, which is the single most attractive feature of this business: a sticky installed base that renews by default rather than one-off license sales.

The operation is deliberately lean. Four full-time employees run the business remotely, supported by a small leased space housing servers and equipment. Sales and marketing efforts are described as limited, meaning the revenue base is largely inertial and relationship-driven rather than the product of active demand generation.

The seller is retiring and has emphasized continuity of client relationships and the legacy of the business. That framing signals a stable, long-tenured customer book but also raises the classic question for buyers of legacy software: is the product modern and maintainable, or is this a mature installed base coasting on switching costs and habit?

Why we like it

Earnings quality is excellent for the size: 95 percent recurring revenue on $1.1M in sales with $575K in cash flow means roughly 52 percent margins and predictable, contract-like income. A book that renews by default is worth far more than transaction-based software revenue of the same headline size.
The moat here is switching costs and tenure. Twenty-two years serving a niche job processing use case with a license-and-support model creates deep embeddedness in customer workflows, and mission-critical operational software is painful and risky to rip out. Limited churn plus limited sales spend suggests the base is genuinely sticky.
This is durable, non-discretionary spend. Job processing software sits inside how clients run daily operations, so it survives downturns better than discretionary tools that get cut first when budgets tighten. Recurring B2B operational software is close to the ideal recession-resistant profile.
The operator advantage is obvious upside: sales and marketing are described as limited, meaning the current owner grew and held this base largely passively. A buyer who bolts on even modest, disciplined go-to-market motion inherits a proven product with real pricing power and untapped expansion.

How to improve it

Audit and reprice the installed base in the first 90 days. A 22-year-old software vendor with limited sales effort almost always has customers on legacy pricing that has never been indexed to inflation. Modest annual price increases of 5 to 10 percent on a 95 percent recurring base flow almost entirely to cash flow.
Instrument the revenue: build a clean churn, retention, and cohort report by product line. You cannot improve or defend what you cannot measure, and understanding which of the three products is growing, flat, or declining tells you exactly where to invest maintenance and sales dollars.
Stand up a basic, repeatable sales and marketing motion. Even a single dedicated closer plus a simple inbound funnel and referral program could reactivate dormant demand, since the current base was largely won without active selling. This is the clearest lever to break the flat revenue line.
Harden the technology and infrastructure. Migrate the on-premise servers in the leased space toward a modern cloud or hosted architecture to reduce single-point-of-failure risk and lower fixed operating overhead. This also makes the product easier to sell to newer buyers wary of legacy on-prem software.
De-risk the four-person team, especially any single developer who holds the codebase knowledge. Document the architecture, cross-train, and put retention incentives in place before close, because a lean legacy software business lives or dies by whoever maintains the code.
Expand from license-and-support into a fuller subscription and services attach. Add onboarding, integrations, or premium support tiers to lift revenue per account within the existing base, which is far cheaper than acquiring new logos.

Diligence notes

Verify the 95 percent recurring claim contractually. Pull the customer contracts, renewal terms, and billing history to confirm revenue is genuinely subscription or maintenance-based rather than lumpy re-licensing. Confirm auto-renewal language, term length, and any month-to-month exposure.
Build the true customer concentration and churn picture. A niche vendor with four staff may have meaningful revenue tied to a handful of long-tenured accounts, so quantify top-10 customer concentration and multi-year logo retention. Concentration risk is the most likely thing to compress the multiple here.
Assess the technology stack and code health closely. Determine the age of the codebase, the languages used, technical debt, on-premise versus hosted deployment, and how dependent the product is on one key developer. Legacy software cash flows are only as safe as the maintainability of the underlying product.
Normalize the $575K cash flow and reconcile it to revenue. Confirm add-backs, the retiring owner's actual role and replacement cost, and whether the lean four-person structure is sustainable or understaffed. Clarify why revenue appears flat and whether that reflects stability or slow decline.
Pin down the transition plan given the seller is retiring and emphasizes legacy and client continuity. Since no transition offer is disclosed, negotiate a defined handover period and customer introductions, because relationship-driven legacy software depends heavily on the founder's goodwill with long-term clients.

Source

Originally listed on BizBuySell. View original listing →