HR Foundation Package for POS software providers
What this looks like in your business
A POS provider that grew from a few developers and a hardware reseller into a team of installers, support agents and trainers has no written HR at all. People were hired by a founder's phone call, and each manager invents rules for leave, visits and overtime. The HR Foundation Package gives such a business its first working basics: a handbook that describes field engineers and support agents, a small set of tested processes, standard letters and a first set of records. Owners reach for it when the next hire will report to someone other than the founder, or when two teams disagree about who owns a till fault.
Where unwritten HR starts to cost you
In a young POS company the founder is the policy. That works until the field team spreads across several cities and the support desk runs shifts through the busiest trading hours of shops, restaurants and pharmacies. Then questions arrive that nobody has answered in writing. Does a visit that overruns into the evening earn time off? Who approves a developer's weekend work after an update breaks shop setups? How long does a new support agent shadow calls before answering a shop owner alone? Without answers, each manager decides differently, and the engineers compare notes. Hardware and software teams already blame each other over faults, and unwritten rules give that blame somewhere to live. Training is thin because nobody has written what a trained installer or trainer must be able to do. The foundation package replaces these private decisions with a short, agreed set of public ones, so a new joiner in any role can find the rule and a manager can apply it the same way each time. The package is meant to end that pattern before the team doubles in size and the habits harden into unwritten custom that is difficult to undo.
The sequence for building the basics
GullyHR would first take a baseline inventory: who works for you, in which role, under what terms, and which documents already exist. For a POS provider that means developers, quality testers, installation and field engineers, hardware technicians, support agents, trainers and sales executives, each with their own working pattern. We then settle the decisions that block drafting. Is support on a roster or on call? How are field visits recorded? Is there a release freeze? Only then do we write. The handbook speaks to your teams in your terms, covering shifts, visit days, leave around festivals and the handling of customer equipment. Five core processes are written as one-page documents, for example joining, leave and attendance, field visit recording, fault escalation between hardware and software, and exit. Each is tested with a real case from your business before handover. Standard letters follow, together with a first set of HR records and a simple report on the schedule agreed in writing. Throughout, we keep each document short enough for a field engineer to read on a phone between visits, because a long handbook that nobody opens does not settle any dispute.
Testing the fault escalation process
Suppose the escalation process is one of the five. A restaurant owner calls at lunch because the kitchen printer has stopped after an update. The support agent opens a ticket. The draft process says the agent checks the cable and driver steps, and if the printer still fails, sends it to a hardware technician within a stated time; if the fault follows the update, it goes to a developer with the ticket and release number. We test it against last month's real printer fault. The test shows that the ticket had no field for the release version, the hardware technician was never told the shop was a restaurant at peak, and the developer saw the ticket the next morning. We add the field, add a trading-hours flag, and name who confirms the fix to the shop owner. The process is rewritten before handover, so what you receive has already met a real case. Your support lead then approves the final one-page version before it is issued. You see the failed test and the fix in the handover notes, so the reason for each field is visible to the next person who edits the process.
Roles, records and what stays with you
A foundation package ends with names against tasks. You would name one person for employee records, one for each process, and one approver for letters. In a business of this kind that means the support lead owns the rota, an operations head owns visit logs and the founder or a senior manager owns offers and pay. We record where each file lives, who sees personnel files, and how a new joiner receives the handbook and standard letters. The first HR report is simple: headcount by role, joiners, leavers, open roles and leave taken, on a schedule agreed in writing. Choices about pay, promotion, hiring and any dispute remain yours. Letters and policies that touch employment law go to your own legal adviser before issue, because GullyHR does not give legal advice. We hand over documents your managers can use unaided, and we do not run payroll or file returns. Everything is stored where you can open it yourself, with a short note on how each record is updated, so the work does not depend on GullyHR remaining involved after the handover. Reviewing the first report together closes the engagement.