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.