The Pipeline Dashboard

Most grants teams track their pipeline in a spreadsheet that’s wrong by Monday morning. Someone updates it when they remember; deadlines drift; status columns go stale because the source of truth lives in someone’s head, on someone’s calendar, in someone’s inbox. The pipeline review meeting becomes “let’s reconcile what’s actually happening” before it becomes anything strategic.

Grantable’s dashboard avoids that by being a view of work you’re already doing, not a separate tracker to maintain. It reads from your workspace files — every grant in your /Applications/ folder, every prospect in /Prospecting/ — and surfaces them as a list, a kanban board, or a calendar. You don’t update the dashboard. The dashboard updates itself.

How the Dashboard Gets Its Data

The dashboard list view showing grant projects with inline-editable fields for status, deadline, funder, and priority

This is the part most teams underestimate at first. The dashboard isn’t a separate database. It reads file metadata — properties attached to each grant document or prospect folder: status, stage, due date, funder name, ask amount, priority. When those properties are set, the dashboard sees them. When they’re not, the row doesn’t appear.

That metadata gets set in three ways:

AI sets it during work

When the prospecting skill writes a Prospect Brief, it stamps the funder name and status into the file. When you generate a Grant Opportunity Brief, the AI adds stage and amount. When you accept a prospect, status updates. The bookkeeping happens as a byproduct of the work — you don't have to remember.

You edit inline in the dashboard

Every cell on the dashboard is editable. Status and stage are dropdowns; due date is a calendar picker; funder and amount are click-to-edit text fields. Changes save instantly and the metadata updates on the underlying file.

You tell the AI in conversation

'The CIAF application has a due date of June 15.' 'Mark the Healy Foundation brief as submitted.' Grantable updates the file's metadata and the dashboard reflects it on the next render.

Watch out

The dashboard can only show what’s in the metadata. If a deadline is mentioned in the body of a document but no due_date property was set, the dashboard won’t see it. If something looks wrong or missing, fix the metadata — either inline on the dashboard, or by telling the AI.

Three Views, Three Questions

The kanban view showing grant opportunities organized in columns by status, with drag-and-drop between stages

Each view is optimized for a different kind of question.

List view — 'what's the state of everything?'

A sortable, filterable table with columns for status, stage, funder, due date, amount, priority. Best for bulk audits, pipeline reviews, and filtering by ask range or stage.

Kanban view — 'where is everything in the funnel?'

Cards organized by status: Not Started, In Progress, Under Review, Submitted, Awarded, Declined. Drag a card from one column to another to update its status. Best for visualizing throughput and bottlenecks.

Calendar view — 'when is everything due?'

Opportunities plotted on a calendar by due date, color-coded by status. The view that surfaces deadline clusters before they become a fire drill.

What to Watch For

The dashboard isn’t just a tracker — it’s a strategic surface. A few things to scan for:

Deadline clusters — three submissions due in the same week is a planning problem, not a Friday-afternoon problem. The calendar surfaces them while you can still adjust.
Stage distribution — if everything is in prospecting and nothing is in active drafting, your pipeline will have a revenue gap in three months. The kanban surfaces that imbalance.
Dollar concentration — when 70% of your projected revenue depends on one application, the portfolio is fragile. The list view (sorted by amount) makes that visible.

The dashboard is a view, not a system. It assembles itself from the metadata on your workspace files; you keep it accurate through a combination of AI bookkeeping during the work, inline edits when you spot something off, and conversational updates when something happens outside the workspace. There’s no separate spreadsheet to reconcile.

Keeping It Honest

The metadata-driven dashboard model has one failure mode worth naming: a file with stale metadata is invisible to the dashboard if the staleness flips a key field to wrong. A submitted application that still says status: in_progress skews your kanban. A funded grant that says stage: prospecting skews your forecast.

Pro tip

End every pipeline meeting with one minute on the dashboard, sweeping for staleness. Anything you discussed that doesn’t match what the dashboard shows? Fix it inline right there. The cost of a fix is seconds; the cost of a wrong dashboard at the next review is a meeting wasted reconciling.

Check your understanding

A grant application file exists in your /Applications folder but isn't showing up on the dashboard. What's the fastest fix?

Key Takeaways

The dashboard reads file metadata from your workspace — it's a view of work, not a separate tracker to maintain
Metadata gets set three ways: the AI during work, inline editing on the dashboard, or telling the AI in conversation
Three views answer different questions — list (state), kanban (funnel position), calendar (deadlines)
End pipeline meetings with a one-minute staleness sweep — fix anything that doesn't match what was discussed

Next Lesson

The dashboard is a snapshot of where your work stands today. The deeper value of working in Grantable is what compounds across dashboards — the years of conversations, decisions, and relationships your workspace remembers. Next we’ll look at how that institutional memory accumulates, why search across the whole workspace matters, and what to capture on purpose so future team members can find it.