Frequently asked questions

Votare is a team-operations platform. In one workspace you can run hackathons and voting, schedule events and pick squads, run weekly MVP recognition, plan capacity, track projects and roadmaps, send and e-sign client documents, log time, and publish leadership reports — with roles, audit logs, and fraud detection built in.

Agencies, studios, and any team that builds together. It started as a hackathon voting tool and grew into a broader operations platform, so it fits both teams that want lightweight voting and recognition and teams that need planning, delivery, and client-facing documents.

Votare is in public beta. While pricing is being finalised, every team gets full access for free — no credit card required. Early teams get locked-in pricing when paid plans launch.

Voting allows one vote per person or email per hackathon, backed by per-device and IP + user-agent de-duplication, email-alias normalization (catching Gmail dot and plus tricks), and optional per-hackathon email allowlists. Anything suspicious is logged as a violation for admins to review.

Yes. Hackathons support external voting where participants verify with a one-time code sent to their email, alongside member voting for signed-in users. You can restrict eligible voters with an email allowlist.

Weekly MVP is an organization-wide, group-scoped vote that resets every Monday — one vote per person per group per week. Event MVP is per-game: only players selected for that event can vote and be voted for, and it stays open for 48 hours after the event.

Yes. For both hackathons and weekly MVP you can show tallies live or keep them hidden until you announce results or the week ends. Turnout is still visible so you know participation without revealing who's ahead.

You allocate people to projects, hackathons, tickets, or labels across date ranges with hours per day, and Votare measures utilization against your organization's business hours, holidays, and timezone — so capacity reflects reality rather than an idealized week.

Yes. Each member can subscribe to their own allocations from any calendar app using a personal iCal link, and can opt into a daily summary email and allocation-change alerts.

Editing is limited to an allocation's creator, organization admins, and anyone granted the resource-coordinator permission. Everyone else sees a read-only view. Every change is captured in an append-only history with field-level diffs.

Yes. Build proposals, SOWs, and contracts, share them by secure link with optional password and expiry, and collect verified e-signatures. Recipients confirm with an emailed one-time code, and acceptance captures a signature plus device fingerprint, IP, and user-agent, with a certificate PDF available.

Studio drafts client documents with AI from built-in templates like SOWs and proposals, applying your organization's branding (logo and accent color) and keeping a history of what was generated.

Every member has a base role (owner, admin, or member) and can belong to named groups that scope voting, events, and reports. Specific abilities — editing the planner, managing events, authoring reports, operating the time tracker, viewing MVP history — can be granted to a person or a whole group without making them an admin.

Sensitive actions (role changes, logins and failed logins, organization changes, voting violations) are recorded with actor, timestamp, IP, and user-agent. Every transactional email is logged with its provider and delivery status, and voting anomalies are captured as violations.

Only what you make public. Organizations, hackathons, and roadmaps are indexed only when their visibility is explicitly set to public; unlisted content is reachable by direct link but not crawled, and private content stays members-only.