Draft — placeholder page
This page exists so the site structure is complete and navigable. The copy is a skeleton, not finished content: it has not been written, fact-checked against the product truth inventory, or reviewed. This page isnoindex and excluded from sitemap.xml until its entry is removed from DRAFT_PAGES insrc/site/config.mjs.
Election software for community and property management companies
For a management company weighing the administrative load and cost of elections across a portfolio of associations.
Planned sections
Each of these becomes an H2 with an answer block of 40 words or fewer directly beneath it, then the proof.
- The problem management companies deal with today
- Why you cannot be the Inspector of Elections — and what that means for you
- What BallotLink does for you
- How elections roll out across a portfolio
- What it costs per election
- The objection we hear most
- Questions management companies ask
Needed before this page can be written
- This page has to handle a genuinely awkward fact head-on: the software deliberately blocks a management company from administering or billing an election for itself. Sell that as the protection it is, rather than working around it.
- Portfolio economics — cost per door, or cost per association per year — needs Brandon’s real pricing before it can be argued.
- Confirm what a management company can actually do in the product today, against bucket A. Do not infer capabilities from the appendix role table, which reconciliation §2.2 says is part aspiration.
- Link across to the election services company page, since that is the route to serving as inspector.
Meanwhile
The pages that are written are the homepage, the guide forInspectors of Elections, and the one for election services companies.