HR Foundation Package for Accounting software providers
What this looks like in your business
An accounting software provider that has grown from a founder and a few developers to a team with testers, trainers and a support desk has people records in spreadsheets and rules in the founder's head. The HR Foundation Package is for that moment. GullyHR writes a handbook, five core processes, standard letters, first HR records and a simple report, each tested before handover. In a business like yours, that means the handbook speaks to seasonal support agents and domain experts as well as developers, and the processes cover the crunch weeks when rule changes land.
A handbook written for crunch weeks, not copied
A handbook copied from a generic template fails in an accounting software company on the first filing deadline. It says nothing about extra hours during a release crunch, nothing about time off in return, nothing about how seasonal support agents are brought in or how long they train before they take calls alone. It describes one kind of employee, when you have developers who sit in sprints, domain experts who are asked questions at any hour, implementation consultants who travel to client sites, and helpdesk agents who work in shifts that stretch when a deadline nears. GullyHR writes the handbook after talking to people in each group, so the leave rules, working hours, escalation lines and conduct expectations fit how the product is really built and supported. Words are kept plain, so a new tester or a reseller manager reads it in one sitting and knows what is expected. Anything touching your country's employment rules goes to your own legal adviser before it is issued. Reseller managers and trainers who visit client sites are covered by the same pages, so nobody is left reading rules written for someone else.
Five processes chosen for how you really work
The five core processes are chosen with you, not fixed in advance, and in this kind of business they tend to be joining, leaving, leave and overtime in release weeks, performance and role changes, and seasonal support hiring. Each is written as a single page that says who starts it, who approves, what record is kept and what happens when someone is away. GullyHR then tests each one. For joining, that means walking a pretend developer and a pretend support agent through every step, from offer to the first week, and noting where a laptop, a training slot or an access request would stall. For leaving, it means walking a domain expert through handover of the rule modules they own. Gaps found in the test are fixed before the page is handed over. The standard letters, offer, confirmation, role change and exit, are drafted at the same time, so managers do not write them from scratch under deadline pressure. Each page also names the record produced at the end, such as a signed offer or a filed handover note, so nothing relies on memory.
Suppose a desktop vendor hires its first trainer
Suppose a desktop accounting vendor with a loyal base of traders has twenty-odd people and has just agreed to hire its first full-time implementation trainer, because partners keep asking for live sessions after each release. The founder has been agreeing terms by phone. GullyHR starts with the foundation records: a single employee file template, a leave and overtime tracker, and a role description for the trainer written with the head of support. The joining process is walked through with the real hire. The offer letter uses the standard template, the first week has a written plan that includes shadowing two support calls, and the partner training calendar is attached to the role. The decision for the founder is whether the trainer reports to support or to product. Both are defensible, and GullyHR lays out what each choice means for the review routine and for who approves travel to client sites. The founder chooses, and the choice is written into the role page. The records template and the training plan are tested on the first hire, so the founder sees them working before the package ends.
Who owns the records once we leave
A foundation is only worth having if someone owns it after handover. GullyHR settles that with you before the work ends. One person, such as an operations or admin lead, keeps the employee files, the leave and overtime tracker and the letter templates. The head of support owns the seasonal hiring process and its training record. The product head owns the list of who holds each accounting rule, which links to the exit process. Managers are shown how to use the standard letters unaided, with a short session for each team. The simple report, sent on the schedule agreed in writing, tells the owner headcount, joiners, leavers and open leave balances, so the first questions about people no longer need a spreadsheet hunt. What stays with the owner is every decision the documents record: pay, roles, who is promoted and what the rules are. If the business later needs a monthly retainer or a policy package, those are separate scopes agreed on their own. Where a letter needs a legal view, your adviser reviews it once, and the approved version becomes the template.