Executive Assessment
Two weeks. Written brief. Board-ready.
A structured review of the current IFS environment — support posture, reporting reliability, workflow gaps, custom-logic exposure, upgrade risk — delivered as an executive brief with prioritized recommendations.
This is the engagement most work begins with. It is designed to give an executive sponsor a defensible view of where IFS is quietly losing value, what the fixes cost, and which of them should be sequenced first.
- Interviews with operational, IT, and finance stakeholders
- Environmental scan — customizations, workflows, reports, integrations
- Support-pattern analysis using the current ticket record
- Upgrade-readiness assessment against the current IFS Cloud roadmap
- Written brief with prioritized recommendations and estimated remediation scope
- One-hour executive readout with the sponsor
Reporting Acceleration
Four to six weeks. Working reports. Handover documented.
A focused engagement that resolves the reporting backlog blocking finance, operations, and planning — with the underlying architecture rebuilt so the fix holds.
The reporting problem is rarely the report itself. It is data access, business-definition drift, delivery cadence, and ownership. This engagement addresses all four — so the reports produced are not the next generation of technical debt.
- Prioritization of the top reporting demands (typically 8–12)
- Underlying SQL and data-access review — PL/SQL, views, custom logic
- Delivery: Quick Reports, Crystal, SSRS, or IFS Report Designer
- Business-definition documentation for every measure delivered
- Handover documentation and 30-day support tail
Workflow Automation Sprint
Three to five weeks. One workflow domain. End-to-end.
One defined workflow domain — approvals, service objects, exception handling, cross-module notifications — automated end-to-end using IFS-native BPA, custom events, and workflow logic.
Workflow automation in IFS is not a matter of buying a bolt-on. The platform has the mechanisms — the challenge is designing them against real operational flow, and documenting them well enough that the internal team can maintain what is delivered.
- Current-state process mapping in the workflow domain
- Target-state design reviewed with operational stakeholders
- Implementation using IFS BPA, custom events, and workflow logic
- End-user testing with the operational team
- Documentation for internal maintenance
Fractional Solutions Architect
Retained monthly. Senior judgment on tap.
A senior techno-functional architect embedded on a fractional basis — for organizations whose internal IFS bench is one person deep and whose next major decision cannot wait for a full-time hire.
The retainer is priced to be a defensible line item rather than a heroic budget request. It provides an executive-level IFS voice on architectural decisions, upgrade posture, customization tradeoffs, and vendor management — without the cost or commitment of a permanent hire.
- Weekly working session with the internal ERP or IT lead
- Monthly executive readout with the sponsor
- Architectural review of any customization, integration, or upgrade decision
- Escalation availability for critical support items
- Quarterly written posture review for the executive team
AI-Assisted Integration Sprint
Three to five weeks. CA$6,000. One reliable connection.
A fixed-scope integration between IFS Cloud and one external system — designed, built, tested, and documented so it stays reliable after handover.
AI accelerates the coding phase, which is why this engagement can be priced lower than a traditional integration project. The hard part — understanding IFS data structures, transaction boundaries, error handling, and what happens when the other system sends garbage — still requires senior judgment. This sprint covers both: AI-assisted development speed plus principal-level IFS design so the integration does not become tomorrow's support burden.
- One integration target: CRM, purchase order receipt, or customer orders
- Data mapping and validation rules documented in business language
- IFS-side delivery: custom events, APIs, BPA triggers, or report exports as appropriate
- Error handling, retry logic, and alerting design
- Testing plan and handover documentation
- 60-day support tail
B2B EDI & Application Integration Setup
Four to six weeks. From CA$8,000 fixed.
Enable IFS Cloud to reliably ingest and send data to trading partners, HR platforms, payroll systems, and IT service tools using IFS Connect and IFS Cloud projection endpoints.
B2B EDI and application integration failures do not announce themselves. They show up as delayed orders, duplicate suppliers, payroll out of sync, or a ServiceNow ticket that never reaches the maintenance planner. This engagement configures the IFS Connect service bus and projection endpoints as a repeatable pipeline, with mapping, validation, error handling, and documentation your team can operate long-term.
- One integration target or trading partner with a defined document/API set
- IFS Connect configuration — routing addresses, routing rules, envelopes, transformers, message queues
- IFS Cloud projection endpoint selection and authentication through IFS IAM
- Inbound/outbound transport design — SFTP, file drop, REST, or SOAP
- Data mapping, validation rules, duplicate prevention, and error routing
- End-to-end testing with sample payloads and the operations team
- Technical handover document and runbook
- 60-day support tail
What this firm does not do
Greenfield IFS implementations. Multi-country transformation programs. Bench staffing. RFP responses over 40 pages. Anything that would compromise the firm's capacity to deliver every engagement principal-led.
If the work is genuinely a program rather than an engagement, the responsible answer is a referral to a firm built for programs — not a stretched delivery from a boutique.
Most engagements start with the Executive Assessment.
Two weeks. Written brief. A defensible view of what the IFS environment is actually costing the business, and what to fix first.
Request Assessment