Bought auth two or three years ago and it worked. Then the invoice started tracking their success. The only reader actively shopping.
Seeding strength: STRONG. Direct verified testimony. This persona's verdicts are evidence.
Runs engineering or is the technical founder at a company with real revenue. They bought auth two or three years ago and it worked. Then they started closing bigger customers, and the invoice started tracking their success.
They have a live bill, a renewal date, and a spreadsheet somewhere comparing what leaving would cost. They are the only persona actively shopping.
They know everything about our pitch already. Per-connection SSO pricing, the migration problem, the negotiating position they do not have. They do not need the setup. They need to know whether we are real.
They do not know whether we can be trusted. We are a young vendor with no third-party compliance certification and no pen test on record. They will find that out, and they would rather find it from us.
The bill tracking their success:
"Auth0 looks great but it's just damn expensive when you start getting more users." — resthedev, HN 25534406
Paying per connection for connections nobody uses. This is the sharpest sentence in the entire corpus and it is almost exactly our product brief written as a complaint:
"We're a SaaS who need a few dozen enterprise SAML connections, but each connection only has 5-10 logins per month. Their sales team flat-out told us that our only option is the $25k/year enterprise plan plus more for each connection. It's totally bonkers." — wldlyinaccurate, HN 22314744
Pricing that starts steering the architecture:
"We started on Auth0 but left when their pricing model started to influence architecture decisions and realized how rough migrating out could be." — Schnitz, HN 25855701
Having no way out, which is the real fear underneath the other two:
"If you are vendor-locked into, say Auth0, and they increase their price 300%… What choice do you have? What negotiation position do you have? None… They know you cannot leave." — Alupis, HN 41196814
And the shape of the relief they are looking for:
"Okta / Auth0 pricing is negotiable… we used to pay per customer connection now we pay a flat fee" — youngtaff, HN 41785644
Fluent and specific. SSO, SAML, connection, per-user, MAU, lock-in, migrate out, flat fee, renewal. They say "auth" for the category and "logins" for the events. They will read an acronym without blinking.
They are the one persona for whom "SSO" in a headline is a feature, not a barrier.
pg_dump is a mechanism."Does the bill still work when I win, and can I get out if it doesn't?"
Seeded from five verified Hacker News comments plus the wider cost, lock-in and migration clusters of the 539-item corpus. Every quote above was re-fetched from a different endpoint than the search that found it, so the wording is theirs.
Known weakness: this population is loud, which is exactly why my assignment-04 headline came out aimed at them. Everyone in this corpus has already been billed. Their evidence is excellent and it is not representative. Do not let a strong verdict from this persona outvote a Q1 failure from reader 1.
Surface under test: "Land the enterprise deal. / Keep the same bill." with the login-system lede and "Get an instance". This reader ran on Kimi K3.
Full comprehension and instant care: "that's exactly my wound." The headline that failed every other reader was written for this one.
What blocked them: no price number and no exit visible on the screen. "Get an instance" appearing twice with zero price signal pattern-matched to the vendors that burned them. They would have gone straight to Pricing, and closed the tab on "contact us".
| Q1 what is it | Q2 do you care | Q3 what next | Left cold by headline |
|---|---|---|---|
| PASS | PASS | PASS | No |
What is this? "It's a login system I'd run myself, not rent from them. 'Your database, not ours' - that's the whole pitch in four words: my user table lives on my infrastructure, not locked in theirs."
Do you care? "Some. I've got a live Auth0 bill right now that goes up every time we close a bigger logo, and 'your database, not ours' is exactly the sentence that would make me stop scrolling - it's the thing Auth0 will never say to me. But 'care' and 'convinced' aren't the same thing yet."
What next? "I'd click the Enterprise toggle before I'd click 'Set up login.' I want to see whether 'work SSO' - which they're offering plainly on the Founders tab, no asterisk - turns into a gated, per-connection thing the second I click over. That's the tell."
What stops you? "No price on the screen at all. Also nothing here about getting out - no mention of exporting my own data, no offline licensing. 'Your database, not ours' is a claim. I need the mechanism, not the sentence."
That run-02 objection became the run-03 test: they were sent to the Enterprise door with the question they named as their motive.
| Door | Q1 | Q2 | Q3 | Q4 objection |
|---|---|---|---|---|
| Founders | PASS | PASS | PASS | no price, no exit, no certification |
| Enterprise | PASS | PASS | PASS | no price on the screen |
On the enterprise door:
What is this offering? "This is an annual licence for running their auth engine on my own infrastructure. One build, one licence, and apparently no metering of SSO connections."
Did you get the answer you came for? "Yes. I came to find out whether enterprise SSO quietly becomes a per-connection charge, and the page says plainly that connections are neither counted nor charged. I believe the statement as written, but I would need it reflected unambiguously in the quote and contract."
What next? "I would click 'Talk to us about on-prem' and ask for the actual annual price, contract terms, migration path, and exit mechanism."
Source: readers/02-burned-switcher.md