Projects

The Timeline is the project’s stepper — one bubble per phase, drawn from the project’s Project Type and your organization’s Group and Phase Labels (see Default settings, below). The current phase is highlighted; each bubble shows how many tasks sit in that phase and how much of it is done, and View tasks expands the checklist. Tasks — and who owns and approves each one — are defined per Project Type in Settings → Projects → Project Types.

Drop in files, call notes, or a transcript and Start Generation drafts the pain point for you — or write it by hand. Each field carries its own Enhance with AI action, and the panel on the right shows a live, per-field Score.

This example project scores 9/10 overall — the average of Problem Statement (10), Expected Outcomes (10), Business Impact Potential (10), Implementation Readiness (5), and Strategic Benefits (10). Additional Information shows 0 because it’s never scored, and it isn’t counted in that average either. Full breakdown of how this is calculated: Settings → Projects → Pain Point AI.

Once the pain point is filled in, Find companies for this pain point → Ask SourceAI hands the same problem statement straight into a startup search.

Companies shortlisted for this project, pulled in from a linked List or added directly. Select one or more to Start Assessment or Contact, and Ask SourceAI to keep searching against the same pain point without leaving the project.

The financial model for the project — cost and expected impact for the PoC itself, then Year 1 through Year 3 of running the solution, netting out to a Net Benefit per period and a running total. Add Impact Calculations link attaches a supporting model, and Additional Info holds any assumptions or caveats.

This is the entry point for correct numbers in Analytics → Financial. That tab is built entirely from what’s entered here, project by project — an empty or partial Business Case is exactly what shows up as a Financial gap in Analytics → Data Health.

A free-text field for the qualitative takeaway — what was actually learned, independent of the score or the outcome. It can be written at two levels: about this specific project (what this PoC, this solution, this team learned), or about the underlying pain point / process more broadly, so the insight survives even if this particular solution doesn’t move forward. Either way, it’s aggregated in Analytics → Learnings, currently filtered to projects at PoC stage or later.

A Project Type is a named, end-to-end workflow — the phases a project moves through, the tasks and approvals required at each one, and the terminology used to describe it. GlassDollar’s default playbook is the starting point for every organization; reshape it, or add new Project Types for how different parts of your business actually work (e.g. Software Procurement vs. Hardware Integration), so a quick evaluation and a multi-year integration no longer share one rigid path.

A group is one of the broad pipeline stages a project moves through — Ideas, Leads, PoCs, or Implementations — used to organize the Kanban board and navigation.

These labels are visible to everyone in your organization. Any Innovation Lead can update them.

Each group keeps its colour indicator wherever it appears. Rename a group from this table, or click the revert icon to restore its default name.

A phase is a more granular step within a group — for example, Sourcing or Assessment within Discovery — used to track a project’s progress in detail.

These labels are visible to everyone in your organization. Any Innovation Lead can update them.

⚠️ Due to backend limitations tied to accurate analytics, it is currently not possible to add or remove groups or phases — only rename them.

Automatically surfaces stalling projects — this is what powers the Status field on every project (General project details, above) and the 🟢/🟡/🔴 dot across the Kanban. Choose one of three modes:

In Automatic/Custom mode, the colour is picked in priority order:

1. Manual override (temporary) — if someone manually sets green/amber/red, that choice holds, but it still ages into amber then red on the same thresholds unless cleared.
2. Task activity in the current phase (preferred signal) — overdue incomplete tasks block green; recent task movement keeps it green or amber; a long quiet spell turns it red.
3. Fallback: time in current phase — used only when there’s no useful task-activity signal, based on how long the project has sat in its current phase (or since creation, if phase history is missing).

Moving to a new phase always resets the clock toward green.

⚠️ Automatic health tracks staleness, not strategic success — a project can show green simply because it recently moved phase or had a task updated, whatever the underlying difficulty of the work or its outcome. Full detail, including exactly what triggers each colour change: Settings → Projects → Health Status.

Every pain point gets an AI-assisted write-up and a transparent score — not a grade of how well it’s written or how important the topic is, only a check of whether the text answers the guiding questions behind each field.

• Field score = questions answered ÷ questions asked. 1 of 2 = 50, 2 of 3 = 67, an empty field = 0.
• Overall score = the average of the fields your organization has switched on (unscored fields, like Additional Information, never count toward that average).
• Renaming a field does nothing to the score. Changing its guiding questions, or the text in it, does.

The Pain Point screenshot above shows this in practice: this project renamed the default Current Challenge field to Problem Statement, and scores 9/10 overall — the average of Problem Statement (10), Expected Outcomes (10), Business Impact Potential (10), Implementation Readiness (5), and Strategic Benefits (10); Additional Information’s fixed 0 isn’t counted.

Full field-by-field guiding questions, required fields, custom fields, and exactly what renaming vs. changing questions vs. hiding a field does to the score: Settings → Projects → Pain Point AI.