Why ConvynHQ

We built the layer that's been missing from the stack.

Most volunteer programs are run on five tools that don't know about each other. ConvynHQ is what happens when you stop stitching.

Today's stack

Signups
Tickets
Hours
Reminders
P2P teams

Five logins, five exports, reconciled by hand every month

ConvynHQ

One data model. One login. One report.

Signups, hours, tickets, reminders, and peer-to-peer teams in one operations layer.

The setup most coordinators inherit

Five tools. Five logins. None of them know about each other.

01

Signups don't tie to hours

The form that captured the volunteer isn't the same place that records whether they showed up.

02

Money flows through someone else

Tickets and donations go through a platform that holds the funds, takes a fee, and brands the receipts.

03

Reports require five exports

Funder reports mean downloading CSVs from each tool, then VLOOKUP'ing the volunteer back together.

It's not a tooling problem. It's an operations-layer problem.

The work that ties signups to hours to receipts to reports has to live somewhere. Right now, that somewhere is the head of one over-stretched coordinator reconciling exports every month. We built ConvynHQ to be that layer.

What changes when you stop stitching

Five small shifts that show up everywhere in the program.

Operations layer, not a signup widget

Signups, hours, payments, comms, and reports share one data model. A report you build today still works next quarter — and a volunteer who shows up in March is still the same row come October.

Hours that survive an audit

Kiosk check-in, self-report, and admin entry all funnel into one approval queue. Elapsed math is auto-capped at 24 hours per shift, so a forgotten check-out can't quietly become a week of phantom hours.

Your money, your Stripe account

We don't hold funds and we don't take a cut on top of Stripe. Receipts go out under your org's name. When you switch, your money flow doesn't change — only the platform fees on top of it do.

Peer-to-peer that doesn't require an account

Team captains get a permanent manager URL by email — no password, no portal, no abandoned signups. The link is their bookmark for the lifetime of the team.

Real docs, no upsells

The Help Center is shipped, written, and finished — fourteen guides covering the actual work, not a wiki graveyard. Support is included on every plan, not gated behind a higher tier.

Who ConvynHQ is built for

Four kinds of orgs whose volunteer ops would be five logins without us.

Nonprofits

Running recurring volunteer programs throughout the year.

Faith communities

Running weekly service and seasonal outreach.

Civic groups

Recruiting volunteers for drives, cleanups, and events.

Advocacy orgs

Running phone banks and action campaigns.

The common thread

A program with structure and cadence.

Structure

Programs that repeat the same shape: same shifts, same roles, same capacity. Decide once, run forever.

Cadence

Weekly volunteer nights, monthly drives, an annual gala. Operations that scale with time, not effort.

What you'd otherwise need

The two common alternatives — and what ConvynHQ does instead.

Spreadsheet stack

  • Five subscriptions, five logins
  • Exports to reconcile every month
  • Volunteer record lives in three places
  • Hours don't tie to events

Point tools glued together

  • One tool for signups, another for tickets
  • Each charges its own platform fee
  • Integrations stop working when one updates
  • Reports require manual cross-referencing

ConvynHQ

  • One data model across the whole program
  • Just Stripe's standard rate, no platform fee
  • Reports overlay every subject in one place
  • Help Center, support, and migration included

What changes the day you switch

Four scenes from a normal week, after.

Reminders go out without you scheduling them.

Every signup gets a confirmation. Every event gets a day-before reminder. You don't queue the campaign — it's already running.

Team captains stop emailing you for help.

Their manager URL is in their inbox. They edit their team, message their crew, and check signups themselves. You haven't gotten a forgotten-password email since.

Your funder report runs in five seconds.

Hours are pre-approved, pre-totaled, and pre-tagged by event and role. You hit Export and the spreadsheet is ready before you've opened email.

Galas seat themselves.

Table capacity, table-number assignment, and ticket types live in one place. The day-of clipboard doesn't need to exist.

What we promise — and what we don't

Six commitments we make today. Not a roadmap, not aspirations.

Stripe Connect — funds settle directly to your bank, never to us.

No per-volunteer or per-seat fees. Flat pricing, transparent tiers.

Full data export at any time. CSV for everything, no contract clause.

Email support during business hours, included on every plan.

Row-level security on every record, audit logs on every write.

Cancel any time after your contract term — no auto-renewal traps.

Ready to stop stitching?

Spin up your org in 60 seconds. Free 30-day trial, no card. You start paying when you start charging — and even then, it's a flat fee with no surprises.