Fixed quote after a free call

Grant reporting automation that starts the report before the deadline does

We build a grant workflow that tracks applications, awards and reporting dates on one calendar, pulls activity, outcome, volunteer hours and spend data from your CRM, case records and accounting into a draft report pack shaped to each funder's template, and reminds the right people well before every due date. Programme and finance leads review every figure, and the charity lead signs off. A typical build costs $1,000 to $2,500 and takes about four to five weeks.

The problem

Why grant reports turn into last-minute scrambles

Each funder asks for something different: quarterly numbers for one, an annual narrative for another, a budget-versus-actual for a third. Reporting dates sit in award letters and inboxes, and the data lives in four systems.

So reports are built in a rush from spreadsheets, figures are hard to trace back, and staff who should be delivering programmes spend days compiling. A missed or weak report puts the next grant at risk.

What we build

What our grant reporting automation includes

Grant pipeline

Applications, decisions, awards, conditions and reporting dates in one tracker.

Reporting calendar

Every due date on a shared calendar with owners and reminders weeks ahead.

Data pull per funder

Activity counts, outcomes, volunteer hours and spend pulled from the CRM, case records and accounting by grant code.

Draft report pack

Figures placed into a draft shaped to each funder's template, with a note on where each number came from.

Narrative prompts

Prompts and past wording collected for programme staff to write the story, not generated for them.

Budget-versus-actual

Spend against the grant budget from your accounting tool, flagged where lines are over or under.

Who does what

Automation does the chasing, people make the calls.

Every step is marked: what runs on its own, what a member of staff reviews and what stays with a person who decides.
  1. 01 Automated

    Due date approaching

    The calendar triggers the report a set number of weeks ahead.

  2. 02 Automated

    Data pulled

    Activity, outcome, hours and spend data are gathered by grant code.

  3. 03 Automated

    Draft prepared

    A draft pack with sourced figures is shared with the owners.

  4. 04 Staff review

    Leads review

    Programme and finance leads check figures and write the narrative.

  5. 05 Charity lead or trustees decide

    Sign-off

    The charity lead approves and submits; nothing goes to a funder automatically.

How it behaves

How grant reporting packs behave

What each person sees and what runs in the background, including what happens when something goes wrong.

What funders see

  • Reports on time in their own format
  • Figures that trace back to records
  • A narrative written by the people delivering the work

What staff see

  • One calendar of reporting dates with owners
  • Draft packs weeks before each deadline
  • Budget-versus-actual flags

What the automation does

  • Triggers reports ahead of due dates
  • Pulls data by grant code
  • Notes the source of every figure

Edge cases and fallbacks

Activity not coded to a grant
Listed for staff to code before figures are included.
Funder changes the template
Flagged so the mapping is updated before the next pack.
Spend over budget on a line
Highlighted for the finance lead to explain.
Accounting data not yet reconciled
The draft says so and pulls again after reconciliation.

Architecture

A grant reporting pack, assembled early at a glance.

The setup we usually start from. We adapt it to the phone system and practice software you already use.
Grant calendar Due dates n8n Report trigger CRM and cases Activity, outcomes Accounting Spend by grant Draft pack Sourced figures Programme leads Review, narrative Charity lead Signs off
  • Input
  • Logic and services
  • Data
  • Output
  • People

How it flows

  1. 1 A reporting date approaching on the grant calendar starts the workflow weeks ahead.
  2. 2 Activity, outcome, hours and spend data are pulled by grant code.
  3. 3 A draft pack with a source for every figure goes to programme and finance leads.
  4. 4 Leads write the narrative and check figures, and the charity lead signs off and submits.

Project planner

How the project runs, phase by phase.

Typical durations for a first version. Your proposal lists the exact phases, dates and what you sign off at each step.

Grant pipeline & grant reporting packs project plan

Typical time to launch: about 4 weeks, then support

  1. 01

    Discovery

    2 to 3 days

    Active grants, funder templates, data sources, grant coding and current process.

  2. 02

    Design

    2 to 3 days

    Tracker fields, calendar rules, data mapping per funder and draft layout.

  3. 03

    Build

    About 2 weeks

    Tracker, calendar, data pulls, draft packs and budget-versus-actual.

  4. 04

    Shadow run

    About 1 week

    The next real report is drafted in parallel and checked against the manual version.

  5. 05

    Launch

    1 to 2 days

    Switch on for all active grants.

  6. 06

    Support

    Ongoing

    New funders, templates and data sources.

What it runs on

Real products only, connected through the access each vendor provides. See all integrations

n8n Your charity CRM API Xero Accounting API (tracking categories) Microsoft 365 or Google Workspace (Sheets, Docs) Airtable or your grants tracker Outlook or Google Calendar

Cost estimate

What it costs, line by line.

Estimates to plan with. Your fixed quote follows a free call, once we have seen your systems and volumes.
  • Discovery and design

    Grants, templates, data mapping and calendar.

    $250 – $450

  • Build

    Tracker, data pulls, drafts and budget-versus-actual.

    $450 – $1,250

  • Integrations

    CRM, accounting, documents and calendar.

    $150 – $400

  • Testing and shadow run

    QA and a parallel real report.

    $100 – $250

  • Launch and training

    Switch-on and walkthrough.

    $50 – $150

  • Total project estimate

    $1,000 – $2,500

Optional monthly care after launch is quoted with your proposal. Fixed quote after a free call. Very different funder templates may each need setup time. CRM, accounting and n8n plans are billed to you directly.

Monthly running costs you pay directly

Estimates from the vendors' published pricing, checked November 2026. Billed to you by each vendor, never marked up.

  • Workspace and accounting: Your Microsoft 365 or Google Workspace and Xero plans, including nonprofit pricing.
  • n8n: Self-hosted Community edition, or n8n Cloud from about €20 a month (Starter), billed annually.

What pushes cost up

  • Systems without an API, or with integration access that must be requested from the vendor
  • Writing data back into your core system rather than only reading from it
  • Several locations, brands or very different processes to support
  • Custom apps, dashboards or a voice line on top of the workflows

What keeps cost down

  • One location and one clear process to start with
  • Cloud software with a documented API
  • Using tools you already pay for instead of adding new ones
  • Approved wording and sample data ready at the start
Get a fixed quote

Privacy and consent

Rules we design for, with the sources.

General information to plan with, not legal advice. Your counsel or data protection adviser confirms what applies to your practice.

US federal awards: reporting frequency

2 CFR 200.329 sets performance reports no less often than annually and no more often than quarterly, due 30 days after quarterly or semiannual periods and 90 days after annual ones.

Source: www.law.cornell.edu

EU and UK: beneficiary data in reports

Reports use aggregated figures; beneficiary data that reveals health or beliefs is special category data under GDPR Article 9 and stays out of drafts.

Source: gdpr-info.eu

Funder terms come first

Each funder's own reporting terms override defaults, and figures are signed off by the charity before submission.

How we deliver

Agile delivery, in 1 to 2 week sprints.

We deliver in short Agile sprints using Scrum, so you see working software every one or two weeks instead of waiting for a big reveal at the end.

Every sprint

  1. 1 Sprint planning. At the start of each sprint we agree which backlog items we will finish, each with written acceptance criteria you can check.
  2. 2 Daily stand-up. A short internal check-in on progress and blockers. You get a written update in your Slack or Teams channel, not another meeting.
  3. 3 Sprint review and demo. At the end of each sprint we demo what was built on test data or in a shadow run, and you accept it or ask for changes.
  4. 4 Retrospective. The team looks at what went well and what to change in the next sprint, and we share anything that affects you.

How scope stays under control

Product backlog
Every feature, fix and question in one prioritised list you can see at any time.
Acceptance criteria
Plain-language conditions for "done" on each item, agreed before work starts.
Change requests
New ideas go into the backlog with an estimate. Nothing changes scope or price without your written approval.
User acceptance testing (UAT)
Before launch your team tests the real workflow against the acceptance criteria and signs off.

Tools we use

Jira, ClickUp or Trello for the backlogSlack or Microsoft Teams for updatesGitHub for code and version historyLoom or a live call for demos

Project manager / Scrum master

Runs the sprints, keeps the backlog and timeline honest, and is your single point of contact.

Business analyst

Maps how the work runs today, writes the workflow specification and acceptance criteria with your team.

Automation engineer

Builds the n8n workflows, integrations, AI steps and error handling.

Backend developer

Writes custom code where a no-code step is not enough: APIs, data sync, secure storage.

Frontend / mobile developer

Builds forms, booking pages, dashboards, web apps or Android apps when the project needs them.

QA engineer

Tests every workflow against the acceptance criteria, including edge cases and failure paths.

DevOps engineer

Sets up hosting, access, backups, monitoring and alerts, and the deployment pipeline.

Who does what at each phase

Free call
Project manager, business analyst
Understand the problem, check it is worth automating and outline a rough range.
Discovery
Business analyst, automation engineer
Map the current process, systems and data, and agree success measures.
Design
Business analyst, automation engineer, backend developer
Write the workflow specification, data flows, compliance notes and backlog with acceptance criteria.
Sprints
Automation engineer, developers, QA
Build, test and demo in 1 to 2 week sprints; you accept or adjust after each demo.
UAT and launch
QA, DevOps, project manager
Your team tests and signs off, we switch on, monitor closely and train the team.
Support
Automation engineer, DevOps
Stabilisation window, then optional monthly care with monitoring and changes.

A point of contact

One person who can answer questions and approve decisions, with about an hour a week during the project.

Access

Admin or API access to the systems involved, created as separate accounts with the least access needed.

Sample data

Real but non-sensitive records (or de-identified ones) so we can design and test against reality.

Approved wording

Message templates, policies and consent wording (for SMS, your opt-in and opt-out text) reviewed by you.

Vendor agreements

Signed agreements with the software vendors that will handle personal data, such as a BAA or processor contract.

Time for testing

A few hours from the people who will use the system, for the demos and user acceptance testing.

Working system

Workflows, integrations and any apps running in your accounts, under your keys.

Documentation

Workflow specification, data-flow map, run book and exported workflow files.

Training

A walkthrough for the team and a short recorded video for new starters.

Handover

All access, credentials and code handed over; you can keep us or take it in-house.

Stabilisation window

Fixes for anything that does not meet the agreed acceptance criteria after launch.

Support options after launch

  • No plan

    You run it yourselves after the stabilisation window and contact us when you need a change.

  • Monthly care

    Monitoring, error alerts, small changes and updates each month, with an agreed response time.

  • Priority care

    Faster response times for business-critical workflows and a monthly review call.

How a project moves through our team

Free call PM and analyst Discovery Process and data Design Spec and backlog Sprints Build, test, demo Your review Accept or adjust UAT and launch Sign-off, go live Support Monitor and improve
  • Input
  • Logic and services
  • People
  • Output
  • Data

How it flows

  1. 1 A free call with the project manager and business analyst to understand the problem and whether it is worth building.
  2. 2 Discovery and design produce a written specification, data-flow map and a backlog with acceptance criteria.
  3. 3 The team builds in 1 to 2 week sprints; you review a demo at the end of each and accept or adjust.
  4. 4 Your team runs user acceptance testing, we launch, then monitor and improve under a support plan.

FAQ

Grant reporting questions questions, answered.

It tracks what each funder needs and when, and pulls the data together so staff are not compiling from scratch. Ours connects to the systems you already use rather than adding another database.

It fills the figures into a draft shaped to each funder's template and notes the source of every number. Programme staff write the narrative and leads check the figures.

No. It can collect prompts and past wording to help staff start, but the story of your impact is written and approved by your team.

They vary by funder: activity numbers, outcomes, case stories, spend against budget and sometimes volunteer hours. US federal awards follow 2 CFR 200.329 timing. We map each funder's requirements during discovery.

Yes. Applications, decisions and conditions sit in the same tracker so the pipeline and reporting stay together.

Reports submitted on time, staff hours per report, figures traced to a source and conditions met.

Free 20-minute call

Want this for your charity?

Book a free 20-minute call. We will look at how the work runs today, tell you honestly whether it is worth building and give you a fixed quote if it is.

Book a free 20-minute call