About
A publication for people who choose software for a living, or just too often.
Workflow Vitals is an independent editorial publication about productivity software, AI tools, and the workflows they fit into. It is not a deals site, a directory, or a marketing operation. It is a place to read about what a tool actually does before you spend time installing it.
- Focus
- Productivity software
- Format
- Guides and features
- Method
- Workflow-first
- Standard
- Tradeoffs included
Between the sales page and the hot take
Most writing about software falls into one of two categories: vendor marketing copy dressed up as an article, or opinion with no visible method behind it. Neither answers the question that actually matters before you adopt a tool: will this fit how I already work, and what will it cost me in time, money and friction to find out?
Workflow Vitals sits between those two extremes, closer to documentation with a point of view than to either. The method is on this page, the limitations of each piece are on the piece itself, and where something is our judgement rather than a fact, it is marked as our judgement.
What this site does
- Reads the documentation, the pricing page and the help centre, and says which is which.
- Names the settings that are switched on before you configure anything.
- Dates every factual claim, so you can tell when a page has gone stale.
- Says who a tool is wrong for, on every page, including the ones we like.
- Publishes its method before its conclusions.
What it will not do
- Invent statistics, studies, sources or expert quotes.
- Publish testimonials, star ratings or reader numbers we do not have.
- Rank tools by what they pay, or let any commercial relationship change a verdict.
- Let a vendor review or approve a page before it goes up.
- Present a vendor's own figure as if it were a finding of ours.
How tools are evaluated
Six questions, in the same order, whether the tool is being recommended or not.
01
Usefulness
What the tool actually does, stated plainly, without adjectives doing the work of evidence.
02
Workflow fit
Where it sits alongside the tools people already use, and what it replaces rather than adds.
03
Setup friction
What it takes to get from download to daily use, including anything that trips people up.
04
Pricing and value
What the plans cost, what each includes, and where the free tier stops being enough.
05
Limitations
What the tool does not do well, or at all. This section is never optional.
06
Who it is for
The kind of work the tool suits, and who should look elsewhere. Also never optional.
The order is part of the method. A good answer to a later question cannot rescue a bad answer to an earlier one, which is why price sits at four rather than at one. The reasoning behind that sequence is set out in our guide to evaluating a tool.
Where the facts on a page come from
Workflow Vitals is a small publication and does not pretend to be a laboratory. What it can do is be exact about the provenance of every claim it makes.
-
Vendor documentation, read closely
Product pages, pricing pages, help centres and terms. Where two of a vendor's own pages disagree, that disagreement is itself worth reporting, and we report it rather than picking the flattering one.
-
Labelled as the vendor's, not ours
A company's own figure is presented as a company's own figure. We do not launder marketing numbers into findings, and we say when a claim has no published method behind it.
-
Dated on the page
Pricing, platform support and privacy defaults all change. Every factual page prints the date its claims were checked, so a reader can tell how much weight it still carries.
-
Judgement marked as judgement
Where we draw a conclusion, it is introduced as our judgement. You are meant to be able to accept the facts and reject the conclusion.
-
What we did not do, stated
If we have not installed it, timed it, or tested it, the page says so. An absence of testing that is not disclosed is a claim of testing.
A tool can be well built and still be the wrong choice
Workflow fit is judged by tracing a real sequence of steps: where a task starts, what tools it passes through, and where the output ends up. Then by checking whether the tool in question shortens that path or adds a new seam to it. A feature list cannot answer that question. Using the tool the way it is meant to be used can.
This is also why coverage here is organised around workflows rather than around categories. The five stages we use to describe where a tool sits, and the argument for one tool per stage, are set out in the guide to building a stack.
Recommendations and independence
Coverage here is not for sale and inclusion is not a favour. No commercial arrangement decides which tools are written about, what a verdict says, or what a page says about a tool’s limitations.
A recommendation here is always conditional. A tool is recommended for a particular kind of work, and the same page says who it is wrong for. Where a tradeoff exists, it is stated rather than left for a reader to find after installing.
How this works
What a reader can rely on when they open a page here, in one place.
Independently operated
Workflow Vitals is a new, independently operated publication. It is not owned by, funded by, or editorially connected to any software vendor, and no vendor has any say in what appears here.
Small, and not padded out
There is no team page, company history or founding date on this site, because there is nothing yet that would be true to put on one. Inventing any of it would be the first thing a reader was right to distrust.
Productivity and AI software
Voice input, writing, meetings, research, automation and note taking, together with the workflows they sit inside. A tool is covered when there is something useful to say about where it fits, and where it does not.
Used before it is judged
A verdict comes from working with the tool, reading its documentation and checking the defaults it ships with. Vendor claims are labelled as vendor claims rather than restated as findings.
Fixed and marked
Pages carry the date their facts were checked. Where one turns out to be wrong or has gone out of date, the intention is to correct it and note the correction rather than edit it quietly.
Handled by the operator
Correspondence about corrections, factual disputes and data protection requests is handled directly by the person who operates the site. What the site collects when you read a page is set out in the privacy policy.