Launched this week
RoutineCut Marketing Report QA Kit
Catch client-report errors before delivery
8 followers
Catch client-report errors before delivery
8 followers
RoutineCut is an offline QA workspace for recurring marketing reports. Drop in a CSV to recalculate KPIs, summarize channels, flag missing or suspicious data, and require human sign-off before client delivery. No account, upload, or tracking.
Hi Product Hunt — I built RoutineCut to catch small, avoidable client-report issues before delivery: wrong date ranges, duplicate keys, impossible ratios, and missing values.
It runs locally from a single HTML file, recalculates CTR, CPC, CVR, and CPA, summarizes channels, flags suspicious rows, and keeps final approval with a human. There is no account, upload, analytics tracker, persistent storage, or automatic client delivery.
The launch version is a USD 29 one-time download. I would value feedback on whether these checks match your pre-delivery workflow and which CSV exports you use most.
The CSV recalc and missing data flags are genuinely useful for my weekly reports. Wish I'd found this sooner instead of wrestling with messy spreadsheets every Monday.
@egementznl0tmv Thanks — glad those checks map to your weekly workflow. The current kit runs locally in a single HTML file, and the CSV never leaves the machine.
A really useful offline workflow, love that nothing leaves my machine. One thing that would make it even better is letting me save a small library of my own QA rules per client so I don't have to re-flag the same recurring quirks like duplicate weekend sessions every month.
@hanifemamacjrw Thanks — that’s a useful gap to call out. The current v1 uses built-in checks and does not save a per-client custom-rule library. I’m logging this as an evidence-backed candidate, not promising a release date.
Love that the sign-off gate sits at the export step instead of being a separate tab to forget about. Feels like a small thing but it's exactly the kind of friction that actually catches mistakes before clients do.
@selahattinf56i Thanks — that placement is intentional. The current kit keeps human approval at the final export step, so a report cannot be treated as client-ready until someone signs off.