Skip to main content
GullyHR

HR process design · Accounting software providers

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

What this looks like in your business

An accounting software provider that has grown from a founder and a few developers to a team with testers, trainers and a support desk has people records in spreadsheets and rules in the founder's head. The HR Foundation Package is for that moment. GullyHR writes a handbook, five core processes, standard letters, first HR records and a simple report, each tested before handover. In a business like yours, that means the handbook speaks to seasonal support agents and domain experts as well as developers, and the processes cover the crunch weeks when rule changes land.

A handbook written for crunch weeks, not copied

A handbook copied from a generic template fails in an accounting software company on the first filing deadline. It says nothing about extra hours during a release crunch, nothing about time off in return, nothing about how seasonal support agents are brought in or how long they train before they take calls alone. It describes one kind of employee, when you have developers who sit in sprints, domain experts who are asked questions at any hour, implementation consultants who travel to client sites, and helpdesk agents who work in shifts that stretch when a deadline nears. GullyHR writes the handbook after talking to people in each group, so the leave rules, working hours, escalation lines and conduct expectations fit how the product is really built and supported. Words are kept plain, so a new tester or a reseller manager reads it in one sitting and knows what is expected. Anything touching your country's employment rules goes to your own legal adviser before it is issued. Reseller managers and trainers who visit client sites are covered by the same pages, so nobody is left reading rules written for someone else.

Five processes chosen for how you really work

The five core processes are chosen with you, not fixed in advance, and in this kind of business they tend to be joining, leaving, leave and overtime in release weeks, performance and role changes, and seasonal support hiring. Each is written as a single page that says who starts it, who approves, what record is kept and what happens when someone is away. GullyHR then tests each one. For joining, that means walking a pretend developer and a pretend support agent through every step, from offer to the first week, and noting where a laptop, a training slot or an access request would stall. For leaving, it means walking a domain expert through handover of the rule modules they own. Gaps found in the test are fixed before the page is handed over. The standard letters, offer, confirmation, role change and exit, are drafted at the same time, so managers do not write them from scratch under deadline pressure. Each page also names the record produced at the end, such as a signed offer or a filed handover note, so nothing relies on memory.

Suppose a desktop vendor hires its first trainer

Suppose a desktop accounting vendor with a loyal base of traders has twenty-odd people and has just agreed to hire its first full-time implementation trainer, because partners keep asking for live sessions after each release. The founder has been agreeing terms by phone. GullyHR starts with the foundation records: a single employee file template, a leave and overtime tracker, and a role description for the trainer written with the head of support. The joining process is walked through with the real hire. The offer letter uses the standard template, the first week has a written plan that includes shadowing two support calls, and the partner training calendar is attached to the role. The decision for the founder is whether the trainer reports to support or to product. Both are defensible, and GullyHR lays out what each choice means for the review routine and for who approves travel to client sites. The founder chooses, and the choice is written into the role page. The records template and the training plan are tested on the first hire, so the founder sees them working before the package ends.

Who owns the records once we leave

A foundation is only worth having if someone owns it after handover. GullyHR settles that with you before the work ends. One person, such as an operations or admin lead, keeps the employee files, the leave and overtime tracker and the letter templates. The head of support owns the seasonal hiring process and its training record. The product head owns the list of who holds each accounting rule, which links to the exit process. Managers are shown how to use the standard letters unaided, with a short session for each team. The simple report, sent on the schedule agreed in writing, tells the owner headcount, joiners, leavers and open leave balances, so the first questions about people no longer need a spreadsheet hunt. What stays with the owner is every decision the documents record: pay, roles, who is promoted and what the rules are. If the business later needs a monthly retainer or a policy package, those are separate scopes agreed on their own. Where a letter needs a legal view, your adviser reviews it once, and the approved version becomes the template.

The first weeks

  1. 01

    Hold a scoping call with the owner and the heads of product and support, and agree the handbook outline and the five processes in writing.

  2. 02

    Collect current offer letters, leave and overtime sheets, role lists and the seasonal support hiring notes from the last filing rush.

  3. 03

    Interview one developer, one domain expert, one implementation consultant and one support agent about hours, escalations and what they were never told.

  4. 04

    Draft the handbook and the first two processes, then walk a pretend joiner and a pretend leaver through them and fix what stalls.

  5. 05

    Hand over the remaining processes, standard letters, employee file template and first report, and train each manager to use them unaided.

The operating context

Build the minimum HR structure in a usable sequence

An accounting software provider sells to accountants, traders and small businesses who expect the product to be right at filing time. Here is how to organise developers, domain experts and support teams around year-end pressure.

Software developers and architectsAccounting domain experts and product analystsTesters and quality leadsImplementation consultants and trainersSupport and helpdesk agentsPartner and reseller managers
Workplace and operations scene: chartered accountants accounting firms.

The decision to work through

Prioritise employee records, essential policies, role ownership and recurring processes around the starting workforce. Workforce to consider: Software developers and architects, Accounting domain experts and product analysts, Testers and quality leads.

Records to prepare

Baseline inventory, implementation plan and accepted foundation documents. Confirm which records are held by the managers of Software developers and architects, Accounting domain experts and product analysts, Testers and quality leads.

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.

  • Desktop accounting software vendors competing with Tally and Busy
  • Cloud accounting and GST billing apps for small businesses
  • Billing software for pharmacies, grocery and retail counters
  • Accounting products for wholesalers, traders and distributors
  • Software for contractors, builders and project businesses
  • Products built for CAs managing several client books

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

It is written for your business. GullyHR talks to people in each group, developers, domain experts, trainers and support agents, and writes around your release weeks, shifts and seasonal hiring. Standard structure helps with layout, but the content reflects how you work. Your own legal adviser reviews anything that touches local employment rules before you issue it, and you approve every page.

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