Skip to main content
GullyHR

HR process design · E-commerce software providers

HR Foundation Package for E-commerce 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 E-commerce software providers

What this looks like in your business

The HR Foundation Package fits an e-commerce software company that has outgrown the founder's memory. Engineers, merchant support agents and onboarding specialists now work from different understandings of paging duty, leave before a sale, notice and what a new starter should receive on day one. The founder reaches for the package when a sale day exposes the gap, or when the first senior hire asks for a handbook and there is none. GullyHR writes the handbook, five core processes, standard letters, first records and a simple report, tests each with real cases from your team, and hands them over on an agreed schedule and fee.

Why informal arrangements stop working here

Early in a software company, people agree things in chat. An engineer will cover a weekend watch, a support agent will swap a shift, a new merchant specialist will learn by shadowing a colleague. That holds until the team is large enough for two people to remember an arrangement differently. In an e-commerce platform business the first cracks show around sale days. Nobody wrote down who must be reachable, who may take leave in the weeks before a promotion, or what a person gets for a night spent on a live incident. On-call duty settles on the few engineers who never refuse. Onboarding specialists run merchant launches from memory, so quality varies by person. Support and engineering argue because the line between them was never drawn on paper. New starters, including front-end and integration developers, guess what is allowed with merchant data and access to live stores. A foundation package does not add bureaucracy for its own sake. It records the decisions you already make, once, in language a new engineer or agent can read on the first day, and it gives each manager one page to point to when a question comes up in the middle of a busy week.

What goes into the handbook and first records

GullyHR begins with what your business already does, read from chat threads, offer letters and the way your last few hires were brought in. The handbook is written for a platform company: working hours and cover across time zones for support, standby and paging rules, the weeks around sale days, conduct with merchants and partner agencies, care of merchant data, and how concerns are raised. The five core processes are chosen with you, and for this kind of business a likely set is joining, leave and the sale-day calendar, standby cover, probation review, and exit with handover of merchant accounts and access. Each is a one-page document with a named owner. Standard letters cover offers, confirmation and exit. The first records are a single sheet per person holding the signed letter, role description and agreed changes, plus a simple monthly report showing headcount, leave booked and open roles. Nothing is handed over until each process has been tried. GullyHR also keeps a short list of choices still open, such as the exact wording on standby time off, so that nobody mistakes a draft for a decision made by the founder.

Testing the leave process before a promotion

Suppose a marketplace software provider is three weeks from the busiest promotion its merchants run. Asha, a merchant support agent, asks for leave in the same fortnight, and so does Ravi, a back-end engineer on the standby rota. Under the draft leave process, the manager checks the sale-day calendar the foundation work produced, sees that the support floor is already at its minimum cover for the promotion week, and declines Asha's dates with a written reason and an offer of the week after. Ravi's request goes to the engineering lead, who finds that two other engineers can cover standby and approves it. GullyHR watches this real case, notes that the manager did not know where to record the decision, and adds a line to the process and a field to the leave record. The founder then chooses whether the minimum cover rule is firm or can be waived in a family emergency, and the answer is written into the handbook. Only then is the process marked tested, and the next one is tried on a real case in the same way, so nothing reaches your managers that has not already worked once in your own company.

Owners, records and what stays with you

A foundation is useful only when each document has a person who keeps it alive. Settle who owns the handbook, probably the founder or an operations lead, and who owns each of the five processes. Engineering leads should own standby cover and the engineering side of joining and exit. The head of support should own leave cover for support agents and the sale-day calendar. Settle where records live, who may open them, and how a manager reports a change in role or pay so that it reaches the person's file. Settle the handover of letters to your own adviser before the first one is issued. GullyHR writes, tests and hands over the set, and trains your managers to use the letters and one-page processes unaided. Decisions on pay bands, promotions, the cover rule and every actual hire or exit stay with you. Where a clause touches employment law in your country, your own adviser confirms it before the handbook is issued. Settle also the interval at which each section is read again, so that the handbook keeps pace with the platform as it grows and changes.

The first weeks

  1. 01

    Meet the founder and heads of engineering and support to list how paging duty, leave and joining are handled now, and what was never written.

  2. 02

    Collect offer letters, role descriptions and recent chat agreements, and compare them for gaps and contradictions before any handbook text is drafted.

  3. 03

    Draft the handbook sections on standby, sale-day leave and merchant data, and review each with the managers who must apply it.

  4. 04

    Write the five core processes as one-page documents, each with a named owner, and run one real case through each, such as a recent joiner.

  5. 05

    Hand over the letters, first employee records and simple report, and walk the managers through using them without GullyHR present.

The operating context

Build the minimum HR structure in a usable sequence

An e-commerce software provider builds platforms and tools that let merchants sell online. Here is how to manage engineers, merchant support and onboarding teams whose busiest day is when their customers hold a big sale.

Platform and back-end engineersFront-end and theme developersIntegration and plug-in developersMerchant onboarding specialistsMerchant support agentsQuality and release 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: Platform and back-end engineers, Front-end and theme developers, Integration and plug-in developers.

Records to prepare

Baseline inventory, implementation plan and accepted foundation documents. A workforce issue to consider: Agency managers handle demanding partners with unclear rules on who gets help first.

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.

  • Hosted storefront platforms for small D2C brands
  • Multi-vendor marketplace software for niche marketplaces
  • Headless commerce and API-first platform providers
  • Order, inventory and warehouse management tools for online sellers
  • Marketplace listing and multi-channel sync software
  • Theme, plugin and app developers on top of larger platforms

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

If more than a few people rely on your arrangements, yes, though it stays short. The handbook covers only what your team meets: standby, leave around promotions, conduct with merchants and data care. GullyHR writes it in plain language, so a new engineer or support agent can read it on day one. You agree scope and fee in writing first, and nothing is padded with sections your business has no use for.

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