The Tuesday problem
Most people who buy an automation product don't have an automation problem. They have a Tuesday problem: the same four things come back every Tuesday, each one takes eleven minutes, and not one of them is hard enough to justify hiring anybody.
That is what Hourbench is built for. Not the enterprise pilot, not the AI demo — the recurring clerical work that is too small to delegate and too frequent to ignore. Here is who that is, in plain terms, and who should keep their money.
The person this was built for
One profile, and it is the one every workflow was chosen against:
- You run the business and you do the admin. There is no ops person sitting between you and the inbox.
- Your tools are ordinary: Gmail or Outlook, Google Sheets, Slack, a CRM you half-use, something that makes invoices.
- You are comfortable with software but you don't write code. Following a setup guide: yes. Debugging a script at midnight: no.
- What eats your week is clerical, not creative: triage, follow-ups, quotes, receipts, reporting, the same announcement rewritten for five platforms.
- You would rather own files than rent another subscription.
If that reads like your week, the rest of this is about what comes off the pile.
What it actually takes over
The Vault is 20 workflows plus a bonus one, in six modules. The grouping isn't decorative — it is roughly the order in which this work starts to hurt.
- 01 Foundations. The unglamorous base: a connection test that tells you which credential is broken before a real workflow finds out, and an error handler that every other workflow reports into.
- 02 Client Communication. Inbox triage, instant replies with lead scoring, website form into the CRM, follow-up sequences — plus the bonus client-onboarding run.
- 03 Content & Marketing. A weekly content calendar, one source turned into five platform-native posts, scheduled publishing, a weekly marketing report.
- 04 Admin & Finance. Quote generation, payment to bookkeeping, overdue-invoice reminders, receipt capture.
- 05 AI Agent Workflows. A research agent, meeting notes turned into actions, a daily briefing, request routing.
- 06 Troubleshooting & Customization. A health monitor for the workflows you are now running, and a sandbox for changing one without breaking it.
Two of those get underestimated every time. Module 01 exists because the most common failure in a homemade automation isn't the logic, it is a credential that quietly expired. Module 06 exists because the second most common one is the edit you made three weeks later.
Where the line is
Honest disqualifiers. If one of these is you, this product will annoy you:
- You need one deep integration, not twenty shallow ones. A custom ERP, a proprietary booking system, an industry tool with no public API — that is developer work, and no template pack changes it.
- Your process isn't stable yet. Automating something you redesign every month means rebuilding it every month. Write it down by hand first, then automate the version that stopped changing.
- You won't connect real credentials. Every workflow here touches your actual mail, sheets and chat. If giving an automation access to your inbox is a no, nothing in the Vault can help you.
- You want it unsupervised from day one. It arrives switched off on purpose, and the safest ones stay drafts rather than sends. You turn workflows on one at a time, after watching each one do the thing once.
What we don't claim
No claimed results, no invented reviews, and no pretending the last step is done.
That sentence is on the sales page and it holds here. All 21 files import into a real n8n install and export back byte-identical, all 28 code nodes run under 131 unit tests — and none of them has yet run against a live Gmail, Sheets, Slack or OpenAI account. Yours would be the first, and the 155-point checklist for exactly that ships with the download. We would rather say that out loud than have you find it out.
Where to start
- First, run
01.01 Connection Test. It tells you in a minute which of your connections isn't actually connected. - Then pick the workflow that matches the task you repeated most often last week. Not the most impressive one. The most repeated one.
- Watch it run once with real data before you activate it. Then take the next one.
Everything else here is downstream of those three steps: why the whole thing runs on n8n, what the rest of the landscape looks like, and the five ways these projects usually die.