When permanent is the right call for SAP Business One
Most SAP Business One hiring questions reduce to one decision: is this a project or a platform? Projects — implementations, migrations, rescues — suit contract resourcing. But the person who owns your B1 system year after year, who knows why the pricing rules are set the way they are and which month-end jobs are fragile: that’s a permanent hire, and getting them right is what this guide is about.
A simple test helps. Will the work still exist in twelve months? Does it depend on knowing your business, not just the software? Would losing this person create real operational risk? Three yeses point to permanent. A defined scope, a fixed end date and a need for scarce specialist skills point to contract. Many businesses end up with both: a permanent owner of the platform, plus contractors brought in for peaks such as an upgrade, a new subsidiary go-live or a reporting overhaul.
The cost of getting this wrong is real. Use contractors for platform ownership and knowledge walks out the door every few months. Use a permanent hire for a short, specialist project and you pay for skills you won’t need next year.
What good looks like
In our experience the best permanent B1 hires share a shape. Technically, they know the modules your business actually runs — not all of B1, the parts that matter to you. A distributor needs inventory and purchasing depth; a manufacturer needs production and MRP. Commercially, they can sit with a finance director and translate. And temperamentally, they’re platform owners: the kind of person who documents things nobody asked them to document.
Where employers go wrong is briefing for a unicorn — deep SDK development plus senior functional consulting plus support management, at a mid-level salary. Those three are different jobs. Pick the one your business needs most, hire for it properly, and buy the others from your partner as needed.
In practice, the three roles look like this. A developer works with the SDK, add-ons, integrations and custom reports. A functional consultant designs processes, configures the system, trains users and works with finance and operations. A support analyst or manager handles day-to-day issues, user administration and partner coordination. Each is a legitimate permanent hire; the mistake is expecting one person to be all three. Write the job spec around the work that needs doing, not around the person you hope to clone, and list only the modules you actually use.
On pay: budget from the current bands, not from what the last person earned. A mid-level UK functional consultant runs £49,500–£66,000 in 2026, seniors £66,000–£82,500, and in-house support analysts £38,500–£63,800 depending on level — the full breakdown is in our SAP Business One salary guide. An advert priced under band doesn’t attract negotiators; it attracts silence. Pay also shifts with location, sector and whether the role is hybrid, so test your figure against live offers, not just last year’s numbers. Benefits matter too: flexible working, training budgets and a clear path to senior or management roles often decide between two similar offers.
How the process should run
Speed decides outcomes in this market. Our standard: qualified shortlist within a week of the brief, first interviews the week after, offer inside a fortnight. Every extra week of deliberation costs you candidates to counter-offers, because the strongest B1 people are always in more than one process.
Keep the stages tight: brief, shortlist, two interview rounds at most, then offer. Agree who makes the decision before you start, give feedback within 24–48 hours, and be open about salary from the first conversation. Vague pay and slow feedback are the two most common reasons good candidates withdraw. Make the interview practical, too. Ask candidates to talk through a real problem, such as a stock valuation mismatch or a slow month-end close, rather than reciting module names.
Expect notice periods of one to three months in the UK — plan the handover around it rather than being surprised by it. Where possible, let the new hire overlap with a departing colleague or your implementation partner so documentation is captured early. Keep in touch with your chosen candidate during notice, so they feel part of the team before day one.
And when the counter-offer arrives (it will), the candidates who still join you are the ones who were moving for the role, not just the rise. Ask in the first interview what is driving their move, and revisit the answer before offer stage. That’s a matching problem, and it’s exactly the part we’re good at after a decade in this niche.
Hiring a permanent B1 professional this year? Send us the brief and we’ll come back with a benchmarked salary, a realistic timeline, and a shortlist that shows up.