HR Foundation Package for ERP software providers
What this looks like in your business
An ERP provider that has grown by winning projects has people on client sites, a few developers, a support desk and a founder who still approves leave. The Foundation Package gives that business its first working HR system: a handbook that speaks to consultants and support engineers, five core processes written as one-page documents, standard letters, first records and a simple report. Owners reach for it when the third or fourth implementation is running, nobody can say who is on which site, and every go-live weekend creates a new argument about time off.
Why a project firm needs the basics first
In a firm that sells and installs systems, HR basics are missing because every hour has gone to delivery. Consultants were hired by the project manager who needed them, with an offer written in an email. Developers joined on the same terms as a friend of the founder. Nobody wrote down what a consultant should do when the client asks for something outside the statement of work, or who approves a weekend of cut-over work. The result is that every new rule is invented in the middle of a go-live, when people are tired and the client is watching. Support engineers have a rota that exists only in a chat group. Data migration specialists wonder whether their work counts for anything. Pre-sales consultants promise start dates that delivery learns about later. A foundation is not a long project. It is the small set of agreed written things that stops the same disagreement from being held again for each client, and gives a new project manager something to read on the first morning. Each section is read aloud with the delivery head, to catch wording nobody would use.
What goes into the first handbook
GullyHR begins by asking how your projects really run, then writes the handbook around that. Sections cover working at a client site, including conduct, use of client systems and the care of client data; how a go-live weekend is planned, recorded and followed by time off; how change requests from a client reach the project manager before a consultant says yes; how the support rota works and who covers it; and how a consultant's notes are left behind when they move to another client. The five core processes are chosen with you and are normally joining, project assignment and site check-ins, leave and time off after cut-over, appraisal, and exit with a handover of client knowledge. Each is one page, with an owner, a trigger and a record. Before handover, each is tested on a real case, such as the last consultant who joined or the last weekend worked. Standard letters follow: appointment, project assignment and exit, each with a short note on when to use it. Your legal adviser reviews the letters before use.
Suppose a founder holds the first workshop
Suppose a founder runs an ERP partner with two project managers, eight consultants, three developers and a small support team. She agrees the scope with GullyHR in writing, then sits in a first working session with the delivery head. Together they pick the five processes. They decide that project assignment is the first to write, because three consultants are on client sites and no document says who approved the arrangement or when it ends. GullyHR drafts a one-page assignment process: the project manager completes a short assignment note, the founder approves it, the consultant receives a letter naming the client site and the review date, and HR keeps the note in the employee file. The process is tested on a consultant starting the following week, and the delivery head finds the note needs a line for travel arrangements. It is added. Only then does GullyHR move to the leave and cut-over process. The founder's decision is to keep the weekend time-off rule modest and clear, rather than perfect, so managers can actually use it.
Roles, records and what stays with you
Handover is where a foundation stands or falls. GullyHR names who owns each process and where its record sits, then walks those people through the documents. In an ERP firm the delivery head owns project assignment and the go-live effort note, project managers complete them, the founder or office manager holds employee files, and the support lead keeps the rota and the log of cover. The first HR records are an employee file for each person, a module skills list, a project assignment register and a leave record. The simple report, on a schedule agreed in writing, lists headcount by team, who is on which site, open roles and leave balances, so the founder sees the picture without asking five people. Standard letters and templates are written so managers can use them without calling GullyHR. What stays with you: pay decisions, the choice of what to adopt, and any legal question, which your own adviser answers for your country. The handbook is yours to run after handover. The first report is built from those same records, not from a separate spreadsheet.