wopie.

For nonprofits

Donor reports, grant updates and impact briefs. Ready.

The reporting that keeps funders close and the team small, pulled from your CRM, spreadsheets and inbox, written for the reader, and held for approval before it reaches a donor or board.

Free to start. No card. Live in your first channel in two minutes.

Wopie deliversDonor reportsGrant updatesImpact briefsBoard packs

The problem

What actually eats the week for nonprofits.

Three things that quietly cost the team days a month, and what Wopie does about each one.

  • Funder reporting is a second job

    Grant updates and donor reports are due on someone else's calendar, and they always land on the same two people.

    Wopie drafts each one from the numbers your team already tracks, in your voice, on time.

  • Impact is trapped in spreadsheets

    Programme data lives in exports and CRM records that no board member or funder can actually read.

    It turns them into a brief written for the person receiving it, with the numbers that support the story.

  • A small team, fixed overheads

    The monthly assembly does not shrink just because the team does.

    Wopie takes the recurring assembly so your hours go to the mission instead of the reporting.

Why nonprofits choose Wopie

Built for the way nonprofits really work.

  • Keeps funders close

    Donor and grant reporting drafted on time, in the voice your supporters expect, from the numbers your team already tracks.

  • Turns data into a brief

    Program spreadsheets and CRM records become an impact brief a board or funder can read. Not another raw export.

  • Stretches a small team

    The recurring assembly gets done for you, so your hours go to the mission instead of the monthly report.

The work it takes off your plate.

Each one shows what it costs you today, what you ask in the channel, the steps Wopie runs, and the finished work that comes back.

Quarterly donor report·Development·#development

Today: Donor reporting lands on the same two people every quarter.

@wopie build this quarter's donor report from the CRM and program sheet

How it runs

  1. 1Pulls giving, campaigns and donor records from Salesforce
  2. 2Reads programme outcomes from your Google Sheet
  3. 3Writes the quarter against the goals recorded in Notion
  4. 4Drafts it in your template and holds it for sign-off

A donor-ready report in your template

Salesforce SalesforceGoogle Sheets Google SheetsNotion Notion
Waits for approval before any donor send.
Grant update to the funder·Grants·#grants

Today: Grant updates are due on the funder's calendar, not yours.

@wopie draft the mid-grant update for this funder against our milestones

How it runs

  1. 1Reads the grant's commitments and milestones in Notion
  2. 2Pulls spend and programme numbers from your Google Sheet
  3. 3Writes the update against each stated goal
  4. 4Prepares it in Gmail and waits for approval before it reaches the funder

A written update tied to the grant's goals

Notion NotionGoogle Sheets Google SheetsGmail Gmail
Sends only after a human signs off.
Board pack·Leadership·#leadership

Today: The pack is assembled by hand the weekend before the meeting.

@wopie assemble this month's board pack from finance and program updates

How it runs

  1. 1Reconciles the period's finances in Xero
  2. 2Pulls programme and fundraising numbers from your Google Sheet
  3. 3Reads prior minutes and still-open decisions in Notion
  4. 4Assembles the pack with the decisions the board has to make flagged

A board pack, decisions flagged

Xero XeroGoogle Sheets Google SheetsNotion Notion
Posted internally for the team.
Impact brief for the newsletter·Comms·#comms

Today: The story is in the data, but nobody has time to find it.

@wopie turn last month's program numbers into an impact brief

How it runs

  1. 1Reads programme results from your Google Sheet
  2. 2Pulls context and beneficiary notes from Notion
  3. 3Finds the change worth telling and the numbers that support it
  4. 4Drafts the brief into Google Docs for comms to shape

A story-shaped brief from the data

Google Sheets Google SheetsNotion NotionGoogle Docs Google Docs
Drafts for comms to finish.

How it works

One brief. Then it owns the work.

  1. 01Delegate

    Mention @wopie in a channel or thread, the way you'd brief a colleague.

  2. 02Gather context

    It reads the thread and pulls live data from the tools you've connected.

  3. 03Produce

    It builds the finished thing: the report, the replies, the pack, the brief.

  4. 04Approve

    Anything sensitive, external or irreversible pauses for your yes.

  5. 05Deliver

    The output lands back in the thread, and again on schedule if you ask.

One brief across your stack

It reads the tools nonprofits live in.

  • Slack Slack
  • Microsoft Teams Microsoft Teams
  • Salesforce Salesforce
  • HubSpot HubSpot
  • Xero Xero
  • QuickBooks QuickBooks
  • Notion Notion
  • Google Sheets Google Sheets
  • Google Docs Google Docs
  • Gmail Gmail

See all integrations, 3,200+ in total.

Not a chatbot, a copilot, or an automation

Other AI waits for a prompt. Wopie works for your mission.

  • ✕ A chatbot answers, then you go and do the work.
    Wopie does the work and hands back the finished thing.
  • ✕ A copilot only helps inside the one tool it lives in.
    Wopie reads across every tool the job actually needs.
  • ✕ An automation breaks the moment a field moves.
    Wopie adapts, and says so when something doesn't add up.
  • ✕ Point tools need a fresh prompt every single time.
    Wopie runs on your schedule, in the channel you already use.

Keep control

Board-ready internally. Approved before it reaches a donor.

Internal packs post on their own. Donor and funder messages wait for a human, credentials stay encrypted, and your data never trains a model.

Permission rules

#sales · set by admins
Wopie wants toPost inside a channel it's invited to
Rules
checking the channel's rules…

Audit trail

  • Every decision is recorded here with who, what and when.
wopie #sales · 8:04 AM

Each one references the last conversation and the open question, not a template. 7 follow-ups written.

Paused. These send from each owner's inbox. Each owner reviews and edits their own before anything sends.

ApproveEdit

Every approval, edit and rejection is recorded with who, what and when.

  • SOC 2-ready controlsControls mapped to SOC 2 criteria; audit evidence available for review.
  • ISO 27001-aligned policiesSecurity policies written against the ISO 27001 control set.
  • GDPR-aware data handlingData minimisation, export and deletion on request, EU-aware processing.
  • DPA publishedOur data processing agreement is public at wopie.ai/legal/dpa and can be countersigned for your procurement review.
  • SSO / SAML-readySingle sign-on flows ready for identity-provider setup.
  • Audit trail availableEvery delegated request, output and approval is recorded.
  • Built on independently audited providersAWS, Vercel, Supabase, Anthropic, Slack, Microsoft and Stripe each hold their own SOC 2 and/or ISO 27001 attestations for the layers they run. Those are theirs, not ours; Wopie's own attestation is in progress.

Questions

Questions Nonprofits teams ask first.

Yes. Credentials are encrypted and access-limited, Wopie only sees what you connect, and your data is never used to train foundation models.