Technology for charities, built around the mission rather than the software

Usually not, and we would rather say so early. A great deal of what looks like a CRM problem is an integration problem — the CRM is fine, it simply cannot see the finance system. Replacing it is expensive and disruptive, and it is worth exhausting the cheaper answer first.

That depends on the work, and the honest answer is that we are not the cheapest option available. What we try to do is scope to the smallest thing that solves the actual problem, and tell you when a product or a process change would do the job instead of a build.

Automation can prepare a claim, gather the eligible transactions and flag the exceptions. It does not decide tax compliance. Review and approval stay with your team, and the rules are applied according to current HMRC guidance at the time of implementation. We do not offer advice on your compliance position.

Roles, permissions, retention and audit trails are part of the build rather than added afterwards, and we work to your data protection requirements. We do not give legal advice on compliance — that judgement stays with you and your DPO.

This is common and worth addressing before it becomes urgent. Options usually range from taking over support, to simplifying the system so it costs less to run, to moving the function into something you already own. Which applies depends on what it does and who depends on it.

No. The organisations we have worked with in this sector vary considerably in size, and the constraint is usually whether there is a real process problem worth solving rather than headcount.

Fourth, after simplifying, connecting and automating. Applied to a process that should have been simplified first, AI makes the wrong thing faster. There is a fuller argument on our AI and automation page, including where we think it does not belong.