Skip to main content
GullyHR

HR process design · ERP software providers

HR Foundation Package for ERP software providers

The HR Foundation Package is a fixed-scope engagement for a business with no real HR system yet. On a schedule agreed in writing, GullyHR writes, tests and hands over an agreed set of basics: an employee handbook, five core processes, standard letters, first HR records and a simple report. Scope and fee are agreed in writing before the work starts.

Colleagues organising HR folders and reviewing a setup plan.

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.

The first weeks

  1. 01

    Agree scope and fee in writing, then hold a first session with the founder and delivery head to list current projects and people.

  2. 02

    Choose the five core processes, with joining, project assignment and exit with handover of client knowledge almost certain to be among them.

  3. 03

    Draft the handbook sections on client-site conduct, go-live weekends, change requests and the support rota, and review them with project managers.

  4. 04

    Write the standard letters for appointment, project assignment and exit, then send them to your legal adviser before any manager uses them.

  5. 05

    Test each process on a real recent case, set up employee files and the project assignment register, and hand over the first monthly report.

The operating context

Build the minimum HR structure in a usable sequence

An ERP software provider sells and installs systems that run a client's finance, stores, production and people. Here is how to manage functional consultants, developers and support teams through long, demanding client projects.

Functional consultants (finance, supply chain, production)Technical developers and report writersData migration specialistsImplementation project managersTrainersSupport and maintenance engineers
A developer discussing career progression with an engineering manager and HR partner

The decision to work through

Prioritise employee records, essential policies, role ownership and recurring processes around the starting workforce. Workforce to consider: Functional consultants (finance, supply chain, production), Technical developers and report writers, Data migration specialists.

Records to prepare

Baseline inventory, implementation plan and accepted foundation documents. A workforce issue to consider: Teams work long hours around cutover, then return to normal work with no time to recover.

An exception to test

Check which missing decisions block the next step and separate setup work from ongoing transaction handling.

Which parts of your business should the scope cover?

The right workforce and approval structure depends on the operations you run. Confirm which of these apply, and whether they share one HR process.

  • ERP implementation partners for SAP Business One, Odoo or Microsoft Dynamics
  • Tally partners selling add-ons and customisation
  • Zoho partners and implementation consultants
  • Industry-specific ERP product companies
  • ERP providers for pharma and retail distribution
  • Manufacturing ERP and MRP software vendors

When to consider this service

  • Each manager joins, approves leave and confirms probation in their own way, and you only hear about the difference when two employees compare notes.
  • The appointment letter is a file copied from a former employer, and nobody is sure which version is current.
  • Month-end payroll starts with a scramble to find who joined, who left and who took unpaid leave.
  • You have no handbook, so every question about notice, holidays or conduct is answered from memory and sometimes answered differently.

Businesses this service is designed for

  • Founder-led businesses of roughly 20 to 100 people where HR has so far been handled by the founder, an admin manager or an accountant.
  • Companies that have grown past the point where one person's memory can carry hiring, leave and payroll inputs.
  • Businesses preparing to hire a first HR manager, who want a working base for that person to inherit.
  • Companies with several managers who each handle people matters in their own way and want one consistent method.

What we design

GullyHR does the drafting, testing and handover; you decide how your business wants to run. We start from what you do today, write the agreed basics in plain language, try each one on real cases from your own team, and correct it before it is handed over. You give us access to your people, current documents and decisions on policy. The work is a defined package with a scope agreed in writing, a mid-point review and a handover session. It is not open-ended consulting, and anything outside the agreed list is scoped separately. Where a document touches employment law, we flag it for review by a qualified professional rather than giving a legal opinion.

An employee handbook written for your business, not copied from another.

Working hours, holidays, leave, conduct, notice and the everyday rules are set down in plain language, using the decisions you make with us. Points that depend on law are marked for confirmation with a qualified professional.

Five core processes written as one-page documents.

Joining, attendance and leave, monthly payroll input, probation and confirmation, and exit. Each page shows the steps, who does each one, what gets recorded and when the document will next be reviewed.

Each process is tested before it is handed over.

We run every process on real or recent cases from your team, such as a recent joiner or a leave request, and see where it breaks. The page is corrected after the test, not before it.

Standard letters and templates your managers can use unaided.

Appointment, confirmation, warning, relieving and the other letters you actually send are drafted once, in a consistent form, with clear fields to fill. Legal wording is flagged for professional review.

A first set of HR records and a simple report on a schedule agreed in writing.

An employee master, a leave record, an exit record and a probation tracker are set up, along with a short monthly set of figures such as headcount, joiners, leavers and open confirmations.

From current practice to a working process

Walk through the present process with the people who run it. Identify the trigger, missing information, decisions and exceptions before drafting the future workflow.

  1. 01

    Weeks 1 and 2: baseline

    We agree the scope in writing, collect your current documents and speak to the people who do the work. We write down how each of the five processes runs today and list what is missing, so the starting point is clear to everyone.

  2. 02

    Weeks 3 to 5: decisions and first drafts

    We bring you a short list of policy decisions to make, such as leave types, notice and probation length. Once you decide, the first drafts of the handbook, process pages and letters are written.

  3. 03

    Weeks 6 and 7: testing on real cases

    Each process is run on recent or live cases with the people who will use it. We note every point where it hesitates, a missing step or an unclear owner, and fix it.

  4. 04

    Week 7 or 8: mid-point review

    A review with you on what is written, what has been tested, what is slipping and what has changed. Scope changes, if any, are agreed in writing at this point rather than assumed.

  5. 05

    Weeks 8 to 10: records and reporting

    The first HR records are set up and filled from your existing information, and the recurring reporting set is built and run once on real data, so the first report is seen before handover.

  6. 06

    Weeks 11 and 12: manager briefing and refinement

    The people who will run each process are briefed on their part. We make final corrections from what they find and from the first live use of the documents.

  7. 07

    Week 13: handover

    A handover session covers each document, who owns it and when it is next reviewed. You receive everything in editable form, with a short note on what to look at in the next quarter.

Test normal and exception cases with the process owner, record changes, and agree acceptance before handing responsibility to the internal team.

The tools your team takes over

  • An employee handbook written for your business, with law-dependent points marked for professional confirmation.
  • Five one-page process documents covering joining, attendance and leave, monthly payroll input, probation and confirmation, and exit, each with an owner and a review date.
  • A record of the test run for each process, showing what was tried and what was corrected.
  • A set of standard letters and templates for the stages you actually use.
  • A first set of HR records: employee master, leave record, probation tracker and exit record.
  • A simple reporting set with a short note on how to read and use it.
  • A responsibility sheet showing who in your business owns each document and each step.
  • A handover session with the people who will run the processes.

What your team provides

  • Access to the people who run joining, leave, payroll input, probation and exit today, for short conversations.
  • Your current documents, letters and records, even where they are rough or incomplete.
  • Decisions on policy points that only you can take, such as notice terms and leave entitlements.
  • Real cases from your own team to test each process against, shared in confidence.

Share personal records only after the scope, access and handling arrangements are agreed.

Responsibilities and approvals

The client owns employee records and approves policies, spending and employment decisions. GullyHR's assigned responsibilities are documented in the engagement.

Scope and plan

GullyHR
Proposes the scope, the 90-day plan and the dates for the mid-point review and handover, and records them in writing.
Your team
Confirms the scope, names one point of contact and keeps the review dates in the diary.

Policy decisions

GullyHR
Lists each decision needed, sets out the options and says what other businesses of your size commonly do.
Your team
Makes the decisions promptly, since drafting waits on them.

Drafting

GullyHR
Writes the handbook, process pages, letters and templates in plain language.
Your team
Reviews drafts, corrects facts about how the business really works and approves the final versions.

Testing on real cases

GullyHR
Runs each process on live or recent cases and records what needed to change.
Your team
Provides cases, makes the managers and staff involved available and shares the records needed.

Records and a report on an agreed schedule

GullyHR
Sets up the first records, loads your existing information and builds the report format.
Your team
Supplies employee information, confirms its accuracy and keeps the records updated after handover.

Employment law points

GullyHR
Marks every point that depends on law and coordinates review by a qualified professional where you ask for it.
Your team
Engages its own legal adviser, or asks GullyHR to arrange the coordination, and decides what to adopt.

Measures to agree before work starts

These are measures to track against your baseline, not promised results. Agree definitions, record sources and review dates at the start.

  • Processes written and tested
  • Processes with a named owner
  • Processes with a review date
  • Letters and templates in use
  • Employee records complete
  • Report produced on the agreed schedule
  • Handover session completed

Tools and implementation dependencies

The records and the report can be kept in a spreadsheet you already own, and that is a perfectly sound way to start. If you want them held in software, the employee master, leave record and attendance data can be set up in GullyHR's HRMS software, because the process pages already name the fields, owners and approvals the software needs. That decision is yours and is made after the processes are settled, not before. Nothing in the package requires you to buy software.

Read the full HR foundation package service guide →

Agree the engagement before work starts.

The standard package

The full set described on this page, run over about 90 days against a scope and fee agreed in writing before work begins.

Package with a software follow-on

After handover, the records and processes are set up in HR software as a separately scoped piece of work, built from the pages already written.

Package with ongoing support

After handover, a light monthly arrangement through fractional HR management to run, review and refresh the documents as the business changes.

Package after a process review

For businesses that have already seen a process audit, the package starts from its findings instead of repeating the baseline.

Scope and exclusions

  • The written scope defines the process, templates, testing and handover included. Continuing transaction handling and additional systems work are agreed separately.
  • You already have written processes and want them reviewed rather than rebuilt; the HR Process Audit rates what exists.
  • You need one process fixed, not five; a single process design project is smaller and quicker.
  • You are a very small team not yet hiring regularly; a sector starter pack gives you the basics without the 90-day programme.
  • You want someone to run HR for you rather than hand it over; outsourced HR management does that.
Confidentiality, specialist review and accountability

Limit access to the records needed for the agreed work. Confirm authorised users, secure sharing, retention and return or deletion arrangements before exchanging personal information.

Applicability depends on locations, workforce arrangements and the issue under review. Confirm applicable requirements with your qualified adviser before adopting policies or employment actions; this service is not a legal certification.

Employment-law opinions, statutory filings, professional or clinical standards and safety-critical technical decisions require the appropriate qualified professional; include those dependencies in the scope.

Questions before you decide

No. GullyHR writes it from how your projects, client sites and support rota actually work. Sections on go-live weekends, change requests and client data are drafted from your own practice, then tested with your project managers. Plain language is the aim, so a new consultant can read it on the first day. Your legal adviser reviews the final text for your country before it is issued.

Discuss this process

Tell us the teams and locations involved, what is happening today and what you want this work to resolve.

Start with your business need

What does your HR team need to solve?

Tell us your industry, team size and the issue you want to address. Bring one example of where work gets delayed or ownership is unclear, and the deadline or decision you are working towards.

  • A free first conversation with an HR practitioner
  • A clear scope and fee before any paid work
  • A practical next step for your business

Let’s start with your business

Share your contact details and the HR challenge on your mind. We’ll help you find the right starting point.

Include your country code, for example +44 or +1. Indian numbers can be 10 digits.

Your details stay private. Privacy policy