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:54:35 +10:00
commit 344b1701dd
505 changed files with 56231 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/launch/outreach.md
+177
View File
@@ -0,0 +1,177 @@
# Outreach pack
Everything here is written to be sent by one person who runs a linen room to another person who
runs a linen room. That is ThreadCount's only real advantage in a market full of enterprise
inventory suites, and the moment the writing sounds like a vendor it is gone.
Three rules that shaped all of it:
- **Lead with the problem, not the product.** A linen services manager does not want software. They
want to stop being asked why Willow Ward's uniform spend doubled.
- **The price is the hook, and it is not "cheap".** The software is free, a small room is hosted
free, and a hospital pays $1,290 a year for hosting — say it plainly and early, because a number
a linen room can approve itself is the single fact that gets a reply.
- **Never claim a customer you don't have.** No "trusted by", no invented logos, no fake numbers. A
first-mover asking someone to be an early site is an honest and appealing position; pretending to
be established is neither, and it collapses on the first question.
---
## 1. Cold email — to a linen services / uniform coordinator
Subject lines, in rough order of how well they tend to travel. Keep them lower-case-ish and
specific; anything that reads like a campaign gets filtered.
- `Uniform stock — something I built for my own linen room`
- `A tool for uniform issuing and stocktakes, free to run`
- `A question about how you track uniform issues`
Body:
> Hi {first name},
>
> I coordinate uniforms for a hospital linen room, and I got tired of not being able to answer two
> questions: what's actually on the shelf in each size, and which ward a garment was issued to.
>
> So I built something to do it — issuing against entitlement, barcode scanning on a phone,
> stocktakes by shelf, and a cost centre export finance will take. It's called ThreadCount and it's
> free to run yourself, free hosted for a small room, and $1,290 a year hosted for a facility our
> size. No per-user charge, no sales process; I'm not trying to build a company out of it.
>
> I'm looking for a couple of other linen rooms to use it properly and tell me where it falls over.
> If that sounds useful, the demo is a stocked room you can poke at without signing up:
> https://threadcount.tech/demo
>
> If it's not for you, no follow-up — I won't email again.
>
> {name}
**Why it's shaped like that:** it opens with a job title rather than a pitch, states the two
questions any coordinator recognises, gives the price in the third paragraph where it lands as
relief rather than a gimmick, and closes with an explicit promise not to chase. That last line
costs nothing and materially raises reply rates, because the reader stops weighing whether
answering commits them to anything.
**Do not** add a follow-up sequence to this. The site tells people there isn't one.
---
## 2. Warm intro — when someone offers to pass it on
Short enough to be forwarded without editing.
> ThreadCount is a tool for hospitals, aged care and clinics — free to run, hosted from $1,290 a year — uniform stock by size, issuing against
> entitlement with manager approvals, barcode scanning on a phone, stocktakes, and a cost centre
> export for finance. Built by a uniform coordinator for their own room, not by a vendor.
>
> Demo, no sign-up: https://threadcount.tech/demo
---
## 3. Reply templates
**"What does it cost?"**
> The software is free — run it on your own server and there is nothing to pay. Hosted on
> threadcount.tech it is free for a room under 60 staff records, and $1,290 a year for a facility
> past that, which covers the hosting, 35 days of backups and me answering email the next business
> day. No per-device or per-user charge, and every feature is in every edition. Health services
> with several sites: $4,990 a year for five, with one sign-in across them.
**"Who else uses it?"**
> Honestly — it's early, and I'd rather say that than pad a list. It runs a real linen room every
> day, which is mine. That's the trade: you'd be early enough to shape it, and I'm around to fix
> things quickly.
**"What about our data / IT security?"**
> Fair question and the right one to ask before real staff data goes in. Everything is Australian
> hosted, kept separate per facility, and only visible to the accounts you invite. There's a plain
> summary at https://threadcount.tech/security and a full privacy policy at
> https://threadcount.tech/privacy — worth sending to your information security team early rather
> than late.
**"Can we get our data out?"**
> Yes, whenever you want. Every report and register exports as CSV, the ward request queue included.
> An admin can also download the whole facility as a single backup file — catalogue, staff,
> departments, suppliers, locations, and every issue, order and count. There's nothing to cancel and
> nothing held back.
---
## 4. Fifteen-minute demo script
Do not tour the menus. Walk one morning at the counter.
1. **Set the scene (1 min).** "This is a linen room with a catalogue, a staff register and stock on
the shelf. I'll do what a coordinator does before lunch."
2. **Issue to someone (3 min).** Scan a garment, pick the staff member. Point out the ward, cost
centre and last-issued sizes already on the record, and the entitlement balance on screen. Issue
below entitlement so the credit slip appears.
3. **The exception (2 min).** Try to go over entitlement. Show that it isn't blocked — it asks for
the approval, and records who approved it. This is the moment most coordinators lean in.
4. **A size change (1 min).** Exchange a medium for a large as one movement. Note that this is the
thing that quietly wrecks per-size numbers when it's done informally.
5. **Count a shelf (3 min).** Open a stocktake on the phone, scan a few, show the expected figure
on screen, force a variance and let it ask for a reason.
6. **What finance gets (3 min).** The cost centre report, one line per ward, and the CSV. Click a
ward's code to open the issues behind its figure — that is the answer to the question the whole
call opened with. Say plainly that if their finance team needs a different layout, that's a small
change.
7. **Close (2 min).** "There's a 60-day trial with no card. The demo resets, so if you want to try
it properly, set up your own facility — the catalogue and staff register come in from CSV."
**If time is short**, cut steps 4 and 6. Never cut step 3; the approval flow is what distinguishes
this from a spreadsheet.
---
## 5. Boilerplate
Reuse these verbatim so the description is identical everywhere it appears. Consistency across
listings is worth more than clever variation.
**One line (≤ 90 chars)**
> Uniform stock management for hospitals, aged care and clinics. Free to run, hosted from $1,290 a year.
**Short (≤ 160 chars — matches the site's meta description)**
> Uniform stock management for hospitals, aged care and clinics. Track what's on the shelf, who
> took it and what it cost the ward.
**Medium (~60 words)**
> ThreadCount is uniform stock management for hospitals, aged care and clinics. It follows a garment from
> the shelf, to the person wearing it, to the supplier order that puts another one back — issuing
> against entitlement with manager approvals, barcode scanning from a phone, stocktakes by shelf,
> and cost centre reporting finance will accept. Built by a uniform coordinator for their own room.
**Long (~120 words)**
> ThreadCount is uniform stock management for hospitals, aged care and clinics. The software is free
> and the code is published; hosting is free for a small room and $1,290 a year for a facility, with
> no per-user charge and every feature in every edition.
>
> It answers the two questions a linen room can rarely answer: what is on the shelf in each size,
> and who took it. Garments are issued to a named person against their entitlement, with their
> manager's approval recorded where someone goes over. Barcodes are read by the camera on an Android phone,
> so a room with a phone in it buys no scanner hardware at all. Stocktakes are counted by shelf with
> variance reasons captured while the reason is still known. Uniform spend attributes to the ward
> that incurred it and exports as a journal finance can upload.
>
> Australian hosted, separate per facility, and yours to take away — every report and register
> exports as CSV, and the whole facility as one backup file.
**Category words for listing forms:** inventory management, healthcare, uniform management, asset
tracking, stocktake, barcode scanning, hospital operations.
**Facts that must stay accurate everywhere:** free to run yourself; hosted free under 60 staff
records, $1,290 a year per facility above it, $4,990 a year for a health service of five (prices in
`lib/plan.ts`); facilities from before plans stay free with everything; Australian hosted; web plus an Android app; no
iOS app; camera scanning works in the Android app and in Chrome or Edge, and nowhere else — an
iPhone types the code or uses a USB scanner; every report and register exports as CSV, the ward
request queue included — it was the last one without one; the whole facility exports as one backup
file; there is no sales team.