Interview Scorecards and a Structured Selection System for ERP software providers
What this looks like in your business
An ERP provider interviews several kinds of people: consultants who will sit with a client's finance team, developers who write reports, data migration specialists, trainers, support engineers and pre-sales consultants who talk to buyers. Without an agreed system, each interviewer asks what interests them, and the best talker with the right certificate wins. Owners reach for a structured selection system after a hire who looked strong at interview struggled at the first client site. GullyHR builds the stage map, criteria, interview kits and scorecard so every panel asks the same things and records the same evidence.
Why interviews go wrong in this trade
Selection in an ERP firm fails in predictable places. Candidates describe projects they took part in, not projects they carried, and an unstructured conversation cannot tell the two apart. A certificate suggests knowledge of the screens, while the real work is knowing what a client's accounts clerk does when the screen says something unexpected. Panels split: the delivery head values calm at a client site, the founder values commercial instinct, the senior developer values technical depth, and without agreed weights the loudest voice decides. Pre-sales hires are judged on presentation and then must live with what they promised to delivery. Trainers are picked for knowledge and fail because nobody watched them teach. Support engineers are judged on the same questions as developers, even though the work is patience and clear writing. A good candidate with a missing must-have, such as no live cut-over, is sometimes hired because the team likes them, and the gap appears on the first project. A system fixes the decision rule before the interviews begin. Agreed rules protect good candidates too.
Stages, criteria and kits for each role family
GullyHR starts by mapping how you hire today, who sees a candidate and in what order, and how long each stage waits. It then separates role families, for instance functional consultants, developers and report writers, data migration specialists, trainers, support engineers and pre-sales. Each family gets its own stage map and a criteria grid that states, before anyone is interviewed, what good looks like and how heavily each criterion weighs. A consultant grid would weigh live implementation experience, the ability to explain a process to a non-technical client, willingness to work at a site and calm during a go-live. A developer grid weighs how they read a requirement and write a report. Interview kits follow, with the same questions for each candidate, rating anchors that describe a weak, adequate and strong answer, and a short practical task suited to the role, such as walking through a stock-valuation mismatch. Bias guardrails are built into how the panel works, including scoring before discussion. Offer templates are prepared for your legal adviser to review.
Suppose two support engineer candidates tie
Suppose an ERP product company needs a support engineer and has two finalists. Asha has strong technical answers and an immediate manner; Dev has fewer certificates but answered the practical task by asking what the client had already tried. The support lead, a project manager and the founder each score independently on the scorecard before the panel discusses. The scores split: the founder rates Asha higher on commercial instinct, while the support lead rates Dev higher on diagnosing and writing a clear reply to a worried client. The decision rule says the weights agreed for support engineers put clear writing and calm diagnosis ahead of commercial instinct, and neither candidate has a missing must-have. The panel reads the evidence recorded against each criterion and sees that Dev's practical task was stronger on the two heaviest criteria. They agree on Dev, and the founder approves the offer. The scorecard is filed with the hiring record. Asha is told, honestly, that the roles weigh different skills, and the founder notes that she would fit a pre-sales opening later.
Who scores, what is filed, what you decide
A selection system needs roles that stay the same from hire to hire. The hiring manager owns the criteria grid for their role family. Each panellist owns their own scores, recorded before discussion. One person, a project manager or office manager, owns the candidate file and keeps the scorecards, the practical task, and the decision note. The founder or delivery head owns the final choice and the offer. Records to settle are the stage map, the criteria grid with weights, the interview kit, the scorecard and the decision note. Handovers matter too: the criteria that the panel recorded for a new consultant should pass to the project manager as a short starting plan, so what the candidate still has to learn is known on day one. A candidate with a missing must-have goes to the owner with the gap stated plainly, not decided by the panel's mood. What stays with you: the weights, the final selection, pay and the offer. Contract wording is confirmed by your own legal adviser. GullyHR builds the system and trains your panel to use it.