What a nonprofit reporting build actually covers
Most nonprofits are not short of data. The CRM holds constituents and gifts, the ledger holds fund and grant codes, and program staff keep attendance and outcome counts in a spreadsheet or a Microsoft Form. The problem is that no single system answers the question a funder or a board asks — how much of this award is left, what did it deliver, and are the donors who paid for it still with us. The work is engineering the layer underneath: connecting those sources, agreeing the definitions, and modelling them so the numbers hold up under scrutiny. Microsoft’s own Power BI documentation (opens in new tab) describes the platform’s data, model, report and service layers, and a reporting pack that survives an audit needs all four built deliberately.
Definitions decide these projects. Whether a multi-year pledge counts in the year it was promised or the year it was paid, whether in-kind gifts sit in the same total as cash, whether a donor who gave last in month thirteen is lapsed or merely late — each choice moves the headline figure. We settle those with your finance and development leads first and encode them in DAX measures (opens in new tab) that every report page reuses, so the definition lives in one place instead of in six versions of the same spreadsheet.
Deliverables for a typical engagement: the report files and semantic model in your own tenant, tested measures for grant and restricted-fund balances, donor retention and recurring giving, program delivery and cost per participant, workspace and row-level security configuration, a refresh schedule with monitoring notes, and written documentation. Timeline is typically 2–4 weeks from kickoff, stated in your scope before you commit, with 30 days of post-delivery hypercare included.
Where the data actually lives
Nonprofit reporting is rarely a single-source problem, and the connection work is usually the honest majority of the effort. The table below shows the systems we most often join, what we take from each, and which reporting question it answers. During scoping we confirm what your systems really expose — a supported connector, an API, or a scheduled export — rather than assuming access we have not seen.
| Source system |
What we typically pull |
What it feeds |
| Blackbaud Raiser’s Edge NXT |
Constituents, gift transactions, appeals, campaigns and fund designations |
Donor retention and lapsed-donor cohorts, appeal and campaign performance |
| Salesforce Nonprofit Success Pack (NPSP) |
Contacts and households, opportunities recorded as gifts, recurring donations, general accounting units |
Donor lifecycle, recurring-giving attrition, pipeline and major-gift views |
| Dynamics 365 and Dataverse |
Constituent, award and case or delivery records held in your Microsoft tenant |
Grant lifecycle stages and program delivery against commitment |
| Accounting (Financial Edge NXT, Sage Intacct, QuickBooks) |
Fund and grant codes, budget versus actual, restricted and unrestricted balances |
Restricted-fund reporting, grant burn rate, program cost allocation |
| Program spreadsheets and Microsoft Forms |
Service counts, attendance registers and outcome measures collected in the field |
Program outcome pages and the delivery section of funder reports |
Licensing, and what we will not promise
Microsoft runs its own grant and discount programs for eligible nonprofit organizations across Microsoft 365, Azure and Dynamics 365, with eligibility assessed and registration handled by Microsoft — the current offers and conditions are published on Microsoft’s nonprofit page (opens in new tab). We are an independent consultancy, not a reseller of those grants, so we will not quote you an offer, a discount percentage or an approval outcome. What we will do during scoping is look at what your tenant already carries and size reporting licences around it, which for most organizations is a question of how many people author reports versus how many merely view them. Our guide to which Power BI licences a small organization actually needs walks through that trade-off, and what a Power BI dashboard build really costs covers the factors that move a fixed fee up or down.
Who this is for
It fits small and mid-sized nonprofits — roughly the size where one person owns both the funder report and the board deck. A development director who can see total raised but not who lapsed. A finance lead rebuilding a restricted-fund schedule by hand every quarter because the CRM and the ledger disagree. A program manager asked to evidence outcomes for a renewal with three weeks’ notice. An executive director who wants the board pack to be a link rather than a fortnight of assembly. If your data is accurate but arrives too late and too manually to influence anything, that is the gap this closes.
This page is the nonprofit-shaped version of our wider fixed-fee Power BI dashboard development service, so nothing here is a different engineering standard — only a different vocabulary, in the same way our OEE and downtime dashboards for manufacturers speak reason codes and cycle times instead of grants and cohorts. The underlying work — connect the sources, agree the measures, deploy under governance — is the same on both.
Fixed-fee project tiers
Three common shapes cover most nonprofit requests. Every fee is fixed and put in writing after your free consultation — the table shows scope and typical timeline, not prices, because an honest price requires seeing your sources first.
| Tier |
Scope |
Typical timeline |
Fee |
| Grant and restricted-fund starter |
One or two sources: spend-to-date and remaining balance per grant, burn rate against the award period, budget versus actual by fund, and refresh configured |
About 2 weeks |
Fixed fee — scoped after your free consultation |
| Donor retention and campaign pack |
CRM joined to the ledger: retention and lapsed-donor cohorts, recurring-giving attrition, appeal and campaign performance, average gift trends, and development-team views |
2–3 weeks |
Fixed fee — scoped after your free consultation |
| Board and funder reporting rollout |
CRM, finance and program sources in one governed model: board pack pages, program outcome reporting, row-level security by program or region, and admin documentation |
3–4 weeks |
Fixed fee — scoped after your free consultation |
Whatever the tier, you own every artifact — report files, semantic model, measure definitions and workspace settings live in your Microsoft tenant from the first day.