The first ten years of SaaS were a land grab. The next ten were a features arms race. We are now somewhere in year fifteen of the features arms race and the tools your team uses every day are slower, busier, and more expensive than the ones they replaced. The spreadsheet you abandoned in 2014 because it was “not built for teams” loaded in 80 milliseconds. Your replacement loads in four seconds and shows you a what’s-new modal before you can read a single ticket.
ByeBloat is a small bet that the next decade rewards the opposite instinct. We are building a growing suite of small, sharp work apps — Tickets, Live Chat, Channels, Tasks, Notes today, with more shipping after — that share an identity layer and almost nothing else. Each one does one job. Each one is allowed to stay small. The only feature we have committed to ship in every product is the keyboard shortcut for “close this and get back to work.”
The bloat compound
Every SaaS company you have ever used is on the same trajectory. They sell into a small team that loves the product. The team grows. The buyer changes from a practitioner to a procurement committee. The procurement committee asks for SSO, audit logs, custom fields, fine-grained permissions, an approval workflow, an in-app inbox, AI summaries, an integration with a tool nobody on the original team has heard of, and — crucially — they ask for all of it before they will renew.
The vendor says yes, because the alternative is losing the deal. The features ship behind feature flags. The flags become settings. The settings become an admin panel. The admin panel grows a search bar. Six years later, a new hire opens the app and the first thing they see is a sidebar with 47 icons.
Every feature you ship is a feature you have to support, document, test, and explain forever. The compound interest on yes is ruinous.
What “no” looks like in practice
Saying no is easy when you are a blog post. It is hard when there is a real customer with a real check waiting on the other side of a real Zoom call. So we wrote it down, and we point at the document when we need to.
- One product, one job. Tickets is for tickets. It does not have a chat tab. Live Chat is for chat. It does not have a help center. If you want both, buy both — they share your login.
- No settings on the homepage. Configuration belongs in a corner of the app, not in the daily workflow. If a team needs to configure something to do their job, we got the defaults wrong.
- No what’s-new modal. Ever. We will write a changelog. You can read it if you want.
- No AI features that the user did not ask for. We use AI internally for unglamorous things — spam detection, duplicate ticket merging — but we do not put a sparkle button in your face.
The economics of small
Small software is cheaper to build, cheaper to run, and easier to price honestly. We charge a flat $29.99 per user, once, for early adopters. That is the price of a paperback novel and it is the only number on the pricing page. There is no “contact sales” tier because there is nothing to negotiate.
A small product also lets us hold a higher quality bar. When the surface area is bounded, you can actually finish things. Animations can be tuned. Empty states can be hand-written. The first-run experience can be a single screen instead of a six-step checklist.
Who this is not for
ByeBloat is not the right tool for a 400-person support org with a dedicated workflow team. It is not going to replace ServiceNow. We do not have an enterprise plan and we are not going to ship one in 2026. If you need approval chains, audit exports, or a vendor-managed SOC 2 portal, you should buy something else, and we will cheer you on.
We are building this for the team of three to thirty that is one renewal cycle away from rage-quitting their entire stack. If that is you — welcome. The door says no on it, but it opens from the inside.