No enterprise procurement. No annual contract minimums. Free for clubs and classrooms. A few dollars per poll for larger elections. A flat school-wide annual plan for schools that want unlimited use.
For small polls inside a classroom or club.
For larger elections without a school-wide plan.
For schools running multiple polls a term.
Pricing is low enough that a student council budget can cover it without going through formal procurement.
The first goal is real usage data, not revenue. The system is free at our pilot school so we can prove the idea works with 200+ real voters in a real student council election.
Document the results. Use the case study to pitch other schools in the area. Charge nominal fees to early adopters who want managed hosting.
Once 3–4 schools are using it with documented results, move to the $200–500/year annual plans. The product is strong enough. The challenge is distribution.
ElectionBuddy charges $100–500 per election. Simply Voting targets organizations at $1,000+/year. There is willingness to pay. True Anonymity is priced deliberately below that range to fit student council budgets.
| Feature | Classroom (Free) | Per Election | School-Wide |
|---|---|---|---|
| Polls per year | Unlimited | Pay per use | Unlimited |
| Voters per poll | 100 | 1,000 | Unlimited |
| All 4 question types | ✓ | ✓ | ✓ |
| "I choose not to vote" | ✓ | ✓ | ✓ |
| Three visibility settings | ✓ | ✓ | ✓ |
| One-time codes | ✓ | ✓ | ✓ |
| English & 繁體中文 | ✓ | ✓ | ✓ |
| Auto PDF/XLSX/JSON reports | — | ✓ | ✓ |
| Scheduled auto-close | — | ✓ | ✓ |
| Direct support | Community | 48-hour SLA | Direct line |
| Onboarding session | — | — | ✓ |
| Custom domain / branding | — | — | Planned |
Yes. Free forever for up to 100 voters per poll. We expect this to cover most clubs, individual classrooms, and small committees. If a poll outgrows it, you can pay $5–10 for that one election, or move to the school-wide plan.
This is one of the open gaps in the spec. Right now, onboarding is informal — we work directly with the student council advisor to set it up. A proper sign-up flow, install/setup guide, and operator training timeline are on the roadmap.
The app itself stores no identity data with votes. However, the code distribution step requires the school to handle an eligible-voter list. How that list is stored, by whom, and when it's deleted is currently undefined. This is on the roadmap as the first thing to formalize before a school IT department will sign off.
Also an open spec question. Results are stored indefinitely today, but there's no formal retention policy and no scheduled deletion. Schools that need audit trails or data retention compliance will need this answered before procurement. See the roadmap →
Honest answer: this is the biggest unsolved problem in the system. The spec lists possible mitigations (short expiry, school-network requirement, school-portal delivery) but none are committed to. Full discussion on the roadmap →
Yes — student councils, debate clubs, and similar student-run organizations get the Per Election rate without the school-wide annual commitment. Email us directly.