Groundwork · For community-led development

Keep the project record current. Let the client report follow.

Most development consultants rebuild the same picture every month: trawling emails for the latest budget, re-keying risks into Word, and writing funder updates from memory. Groundwork keeps one live record per project, so reporting becomes an export, not an evening.

Discuss a pilot See the core platform

The workflow

One record, end to end

Portfolio
Five stage gates
Budget · funding · risks
Monthly report / feasibility / bid
Health card

What changes

Three things that stop being painful

Outcome 1

Projects move through visible stage gates

Every project sits at a named stage with what's needed to progress, so a portfolio review takes minutes and nothing stalls quietly.

In the product: A project page with stage tracking, and a portfolio view across every engagement.

Outcome 2

Budget, funding and risks live with the project

Figures and risks are recorded once, against the project — not scattered across spreadsheets that disagree with each other.

In the product: Budget, funding and risk tabs on each project, drawn on by every draft.

Outcome 3

Reports draw from the live record

Monthly reports, feasibility studies and funding bids are drafted from the current project data, with citations back to your source documents.

In the product: Drafts assembled from project records and the vault, exported in your branding.

In the workspace

What lives here

A portfolio of development projects, each with five stage gates
Budget lines, funding sources and a risk register per project
The document vault: feasibility work, surveys, minutes and correspondence, all citable
Confirmed organisational facts shared across every draft
A health card summarising each project's status for the client

Deliverables

What comes out

Monthly client reportFeasibility studyFunding bidProject health card (PDF)Presentation slides

Every draft cites the document and page it drew from, and your workspace is isolated from every other customer's at the database level. You review and send everything — Flowgrid never submits anything to a funder on your behalf.

Is this for you?

A good fit — and an honest miss

Likely a good fit

You run several community-led development engagements at once.
Clients or funders expect regular written reporting against a live project.
Your evidence base is documents: surveys, minutes, studies, correspondence.

Probably not yet

You need construction-phase tools like Gantt scheduling or site management.
You want a system that submits applications to funders automatically — Flowgrid deliberately doesn't.
Your work is one-off with no recurring reporting to reuse records for.

Next step

Bring one live project. We'll set it up together in the pilot.

Discuss a pilot Ask a question first