§1Case CS-03
Shops. $903 a month. Sample case, fictional client. Photos show our engineer at the stock room cabinet and at a back-room fix.

Client | Bike shop, 7 people |
Monthly bill | $903 a month |
How it adds up | 7 people × $129 |
Time to switch | 4 days |
Result | Card readers on their own network, demo sample |
On busy Saturdays the card readers kept dropping out. They shared the Wi-Fi with customers waiting on repairs, and the owner took cash and hoped for the best.
Sam put the card readers on their own network and the customers on another. The till software caught up on a year of updates, and each member of staff got a login.
A small shop with a simple setup, so the switch took four days. All 12 issues closed, and the first Saturday afterwards passed without a dropped payment.
§2Client note
I used to dread a sunny Saturday. Now the only queue in the shop is for the bikes.
Card readers on their own network
Customer Wi-Fi kept apart
A login for each member of staff
§3Day by day
Sample timeline. The last column counts the issues still open.
When | Step | By | Open issues |
Day 1 | Visit after closing, tills, readers and Wi-Fi listed | Yuki | 12 |
Day 2 | Card readers moved to their own network | Sam | 6 |
Day 3 | Till software updated, security on | Erik | 2 |
Day 4 | Switch done. Team meets us before opening. | Meera | 0 |
After the switch | |||
Week 2 | First full Saturday, no dropped payments | Meera | 0 |
Quarterly | Plain review with the owner | Erik | 0 |
§4What we found
Area | Issue | Closed |
Network | Card readers shared the customer Wi-Fi | Day 2 |
Tills | Till software a year behind on updates | Day 3 |
Accounts | One till login for all seven staff | Day 4 |
The other 9 issues stay in the shop's own list.

First visit | 12 |
Closed | 12 |
Open at the end | 0 |
§5More cases