In short

Start by looking at ready-made case management software. Configure it if your service needs its own fields, forms and reports. Build only when the work is genuinely different from what products are designed for, or when several systems need to work together in a way no product supports.

Whichever route you take, start from the work, not a feature list, and know how you would get your data out before you put it in.

A word on where we stand: Blue Door builds and operates Seren, ready-made case management software for UK charities and advice services, and we also build custom CRM and case management systems. So we're not neutral. This guide is written to help you choose well, including when neither is the right answer for you.

The three routes

Buy

Use a ready-made product largely as it comes. You get a system that already works, that other organisations use, and that the supplier keeps improving. The trade-off is that your service adapts to the product.

Configure

Use a ready-made product and shape it with its own settings: your fields, forms, case stages, permissions and reports. For most charities this is the sweet spot. It needs someone to own the configuration and write down what was set up and why.

Build

Have software designed and built around your service. It can fit exactly, connect systems that don't talk to each other, and put approval points where you need them. The trade-off is that you depend on whoever supports it, so choose a team that supports what it ships.

Side by side

QuestionBuyConfigureBuild
Fit to your serviceGood if your work matches how the product was designed.Good for most services; the product is shaped with its own settings.As close as you need, because it is designed around your work.
Time to get startedUsually the quickest.Quick, plus time to agree fields, forms and reports.Longest; best done one service or team at a time.
Changing it laterLimited to what the product allows.Usually straightforward within the product's settings.Anything is possible, but each change is development work.
Funder and trustee reportingStandard reports; check they match your funders.Reports set up around your outcomes and funders.Reports designed in from the start.
AI and automationWhatever the product offers.Whatever the product offers, plus connections around it.Designed around your jobs, with your own approval points.
Data, ownership and exitCheck export options and where data is hosted.As for buying; also record what you configured.Agree ownership, hosting and exit before you start.
Who supports itThe product supplier.The supplier, and whoever configured it.Whoever built it, so choose a team that supports what it ships.

Signs a ready-made product will do

  • Your work follows a familiar path: referral, assessment, casework, outcomes, closure.
  • Your funders ask for reports that products in your sector already produce.
  • You'd rather adapt a few habits than own a system.
  • You have no strong need to connect it to other systems.

If that sounds like you, look at case management products built for your sector, including Seren, and configure the one that fits best.

Signs a custom build may be worth it

  • Your service works in a way products don't model well, such as several services sharing records under different rules, or partner agencies working on the same case.
  • The real pain is between systems: data retyped between your CRM, finance, forms and inbox.
  • You need approval points, audit or AI help designed around specific jobs.
  • You've already tried configuring products and keep hitting the same walls.

A custom build doesn't have to mean replacing everything. Often the best answer is a ready-made product plus a small amount of custom work around it, connecting the systems you already use.

Questions to ask any supplier

Whoever you talk to, including us, ask them to show rather than tell:

  • Show one person's record from referral to closure, with notes, tasks and outcomes in one place.
  • Show how our funder and trustee reports come straight from the records.
  • Show who can see which records, and how sensitive records are restricted.
  • Explain how we get our current data in, and how we get all of it out if we leave.
  • Tell us where the data is hosted and who can access it.
  • Tell us who supports the system, how, and what happens when something goes wrong.
  • If AI is involved, tell us what it can see, where processing happens, and where a person approves.

Red flags

  • A demo that never uses your own example of a real case.
  • Vague answers about getting your data out.
  • AI features that act without a person approving, or that can't say what data they use.
  • Reporting described as "you can export to Excel" when you asked about funder reports.

How to decide

Write down the five jobs that cause your team the most pressure, the reports your funders and trustees need, and who needs to see what. Then test each option against that list, using a real case. If you'd like a second opinion, we're happy to look at it with you, and we'll tell you if a ready-made product is the better answer.

Further reading: CRM systems should fit the work, not fight it, and our step-by-step walkthroughs of referral intake and funder reporting.

Questions

Should a charity buy or build case management software?

Most charities should start by looking at ready-made case management software. Configure it if your service needs its own fields, forms and reports. Build only when the work is genuinely different, or several systems need to work together in a way no product supports.

What is the difference between configuring and building?

Configuring means shaping an existing product with its own settings: fields, forms, workflows and reports. Building means writing software for your organisation. Configuration is usually quicker and cheaper to change; a build fits more closely but you depend on whoever supports it.

Is Blue Door neutral?

No. We build and operate Seren, a ready-made case management product, and we also build custom systems. This guide is written to help you choose fairly, including when neither of ours is the right answer.

What should we ask any supplier?

Ask them to show one person's record from referral to closure, how your funder reports come straight from the records, who can see which records, how you get your data in and out, and who supports the system when something goes wrong.