Building Lumrick: a unified CRM for the complexities of charity management

Running a charity involves much more than collecting donations.

Behind every fundraising campaign are donor records, financial transactions, reporting requirements, communication activities, volunteer coordination, and administrative responsibilities. Depending on the charity's size, structure, and activities, teams may also need to manage beneficiaries, cases, events, branches, and Gift Aid claims.

When these activities are spread across disconnected tools and spreadsheets, maintaining a reliable overview becomes increasingly difficult. Information gets duplicated, administrative work grows, and teams spend valuable time moving between systems instead of focusing on their charitable objectives.

This is the problem we set out to address with Lumrick, a charity CRM designed to bring essential charity management workflows together within one platform.

Currently in the testing phase, Lumrick is being developed to help charities manage their day-to-day activities through a unified digital system, with a particular focus on the operational and administrative needs of UK charities.

The problem: charities need more than a donation form

Digital fundraising has become an important part of charity operations, but accepting donations is only one component of the overall process.

A charity also needs to maintain donor relationships, track incoming contributions, organize fundraising campaigns, communicate with supporters, and produce financial and operational reports. UK charities may additionally need to manage Gift Aid declarations and claims where applicable, while meeting their wider accounting, governance, and record-keeping obligations.

The difficulty is that these responsibilities are closely connected, yet they are not always managed through the same software.

A donation recorded in one system may need to be reconciled with financial records elsewhere. Donor information collected during an event may need to be transferred into a CRM. Campaign managers may require reports that combine fundraising activity with payment information.

Each disconnected workflow introduces additional administrative effort and creates opportunities for inconsistent records.

For smaller charities, the challenge can be particularly significant. They need dependable processes, but maintaining multiple specialist subscriptions and integrating separate systems can add both financial and operational complexity.

The goal behind Lumrick was to explore a more unified approach: instead of requiring charity teams to navigate a collection of unrelated tools, provide a central platform around which their everyday workflows can be organized.

The challenge: bringing connected workflows into one platform

Building a charity CRM is not simply a matter of creating a database of donors.

The system needs to account for the relationships between people, donations, campaigns, payments, communications, and the organizations responsible for managing them. It must also support different user responsibilities and protect information belonging to separate charities.

Several challenges shaped the direction of Lumrick.

1. Connecting donor management with fundraising

Donors are central to a charity's operations, but their records become far more useful when they are connected to actual fundraising activity.

Charities need to understand which donations have been made, which campaigns they support, and how supporter information relates to ongoing engagement.

Lumrick is being developed around connected donor, donation, and campaign management workflows. The intention is to reduce the fragmentation between maintaining supporter information and managing the fundraising activities that depend on it.

2. Managing payments across different providers

Charities operate in different markets and may have different requirements for accepting donations.

Supporting multiple payment providers introduces more complexity than simply adding a checkout button. Payment methods, currencies, transaction statuses, recurring contributions, and reporting all need to be handled consistently.

Lumrick's planned payment integrations include Stripe, PayPal, and GoCardless, allowing the platform to accommodate different payment scenarios.

The architectural challenge is to make payment processing part of the wider donation management workflow rather than treat each provider as an isolated feature.

3. Supporting Gift Aid and administrative responsibilities

For eligible UK charities, Gift Aid can increase the value of qualifying donations, subject to the applicable rules and requirements.

However, the process also introduces administrative responsibilities. Charities need to maintain relevant donor declarations, identify eligible donations, and prepare and submit claims in accordance with HMRC requirements.

The opportunity for a charity management platform is to connect donation records and relevant donor information with the processes needed to prepare and manage Gift Aid claims.

Lumrick is being developed with an HMRC integration direction in mind, with the intention of helping charities manage this workflow within their broader operational environment. The charity's own eligibility, declarations, approvals, and submission responsibilities remain important parts of the process.

4. Maintaining control across teams and branches

Not every charity operates from a single location or with a small team.

Organizations may have multiple branches, departments, or users who need access to different parts of the system. A branch administrator, fundraiser, finance user, and senior manager may all require different permissions.

A shared platform must therefore balance collaboration with appropriate access controls.

Lumrick's architecture incorporates multi-tenant organization management, role-based permissions, branch-level access, and audit-oriented controls. These capabilities are intended to help ensure that users can work within their assigned responsibilities while keeping each charity's information appropriately separated.

Our approach: building around the charity's operational lifecycle

Rather than treating every feature as an independent module, Lumrick is being developed around the relationships between the activities charities perform every day.

The platform brings together several operational areas that can otherwise be scattered across separate tools.

Donor and donation management

Donor management provides the foundation for maintaining supporter information, while donation management records the contributions associated with those supporters.

Connecting these areas helps establish a more coherent view of fundraising activity and provides a basis for related reporting, communication, and Gift Aid workflows.

Campaign and event management

Fundraising campaigns and events are important ways for charities to engage supporters and collect donations.

Lumrick includes campaign and event management within its broader product scope, with the aim of connecting fundraising activities to the donor and donation records they generate.

This creates a more integrated operational model than managing campaigns, supporters, and transactions in isolation.

Payment integrations

The platform is being developed with support for multiple payment providers, including Stripe, PayPal, and GoCardless.

The intended approach is to connect payment activity with donation records so that transaction information can be managed within the wider charity workflow.

Because providers have different capabilities and payment models, each integration must account for its own requirements rather than assume that all transactions behave identically.

Communications and supporter engagement

Maintaining donor relationships requires more than recording transactions. Charities also need ways to communicate with supporters and organize outreach.

Lumrick's planned communication capabilities include email templates, bulk messaging, audience segmentation, and integration with email delivery services.

The objective is to help charities organize supporter communications alongside the records and activities those communications relate to.

Reporting and operational visibility

Charity teams need reliable information to understand fundraising activity, review operations, and prepare reports.

Lumrick's reporting direction includes filtering and exporting relevant information into formats such as Excel and CSV.

The wider objective is to make operational information easier to retrieve without requiring staff to manually assemble the same data from multiple disconnected sources.

Beneficiary and case management

Depending on their mission, charities may also need to manage beneficiaries and the cases associated with their services.

Lumrick's broader module scope includes beneficiary and case management, extending the platform beyond fundraising alone.

This is an important distinction: a charity CRM should reflect the operational needs of the organization, not assume that every charity's work begins and ends with donations.

The architectural challenge: one platform, multiple organizations

A unified charity CRM introduces an important technical requirement: bringing multiple organizations into a common application without compromising the separation of their data.

Lumrick is being designed around a multi-tenant architecture in which users, organizations, memberships, and permissions work together to determine who can access which information.

The model accounts for users who may participate in an organization, hold specific roles, and have access limited by their assigned responsibilities or branch.

This approach is important for several reasons.

• Data isolation: Each charity must be able to manage its records without exposing them to unrelated organizations.
• Role-based access: Users should receive permissions appropriate to their responsibilities rather than unrestricted access to every function.
• Branch-level control: Organizations with multiple branches need ways to manage access and workflows according to their structure.
• Accountability: Audit-oriented records and approval workflows can help organizations maintain visibility into relevant administrative actions.

These are not merely technical implementation details. They influence how safely a shared platform can support organizations with different structures, staff members, and operational requirements.

What makes this project different from a conventional CRM?

A general-purpose CRM typically focuses on managing customer relationships, sales activities, or commercial pipelines.

A charity management platform must account for a different set of relationships and responsibilities.

Its records may connect donors to donations, donations to campaigns, transactions to payment providers, and qualifying donations to Gift Aid workflows. The same platform may also need to support volunteers, beneficiaries, events, cases, branches, and organizational permissions.

The challenge is therefore not just adding charity-specific fields to a standard CRM.

It is designing a system in which these activities can work together while accommodating the compliance, governance, and administrative needs relevant to each organization.

That is the direction guiding Lumrick's development.

The intended value: less fragmentation, better operational visibility

Lumrick is being built to help charities organize their day-to-day work within a single operational environment.

By bringing related workflows together, the platform aims to reduce the need to move repeatedly between disconnected systems, make information easier to access, and provide a more consistent foundation for managing fundraising and organizational activities.

The intended benefits include:

• More connected records: Donors, donations, campaigns, and related activities can be managed within a shared platform.
• Simplified administration: Bringing relevant workflows together can reduce reliance on manual information transfer between separate tools.
• A clearer operational picture: Centralized records and reporting can help teams review their activities more efficiently.
• Better access management: Organizational roles and branch-level permissions provide a framework for controlling access.
• Room to grow: A multi-tenant foundation allows the product to support different charities and organizational structures.

These are the outcomes the platform is designed to pursue. Their actual impact will need to be evaluated through testing, user feedback, and operational evidence as the product progresses.

Where the project stands today

Lumrick is currently in the beta testing phase.

This stage is important because a platform that connects fundraising, payments, donor management, and administrative workflows needs to be evaluated as an integrated system, not just as a collection of individual screens.

Testing needs to examine how records move between modules, how payment statuses are handled, how permissions behave across organizations, and how the system responds to real-world operational scenarios.

For example, a donation workflow may involve a donor record, a campaign, a payment provider, a transaction status, and reporting requirements. Each part must work correctly on its own, but the overall workflow must also remain consistent when those parts interact.

Similarly, multi-tenant access controls need to be validated across different roles and organizations rather than assessed only through individual permission settings.

These considerations make integration testing, workflow validation, and feedback from intended users important parts of preparing Lumrick for practical use.

The bigger picture

Charities exist to serve their communities and advance their missions. Administrative processes are necessary, but fragmented systems can make those responsibilities more difficult to manage than they need to be.

Lumrick is our effort to address that challenge through a unified charity management platform.

By bringing donor relationships, fundraising, payment integrations, Gift Aid workflows, communications, reporting, and other operational modules into one system, the product is being designed to provide charities with a more connected way to manage their daily activities.

The objective is not simply to digitize individual tasks. It is to make the relationships between those tasks easier to manage.

As Lumrick progresses through testing, the focus remains on validating those workflows, strengthening the platform's foundations, and refining the experience around the practical needs of charity teams.

Building software for a complex industry requires more than implementing features. It requires understanding the workflows, responsibilities, and relationships that make the industry different.

That is the principle behind Lumrick, and it is the same approach we bring to building tailored digital products at GeekyBugs.

Looking to build a custom CRM or business management platform?

Explore our software development services and talk to GeekyBugsabout how a purpose-built digital solution could support your organization's workflows.