Fixed quote after a free call

Peer-to-peer fundraising pages and donation processing, automated end to end

We build DIY fundraising tools with one-step registration: a supporter signs up for your event or challenge and their fundraising page is created automatically on JustGiving or your own platform, every donation is processed into your CRM, and fundraisers get progress nudges and thank-you prompts. Standalone donation pages run on Stripe or Donorbox and feed the same workflow. A typical build costs $1,000 to $2,500 and takes about four to five weeks.

The problem

Why fundraisers stall before they start

Supporters who sign up for a run, a challenge or a birthday fundraiser often stall at the next step: creating a fundraising page. Every extra form loses people, and pages that do get made sit outside the CRM.

Donations then arrive through several platforms, each with its own export. Staff download files, match fundraisers to supporters and retype gifts, and fundraisers rarely get the encouragement that keeps them asking.

What we build

What our peer-to-peer fundraising automation includes

One-step registration

A single sign-up form for your event or challenge that registers the supporter and starts page creation.

Automatic page creation

Fundraising pages created through the JustGiving API as unclaimed pages the supporter claims, or on your own site.

Donation page processing

Gifts on Stripe Payment Links or Donorbox pages processed into the CRM by webhook.

Fundraiser nudges

Messages at milestones, quiet spells and the event date, with your approved wording and stop rules.

Team and event totals

Running totals per fundraiser, team and event for your website and staff.

Thank-you prompts

Fundraisers reminded to thank their donors, and staff tasks for top fundraisers.

Who does what

Automation does the chasing, people make the calls.

Every step is marked: what runs on its own, what a member of staff reviews and what stays with a person who decides.
  1. 01 Automated

    Supporter signs up

    One form registers them for the event or challenge.

  2. 02 Automated

    Page created

    Their fundraising page is created and the link sent.

  3. 03 Automated

    Donations processed

    Gifts flow into the CRM linked to the fundraiser.

  4. 04 Staff review

    Staff support fundraisers

    Events staff call top and stalled fundraisers and handle questions.

  5. 05 Charity lead or trustees decide

    Campaign decisions

    Targets, incentives and event rules are set by the charity lead.

How it behaves

How fundraising pages and donations behave

What each person sees and what runs in the background, including what happens when something goes wrong.

What fundraisers see

  • One sign-up and a ready fundraising page
  • Encouraging nudges at milestones
  • Prompts to thank their donors

What staff see

  • Every fundraiser and gift in the CRM
  • Team and event totals
  • Tasks for top and stalled fundraisers

What the automation does

  • Registers supporters and creates pages
  • Processes donations by webhook
  • Sends nudges with stop rules

Edge cases and fallbacks

Supporter already has a page
Linked to their existing page instead of creating another.
Supporter never claims the page
One reminder, then a task for events staff.
Donation refunded on the platform
The CRM gift is updated and the fundraiser total adjusted.
Giving platform API unavailable
Sign-ups are saved and pages created once the API recovers, with an alert.

Architecture

One-step sign-up to processed donations at a glance.

The setup we usually start from. We adapt it to the phone system and practice software you already use.
Sign-up form Event, challenge n8n Register and create Fundraising page JustGiving or own Donation pages Stripe, Donorbox Charity CRM Fundraisers, gifts Events team Supports fundraisers Nudges Milestones
  • Input
  • Logic and services
  • Output
  • Data
  • People

How it flows

  1. 1 A supporter signs up once for your event or challenge.
  2. 2 Their fundraising page is created automatically and the link sent to them.
  3. 3 Donations from fundraising and donation pages are processed into the CRM.
  4. 4 Fundraisers get milestone nudges and staff support top and stalled fundraisers.

Project planner

How the project runs, phase by phase.

Typical durations for a first version. Your proposal lists the exact phases, dates and what you sign off at each step.

Automated donation & peer-to-peer fundraising pages project plan

Typical time to launch: about 4 weeks, then support

  1. 01

    Discovery

    2 to 3 days

    Events and challenges, giving platforms, page settings, CRM fields and wording.

  2. 02

    Design

    2 to 3 days

    Sign-up form, page template, donation processing, nudge timing and totals.

  3. 03

    Build

    About 2 weeks

    Registration, page creation, webhooks into the CRM, nudges and totals.

  4. 04

    Shadow run

    About 1 week

    A small test event or staff team runs through the full flow.

  5. 05

    Launch

    1 to 2 days

    Open sign-ups for a live event.

  6. 06

    Support

    Ongoing

    New events, page templates and nudge wording.

What it runs on

Real products only, connected through the access each vendor provides. See all integrations

n8n JustGiving API (moving to Blackbaud SKY API) Donorbox API and webhooks Stripe Payment Links and webhooks Your charity CRM API Your email or SMS platform

Cost estimate

What it costs, line by line.

Estimates to plan with. Your fixed quote follows a free call, once we have seen your systems and volumes.
  • Discovery and design

    Events, platforms, form and nudge rules.

    $200 – $400

  • Build

    Registration, page creation, webhooks and nudges.

    $500 – $1,250

  • Integrations

    Giving platforms, Stripe and CRM.

    $200 – $450

  • Testing and shadow run

    QA and a small test event.

    $50 – $250

  • Launch and training

    Live launch and events team walkthrough.

    $50 – $150

  • Total project estimate

    $1,000 – $2,500

Optional monthly care after launch is quoted with your proposal. Fixed quote after a free call. Platform fees, Donorbox's paid API add-on and Stripe processing are billed to you directly.

Monthly running costs you pay directly

Estimates from the vendors' published pricing, checked November 2026. Billed to you by each vendor, never marked up.

  • Giving platforms: Each platform's own fees; Donorbox lists its API access as a paid add-on.
  • Stripe: Stripe's own published processing fees.
  • n8n: Self-hosted Community edition, or n8n Cloud from about €20 a month (Starter), billed annually.

What pushes cost up

  • Systems without an API, or with integration access that must be requested from the vendor
  • Writing data back into your core system rather than only reading from it
  • Several locations, brands or very different processes to support
  • Custom apps, dashboards or a voice line on top of the workflows

What keeps cost down

  • One location and one clear process to start with
  • Cloud software with a documented API
  • Using tools you already pay for instead of adding new ones
  • Approved wording and sample data ready at the start
Get a fixed quote

Privacy and consent

Rules we design for, with the sources.

General information to plan with, not legal advice. Your counsel or data protection adviser confirms what applies to your practice.

UK: Gift Aid on sponsorship

Gift Aid needs a valid donor declaration and records kept by the charity, so page donations carry declaration status into the CRM.

Source: www.gov.uk

US: event benefits and receipts

Where a payment buys an event place or benefit and exceeds $75, a quid pro quo statement is required, so registration fees and donations are kept separate.

Source: www.irs.gov

UK: messages to fundraisers

Nudges to supporters follow PECR regulation 22, including the charity soft opt-in and a simple way to refuse in every message.

Source: www.legislation.gov.uk

How we deliver

Agile delivery, in 1 to 2 week sprints.

We deliver in short Agile sprints using Scrum, so you see working software every one or two weeks instead of waiting for a big reveal at the end.

Every sprint

  1. 1 Sprint planning. At the start of each sprint we agree which backlog items we will finish, each with written acceptance criteria you can check.
  2. 2 Daily stand-up. A short internal check-in on progress and blockers. You get a written update in your Slack or Teams channel, not another meeting.
  3. 3 Sprint review and demo. At the end of each sprint we demo what was built on test data or in a shadow run, and you accept it or ask for changes.
  4. 4 Retrospective. The team looks at what went well and what to change in the next sprint, and we share anything that affects you.

How scope stays under control

Product backlog
Every feature, fix and question in one prioritised list you can see at any time.
Acceptance criteria
Plain-language conditions for "done" on each item, agreed before work starts.
Change requests
New ideas go into the backlog with an estimate. Nothing changes scope or price without your written approval.
User acceptance testing (UAT)
Before launch your team tests the real workflow against the acceptance criteria and signs off.

Tools we use

Jira, ClickUp or Trello for the backlogSlack or Microsoft Teams for updatesGitHub for code and version historyLoom or a live call for demos

Project manager / Scrum master

Runs the sprints, keeps the backlog and timeline honest, and is your single point of contact.

Business analyst

Maps how the work runs today, writes the workflow specification and acceptance criteria with your team.

Automation engineer

Builds the n8n workflows, integrations, AI steps and error handling.

Backend developer

Writes custom code where a no-code step is not enough: APIs, data sync, secure storage.

Frontend / mobile developer

Builds forms, booking pages, dashboards, web apps or Android apps when the project needs them.

QA engineer

Tests every workflow against the acceptance criteria, including edge cases and failure paths.

DevOps engineer

Sets up hosting, access, backups, monitoring and alerts, and the deployment pipeline.

Who does what at each phase

Free call
Project manager, business analyst
Understand the problem, check it is worth automating and outline a rough range.
Discovery
Business analyst, automation engineer
Map the current process, systems and data, and agree success measures.
Design
Business analyst, automation engineer, backend developer
Write the workflow specification, data flows, compliance notes and backlog with acceptance criteria.
Sprints
Automation engineer, developers, QA
Build, test and demo in 1 to 2 week sprints; you accept or adjust after each demo.
UAT and launch
QA, DevOps, project manager
Your team tests and signs off, we switch on, monitor closely and train the team.
Support
Automation engineer, DevOps
Stabilisation window, then optional monthly care with monitoring and changes.

A point of contact

One person who can answer questions and approve decisions, with about an hour a week during the project.

Access

Admin or API access to the systems involved, created as separate accounts with the least access needed.

Sample data

Real but non-sensitive records (or de-identified ones) so we can design and test against reality.

Approved wording

Message templates, policies and consent wording (for SMS, your opt-in and opt-out text) reviewed by you.

Vendor agreements

Signed agreements with the software vendors that will handle personal data, such as a BAA or processor contract.

Time for testing

A few hours from the people who will use the system, for the demos and user acceptance testing.

Working system

Workflows, integrations and any apps running in your accounts, under your keys.

Documentation

Workflow specification, data-flow map, run book and exported workflow files.

Training

A walkthrough for the team and a short recorded video for new starters.

Handover

All access, credentials and code handed over; you can keep us or take it in-house.

Stabilisation window

Fixes for anything that does not meet the agreed acceptance criteria after launch.

Support options after launch

  • No plan

    You run it yourselves after the stabilisation window and contact us when you need a change.

  • Monthly care

    Monitoring, error alerts, small changes and updates each month, with an agreed response time.

  • Priority care

    Faster response times for business-critical workflows and a monthly review call.

How a project moves through our team

Free call PM and analyst Discovery Process and data Design Spec and backlog Sprints Build, test, demo Your review Accept or adjust UAT and launch Sign-off, go live Support Monitor and improve
  • Input
  • Logic and services
  • People
  • Output
  • Data

How it flows

  1. 1 A free call with the project manager and business analyst to understand the problem and whether it is worth building.
  2. 2 Discovery and design produce a written specification, data-flow map and a backlog with acceptance criteria.
  3. 3 The team builds in 1 to 2 week sprints; you review a demo at the end of each and accept or adjust.
  4. 4 Your team runs user acceptance testing, we launch, then monitor and improve under a support plan.

FAQ

Peer-to-peer fundraising questions questions, answered.

Supporters raise money from their own friends and family through a personal fundraising page, usually for an event, challenge or occasion. The charity provides the page, the cause and the encouragement.

JustGiving through its API, which is moving to Blackbaud SKY API, Donorbox through its API and webhooks, and Stripe for your own donation pages. Other platforms are confirmed per project.

Yes. JustGiving's API can create an unclaimed fundraising page that the supporter then claims with a link, so sign-up and page creation become one step.

Each gift on a Stripe or Donorbox donation page triggers a webhook that creates or updates the supporter and gift in your CRM, linked to the right campaign and fundraiser.

No. A few nudges at milestones and quiet spells, with clear stop rules and an easy way to opt out.

Sign-ups that become active pages, average raised per page, gifts processed without manual entry and fundraisers thanked.

Free 20-minute call

Want this for your charity?

Book a free 20-minute call. We will look at how the work runs today, tell you honestly whether it is worth building and give you a fixed quote if it is.

Book a free 20-minute call