Requirements gathering
Defining a shared understanding of your requirements across your teams is a key foundation for project success.
Get clear on what you need before you choose technology
Requirements gathering captures what your technology needs to enable you to do. It is a collaborative process that builds shared understanding across teams and creates a clear statement of needs that guides partner selection and implementation.
We work iteratively with your teams to capture charity CRM requirements that are accurate, complete and usable — drawing on experience from more than 550 NFP technology projects. The insight from the process itself is often as valuable as the final requirements document.
What does requirements gathering include?
Requirements register
A complete, prioritised document covering functional, technical and data requirements. Separates essential from desirable so you can evaluate suppliers against consistent criteria, not just demos.
Current systems and integrations map
A clear picture of what exists today and what needs to change, so new systems can be configured correctly from the start.
Stakeholder sign-off
Formal agreement from key stakeholders on what you need. Protects against scope creep and gives leadership confidence the process was thorough.
Tender-ready documentation
Your requirements formatted and ready to use directly in an invitation to tender or RFP — consistent from brief through to evaluation.
Is requirements gathering right for us?
- You are planning to select a new CRM, membership management system or digital platform and want to approach that process with clarity
- Different teams have different views on what the new system should do, and you need a structured way to build shared understanding and resolve those differences
- Your board or senior leadership needs confidence that the investment decision will be well-founded
- You want tender documentation that enables partners to understand your needs and respond with accurate proposals, not generic pitches
- A previous technology project did not deliver what was expected and you want to understand why before starting again
As a fiercely independent consultancy, Hart Square does not sell software, accept commissions, or partner with vendors. Our advice is 100% objective, technology-agnostic, and client-first — built on experience from more than 550 projects with charities and membership organisations.
What you get
How does requirements gathering work?
We work iteratively with your teams throughout the process — not just at the start and end. A typical engagement runs in four stages.
Discovery
Structured workshops with all business areas — including end users, not just leadership — to build a shared understanding of what the organisation needs from a new system.
Documentation
Functional requirements captured for each area, alongside non-functional requirements covering security, performance and documentation needs. Current systems and integrations mapped.
Prioritisation
A facilitated session to distinguish must-haves from nice-to-haves, so that when no single system meets every requirement, you have a principled basis for the decision.
Sign-off and pack
A complete requirements document formatted for use in your selection process, with stakeholder sign-off secured where needed.
How does requirements gathering connect to other work?
- Business process review: if you need to map your processes before defining requirements, a process review often runs immediately before this engagement — the findings become the foundation for an accurate requirements document
- Technology selection: your requirements document is the core input to selection, shaping the longlist, the ITT and your evaluation criteria
- Partner selection: the same requirements inform how you choose an implementation partner, not just the technology
Frequently asked questions
What is involved in charity CRM requirements gathering?
Charity CRM requirements gathering is a structured process of identifying and documenting what your organisation needs from a new system before evaluating suppliers. It covers functional needs, technical requirements, data considerations and integrations, and includes input from the teams who will use the system day to day. The output is a prioritised requirements document that guides procurement and enables objective supplier evaluation.
How do you run a nonprofit CRM requirements process?
A nonprofit CRM requirements process involves facilitated workshops to capture and prioritise needs across business areas, followed by structured documentation and stakeholder sign-off. The process must include end users alongside leadership, and should produce documentation ready to use directly in a tender or RFP. The output clearly distinguishes between essential requirements and desirable features.
What are membership management software requirements?
Membership management software requirements typically cover membership record management and renewals, subscription billing and payment processing, event registration and CPD tracking, communications and member portal functionality, and integration with finance systems. Unlike CRM requirements for donor-focused organisations, membership management software requirements are primarily membership-first — focused on subscription lifecycles, automated renewals and member engagement.
Why do charities need a formal requirements process before selecting a system?
Without a clear requirements document, organisations compare systems without a consistent framework. Suppliers emphasise different features, making proposals hard to evaluate objectively. A proper requirements process makes selection faster and fairer, protects the organisation if a system fails to deliver what was agreed, and ensures the brief to potential partners is clear enough to attract accurate proposals.
How does Hart Square's requirements gathering differ from doing it in-house?
We bring an independent perspective that is harder to maintain internally, particularly on prioritisation. We also bring direct knowledge of what suppliers in the sector can and cannot realistically deliver, and the requirements that are commonly missed in NFP technology projects — built across more than 550 projects with charities and membership organisations.
