Is your charity leaving Gift Aid unclaimed? Five gaps to check

Around £560 million in Gift Aid is still estimated to go unclaimed each year. Here are five operational gaps worth checking.

By AJ, Technology Partner · Published 29 September 2026 · 5 min read

Gift Aid Awareness Day 2026 is on Thursday 1 October, and CFG’s #TickTheBox campaign encourages donors to add Gift Aid when they give. That matters. But charities also need to make sure the Gift Aid they are already entitled to claim does not disappear between the donation and the records used to submit it.

What the numbers say

A long-standing HMRC-commissioned estimate, commonly rounded and still cited by CFG, puts unclaimed Gift Aid at around £560 million a year. CFG’s 2024 survey of 100 charity leaders found that 20% described the claiming process as difficult or very difficult.

That does not mean £560 million is sitting in one obvious pot waiting to be recovered. It does show why Gift Aid is an operational process, not only a fundraising tick box.

Five places Gift Aid slips through the gaps

These are practical failure modes worth checking first. They are not measured shares of the £560 million estimate.

1. The declaration never meets the donation

A valid Gift Aid declaration gives the charity permission to claim, but you still need records showing which donations it covers. Paper forms, telephone declarations, event records and online gifts easily end up in different places. If the declaration and the donation never meet in your working data, the claim can be missed.

2. Online giving does not reconcile cleanly

Different platforms pass different information into your systems. The practical control is reconciliation: know what the platform has already handled, what data has been passed to you and what remains for your own claim. Without that, eligible donations can be missed and duplicate claiming becomes a risk.

3. Small cash and contactless giving is overlooked

The Gift Aid Small Donations Scheme can provide a top-up on eligible cash and contactless donations of £30 or less, without an individual declaration. Under the standard rules, up to £8,000 of qualifying small donations can generate up to £2,000 of top-up in a tax year, subject to eligibility and matching rules.

4. The backlog never reaches the top of the list

Gift Aid can generally be claimed within four years of the end of the financial period in which the donation was received. That gives charities time to recover missed claims, but it also lets a backlog sit untouched until the deadline turns urgent.

5. The data is not trusted enough to claim

Missing addresses, inconsistent supporter records, unclear declarations and donations coded in different ways all create friction. HMRC requires specific declaration information and charities need records that support each claim. When the data is uncertain, caution is sensible, but the cost is missed income and repeated manual checking. The same ownership and adoption problems often appear after wider system changes, which is why CRM implementations can fail after go-live even when the technology itself works.

A quick diagnostic

Gap	What to check	Why it matters
Declarations	Can each declaration be linked to the donations it covers?	Missing links can leave otherwise eligible donations out of a claim.
Online giving	Are platform exports reconciled against your own records?	It reduces missed donations and duplicate-claim risk.
Small donations	Have you checked whether GASDS applies?	Eligible cash and contactless giving can generate additional income.
Backlog	What sits inside the four-year claim window?	Older missed claims eventually fall outside the deadline.
Data quality	Are supporter, declaration and donation records complete enough to support the claim?	Confidence depends on evidence you can explain and reproduce.

A five-question self-check

• Can you match each Gift Aid declaration to the donations it covers?
• Do you reconcile online-giving platform data against your own records on a regular schedule?
• Have you checked whether eligible small cash and contactless donations could qualify under the Small Donations Scheme?
• When did you last review the previous four years for donations that may have been missed?
• Would your team be comfortable explaining the records behind a Gift Aid claim to HMRC?

If any answer is “not sure”, the next step is not necessarily new software. It is finding where the record or handoff breaks.

Gift Aid is also a data discipline

The clean-up that improves Gift Aid readiness improves the wider supporter picture too. Duplicates become easier to spot, consent and preferences are clearer, appeal coding is more consistent and reports depend less on one person’s spreadsheet.

Whether you work in a specialist CRM or a mix of simpler systems, the principle is the same: there should be a reliable way to connect the supporter, the donation, the declaration and the claim.

What to do next

1. Take one recent period and reconcile donation records against Gift Aid declarations and online-platform exports.
2. Separate definite gaps from records that simply need an eligibility check.
3. Check the age of any backlog against HMRC’s four-year claim window.
4. Review whether the Small Donations Scheme is relevant to your cash and contactless fundraising.
5. Document who owns the process and what evidence is kept for each claim.

How RAAJE can help

Our Gift Aid & Data Health Check is a focused review of your actual records and current process. It looks for potential missed Gift Aid, checks how declarations connect to donations, reviews supporter-data quality and gives you a prioritised action plan. See the Health Check on our charities page.

If the review finds an opportunity, we can also clean the underlying data, set up a repeatable claim-ready process and, if you want us to, manage claim submission once the appropriate HMRC authorisation is in place. Before we see any records, we agree in writing how your supporter data will be handled. HMRC pays your charity directly.

If your current setup is part of the problem, explore RAAJE CRM for contacts, organisations, opportunities, activities and follow-up, and RAAJE Email for campaigns, forms, segments and automated journeys.

Tick the box for the donor. Then tick the box on the process behind it.

Ask about a Gift Aid & Data Health Check

Frequently asked questions

How much does Gift Aid add to a donation?

For an eligible Gift Aid donation, a charity can claim 25p for every £1 donated by a qualifying UK taxpayer.

How long does a charity have to claim Gift Aid?

HMRC says claims generally need to be made within four years of the end of the financial period in which the donation was received. The relevant period depends on the charity’s legal structure.

Can cash and contactless donations qualify without a Gift Aid declaration?

Some can. The Gift Aid Small Donations Scheme covers eligible small cash and contactless donations of £30 or less without an individual declaration. It has eligibility, matching and connected-charity rules, so check HMRC’s guidance before claiming.

Can RAAJE submit a Gift Aid claim for us?

Yes, once the appropriate HMRC authorisation is in place. HMRC pays the charity directly.

When is Gift Aid Awareness Day 2026?

Thursday 1 October 2026. CFG has run the #TickTheBox campaign since 2018 to encourage donors to add Gift Aid when they give.

AJ’s perspective

Gift Aid is a good example of what happens when data and process drift apart. The opportunity can be real, but if declarations, donation records and platform exports do not connect, the team ends up reconciling information manually or holding back because it cannot trust the record.

I would start by making the flow of information and ownership dependable, then decide whether the current systems can support that reliably. Technology should make the process easier to run, not become another layer to reconcile.

From missed claims to a reliable process

Find out what your Gift Aid process could be missing.

RAAJE reviews the data, joins up the process and gives your team a clear next step.

Ask about a Health Check

Sources

1. HMRC, UK charity tax relief statistics commentary, updated 1 July 2026.
2. HMRC Research Report 482, Charitable Giving and Gift Aid, published 19 March 2018.
3. Charity Finance Group, Gift Aid Awareness Day 2026.
4. Charity Finance Group, 2024 Gift Aid survey findings.
5. HMRC, Claiming Gift Aid: how to claim.
6. HMRC, Gift Aid Small Donations Scheme.
7. HMRC, Gift Aid declarations.
8. HMRC, Charities Online agents, nominees and collection agents.

CRM versus marketing automation: what is the difference?

CRM structures commercial relationships, while marketing automation manages communications and journeys.

By AJ, Technology Partner · Published 23 July 2026 · Updated 6 August 2026 · 5 min read

In brief

The distinction matters because buying one system and expecting it to perform both jobs usually creates workarounds. Salesforce’s 2026 State of Sales research found that sales teams use an average of eight tools, 42% of sales representatives feel overwhelmed by too many tools and only 34% of teams operate on one platform. The lesson is not that every business needs one enormous platform. It is that every tool needs a defined purpose and a sensible connection to the rest of the process.

What a CRM is designed to do

A customer relationship management system answers operational questions: Who is the customer? What has happened? Who owns the next action? Which opportunities are moving? Which accounts need attention?

Its value comes from becoming the shared record for contacts, companies, opportunities, activities and decisions. That record supports consistent follow-up, forecasting and customer continuity. A CRM cannot create discipline by itself. Teams still need agreed stages, ownership rules and data standards.

What marketing automation is designed to do

Marketing automation answers a different set of questions: Who should receive this communication? What permission do we hold? Which message or journey is appropriate? What happened after delivery? What behaviour should trigger the next step?

It can support newsletters, campaigns, forms, segmentation and customer journeys, but automation is not permission. The UK Information Commissioner’s Office states that organisations must plan direct marketing around data protection and electronic-communications rules, explain how information will be used and respect objections or opt-outs.

CRM vs marketing automation

Question	CRM	Marketing automation
Primary purpose	Manage relationships and commercial activity	Manage audience communication and journeys
Typical users	Sales, account management, service and leadership	Marketing, communications and lifecycle teams
Core unit	Contact, company, opportunity and activity	Audience, segment, campaign, message and trigger
Key control	Ownership and pipeline discipline	Permission, relevance and communication rules
Common failure	Incomplete data and inconsistent use	Automating poor data or sending without appropriate permission

When does a business need both?

You are likely to need both when marketing generates more interest than a person can track manually, sales needs a reliable opportunity record, communications depend on behaviour or lifecycle stage, or customers receive contradictory messages because teams work from different lists.

The connection should be selective. Marketing does not need every internal sales note. Sales does not need every email event. Agree which fields move, in which direction, under what rules and who resolves errors.

The operating model matters more than the connector

Start with four decisions: the definition of a qualified lead, the moment ownership changes, the minimum information required at handover and the event that returns a contact to marketing nurture. Document exceptions as carefully as the normal path.

RAAJE CRM and RAAJE Email are separate current apps that can be implemented around this shared operating model. Their public value is not a hidden technology choice. It is the combination of configured systems, practical implementation and ongoing support.

A practical decision test

1. If your immediate problem is scattered contacts, unclear opportunities or missed sales actions, prioritise CRM.
2. If your immediate problem is inconsistent campaigns, manual audience segmentation or disconnected forms and journeys, prioritise marketing automation.
3. If leads move between marketing and sales but context disappears at the handover, design both systems together.
4. If the process is still undefined, map it before configuring either tool.

The objective is not to own more software. It is to make the journey easier to manage and harder to break.

Clear answers

What is the difference between CRM and marketing automation?

CRM manages relationships, ownership, opportunities and commercial activity. Marketing automation manages permission-based audience communication, segmentation and journeys.

Does a business need both systems?

Often yes, once marketing volume, sales follow-up or customer journeys become too complex for one shared list or inbox. The systems should exchange only the information required for agreed workflows.

Which system should come first?

Start with the clearest operational problem. Prioritise CRM when relationship and pipeline control are weak, or marketing automation when audience communication and journeys are the main constraint.

FAQ

Can marketing automation replace a CRM?

Usually not. Marketing automation can store contact and engagement information, but a CRM is designed to manage relationships, opportunities, ownership and commercial activity.

Can a CRM send marketing emails?

Some CRM systems include communication functions, but permission management, segmentation, journeys and campaign operations may require dedicated marketing automation.

What should trigger a handover from marketing automation to CRM?

The handover should happen when a contact reaches an agreed level of interest or qualification that requires human commercial follow-up. The CRM should receive the relevant context, owner and next action rather than only a name and email address.

Do CRM and marketing automation need to share every field?

No. Share only the information required for agreed workflows, reporting and customer continuity, with clear ownership and data controls.

AJ’s perspective

CRM and marketing automation work best when each system has a clear job.

I would rather connect two focused systems around a well-defined handover than force every process into one platform simply because the features exist.

The important design work happens before the connector: define the data owner, the handover trigger, the minimum fields that need to move and what should happen when the workflow fails.

New RAAJE series

Continue with the launch collection

• Build, Buy or Use a Managed Marketing Stack?
• Why CRM Implementations Fail After Go-Live
• The Customer Journey Handover Map
• The Cost of Slow Lead Response
• Why Marketing Systems Beat One-Off Campaigns

From insight to implementation

Design the handover before connecting the systems.

RAAJE helps businesses define the commercial process, implement RAAJE CRM and RAAJE Email, and establish the ownership required to keep both useful.

Start a conversation

Sources

1. Salesforce, State of Sales, Seventh Edition, 2026. Survey of 4,050 sales professionals across 22 countries.
2. Information Commissioner’s Office, Direct marketing guidance, updated 28 April 2026.

Build, buy or choose a managed marketing stack?

The right answer depends on capability, ownership and the real cost of making technology useful.

By AJ, Technology Partner · Published 23 July 2026 · Updated 6 August 2026 · 5 min read

The sourcing decision

The choice is becoming harder because the market is vast. Chiefmartec counted 15,505 commercial marketing-technology products in its 2026 landscape, up from 150 in 2011. More choice creates optionality, but it also increases evaluation and integration work.

When building is rational

Build when the capability is central to how the organisation differentiates, standard products cannot support an essential requirement, and the business can fund product management, security, maintenance, support and continuous improvement.

Do not confuse configuring an existing system with building a product. Genuine ownership continues after launch. The organisation inherits the backlog, technical debt, documentation, incident response and succession risk.

When buying is rational

Buy when the requirement is common, the market offers a credible product and your team can operate it. Buying can accelerate deployment, but it still requires selection, configuration, data migration, adoption, integration and governance.

Zylo’s 2025 SaaS Management Index analysed more than 40 million licences and $40 billion in managed SaaS spend. It reported an average of 152 applications among organisations with 1 to 500 employees and average SaaS spend of $4,830 per employee across its dataset. The sample reflects Zylo customers and should not be treated as a benchmark for every small business. It does show how quickly unmanaged purchasing can expand.

When a managed model is rational

Use a managed model when the capability matters but the business does not want to become its own systems integrator, administrator and first-line support team. The provider should contribute implementation, operating design, maintenance and a clear accountability model, not simply resell access.

Managed does not mean surrendering control. The customer still needs clarity on data ownership, portability, security responsibilities, service scope, configuration rights and exit arrangements.

The RAAJE build, buy or managed decision framework

Question	Build	Buy	Managed
Is this strategically differentiating?	Usually high	Usually low to medium	Low to medium
Do we have product and technical ownership?	Required	Helpful	Shared with provider
How quickly is value needed?	Slower	Potentially faster	Faster when implementation is included
Who integrates and supports it?	Internal team	Internal team or partners	Defined managed responsibility
What must remain under our control?	Architecture and roadmap	Configuration and data	Outcomes, data and service governance

Look beyond licence cost

Compare the complete operating model: discovery, selection, implementation, data preparation, integration, security review, training, administration, support, upgrades, reporting and exit. A low subscription can still create a high internal workload.

McKinsey’s survey of 250 CIOs and technology decision-makers found that more than half believed close provider relationships were necessary to achieve their digital-transformation goals, while about 60% considered a provider’s ability to engage with the business an important selection criterion. The respondents were large organisations with substantial IT budgets, so the percentages are not direct SMB benchmarks. The principle is still useful: technology value depends on business engagement, not only technical supply.

Sequence the decision

1. Define the business problem and the outcome that matters.
2. Separate differentiating requirements from standard requirements.
3. Assess the capacity to own implementation and ongoing operation.
4. Compare build, buy and managed models using the same full-life criteria.
5. Test one bounded workflow before expanding the stack.
6. Record exit, portability and governance requirements before commitment.

RAAJE technology uses a managed model for current apps because implementation and ongoing operating support are part of the proposition. RAAJE Consulting remains available where the problem requires broader Strategy, Communication, Technology or Execution work.

Clear answers

When should a business build its own technology?

Build when the capability creates genuine strategic differentiation, standard products cannot meet an essential requirement and the organisation can own product management, security, maintenance and support over time.

When is buying software the better choice?

Buy when the requirement is common, a credible product already exists and the team has the capacity to configure, govern and operate it.

What does a managed technology model add?

A managed model combines software with implementation, operating support and defined accountability, reducing the amount of integration and administration the customer must own internally.

Related: AI for SMEs: why capability matters more than replacement.

FAQ

Is building software cheaper than buying it?

Not necessarily. Building includes product management, engineering, security, maintenance, support and opportunity cost, not only initial development.

What is a managed marketing stack?

It is a set of commercial systems delivered with defined implementation, configuration, operational support and accountability rather than software access alone.

Does a managed service create vendor lock-in?

It can if data portability, configuration ownership, documentation and exit arrangements are unclear. These should be agreed before implementation.

Can a business combine build, buy and managed models?

Yes. Many organisations build differentiating capabilities, buy standard tools and use managed support where integration or operating capacity is constrained.

AJ’s perspective

Technology decisions become much clearer when ownership is treated as part of the product decision rather than something to solve later.

My starting question is not simply what a platform can do. It is who will configure it, connect it, support it and improve it after launch.

If that responsibility is unclear, a licence comparison is incomplete. A managed model can be the right answer when it closes that operating gap without taking control of the business outcome away from the customer.

New RAAJE series

Continue with the launch collection

• CRM vs Marketing Automation
• Why CRM Implementations Fail After Go-Live
• Agency Tool Sprawl Is Quietly Eating Your Margin
• Why Marketing Systems Beat One-Off Campaigns
• The Customer Journey Handover Map

From insight to implementation

Choose the ownership model before choosing the product.

RAAJE helps organisations define the requirement, assess operating capacity and implement a proportionate technology model without unnecessary complexity.

Start a conversation

Sources

1. Scott Brinker and Frans Riemersma, State of Martech 2026, 6 May 2026.
2. Zylo, 2025 SaaS Management Index, 16 January 2025.
3. McKinsey & Company, CIOs are redefining what a successful relationship with their IT providers looks like, 1 October 2019. Survey of 250 global CIOs and similar decision-makers.

Agency tool sprawl is quietly eating your margin

Fragmented tools create hidden operational cost and friction.

By AJ, Technology Partner · Published 14 July 2026 · Updated 31 July 2026 · 5 min read

Tool sprawl rarely begins with a technology strategy. It begins with a series of reasonable purchases.

A CRM is selected to manage opportunities. An email platform is added because the CRM’s campaigns are limited. Reporting moves elsewhere because client dashboards need more flexibility. A design tool, scheduler, automation platform and several specialist applications follow. Each decision solves a local problem. Together, they create an operating model that nobody deliberately designed.

What agency tool sprawl actually is

Tool sprawl is not simply having several applications. A mature agency may need specialist software. Sprawl appears when the relationship between those tools is unclear.

The warning signs are familiar: the same client record exists in several places, reporting depends on manual exports, nobody owns renewals, and staff need to switch between applications to complete one workflow. Technology that should create leverage begins consuming attention instead.

Why rational software choices create an irrational stack

Most tools enter an agency through a valid use case. The architectural problem appears later, when nobody evaluates the combined system.

Zylo’s 2026 SaaS Management Index reports an average portfolio of 305 applications across the organisations in its dataset. It also reports average annual SaaS spend of $55.7 million and notes that portfolios have broadly flattened while costs continue to rise. That matters because consolidation is no longer only about removing unused applications. Pricing models, AI add-ons and consumption charges can increase exposure even when the number of tools stays stable.

The market gives agencies more choice than they can reasonably govern

The 2026 marketing technology landscape contains 15,505 products. Although the total grew by only 0.79% year on year, 1,488 products were added and 1,367 removed.

That churn creates operational risk. A platform can change ownership, pricing or product direction. Every isolated tool creates another contract, data boundary, training requirement and migration dependency.

The real cost is in the handoffs

Subscription fees are visible. Handoffs are not.

Every time information is copied from one system to another, somebody spends time, introduces delay and creates the possibility of error. The commercial cost appears in slower onboarding, inconsistent follow-up, weaker reporting and less time available for client work.

Fragmented stack	Connected operating system
Client data exists in several tools	One governed customer record
Reports require manual assembly	Data flows into a shared reporting layer
Each application has separate ownership	Architecture and renewals are managed together
New staff learn many disconnected processes	Workflows follow one operating model
Cost is assessed subscription by subscription	Value is assessed across the complete system

How to diagnose tool sprawl

• No single person can list every application, owner and renewal date.
• Client data is entered more than once.
• Reporting depends on spreadsheets and exports.
• Teams keep applications because migration feels harder than renewal.
• Several tools provide overlapping functionality.
• The agency cannot connect software cost to client or operational value.

How to reduce sprawl without damaging capability

1. Map workflows before applications. Document how leads, clients, content and reporting move through the agency.
2. Choose systems of record. Decide where customer, campaign and operational data should live.
3. Identify overlap and handoffs. Consolidate where one platform can perform the work without weakening the process.
4. Assign ownership. Every tool needs a commercial owner, technical owner and review date.
5. Consolidate in stages. Remove complexity without disrupting client delivery.

What a connected modular system looks like

Modular does not mean disconnected. Each component should have a clear purpose, a defined relationship with the rest of the system and an owner accountable for the data and workflow it supports.

For most agencies, the operating model can be organised around four connected capabilities:

1. Customer data. One governed record for contacts, organisations, opportunities and relationship history.
2. Communication. Email and automated journeys use customer data and return engagement information to the shared record.
3. Content and creative. Collaborative workflows help teams produce consistent work without separating delivery from the wider client process.
4. Insight. Reporting connects activity with pipeline and customer outcomes rather than measuring each application in isolation.

The goal is not to force every capability into one platform. It is to ensure the tools an agency genuinely needs work as one understandable, supportable system.

How RAAJE approaches consolidation

RAAJE does not begin with a target number of applications. We begin with the operating model.

RAAJE CRM and RAAJE Email are the current commercial foundations of RAAJE technology. RAAJE Design Plus supports collaborative creative workflows where that capability is needed. RAAJE apps can be adopted individually. The objective is not bundling for its own sake. It is reducing unnecessary boundaries between customer data, communication and delivery.

Clear answers

What is agency tool sprawl?

Agency tool sprawl is the uncontrolled accumulation of separate or overlapping software across client management, communication, design, automation and reporting.

Why does tool sprawl reduce margin?

It adds subscription cost, manual handoffs, training time, duplicated data and reporting work. Those costs consume capacity that could otherwise support client delivery.

Does consolidation mean using only one platform?

No. Consolidation means reducing unnecessary duplication and designing clear connections between the specialist tools the agency genuinely needs.

FAQ

How many SaaS applications does the average organisation use?

Zylo’s 2026 SaaS Management Index reports an average portfolio size of 305 applications across its dataset.

How large is the marketing technology market?

Chiefmartec counted 15,505 marketing technology products in its May 2026 landscape, with 1,488 additions and 1,367 removals during the year.

What is the first step in reducing tool sprawl?

Map the agency’s workflows and systems of record before deciding which applications to remove or replace.

Is RAAJE technology one compulsory bundle?

No. RAAJE CRM, RAAJE Email and RAAJE Design Plus can be adopted individually according to the operational need.

AJ’s perspective

Complexity is sometimes necessary. Unmanaged complexity is not. I look for the points where data stops, people copy information, or nobody can explain why a tool still exists. Those boundaries usually reveal more about the health of the stack than the subscription total does.

New RAAJE series

Continue with the launch collection

• CRM vs Marketing Automation
• Why CRM Implementations Fail After Go-Live
• Turn Brand Guidelines Into a Working Creative System
• Build, Buy or Use a Managed Marketing Stack?
• The Customer Journey Handover Map

Reduce complexity with intent

Design the operating system before buying another tool.

RAAJE can map your current stack, identify unnecessary handoffs and define a practical consolidation path around CRM, email and collaborative design.

Start a conversation