The method
The Embedded Intelligence Method
Advisory, configuration and AI held by one senior specialist, inside your team, for the length of the engagement.
What it is
The Embedded Intelligence Method is the name for how a Unit4 engagement runs here. A single senior specialist sets the strategy, writes the test script and the SQL, and builds the AI application.
Bear Consulting Services is a specialist Unit4 Business World consultancy operating as a sole practice, by design rather than by stage of growth. Mircea Rogojan-Rush carries the work from scoping through to delivery, and there is no handover to a delivery team. He works inside the client team, at the change board, the systems stand-up, the audit meeting and the executive briefing, with access appropriate to the agreed work. Nothing is handed across a boundary, so nothing is lost at one.
Engagements are retained, embedded and deliberately capped, typically one or two concurrent clients. The practice model is set out in full on the about page.
The method has three pillars.
Pillar 01
Strategic ERP advisory. Programme architecture, governance design and transformation roadmaps.
Pillar 02
AI engineered to the system. Bespoke AI built against the Unit4 data model.
Pillar 03
Embedded delivery. One senior specialist working as a peer inside the client team.
Each pillar below carries the engagements that exercised it. A reader who does not take the pillar headings on trust can read the work instead.
Pillar 01: strategic ERP advisory
Programme architecture, governance design, transformation roadmaps. Multi-stream, multi-year. Authored at the level decision-makers actually need to commit budget against.
In practice that is three kinds of document. Independent system reviews of HR and payroll installations, carrying findings, remediation options and consultancy estimates, written for an executive audience. Transformation deliverables that sit above the system: workforce and people plan analysis, HR transformation plans, knowledge and training strategy, and executive briefings for leadership teams. Data migration strategies and the matching migration test strategy, defining validation rules, reconciliation checkpoints and rollback criteria before any load runs.
Worked example, local government
A payroll review forecast to free 500 administrative hours a year
A council payroll running multiple pay entities, including a schools payroll, was carrying manual effort nobody had mapped end to end. The review mapped the workflows from user interviews, specified the system fixes and the automation opportunities, and sequenced them into a phased improvement roadmap. The move to self-service time, attendance and travel claim entry that the review enabled was forecast to save 500 administrative hours a year.
Worked example, policing
A policing data migration validated across 50+ data categories
An operational database had to move into a new system without loss of integrity, on a fixed programme timetable. The strategy defined data integrity validation rules across more than fifty data categories, with source-to-target field mapping and reconciliation category by category.
Pillar 02: AI engineered to the system
Bespoke AI built against the Unit4 data model rather than bolted on beside it, and grounded in the organisation's own documents.
There is one worked example, and it is a named product rather than a description of a capability.
Worked example, PolicyAI
An HR policy assistant that cites its source
PolicyAI answers staff and line manager policy questions from an organisation's own published policy library, citing the source document for each answer. It is built on Anthropic Claude Opus, deployed on Vercel, with Azure Active Directory single sign-on. PolicyAI is a prototype: a working version was documented in a March 2026 briefing, and production deployment requires agreement on identity, security, information governance and support.
Pillar 03: embedded delivery
One senior specialist working as a peer inside the client team, with direct responsibility for the agreed advisory and implementation work.
That includes the unglamorous end of a Unit4 estate. Service management runs to the ITIL pattern: service desk and service levels, incident, event, problem, release and change management, request-for-change documentation, and helpdesk key performance reporting.
Worked example, higher education
A support backlog cut by 50 per cent in a higher-education Unit4 team
A central Unit4 support function in higher education was carrying a ticket backlog its own team could not clear and could not independently prevent. The backlog was halved and full compliance with the agreed service levels was reached across the team's tickets. The triage and resolution routine, and the training needed to run it, stayed with the team.
Worked example, local government
An upgrade acceptance programme across 16 HR and payroll process areas
A local government HR and payroll estate faced a major-version upgrade that had to be accepted across the whole process set rather than sampled. An acceptance strategy and a reusable master script library carried phased execution across 16 HR and payroll process areas, with defect status reported on a dated cadence and a recommendation put to the project board.
The operating rules
Five rules run through every engagement. They are written here so that they can be held to.
- Diagnose before deciding. A strategic decision about a Unit4 estate should not be taken against a system the organisation does not currently understand.
- Findings first, evidence below. Reports lead with the answer and the priorities, with the supporting evidence held underneath for the reader who wants it.
- Every configuration change leaves a trail. A written baseline, a test execution record and a post-change validation, so the change has an audit trail after the consultant leaves.
- Go-live decisions are made against quantified residual risk. Not a status colour.
- Validation comes before the first record moves. Test strategies define validation rules, reconciliation checkpoints and rollback criteria before a single record moves.
What comes out of it
The documentation comes out of the work rather than after it. These are the deliverable types an engagement produces.
- Procedure layer
- Procedure manuals and standard operating proceduresMonthly payroll playbooks, error catalogues, decision trees and process maps, line manager guides and support operations manuals.
- Build record
- Build documentation and solution design documentsHR solution design built by extracting the live configuration from the production database, so the document describes the system as it runs.
- Acceptance
- Acceptance strategies and evidence packsTest strategies for upgrades, migrations and greenfield builds, with user acceptance strategies, exit plans and reusable script templates.
- Programme
- Plans and cut-over materialBuild plans, upgrade milestone plans, project gantt charts, cut-over plans, go-live runbooks and critical path documentation.
- Governance
- Governance structure and control designResponsibility matrices, risk logs and registers, communications plans, sponsor updates on a weekly cadence, and segregation of duties and permission matrices with create, read, update and delete mapping per role.
- Capability
- Training curricula and workshop suitesWorkbooks, facilitator guides, job aids, slide decks and knowledge checks, plus workshop suites and one-to-one training plans.
- Leadership
- Executive briefings as self-contained HTMLDocuments leadership can read on any device, without a slide deck or an attachment chain.
- Above the system
- Transformation deliverablesWorkforce and people plan analysis, HR transformation plans, and knowledge and training strategy.
No count is attached to any organisation. Client work is described at sector level throughout this site. The written form of several of these arguments sits in the insights layer.
How it is engaged
Five routes in, in ascending commitment. One of them carries a published figure.
Rung 0
Unit4 configuration health check
Twelve questions on your own configuration, scored on the page. Free, self-serve, about two minutes, no email address at any point.
Rung 1
Unit4 X-Ray
A structured strategic diagnostic of a defined area of a Unit4 Business World estate, delivered as a written executive-grade assessment with a prioritised remediation roadmap.
See the Unit4 X-Ray briefRung 2
Documentation and governance package
The procedure, build and control layer for an agreed process set. Fixed fee, fixed duration, scope agreed up front. The fee is confirmed in the first call.
Rung 3
PolicyAI deployment
Fixed fee and fixed duration, with a written quotation setting out the agreed scope, fees and operating responsibilities. Policy ownership, query-log handling and deployment rights are set out in the written agreement. The fee is confirmed in the first call. PolicyAI is a prototype: a working version was documented in a March 2026 briefing, and production deployment requires agreement on identity, security, information governance and support.
See PolicyAIRung 4
Embedded advisory and delivery
Day-rate or fixed-scope, inside IR35 where required, with scope, deliverables and fees agreed in writing. The fee is confirmed in the first call.
Commissioning is subject to your organisation's procurement rules and delegated authority.
Start with a 30-minute call
The call is thirty minutes with Mircea Rogojan-Rush, who founded the practice and delivers every engagement. It is booked directly rather than arranged by email.
You leave it with a view on whether this model fits your situation, and with the one route on the ladder that matches what you described.
Commissioning is subject to your organisation's procurement rules and delegated authority.