The same exports are rebuilt every cycle
Spreadsheets are copied, cleaned, joined and reformatted in almost the same way each month or quarter.
Recurring report automation
Stop rebuilding the same report every month.
We turn one recurring client report into a reliable, repeatable workflow in 10 business days — without replacing your current tools.
- Existing tools
- Fixed scope
- Client-owned workflow
- Human checked
From manual cycle to reliable system
Human checked- 01Export
- 02Copy / paste
- 03Format
- 04Check
- 05Send
Monthly client report
One source
of truth
of truth
✓ Source reconciled
10 days
Fixed implementation sprint
1 report
One existing recurring deliverable
2 inputs
Maximum launch boundary
0 migrations
Built around current tools
Recognition
Your reporting day should not start from scratch.
The report already exists and provides value. The problem is the production cycle around it: repeated exports, hidden rules, formatting drift and checks that live in one person’s memory.
One person remembers the hidden steps
Checks, exceptions and client-specific adjustments depend on knowledge that has never been written down.
Numbers and layouts drift
Small variations in filters, formulas, dates or formatting create avoidable review work and client-facing risk.
Every new client adds another production block
Growth increases reporting labour instead of reusing a controlled workflow your team can operate.
The change
Keep the judgement. Remove the repetition.
The service changes how the report is produced, checked and handed over. It does not replace your interpretation, advice or client relationship.
Before · manual cycle
- Export source data into separate working files.
- Repeat copy, paste, filtering and cleanup steps.
- Recreate charts, tables and document formatting.
- Remember exceptions and client-specific rules.
- Recheck totals without one defined QA routine.
After · controlled workflow
- Defined source inputs, owners and refresh dates.
- Repeatable transformations using the simplest reliable method.
- Consistent client-ready output in the required format.
- Visible review points, exceptions and change control.
- Reconciliation checklist and documented handover.
How it works
One bounded path from fit check to handover.
Every stage has a decision, an output and a boundary. The paid diagnostic prevents a small report problem from quietly becoming an open-ended software project.
Fit check
Confirm the report recurs, the inputs are manageable and the workflow sits inside the privacy and scope boundary.
Diagnostic
Map the inputs, rules, output, exceptions, checks, risks and recommended build before touching live systems.
Sprint
Rebuild one workflow using templates, formulas, scripts, queries or a simple dashboard where appropriate.
Handover
Reconcile the output, document the operating steps and transfer the system into client-controlled accounts.
Care, if useful
The optional care plan covers bounded source changes, minor improvements and scheduled quality checks.
Map
Confirm inputs, rules, edge cases, owner and success criteria.
Build
Create the repeatable workflow and client-ready output structure.
Reconcile
Compare output against the source, test exceptions and document checks.
Hand over
Walk through the operating guide, ownership and change-control path.
What you receive
A working system, not a slide deck about automation.
The exact technical method depends on the report. The handover package remains consistent so the workflow can be understood, checked and maintained.
Current-state map
Inputs, owners, transformations, exceptions, review points and the current delivery path.
Rebuilt workflow
A semi-automated template, formula, script, query or simple dashboard appropriate to the current tools.
Client-ready output
Consistent Sheets, Excel, Docs, Slides, PDF or dashboard output that preserves your analysis and brand.
QA and reconciliation
Source totals, date ranges, filters, formulas, exceptions, layout checks and approval status.
Operating guide
Refresh, review, export and delivery instructions written for the person who will run the next cycle.
Change log and support
Versioned changes plus 14 calendar days of bounded handover support after delivery.
Fit boundary
Built for a specific kind of reporting problem.
Narrow scope is part of the value. It makes the price, timeline, data boundary and handover understandable before the work begins.
A good launch fit
- A monthly or quarterly client report already provides value.
- One or two stable source systems or exports.
- An owner-led professional service with 2–20 staff.
- At least five recurring client accounts.
- Reporting day consumes half a day or creates visible quality risk.
- No internal data engineer or automation specialist.
Not a launch fit
- Real-time enterprise BI, data warehouses or multi-department programmes.
- More than two source systems in the first engagement.
- A report that has not yet been defined.
- Regulated calculations, tax, investment or clinical advice.
- Health, student or highly sensitive personal information.
- 24/7 support, uptime guarantees, emergencies or weekend delivery.
Launch pricing
Pay for a decision, then a bounded build.
The fit check confirms whether a conversation is worthwhile. The diagnostic produces a written recommendation before the implementation sprint is approved.
Entry
Report Fit Check
Free · 15 minutes
Confirm recurrence, decision owner, inputs and privacy boundary. No solution design.
Book the fit checkDecision
Report Workflow Diagnostic
NZ$350
Map feasibility, scope, risks, assumptions and the recommended build. Credited to the sprint if you proceed.
Confirm fit firstCore offer
Recurring Report Automation Sprint
NZ$1,800
One report, two inputs maximum, one output family, one review and 14-day handover support.
Review the sprint scopeOptional
Report Care Plan
NZ$450/month
Capped source changes, minor edits, scheduled QA, a change log and one defined improvement allocation.
See care boundariesPrices are in New Zealand dollars. GST, if applicable, is identified in the written proposal. Additional reports start from From NZ$950 after the first workflow is operating.
Demonstration
What a report workflow looks like behind the polished output.
This demonstration uses invented data. It shows the source-to-output logic and QA structure—not a claimed client result.
Boutique consultancy · monthly performance report
Demonstration onlyBefore · source inputs
Two exports with inconsistent labels
| Channel | Result |
|---|---|
| Search | 48 |
| Referral | 31 |
| Direct | 22 |
| Partner | 18 |
Manual cleanup currently happens after every export.
System · defined controls
Mapped rules and visible review points
Input 01Normalise names and date range
Input 02Join client and campaign identifiers
QA gateCheck totals, blanks and exceptions
OutputRefresh branded report template
After · client-ready report
Consistent output with source status
Monthly performance summary
119Total outcomes
+14%Illustrative change
✓ Reconciled to source
Founder-led quality
Built by someone who understands both the system and the client deliverable.
Client Report Works is led by Nova MacCourt, a software and operations practitioner with more than two decades across web systems, automation, product, UX and distributed-team delivery.
Nova scopes every engagement and reviews every final workflow. The service is deliberately narrow: one recurring report, rebuilt into a system the client owns. Specialists are added only where the approved scope requires them.
SystemsSoftware, data flows and practical automation
ExperienceProduct, UX, operations and team delivery
AccountabilityFounder-led scoping and final QA
Questions
Before you send the report.
Start with a high-level description. The public website does not accept report uploads, client files or credentials.
Do I need new reporting software?
Usually not. The sprint is designed around your existing Sheets, Excel, Docs, Slides, PDF or simple dashboard workflow. A new tool is recommended only when it is the smallest reliable option and you approve it.
What does “semi-automated” mean?
Routine collection, transformation, formatting or export steps are automated where practical. Review, commentary, exceptions and final approval remain with a person.
How do you check accuracy?
The sprint defines source totals, date ranges, filters, formulas and exception checks, then reconciles the rebuilt output against the current source and report.
Who owns the workflow?
You do. Wherever practical, the work is built in client-controlled accounts and handed over with documentation and a change log.
Can you automate several reports?
The launch offer starts with one report and no more than two inputs. Additional reports are estimated after the first system is stable.
What data can I send?
Start with a high-level description. Do not send confidential files through the public form. Sensitive, regulated, health or student data is outside the launch scope.
Will AI write the report?
Not by default. AI may assist a bounded drafting step only when appropriate, approved and safe. You remain responsible for judgement and final client-facing content.
What happens after the sprint?
You receive the workflow, QA checklist, operating guide and 14 days of handover support. The optional Report Care Plan covers bounded changes and scheduled QA.
What if the scope changes?
A new source, output family, regulated calculation, migration or materially different report becomes a separate estimate.
How quickly can we start?
After the fit check and paid diagnostic, the sprint is scheduled when the required access, current report, decision owner and project fee are ready.
One report. One reliable workflow.
Show us the report you never want to rebuild again.
You do not need to upload client data. A short description of the report, frequency, inputs and time spent is enough to start.
Book a 15-minute report fit check
Limited weekday slots · no obligation · no public file upload