kyle/threadcount-community
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

ThreadCount Community edition

Browse Source 
Uniform stock management for healthcare linen rooms. Licensed under the GNU AGPL v3.
This commit is contained in:
ThreadCount
2026-09-13 08:45:19 +10:00
commit 1bc2de655a
505 changed files with 56223 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/launch/plans-notice.md
+66
View File
@@ -0,0 +1,66 @@
# The notice to existing rooms
The pricing page promised: *"If that ever changes, the rooms using it will hear before the website
does."* This is how they hear. It goes to every active administrator of every facility that exists
today, sixty days before the plans switch is turned on, and the website does not change until that
day. `scripts/send-plans-notice.cjs` sends it from the production box, and refuses to send without
`--send` — run it once without to see who would get it.
The sixty days are the notice period the new Terms promise for price changes, so the first change
is held to the same standard as every later one.
**Facts the email states, which must be true on the day:**
- The facility is grandfathered: hosted free, with everything, for as long as it exists.
- Nothing needs doing, and nothing on their screens changes.
- New facilities from the go-live date start on Hosted Small (free under 60 staff records) or a
Hosted Facility trial ($1,290 a year after it). Prices from `lib/plan.ts`.
- The source will be published so anyone may run it themselves.
- Replies go to hello@threadcount.tech.
## The email
**Subject:** ThreadCount is introducing plans on {DATE}. Yours stays free.
> Hello {FIRST},
>
> A note from the person who runs ThreadCount, sixty days ahead, because the pricing page said you
> would hear before the website did.
>
> On {DATE} ThreadCount will start charging new facilities for hosting. Nothing changes for
> {FACILITY}. You signed up while it was free, and it stays free for you — every feature, every
> report, both apps, no ceiling on staff records — for as long as your facility exists. There is
> nothing to do, nothing to sign, and nothing on your screens will look different on the day.
>
> What is changing, for facilities created from {DATE}:
>
> - The software itself stays free. The code will be published so anyone can run it on their own
> server, with everything in it.
> - Hosting on threadcount.tech stays free for a room under 60 staff records.
> - A larger facility hosted on threadcount.tech will pay $1,290 a year (or $129 a month), which
> covers the servers, 35 days of backups, and a person who answers email the next business day.
> - Health services running several facilities will be able to buy them together, with one sign-in
> across sites.
>
> The Terms of Service now carry a Fees section that writes the grandfathering down, so it does not
> depend on a promise in an email: https://threadcount.tech/terms
>
> Why now: running it for other people costs money and time, and I would rather charge new rooms
> plainly than let the thing quietly stop being maintained. Charging the rooms that trusted it
> first was never on the table.
>
> If you would prefer to pay anyway, or your health service wants the multi-site arrangement, reply
> to this email. Otherwise, carry on exactly as you are.
>
> Kyle
> ThreadCount · hello@threadcount.tech
## After sending
- The script appends "Plans notice sent {today}, go-live {DATE}" to each facility's plan note, so
the operations console shows who was told and when.
- Put the go-live date in the calendar. On the day: turn the plans switch on in the operations
console (Switches › Plans). The pricing page, the home page, the FAQ, the footer and the sign-up
choice all change within a minute; nothing needs deploying.
- Update the outreach pack's date placeholders, if any remain, and the Play listings' long
description if it says "free" without qualification.