vote.direct

Exact, current vote.direct pricing for an election: flat rate by voter count (email verification included, SMS on paid elections), optional government-ID and mailed-letter add-ons, promotional pricing status, whether a subscription would beat paying per election, and the price-beat offer (vote.direct beats a lower quote from another provider for the same self-serve online election). Same constants the product bills against.

Stored HOA/condo voting-rule summary for any US state: whether electronic voting is expressly allowed, key statutes with citations, quorum, notice and proxy rules, and whether vote.direct may serve as inspector of elections there. Summaries support review; they are not legal advice.

Honest head-to-head between vote.direct and a named competitor (including the cases where the competitor is the better choice), with published prices checked on the competitor’s own pages, a vendor disclosure, and the price-beat offer where the competitor is a paid election platform. Without a competitor, returns which-platform-for-which-need guidance.

The complete third-party review record for vote.direct: every published Capterra and Trustpilot review quoted verbatim with links, including the honest caveats (small record, TrustScore explanation, which reviewers had actually run an election, and anything a reviewer received from us).

Takes no parameters.

Factual overview of vote.direct: free tier and pricing model, verification ladder, ballot-secrecy modes, the dispute-evidence pack (audit trail, results certificate, receipts), voting channels, question types, the full feature list with the no-tier-lock rule, who owns and runs the company, the founder's direct line, and where to read more.

Takes no parameters.

governance.center, the second product from this team: the Board Office for a volunteer-run HOA, condo, nonprofit board, club or congregation. Returns the annual price for a given community size from the same constants Stripe bills, what every band includes, what is priced per use, what the product deliberately does not do, and the support line. Annual price first; the monthly figure is only an explainer.

Build a complete election (ballot, schedule, verification, voter emails) for a person who does not have a vote.direct account yet, and get the link where they claim it: they open it, create an account with their email, and the election appears in their dashboard ready to review and publish. Nothing is charged and no voter is contacted until they do. The link expires in 48 hours. For a person who has an account, or will sign in, create_election_draft works in their account directly.

Elections and surveys in the connected vote.direct account, newest first: id, slug, title, kind (election or survey), status (draft, scheduled, live, closed), schedule, voters and ballots cast, and the links to hand the person.

One election or survey in the connected account, as it is saved now: the schedule in its time zone, every question with its type, seats and options (in the words create_election_draft takes), the settings, the voter list as counts, ballots cast, turnout and quorum, and links. For a DRAFT election it also reports what still blocks publishing, what is worth checking, the exact price the publish step would charge, and who pays it (free, plan, prepaid balance, or card at the finish link). Per-question results are on the election page link; this tool reports counts only, never a voter's name, email or phone number.

Whether a DRAFT election in the connected account can publish now: the checks the publish button runs (schedule, ballot, voter list, state rules, size), each blocker in the words publish would refuse with, warnings a board should hear (voting closes inside the state's notice period, no quorum on an HOA or condo, voters the emailed ballot cannot reach), the exact price and who pays it. Fixing one blocker can show the next, so ask again after each fix. Changes nothing.

The price of one election in the connected account as it stands, from the same function the payment page and the publish step charge: its voter count, the tier, what the total is made of (government ID, texts for a small roster), and who pays it now (free, plan, prepaid balance, or card). Ask again after the voter list changes. Changes nothing.

Create a DRAFT election in the connected account: the ballot, schedule, verification, secrecy, results visibility, optional quorum and state-law checks, and optionally the voter list (emails). A draft charges nothing and contacts nobody. Returns the draft's id, the draft as saved, what still blocks publishing, the exact price, and the finish link where the person reviews, pays if needed, and publishes. Create it once and change it with update_election_draft: an account can create 10 elections an hour. Ask the person for anything you do not know (closing date and time zone, seats, candidates) rather than guessing: this is a binding vote.

Change a DRAFT election in the connected account: title, description, organization name, schedule and time zone, secret ballot, results visibility, quorum, and the ballot (add, remove or change questions, or replace them all). While nobody has paid for it, its state, community type, vote type and verification can change too. Fields mean what they mean in create_election_draft. Changes go through the election editor, so anything the election page would refuse is refused with its reason and nothing is half-changed where that can be checked first. Returns one plain sentence per change, written from the saved election, and what still blocks publishing. A published election is changed by the organizer on its page.

Add eligible voters (email, optional name and unit) to a DRAFT election in the connected account, through the import the voter list page uses. Idempotent: people already on the list are skipped, a voter listed twice is added once, and rows that cannot be added are named by row number. Returns counts, never the rows, and the updated price. For a published election, voters are added by the organizer on the election page, because a larger list can change the price.

Take voters off a DRAFT election in the connected account, by email address or by unit. A voter goes when their email is named, or when every unit they hold is named, so nobody loses a unit by accident; the contact book is not touched. Returns how many were taken off and how many of those named are not on the list, never the rows, and the updated price.

Create a free, anonymous survey in the connected account and publish it (or save it as a draft with publish: false). Surveys are for feedback, not binding votes: anyone with the link can answer and respondents are not verified. For anything binding (a board election, a bylaw amendment, an assessment) use create_election_draft. Question types: single (pick one), multiple (checkboxes), yes_no, rating (1-5 by default; settings {scale: "nps"} makes a 0-10 Net Promoter Score), ranking, open_text. Returns the share link.

Publish a DRAFT election in the connected account, running every check the publish button runs (ballot, schedule, voter list, state law, price) and charging the price from the account's prepaid balance or plan. Free elections (up to 25 voters) publish at no cost. If the balance does not cover it, nothing is charged and the person pays by card, at the finish link or on a payment page from create_checkout_link. Publishing follows a card payment either way: the page the person returns to from Stripe publishes once the payment lands, or call this with after_payment: true, which waits for the payment and publishes without a second charge, never drawing on the balance as well. An election that is already published and paid for answers status already_published with its links, not a refusal. Once published it emails voters their ballots when it can send as the organizer; through an assistant connection it usually cannot, so the result says whether ballots were emailed and, if not, links the election page where the organizer sends them. Confirm with the person before calling this; it can spend their money.

A secure Stripe payment page for a DRAFT election's fee, for the person you act for to pay by card. It creates the page and charges nothing: hand the person the link. The page asks for exactly the price get_election_price reports. Publishing follows the payment either way: the election's page, where Stripe returns them, publishes it once the payment lands, and publish_election with after_payment: true publishes it from here or answers already_published. Refused when nothing is owed (free, already paid, or covered by a plan) and when the prepaid balance covers the fee, because publishing then takes it without a card.