Micro-SaaS · Microns · Public listing screen
A $15k document SaaS: what happens when free hosting ends?
A seller reports near-zero cash costs while hosting runs on credits. The buyer’s operating profit needs its own calculation.
By Deal Preflight · Published and listing observed · Seller figures are unverified
What the public listing states
- Seller asking price
- USD 15,000
- Seller-stated MRR
- About USD 238
- Seller-stated annualized run-rate
- About USD 2,856
- Paying subscriptions stated
- 30
Source: Document-to-Markdown Platform for AI on Microns. This snapshot does not establish current availability or verify any seller claim.
Our arithmetic
63.0 months
Revenue-only payback floor
15,000 ÷ 238 = 63.0 months if every revenue dollar were available to repay the price. This excludes buyer operating costs and is not profit payback.
Simple payback excludes financing, taxes, acquisition fees, reinvestment and future changes unless explicitly included. It is not a forecast.
Three issues to investigate
01
Credits reduce cash spending, not the work or resources needed
The listing says Azure usage is funded by credits. Even if credits can move, they have a balance and terms. The investment case needs a bill at normal usage prices and an allowance for maintenance.
Ask the seller: What would the last three months of hosting, conversion processing and AI usage have cost without credits, and when do those credits expire?
02
Revenue history and recurring run-rate are different
The page gives approximately $1,065 trailing revenue alongside $2,856 annualized recurring revenue. The buyer should reconcile definitions and dates rather than treating the smaller history figure as a full recurring year.
Ask the seller: Can we bridge paid invoices, refunds, subscription changes and annual-plan renewals into a dated MRR schedule?
03
A small customer base makes retention economically material
The seller discloses roughly 13% monthly churn and a largest customer contributing 17% of MRR. These claims need matching definitions and cohorts; they do not establish what revenue survives a transfer.
Ask the seller: Which customers have renewed repeatedly, how is churn defined, and what remains if the largest customer leaves?
What would change the assessment?
- Undiscounted hosting and model-usage bills
- Subscription cohorts, refunds and renewal schedule
- Processor migration plan, code rights and a buyer-run deployment exercise
Next decision: Treat this as a possible strategic software asset whose price must be justified by the buyer’s plan. Establish post-credit costs and recurring receipts before using a profit multiple.
Limits of this teardown
We inspected the public page, not the seller’s private accounts, source records or contracts. The questions above are our analysis, not findings of misconduct. This is a public buyer-side due-diligence example, not professional diligence or investment advice. Deal Preflight sells buyer-side due-diligence reports and workspaces and may benefit if you use the analyzer.