HN Debrief

My Business Is Dying

  • AI
  • Startups
  • SaaS
  • Developer Tools

The post is a candid note from the founder of Bank Statement Converter, a web app that turns bank statement PDFs into spreadsheet files for accounting workflows. He says revenue has fallen from earlier highs, SEO no longer pulls like it used to, and AI chat tools now do enough of the job that many casual users defect to free or bundled alternatives. He also admits he ignored cancellation data and has mixed feelings about going back to salaried software work, which gave people plenty to grab onto.

If your product is a small workflow wrapper with weak distribution and no data moat, assume AI will erase both your SEO funnel and your feature advantage at the same time. Rework pricing, move toward API or agent-facing use cases, and get much clearer on which customers still need reliability, scale, privacy, or compliance badly enough to pay.

Discussion mood

Mostly sympathetic but blunt. People liked the founder's honesty, yet the dominant reaction was that this is a weak-moat utility SaaS getting hit by both AI substitution and old-fashioned product problems like shaky pricing, brittle SEO dependence, and a task that many users can solve another way.

Key insights

  1. 01

    Ignored churn data is the loudest signal

    Skipping over cancellation reasons makes the business look less like a victim of market forces and more like a company flying blind. Optional exit feedback is low-friction and one of the few direct signals from paying users at the moment they decide the product no longer earns its keep. The useful lesson here is not to badger churned customers. It is to instrument the obvious places where they tell you exactly what broke.

    Audit every churn touchpoint now and read the raw feedback before changing roadmap or pricing. If you do not have a tagged view of why paying users leave, fix that before you assume AI is the whole story.

      Attribution:
    • jbs789 #1 #2
    • AdamN #1
    • slazaro #1
  2. 02

    Subscription pricing clashes with episodic use

    For a bank-statement converter, many customers likely buy around tax season, quarter close, or migration events. That makes a monthly plan feel like dead rent, even when the absolute price is low. Several comments point to pay-per-use, annual blocks, or one-time credits as a better fit because they match how the task actually shows up in the customer's life.

    Test usage-based packages and prepaid credit bundles instead of assuming monthly recurring revenue is the natural model. If customers only feel pain a few times a year, charge on that cadence.

      Attribution:
    • einrealist #1
    • johndubchak #1
    • swat535 #1
    • ryandrake #1
  3. 03

    The product may work better as infrastructure

    A few comments landed on the same pivot from different angles. Instead of fighting chatbots, make the converter callable by them. An API, MCP integration, or agent-friendly workflow could let the service become the reliable backend for a task LLMs describe poorly but still need executed well. That reframes the company's value from "website a human visits" to "tool another system invokes when accuracy matters."

    Explore an API-first version with clear batch limits, pricing, and privacy guarantees. If end users start in Claude or ChatGPT, you still want to be the system that does the real work underneath.

      Attribution:
    • 317070 #1
    • yevgenyhong #1
    • unmole #1
    • kodoman #1
  4. 04

    SEO dependence was the real single point of failure

    The most convincing business critique was that discovery came from a narrow search intent and little else. That channel was always vulnerable to competitors, platform features, and now AI summaries that answer the query without sending traffic. A product living on one keyword cluster can look durable right until distribution moves one layer up the stack and the funnel disappears.

    Treat search as rented land and diversify acquisition before the next platform shift finishes the job. Build direct channels, partnerships, or embedded distribution that do not vanish when Google changes the page layout.

      Attribution:
    • librasteve #1
    • alexaholic #1
    • losteric #1
    • dannypostma #1
  5. 05

    AI only erased the low-end of demand

    The comments that went beyond the easy "AI kills SaaS" slogan drew a cleaner boundary. Casual users with a few pages are gone because general-purpose AI is good enough. Heavy users with hundreds of pages, ugly PDFs, compliance needs, or a need for predictable output still have a real problem. That means the business is not necessarily dead. It is being forced upmarket into a smaller, more demanding segment.

    Reposition around volume, consistency, and privacy rather than convenience alone. Your best surviving customers are the ones for whom a wrong parse or a leaked statement is an operational problem, not a minor annoyance.

      Attribution:
    • Swankivo #1
    • cjs_ac #1
    • dchuk #1
    • ernsheong #1
  6. 06

    Contracting works when you leave teams stronger

    The side discussion on consulting was more useful than the swagger that started it. The detailed account from a contractor who does rescue and modernization work makes a clear distinction between outcome-focused consulting and mercenary disruption. The durable model is to pair technical fixes with team repair, transfer knowledge, and make yourself unnecessary. That is why teams refer you back instead of resenting you after the invoice clears.

    If you pivot from founder mode into consulting, sell capability transfer as part of the deliverable. Referrals come from teams that learned something and can maintain the system after you leave.

      Attribution:
    • tonyarkles #1
    • bayindirh #1
    • rightbyte #1
    • IsTom #1

Against the grain

  1. 01

    AI adoption inside companies is broader than skeptics think

    The claim that serious workplaces cannot use AI anymore does not hold cleanly. Comments from people working with on-premise and regulated customers say many are already standing up local models and internal tooling rather than sitting out the shift. For enterprise software, compliance is turning into an implementation detail, not a permanent blocker.

    Do not build your strategy on the hope that enterprise restrictions will slow AI competitors for long. Assume capable buyers will have private model options and ask what advantage remains after that.

      Attribution:
    • RMPR #1
    • kevin_thibedeau #1
    • hobofan #1 #2
  2. 02

    Independent work can be better than returning to payroll

    Not everyone read the founder's fear of salaried work as inevitable. Several comments argued that the current mess in software organizations creates more room for contractors and specialists who can ship, unblock teams, and avoid corporate theater. The credible version of that path is not slash-and-burn freelancing. It is targeted work with clear ownership and a reputation for improving outcomes without leaving wreckage.

    If the product stalls, a consulting bridge may be more attractive than a full-time job search. Package a narrow service around systems you already know well and use it to buy time for a better product decision.

      Attribution:
    • bob1029 #1
    • apt-apt-apt-apt #1
    • rightbyte #1
    • tonyarkles #1

In plain english

API
Application Programming Interface, a defined way for software to expose functions or data to other software.
CSV
Comma-separated values, a simple text file format commonly used to store tabular data for spreadsheets or imports.
MCP
Model Context Protocol, a way for AI models to interact with external tools and systems.
on-premise
Software or infrastructure run inside a company's own environment instead of a public cloud service.
SaaS
Software as a Service, software delivered over the internet and typically accessed through a browser.
SEO
Search engine optimization, the practice of improving a site's visibility in search engine results.

Reference links

Product and technology references

  • Erato
    An on-premise ChatGPT and Cowork alternative mentioned as evidence that regulated customers are adopting private AI tooling.
  • Calm Technology
    Referenced in a side discussion about quiet software, notifications, and subscription fatigue.