Bento's Single-File Show HN Launch Reveals a Service Business: Build Zero-Install, No-Login Internal Tools for Teams Drowning in SaaS

Bento hit the Hacker News front page with 567 points and 136 comments for a tool that sounds almost too plain to be a business: a PowerPoint deck that lives entirely in one HTML file.

But the launch post is where the actual business idea is hiding.

Its creator, starfallg, didn't open with a feature list. They opened with a diagnosis: "our team has been building more and more slidedecks using web frontend technologies... but a common complaint is to make even small edits we need to edit the code either manually."

That sentence describes a workaround, not a want. And workarounds are exactly what a service business should be sold against.

The gap this creates

Most companies sit between two bad options for internal tools: heavyweight SaaS with logins, cloud accounts, and procurement reviews, or a pile of hand-rolled scripts and HTML files that only the person who wrote them can safely edit.

Bento's actual feature set is a map of what that middle ground looks like in practice: a "560KB default package," fully offline operation, no install, no cloud login, live collaborative editing over an encrypted relay running on Cloudflare Durable Objects, and an MIT license.

None of those are exotic technically. What's valuable is that someone packaged all of them into one answer to a problem teams are already living with.

Money play

1. Sell custom single-file HTML tools — decks, calculators, intake forms, small internal dashboards — to teams that are already hand-editing frontend code because nothing else fits their constraints.

2. Make "no install, no cloud login, works offline" the headline of the pitch, not a bullet point buried under a feature list — it is the answer to the IT and security objection before anyone has to raise it.

3. Turn security auditing into a paid line item: the HN thread itself caught Bento's own default build shipping an unexplained "cloudflareinsights.com beacon," which the developer had to go investigate live. That is a reminder — and a sellable service — that "offline and private" claims need to be verified in the actual shipped build, not just claimed in the README.

4. Charge more for the collaboration tier: Bento's live co-editing runs over an encrypted relay on Cloudflare Durable Objects, which is a specific, replicable technical pattern for turning a static single-file tool into a "the team edits it together" product.

5. Give away a base version — MIT-licensed or source-available, the way Bento did — to generate inbound trust, then charge for the custom build, the integration work, or hosting the collaboration relay for teams that don't want to run their own infrastructure.

Bottom line

Bento's pitch worked because it named the workaround before it named the product. Teams that are already stitching together custom HTML tools by hand are a ready-made customer list for anyone willing to build the single-file, zero-install version properly — audited for the telemetry a fast-shipped default build can accidentally include, and priced with a collaboration tier as the upsell.

Source: https://bento.page/slides/