PsTally.
A multi-tenant SaaS built on WordPress Multisite for managing gaming lounges — sessions, staff, shifts, credit, and daily operations, all in one place.
Gaming has always been one of my hobbies. At some point I decided to turn that into a business and opened a game lounge. It was my first business, and I went into it with very little experience on the operational side.
What started as something I enjoyed quickly turned chaotic. Constant disagreements with staff over shifts. Cash discrepancies at the end of every day. Customers underpaying for the time they had actually played. Small problems that kept piling up until managing the lounge started eating all the time that should have gone into running it.
I was spending most of my time resolving disputes instead of building a business. Something had to change.
As a developer, my first instinct was to look for something that already existed. I searched for a POS system, a management tool, anything that could bring order to the business. I found nothing that truly addressed the problem — not even partially.
What I found instead was that most gaming lounges were running on notebooks. Handwritten tallies. End-of-night mental arithmetic. Many owners had simply accepted the chaos as part of the job.
They had not accepted it because there was a better way. They had accepted it because there was no other way.
That realisation changed the question. It was no longer about finding a tool. It was about whether I was the right person to build one.
The business was already running. I could not pause it to build a full system from the ground up over several months. So I started small and built a WordPress plugin for internal use — something that could manage sales, staff, shifts, and daily operations without disrupting what was already in motion.
That alone changed everything.
Shift disputes dropped to near-zero. The expected till figure was calculated before anyone started counting — no mental arithmetic, no guesswork, no accusations. Staff had the same number the owner had. When a discrepancy appeared, it was named and sized immediately, not discovered the next morning after the memory of the shift had faded.
The close variance settled to between Ksh 0 and Ksh 50 per shift — the natural tolerance of cash handling in an 11-hour day. Anything beyond that was now traceable to a specific session, a specific moment, a specific decision.
The first version did not ship a product. It shipped clarity — and clarity ended the arguments.
As I kept using the system, the same thought kept returning. If I had faced these challenges and solved them in a structured way, then other gaming lounge owners were going through the same thing. The notebook was not a Nairobi problem or a small-business problem. It was an industry-wide gap.
The question became how to turn what I had built for myself into something others could use. I did not want to rebuild everything from scratch. So I looked for a way to extend what already existed.
WordPress Multisite gave each lounge its own contained environment — its own data, its own staff, its own reports — while running on a unified platform. What started as a personal tool became the foundation of a scalable product without having to rebuild everything.
owner dashboard · revenue, sessions, debts, and console performance — one unified view
At the centre of every gaming lounge dispute is the session. A customer sits down, games are played, time passes, and somewhere in that process the record breaks down — either between staff and the customer, or between staff and the owner when the shift does not add up at close.
PsTally handles both time-based and price-based gameplay. Every action within a session is timestamped at the exact moment it happens. Games added, payments taken, session opened, session closed — all of it is recorded automatically, not written down by hand.
staff view · active sessions across bays, timestamps locked at every game added
Session start and end times are controlled by the system, not by memory.
Everything that happens during a shift is tied to the staff member who opened it. At close, the system calculates what should be in the till based on every session and every sale during that shift. There is no mental arithmetic. There is no guesswork. There is a number — and then there is what was actually counted.
The shift close is the moment that used to cause the most conflict. Staff count the till at the end of the night. The owner expects a number. If they do not match, the evening ends in a dispute that no one can resolve because there is no reliable record to refer to.
With PsTally, the expected figure is calculated before anyone starts counting. Staff enter what they found. If it matches, the shift closes clean. If it does not, the discrepancy is immediate — named, sized, and recorded — not discovered the next morning.
The number is not an accusation. It is a reference point. That is all it needs to be.
This protects staff as much as it protects the business. When the system produces the expected figure, the staff member is not being doubted — they are being given the same information the owner has. If there is a discrepancy, everyone knows at the same time, from the same source.
Regular customers are valuable. And in this type of business, relationships matter. A customer who has been coming for two years might ask to play now and pay later. Refusing rigidly damages the relationship. Accepting without a record creates a debt that quietly disappears.
PsTally captures every unpaid balance at the moment the session closes — customer name, phone number, amount owed, date opened. When they come back and pay, the payment logs against the same record. The history is there without any extra effort.
The goal is not to make credit difficult. It is to make sure nothing goes invisible. A lounge that knows exactly who owes what, and for how long, can have the right conversation at the right time.
Gaming lounges generate revenue beyond sessions. Drinks, snacks, merchandise — in my lounge, we sold football jerseys. This revenue exists alongside game time every day, but most systems either ignore it or track it separately, forcing the owner to piece together the full picture at the end of the day.
In PsTally, products are treated the same way as sessions. Set them up once with pricing and optional stock tracking. Staff record a sale the same way they open a session — within the same workflow, no switching between screens. Stock updates automatically if enabled.
At the end of the day, the owner sees one number. Gaming revenue and product sales, unified.
Everything feeds into the shift reconciliation. The expected till figure includes product sales. Nothing is left outside the calculation.
Gaming lounges close late. Owners are not always there, and logging into a dashboard at midnight to check how the day went is not a realistic expectation. I experienced this personally — the business ran late, I needed visibility, but I also needed to sleep.
At the close of each shift, staff can send a summary directly to the owner’s WhatsApp. Not a notification that a report is ready. The report itself — sales figures, cash reconciliation result, any discrepancies — in plain language, on the owner’s phone, before anyone has to ask.
The owner knows how the day went before the lights go off.
The result was simple but significant. The arguments stopped. The confusion reduced. I finally felt in control of a business I had started with the intention of enjoying.
PsTally is not about surveillance or adding complexity. It is about removing uncertainty from a business type that has historically operated without the tools to do so. Every session tracked, every shift closed cleanly, every credit balance visible — these are not features. They are the conditions under which a gaming lounge can actually be run rather than just managed.
Building it taught me something I still think about. Just as people adapt to their environment, systems must evolve based on how they are used. PsTally started as a survival tool. It grew into a platform. It continues to evolve. But its purpose has not changed — to give lounge owners the clarity they need to run their business instead of being run by it.
The lounge needed clarity, not surveillance. That is still what PsTally delivers.
Three architectural choices that shaped how the system thinks.
Each session is tied to the shift that opened it at the database level. When a staff member ends their shift, the system calculates the expected till only from sessions they personally owned. No amount of client-side manipulation can expose another staff member’s sessions or pull them into the wrong reconciliation.
This came from a real incident where two staff members were logged in simultaneously and sessions were bleeding across shifts, creating discrepancies that neither person had caused. The fix was not a UI patch — it was enforcing ownership where it cannot be bypassed.
98% of the 882 sessions tracked so far are per-game, not time-based. That ratio did not come from a product decision — it came from watching how customers in this lounge actually think. They ask for two games, not twenty minutes. A time-based system would have introduced a mental model that did not match how transactions were already happening, creating friction at the point of payment.
The software modelled the customer’s mental model, not an imported one.
The system does not smooth over gaps. Every shift closes with an exact figure: what was expected, what was counted, and the difference. The target is Ksh 0–50 — the natural tolerance of cash handling across an 11-hour shift. Anything beyond that triggers a session-level audit trail.
A system that rounds to zero would feel cleaner but would hide the information that matters. Visibility is the product. The number is not an accusation — it is the beginning of an honest conversation.
If this way of building resonates —
No brief required · Tell me what you’re trying to make
What came next
The platform that ended the arguments was rebuilt from the ground up — with the GTM layer engineered in.
PsTally Rebuilt →