HR Foundation Package for Cybersecurity companies
What this looks like in your business
A young security firm can win clients on skill alone for a surprisingly long time, with no handbook, no joining checklist and a rota that lives in one lead's head. The Foundation Package suits the owner who now has analysts on night shifts, testers on client sites and a governance team writing for auditors, and who needs the basics written down once. GullyHR drafts the handbook, writes five core processes, prepares standard letters, sets up first records and tests each piece with your managers before handing it over. The aim is that a new team lead can run a shift change or a joining without calling the founder.
Why a growing security firm lacks the basics
Security firms grow around expertise. The founders are testers, responders or auditors, and the first hires are people they trust and have worked with before. That works until the team passes the size where everyone hears everything. A new analyst joins the monitoring floor and nobody has told her what the escalation chain is or how swaps of night shifts are agreed. A tester returns from a long client engagement and no one knows whether time off is owed. A consultant joins the governance group and signs confidentiality terms weeks after starting, because no one owned the joining steps. The handbook, if one exists, was copied from a larger company and talks about a canteen and an office the firm does not have. Meanwhile, clients and auditors ask how staff are vetted by the firm, how access is removed at exit and how conduct is enforced. Without a foundation, each question is answered from memory, differently by each director. The package exists to replace memory with a short, tested set of documents.
What GullyHR sets up first
GullyHR begins by listing what your firm already does, whether or not it is written down. That means reading any existing offer letters, the confidentiality terms staff have signed, the current rota, and whatever your delivery managers use to record leave and client time. From that list it chooses the five processes that cause most confusion in a security setting. For most firms of this kind they are joining, leave and rest after incidents, shift and on-call cover, confidentiality and conduct, and exit with access and material returned. Each process is written as a single page naming who does what, in what order, and on which record. The handbook is written in your firm's own voice and covers the roles you really have: monitoring analysts, testers, consultants, pre-sales engineers and project managers. Standard letters cover offer, confirmation, warning and exit. First records are a staff register with dates of signed terms, a leave tracker and a simple monthly report. GullyHR keeps each page short enough to be read at a desk before a shift starts, because a process nobody opens protects nobody.
Testing the exit process with a real case
Picture a firm of about thirty people with a monitoring team, a testing team and a small governance group. GullyHR drafts a one-page exit process and, before handing it over, tests it with the delivery manager on a real recent leaver, a tester who resigned for a rival. The manager walks the page step by step. The page says the line lead collects client reports and working notes, the owner confirms no client data remains on the tester's laptop, and the person who keeps the staff register reminds the leaver in writing of the confidentiality duties that continue. In the walk-through the manager notices nobody is named to remove access to client portals. GullyHR adds a step, names the delivery manager as owner, and adds a line to the exit letter. The page is then handed over with a short note on when to use it. The decision to accept or reject the tester's resignation date, and any release from notice, stays with the owner. The tested page and the corrected letter are filed in the first records, so the next leaver follows the same steps without anyone reconstructing them.
Roles, records and what stays with you
When the package is handed over, each document needs an owner, or it will drift. The owner or a director keeps the handbook and issues each revision. The person who looks after joining holds the staff register and checks that signed confidentiality terms are in place before a first shift or first client visit. Shift leads keep the rota and record swaps, and the incident lead records rest taken after a major engagement. Delivery managers use the standard letters and file copies in one place. GullyHR hands over templates your managers can use without help, and a short note on which situations need the owner, such as a warning or a pay change. What stays with the owner is every people decision: who is hired, how much they are paid, who is warned and who leaves. The handbook and letters go to your own legal adviser before issue, because local rules differ. GullyHR writes, tests and hands over. After that the documents belong to your firm. None of this needs software at the start: a shared folder, one register and a monthly report on a schedule agreed in writing are enough.