Exodify — ambassador-led fundraising.One campaign. Many ambassadors.Attribution from link to receipt.
About the product.
Exodify grew from a real fundraising need: knowing which ambassador brought each donation, tracking their activity and managing the campaign in real time.
We built three connected products — a campaign site, an admin dashboard and the platform core — with attribution, permissions, payments, receipts and analytics.
The decisions.
A product from a campaign, not from a slide deck
We did not start from an abstract SaaS hypothesis. We started from a campaign that had to happen, and the requirements were derived from its need: attribution, roles, receipts, reports. A product born from use looks different from a product born from a sketch.
The campaign's brand, not the platform's
A campaign page does not have to look like a fundraising company's template. We separated the experience and brand layer from the payment, attribution and analytics layer — so every campaign can look like its own organization, on its own domain, and still run on the same infrastructure.
Attribution is a system, not a link
The system is designed to attribute a donation to whoever brought it — through a full hierarchy: nonprofit, campaign, admins, ambassador. The attribution rules were defined explicitly and written in a reference document, so that recognition and reward reach the right place even when two ambassadors touch the same donor.
What we built.
The system at a glance
Not a feature list — the dimensions of the architecture itself.
What the core proves
The facts come from the product's reference documents and from what was actually built.
The attribution model
PROOF 01 · IN COREThe logic that was built: First Delegate Wins - the donation is credited to the first ambassador who brought the donor — with a 30-day refresh window and a referral cookie. Above that: full multi-layer tenancy — nonprofit, campaign, admins, ambassador — and attribution climbs up the hierarchy. An additional group layer beneath the ambassador stayed on the planning table, and we say so instead of promising it.
The test run
PROOF 02 · TESTEDThe payment integration passed a full test run - every clearing step, from choosing the amount to the success screen and the receipt sent automatically. A payments infrastructure tested step by step, not a promise on paper.
Built for Israel, from the ground up
PROOF 03 · BUILT INNot localization pasted on at the end: Hebrew and English, RTL and LTR, across all three surfaces — from the campaign page to the dashboard. Receipts are sent automatically, and payment happens in the tools donors in Israel actually use.
The scope
One team, from the research to the campaign. Whoever comes in does not need a platform, plus an ad vendor, plus creative, plus a campaign manager.
- Product and experienceRole research, user journeys, an attribution model, sketches and a development plan.
- Platform developmentThree surfaces on one core: the campaign site, the dashboard and the platform core — with a redeployable environment, monitoring and role-based access control.
- Attribution and paymentsHierarchical attribution, a payment integration that passed a full test transaction, and automatic receipts.
- Campaign brand and executionexodify.io, bilingual; the creative and campaign management — moving people to act, not PPC alone.