Every row of work, answerable in seven questions.
The RAID log your team already keeps — live, shared, and impossible to fudge.
WHY Dash is a multi-user web grid built from the review spreadsheet executive teams actually run on:
Initiatives holding rows of work, where every row carries its
WHY, WHAT, WHO, WHERE, WHEN,
HOW and STATUS — and keeps a dated log of how it got there.
60 days
Full features, no card. Every new account starts here.
- Unlimited projects and rows
- Excel import and export
- Per-row update history
- Invite your whole team
This is what the dashboard actually looks like
Not a screenshot of a mockup — the real grid, rebuilt in the page so you can read it. Grouped by initiative, tinted by health, with the latest update for every row in the last column.
| # | Why | What | Who | Where | When | How | Status | Latest update |
|---|---|---|---|---|---|---|---|---|
| INITIATIVE 1 — Retire the legacy billing service | ||||||||
| 1 | Dual pricing paths double every support ticket | Cut over annual plans | @priya | Billing svc | 2026-11-14 | Feature flag, 10% ramp | IN-PROGRESS | Ramp at 40%, no regressions. 2 days ago · @priya |
| 2 | Refunds are manual and one person knows how | Self-serve refund flow | @marcus | Admin portal | 2026-10-31 | Reuse the seat-change API | BLOCKED | Waiting on the audit-log schema. yesterday · @marcus |
| INITIATIVE 2 — Get the portfolio onto one roadmap | ||||||||
| 3 | Three spreadsheets, three versions of the truth | Import the Q3 RAID logs | @dj | WHY Dash | 2026-10-08 | XLSX import, then dedupe | COMPLETED | 412 rows in, owners mapped. 6 days ago · @dj |
| 4 | Board wants health by initiative, not by row | Roll-up health view | @sam | Dashboard | TBD | Weighted mean of row weights | AT-RISK | Weights disagree with Finance’s. 3 hours ago · @sam |
| 5 | Contractors keep asking what is theirs | Guest read-only access | @priya | Access model | 2026-12-01 | Guest role, no seat | NEW | Scoped per project, not per user. today · @priya |
| 6 | Vendor demo scheduled, decision unmade | Evaluate reporting add-ons | @dj | Procurement | 2026-11-03 | Compare against HTML export | ON-HOLD | Parked until the roll-up lands. 4 days ago · @dj |
Illustrative data. Status colours are the real built-in catalog tints; the row tint is derived from the status’s health weight, so a portfolio reads as a heat map from across the room.
Seven columns, because that is what a review asks
Most trackers store a title and a due date, then let the rationale rot in a comment thread. WHY Dash makes the seven questions the schema itself — a row cannot exist without them.
WHY
The business rationale. Deprioritising becomes a conversation about this, not a silent drift.
WHAT
The work itself. Unique within its initiative, so two people cannot file the same thing twice.
WHO
The owner. Free text with @mentions, so a name is also a notification.
WHERE
Where it lands — the system, region, team or artefact it touches.
WHEN
The date, or TBD. Every change to it is written to the row’s log automatically.
HOW
The approach, so the person picking it up inherits the thinking, not just the task.
STATUS
One of 14 built-in weighted states, each carrying a weight from 0 to 100 and a colour. The weight drives the tint of the entire row, so the portfolio reads as a heat map and a claim that contradicts the colour is visible from the back of the room. The catalog is editable per project.
Every row keeps its own story
The question a review always turns into is “what happened since we last looked?” WHY Dash answers it from the row itself: a dated, authored log, newest first, that nobody has to remember to write.
- Automatic change records. Change
WHENorSTATUSand the row records the old value and the new one — marked as machine-written, so it can never masquerade as your update or become the “latest” line. - Manual updates are stamped. Every entry carries its author and timestamp, and reads newest-first.
- A separate audit trail. The History tab shows the previous value of every field and who last set it — the answer to “when did this become a priority?”
- Nothing is destroyed. Rows and initiatives are soft-deleted with restore, and permanent deletion is a deliberate second act.
updates · newest first
- Weights disagree with Finance’s. Proposing two views: strict and rounded.
- WHEN changed from 2026-11-07 to TBD AUTO
- STATUS changed from IN-PROGRESS to AT-RISK AUTO
- Weighted mean looks right on the sample set; needs the roll-up before it is useful.
What you get on day one
Nothing here is a roadmap item. All of it is in the product when you sign up.
Your spreadsheet, not a migration project
Import the RAID-log .xlsx you already maintain — initiatives, rows, owners, dates and
statuses map straight in. Export back out whenever a stakeholder asks.
- Imports run in a transaction and merge safely with what is already there
- Export to XLSX, to a standalone HTML document, or Copy HTML for one row into any report
- Legacy Mac
.whydashfiles import too, status weights intact
A grid that fits the screen it is on
Built for the moment a director says “put it on the screen”. Columns reflow and wrap, so the grid never scrolls sideways — at any window size.
- Five font sizes (8–16 px) for the wall of a conference room or a laptop
- Double-click to edit; Tab, arrows and Enter move like a spreadsheet
- Drag to reorder rows, and duplicate an initiative to start a fresh quarter
Health you cannot fake
Fourteen built-in statuses each carry a weight from 0 to 100. The row’s tint is computed from that weight, so colour and claim always agree.
BLOCKED,AT-RISKandFAILEDare impossible to hide in a green portfolioCANCELEDandOUT-OF-SCOPEsit at weight 0 and drop out of the tint- The catalog is yours to edit per project — add states, change weights and colours
Context that finds the person
Write @priya in any text cell or in the update log and she gets an email the moment it
saves. No one has to remember who cares about what.
- Mentions are read in the five text fields and in the update log
- Only accepted members of your account are emailed — tagging a stranger does nothing
- Guests can be invited to read without taking a paid seat
- Owners, collaborators and guests are assigned per project
Two people, one grid, no overwrites
Every project carries a version stamp. If someone saved underneath you, you find out before your edit lands, not after.
- Optimistic concurrency on every mutation
- Per-field authorship, so the audit trail says who set each value
- Saved as you type — there is no draft state to lose
Your data leaves whenever you want
Every project exports to a portable JSON backup and restores as a new project or in place. Nothing is held hostage.
- Backups include initiatives, rows, statuses, updates and history
- Nightly database backups run off-box as the whole-app safety net
- A lapsed subscription goes read-only — it does not delete anything
Initiatives hold rows. Rows hold their history.
Two levels, not nine. Enough structure to run a portfolio review, shallow enough that nobody files work in the wrong place and gives up.
Built from the log teams already keep
WHY Dash is not a new methodology to learn. It is the RAID log — Risks, Assumptions, Issues, Dependencies — promoted from a spreadsheet that drifts out of date the week it is shared.
- One source of truth. The grid you review is the grid you export, because it is the same data.
- Enterprise asks stay visible. SSO, compliance and licensing work live as first-class rows with owners and dates, not sticky notes.
- Sign in with your EAFX account. Registration, invitations, seats and billing all live in one place at id.eafx.net — WHY Dash stores no password of yours.
- Team seats to 10,000. Single-seat or per-seat Team licensing, with guests who cost you nothing.
In and out, in formats you already have
A tracker that only accepts its own format is a subscription to a lock-in. These are the doors WHY Dash actually has.
# bring the log you already maintain Import XLSX → initiatives, rows, owners, dates, statuses # hand the review out as a document Export XLSX · Export HTML · Copy HTML (one row) # take everything with you GET /api/projects/:id/backup → portable JSON POST /api/projects/restore → new project, or in place # the Mac app’s files still open .whydash → status weights read as weight or value
Why this matters more than it sounds
The usual failure of a project tool is not that it lacks features. It is that the team stops feeding it once entering data takes longer than doing the work.
So the grid is editable in place, at spreadsheet speed, and the boring bookkeeping — the date that moved, the status that slipped — is written for you.
What you have to do manually is the part only a human can do: decide what is true, and say what changed.
Who may edit, who may read, who pays
Three roles, and the useful asymmetry: reading is not what costs money. You can give a contractor or an executive visibility without buying them a seat.
A guest costs you nothing
Owners run the project and its membership. Collaborators hold a seat and can change the work. Guests read it and cannot change it — which is most of what an auditor, a client, or a department head actually wants.
Invitations go to an email address, and a person accepts into their own EAFX identity. One person can belong to several accounts and switch between them from the top bar, so a consultant on four engagements needs four logins less than you would expect.
A team can never lock itself out: the last owner cannot be demoted or removed by accident.
OWNER
Runs the project and its membership. Holds a seat. Owns the subscription.
COLLABORATOR
Creates and edits rows, initiatives, statuses and updates. Holds a seat.
GUEST
Read-only. Sees the projects you invite them to and nothing else — and uses no seat.
Live this afternoon
There is nothing to install, no template to buy and no administrator to become.
Create your EAFX account
One identity covers WHY Dash, ioBudget and sMarked. Your 60-day trial starts here, and no card is asked for.
Start a project or import one
Open a blank grid, or import the RAID-log .xlsx you already keep. Owners, dates and statuses
come with it.
Tune the statuses
Keep the 14 built-ins or make them yours — names, weights and colours are per project, and the tints follow.
Bring the team in
Invite collaborators by email, give stakeholders guest reads, and run the next review on the live grid.
Pricing you can quote from memory
Every plan includes every feature. The only difference is how many people can change the work.
Trial
Everything, unfettered
- All features, no metering
- No card required
- Converts to a paid plan or simply stops
Single
One owner, unlimited guests
- Unlimited projects, initiatives and rows
- Excel import and export, JSON backups
- Update logs and field history
- $49.99/year if you prefer annual
Team
Per seat, per month
- Owners, collaborators and guests
- Seat counts from 1 to 10,000
- Account switching for people on several teams
- $99.99 per seat/year annually
Prices as of October 2026. Team pricing is per seat — the total is quoted at checkout, and that quote is authoritative. Billing runs through EAFX.
Questions, answered honestly
We keep this in a spreadsheet already. Why move?
Is this a Jira or Asana replacement?
Why exactly seven columns?
What stops the status column from lying?
IN-PROGRESS looks like one and a
BLOCKED row cannot hide in a green wall. And because WHEN and
STATUS changes are logged automatically, a status that slipped quietly is visible in the
row’s history with a timestamp and a name.Can I import what I have today?
.xlsx and the mapping runs in a transaction, merging with
whatever is already in the project. If you used the Mac app, its .whydash files import too. And
everything goes back out: XLSX, a standalone HTML document, or a portable JSON backup that restores as a new
project or in place.What happens if we stop subscribing?
Do we need to run a server?
How does sign-in work?
Start with the why.
Put the roadmap, the RAID log and the next review on one grid — and give every row the dated story of how it got where it is.
One EAFX identity · billing through EAFX · export your data any time