Founders Campaign pilot

Fund the mission. Simplify the follow-through.

HopperForge proposes one focused digital pilot for Pond Hopper Army Foundation: a clear Founders Campaign landing page connected to donation intake and lightweight shirt fulfillment tracking.

Recommendation only. Nothing will be built, published, connected, purchased, or activated without PHAF approval.

HopperForge hero

What to expect

A careful pilot, not a replacement project.

Keep what works

GoDaddy, Google Workspace, PNC, and Zeffy can remain in place while the pilot proves its value.

Clear boundaries

Donations, merchandise purchases, sponsorships, and event registration remain distinct in language and records.

Human approval

PHAF reviews legal, tax, privacy, receipt, fulfillment, and vendor decisions before launch.

Highest-value pilot

One campaign page. One fulfillment view. Fewer handoffs.

The Founders Campaign landing page and fulfillment tracker is the strongest first project because it supports near-term fundraising while addressing the administrative burden created by collecting contact details, shirt sizes, eligibility, and delivery status across separate tools.

01

Public campaign experience

A mobile-first page explains PHAF’s mission, the purpose of the Founders Campaign, and the next action without changing the existing website. The primary donation action can continue to Zeffy, avoiding a second payment system during the pilot.

Charitable contribution

Use donation language and direct supporters to PHAF’s approved Zeffy campaign and receipt flow.

Founders Edition shirt

Describe any shirt as a separate fulfillment item for eligible contributors, subject to PHAF’s reviewed tax and acknowledgment language.

02 / Intake

Capture only what is needed

Name, email, contact preference, and shirt size when applicable—with consent and retention language reviewed by PHAF.

03 / Operations

Track the handoff

A simple admin view records payment verification, eligibility, size, vendor handoff, shipment, and exceptions without building a full donor CRM.

Supporter-to-shirt workflow

  1. 01

    Supporter donates

    The supporter follows the approved campaign link and completes a charitable contribution in Zeffy.

  2. 02

    PHAF verifies

    Zeffy records the transaction and sends funds through its configured payout path to PHAF’s bank account.

  3. 03

    Details are matched

    For contributions meeting PHAF’s approved threshold, staff confirms contact details and shirt size in the tracker.

  4. 04

    Vendor fulfills

    The approved vendor receives the order, ships the shirt, and the tracker is marked complete or flagged for follow-up.

Tools and payment path

Use Zeffy first. Add complexity only when justified.

MadeThis can provide the campaign interface, structured supporter intake, admin fulfillment statuses, exports, and workflow automation. Zeffy can remain the donation and donor-receipt system. Google Workspace may support notifications and operational exports; a print-on-demand or drop-shipping account is needed only after PHAF selects a vendor.

How funds reach PNC
Under the recommended pilot, donations are processed by Zeffy and paid out according to PHAF’s existing Zeffy account and bank configuration. PHAF should verify payout timing and account details directly in Zeffy.
Is Stripe required?
Not for a Zeffy-linked donation pilot. Stripe would be needed only if PHAF later chooses direct card processing for merchandise or other transactions. Its current nonprofit eligibility, rates, and per-transaction fees must be confirmed before activation.
Estimated ongoing cost
Keep the pilot lean: Zeffy’s current pricing model, MadeThis hosting, email volume, domain changes, and vendor charges must be confirmed before an exact monthly estimate is approved. No paid account should be opened without PHAF authorization.

Human review required

Resolve the policy details before launch.

  • Tax and acknowledgment: determine whether and how the shirt affects the deductible amount, fair-market-value disclosure, and donor receipts.
  • Eligibility language: approve whether contributors of at least $100 “may receive” or are guaranteed a shirt, including availability and substitution terms.
  • Privacy and consent: approve what supporter information is collected, who can access it, retention periods, and communication opt-in language.
  • Fulfillment: select the vendor and review inventory, sizing, shipping regions, address changes, returns, damaged items, and sales-tax implications.
  • Record separation: confirm bookkeeping treatment for donations, merchandise, sponsorships, event registration, processing costs, and vendor expenses with qualified nonprofit advisors.

Approval checkpoint

Approve the pilot before anything changes.

If PHAF agrees with this direction, the next step is a scoped implementation plan covering fields, Zeffy handoff, fulfillment statuses, vendor responsibilities, legal copy, and confirmed costs.