Structured workbook
Tables and named ranges instead of a fragile shared file.
Sample case study
Dummy Case Studies
A placeholder story you can duplicate. Replace this copy in WP Admin — the layout stays the same for every new slug.
12 hrs/week
Time saved (sample)
40+
Errors caught
Week 3
Handover
4 people
Team trained
The story
What the client was facing
This is dummy copy. A mid-size team was closing the month in five shared workbooks. Someone copied totals by hand every Friday. Errors showed up in the Monday meeting, and one person was the only one who knew which tab was “real.”
How our services saved time and cost
We scoped a small Excel engagement instead of a new system. Dummy numbers: about 12 hours a week came back to the analysts, weekend overtime stopped, and they no longer paid a contractor to “fix the file” after every close.
How we automated the process
Tables, named inputs, and a refresh path replaced the paste ritual. A short walkthrough meant a second person could run the pack. Edit this story in WP Admin → XL Automation → Case Studies.
What you get
What this sample delivered
Dummy outcomes so you can see the cards. Swap them for a real engagement.
Refresh path
A Monday routine the intern could run without a call.
Checks
Dummy validations so errors show before the meeting.
Walkthrough
A short session recorded as the handover note.
Owner named
One internal contact, not a rotating inbox.
Files they keep
No lock-in. The sample assumes they own the workbook.
Why this engagement
The challenge (dummy)
Typical reasons a team would open a case study page. Edit freely.
Close overran every month
Dummy finance team spent three days reconciling five workbooks.
Nobody trusted the pack
Two versions of “revenue” in the same email thread.
Only one person could update it
Leave coverage meant the Friday pack slipped.
No audit trail
Numbers moved and nobody could say why.
Training never stuck
A previous vendor left a 40-tab file and no notes.
Needed a first page
This slug exists so you can see the template before writing a real study.
How we work
How the dummy project ran
Same six steps as a live delivery. Change the wording per study.
Discover
Mapped the outcome, sources, and who would own the file after handover.
Propose
A written plan, timeline, and price before any build started.
Build
Short sprints with working files the client could review weekly.
Test
Real close / reporting scenarios with the people who run the process.
Handover
Documentation, a walkthrough, and access their team kept.
Support
A defined window for fixes as the data or team changed.
Client stories
What the dummy client said
We would publish this page once the names and numbers are real. The layout is what we needed.
The intern refreshed it on Monday without us. That was the test.
Clear weekly files. No big reveal at the end.
Help centre
Frequently Asked Questions
Is this a real client?
No. Dummy Case Studies is a seeded sample. Replace the copy in XL Automation → Case Studies.
Can I keep this slug?
Yes, or add a new slug and unpublish this one by clearing the title / hiding sections.
Will a new study look like this?
Yes. Add case study in admin uses this same template.
Where does the hub list this?
On /case-studies/ with the other catalogue cards.
Replace this dummy story with yours
Edit this page in WP Admin, or add a new slug and leave this sample in place.
Contact us