Methodology
Every workflow carries one of two labels. We'd rather show you an honest "Researched" than a hopeful "Tested".
Researched
Sourced and summarized, but not run by us. A Researched entry includes:
- the business problem it addresses and the business function it belongs to,
- the tools involved and an outline of the steps, summarized from the public source,
- a setup estimate (a rough guess for someone comfortable with the tools who already has the accounts and API keys; real time is unknown until tested),
- caveats, such as costs billed separately, consent and recording laws, or platform terms-of-service risks,
- a link to the source, and the date we last checked that the source was live.
Tested
Run end-to-end in a sandbox with dummy data, with a public evidence pack:
- the test date and tool versions,
- an execution log or screenshots,
- cost per run,
- failures and what went wrong.
If a test fails, we publish it as failed, with the reason.
Where things stand
Right now: 50 Researched, 0 Tested. Testing hasn't started yet, so every entry is Researched. Tested entries will be listed on Tested workflows.
Independence
- We publish recipes and evidence. We don't build workflows for clients or sell implementation work.
- Sponsorship never buys a Tested label or a ranking, and every sponsored item is labeled as sponsored. See Sponsor.
- Last-checked dates show when we last confirmed the source page was live, not when the workflow was run.