Skip to main content
GullyHR

HR process design · POS software providers

HR Foundation Package for POS 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 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.

The first weeks

  1. 01

    List every employee by role and working pattern, and gather the offer letters, visit logs and rota that exist for developers, engineers and agents.

  2. 02

    Agree with the founder who approves leave, overtime, field visit claims and weekend release work, and write each approver against each decision.

  3. 03

    Draft the handbook sections on shifts, field visits and festival-week cover, and read them aloud with one support agent and one engineer.

  4. 04

    Write the five one-page processes, starting with fault escalation, and test each against a real ticket or visit from the last month.

  5. 05

    Hand over standard letters, the first employee records and the simple report, and walk each manager through using them without help.

The operating context

Build the minimum HR structure in a usable sequence

A POS software provider sells billing systems to shops, restaurants and chains, and supports them when the till stops. Here is how to manage developers, installers and support teams who are called at the busiest hours of their customers' day.

Software developersInstallation and field engineersHardware support techniciansSupport desk agentsTrainers and onboarding staffQuality testers
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: Software developers, Installation and field engineers, Hardware support technicians.

Records to prepare

Baseline inventory, implementation plan and accepted foundation documents. A workforce issue to consider: Engineers cover several shops a day with travel, tools and spare parts, and little time for each fix.

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.

  • Retail shop billing and inventory software
  • Restaurant, cafe and cloud kitchen POS
  • Pharmacy billing with batch and expiry tracking
  • Salon, spa and clinic appointment and billing software
  • Supermarket and grocery POS with weighing scale support
  • Multi-store and franchise POS with central reporting

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

We begin with a plain list of who works for you, in which role and on what terms, plus any documents that already exist. From that baseline we settle the decisions that block writing, such as how support is rostered and how field visits are recorded. Only then do we draft the handbook and processes. You do not need to prepare anything beyond sharing what you have.

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