ContactBook a call

Industries/ Non-profits

Give your team its time back for the work that matters.

We build websites, member portals, funder reporting and volunteer tools for charities, membership organisations, foundations and grant-funded bodies. Everything is sized to what a small team can run and afford, with donor data and accessibility treated as seriously as you treat them.

Staff and volunteers, some wearing lanyards and aprons, working on laptops and paperwork around a long table lined with potted plants in a sunlit room.

Overview

Non-profits, today

Most charities and membership organisations run on more software than anyone planned: a donation platform, a CRM someone set up years ago, an email tool, an accounts package, a volunteer rota in a shared spreadsheet and a website a supporter built as a favour. Each was a sensible choice at the time. Together they mean staff retype the same details into several places, a funder's question takes days to answer, and nobody is quite sure where every supporter's personal data lives. Meanwhile income is harder to win, funders ask for more evidence and teams are stretched thin.

Software fits in the gaps between those systems, and only rarely as a replacement for all of them. Often the most useful work is connecting what you already pay for, so a gift, a tax-relief declaration such as Gift Aid or an unsubscribe recorded once reaches everywhere it needs to. Next come the jobs that swallow days every quarter: funder returns, renewal reminders, thank-you letters and rota chasing. A member portal or a volunteer app earns its place when the alternative is a staff member answering the same email over and over.

Good looks like a small team that trusts its own numbers. Every supporter has one record, consent is stored with the date and wording they agreed to, and a funder return is produced from the same definitions every time. The website follows accessibility guidance because your beneficiaries include people who rely on it, and volunteers can use the tools on their own phones without a training session. Trustees can see what the systems cost, who has access, and what would happen if the one person who understands them moved on.

The pressures

What you are up against

What charity managers and operations leads tell us, usually within the first few minutes of a call.

  1. 01

    Every funder wants something different

    Each grant comes with its own reporting form, its own periods and its own definitions. We pull figures from case notes, the fundraising database and volunteer spreadsheets, then rebuild the return by hand every quarter. A mistake could cost us a funding relationship, and it always lands on the same overstretched person.

  2. 02

    Unsure what data we hold

    Supporter details sit in the CRM, the email tool, old spreadsheets and the website a volunteer built. We know data protection rules apply to us, but nobody can say with confidence who has access, what consent each person gave or how long we keep any of it.

  3. 03

    There is no IT team

    We are a small staff team with plenty of goodwill and very little technical help. Every bit of money spent on systems is money not spent on the people we serve, so we need tools that are cheap to run, simple to maintain and not dependent on one expert.

  4. 04

    Volunteers will not use clunky tools

    Our volunteers give their time freely and have no patience for logins that fail or forms that only work on a desktop. If a tool is awkward they go back to texting the coordinator, and the records we need for safeguarding and reporting never get filled in.

What we build

Software for non-profits

The projects charities and membership bodies most often bring to us, each sized for a small team to run.

What changes

From how it runs now to how it could

How some familiar pieces of charity work change once the systems are connected and doing their share.

TodayWith the right software
Funder returns are rebuilt by hand each quarter from three systems and a spreadsheet.Each funder's return is generated from one agreed set of definitions, ready to check and send.
A gift arrives online, then someone retypes the donor's details into the CRM and accounts.Gifts, declarations and consent flow into the CRM and accounts automatically, recorded once and correctly.
Members email the office to change an address, and someone updates the record by hand.Members update their own details, renew and download receipts in a portal at any hour.
Volunteer shifts are arranged by group text and a spreadsheet only the coordinator understands.Volunteers pick shifts and check in on their phones, and the coordinator sees gaps at a glance.
Nobody can say who has access to supporter data or what consent each person gave.Access is reviewed, consent is stored with its date and wording, and old records are removed on schedule.

In practice

What it looks like on the ground

Two situations we see often in charities and membership organisations: funder returns rebuilt by hand, and a donations site nobody quite owns any more.

01 · Charities & grant-funded organisations

Funder returns rebuilt from scratch every quarter

The problem
Each funder wants different figures over different periods in a different format, drawn from a case management system, a fundraising database and volunteer spreadsheets. It is assembled by hand, and a mistake risks a funding relationship.
What we build
One agreed set of definitions feeding per-funder report templates, generated on each funder's own reporting cycle, with the personal data aggregated at source so returns contain only what they are meant to contain.
What changes
Returns produced in minutes rather than days, consistent between funders, and defensible under audit because every figure traces back to its source records.
More on automated reporting
Charities & membership organisations

02 · Charities & membership organisations

The donations site a volunteer built

The problem
Donations, membership renewals and the mailing list all run through a site built years ago by a supporter who has since moved on. It holds personal data, the payment integration is on an old API version the provider keeps emailing about, and nobody knows who controls the domain.
What we build
Ownership traced and recovered first, including the domain and the payment account. Then a data-protection review of what personal information is held and who can reach it, the payment integration brought to a current supported version, dormant accounts removed, and a modest care plan sized to what a charity can genuinely sustain.
What changes
Income keeps flowing without a nervous migration, the trustees have a defensible answer on data handling, and the organisation is no longer one forgotten renewal away from losing its own domain.
More on software we didn't build

Handled with care

The details that matter here

Charities hold other people's trust as well as their data. These are the things we treat with particular care.

  • Donor and beneficiary data

    Supporter and beneficiary records are often the most sensitive thing a charity holds. We keep personal data in as few places as possible, limit access to the people who need it, aggregate it before it reaches funders, and build with GDPR and your local data protection rules in mind. Your policies and people are what make you compliant, not software.

  • Gift Aid and consent records

    Where tax relief on donations applies, such as Gift Aid in the UK, the declaration, its date and the donor's details need to be captured properly and kept. We build forms and records with that in mind, store marketing consent with the exact wording agreed, and treat fundraising regulator guidance as context for the design.

  • Accessible, volunteer-friendly tools

    Your beneficiaries, members and volunteers include people using screen readers, larger text, older phones and patchy connections. We design and test against WCAG guidance from the first screen, write in plain language, and check donation and sign-up journeys with a keyboard alone, because a form some supporters cannot use is a form that is losing you support.

  • Budgets you can sustain

    We start with what you already pay for and connect it before suggesting anything new, check whether the platforms you use offer non-profit plans, and size any care plan to what your organisation can genuinely keep up. If a spreadsheet or a feature in a tool you already have will do the job, we will say so.

Good first projects

Where to start

Small, contained first projects that help straight away and do not need a large budget to justify.

Guides

Worth reading first

Questions

What non-profits teams ask us

Should we just buy an off-the-shelf charity CRM?

Very often, yes. For donor records, declarations such as Gift Aid, membership and email, an established charity CRM or donation platform will do most of what you need, and it comes with its own updates and support. We would rather help you choose and configure the right one, then connect it to everything else, than build a donor database from scratch. Custom software earns its place in the gaps: a member portal with your own rules, a volunteer app that matches how you actually work, or funder reporting that draws on several systems at once.

We have no IT budget. How do charities usually pay for this?

Often through a grant. Some funders support capacity-building, digital or core costs, and a well-scoped project with a clear purpose is far easier to put into a bid than a vague wish for new systems. We can write a plain-language scope, a description of the problem it solves and a realistic picture of running costs for you to attach to an application. We cannot promise any funder will say yes, and we would always suggest starting with one small project that proves its worth before asking for more.

Our website was built by a volunteer who has moved on. Can you take it over?

Yes, and it is a common situation. We start by tracing who controls the domain, hosting, payment account and any supporter data, because losing one of those does far more damage than an old design. Then we bring the risky parts up to date, document how everything works and recommend whether to keep, improve or replace the site. Plenty of volunteer-built sites are basically sound and simply need someone to look after them properly.

How do you handle our supporters' personal data?

Carefully and sparingly. We collect only what a feature needs, keep it in as few systems as possible, restrict access by role, and remove our own access when a project ends if you ask us to. Personal data is aggregated before it goes into funder reports, and consent is stored with the date and wording people agreed to. We build with GDPR, local data protection law and fundraising regulator guidance in mind, but it is your policies and staff that make your organisation compliant, not any piece of software.

What happens when the grant that paid for it ends?

We plan for that from the first conversation. We favour hosting and services with modest, predictable running costs, avoid building anything that needs a developer for routine changes, and write documentation your staff can follow. Before launch we show you what the system will cost to keep running each year and what a sensible care plan would cover. If ongoing support is not affordable, we make sure the system can be left safely in your hands, with clear notes on what to update and when.

Ready to spend less time on spreadsheets?

Book a free first call and tell us where the admin is piling up. We reply within 48 hours, and we will tell you honestly if a tool you already pay for can do the job.