When something breaks there’s an error, an alert, someone shouting. Fine. But when a workflow is working perfectly the client sees nothing at all — it’s invisible by design. So for months they’re paying for something they’ve no evidence of, and “trust me, it ran 4,000 times” doesn’t quite land.
Do you send clients anything to show it’s working? Or let the results speak and hope nobody asks?
1 Like
Honestly what helped me most was changing what I report. Instead of run counts, I pull out one number that ties back to why they hired me, like “it brought in 1,523 leads this month.” For me that’s landed way better than trying to show it ran a few thousand times.
Then I just send them a short recap every month, something like “here’s what it did for you.” It reminds them it’s still doing its job, so a quiet stretch doesn’t leave them wondering what they’re paying for.
Out of curiosity, do you send them something on a schedule, or give them a link they can check whenever they get nervous?
1 Like
I built LumaTrack to do exactly this! Show the client their Return on Investment (ROI) by tracking each run of every workflow in an auditable ledger. You tell LumaTrack what it would have cost a person to do the job, then every time the automation runs, it credits the ledger. What you get in return is the ability to report to your client to show exactly what their money (invested in building the automations) returns to them in value and savings.
It’s very flexible and customizable, and there’s an n8n node you can stick on the end of any n8n workflow. There is a free plan to try it out to see if you like it. If you have any questions about it, let me know!