The pain
You need a specific workflow fixed.
Claims files that take hours to review. Reports assembled by hand. Technicians who cannot find the right answer in manuals. You need a practical solution with a clear scope.
AI Discovery & Implementation · Scoped engagements
When one problem can be clearly defined, we take it from a scoped problem to a tested, deployed system with training and handoff, through Discovery, Design and Delivery.
Trusted By
Sound familiar?
The pain
Claims files that take hours to review. Reports assembled by hand. Technicians who cannot find the right answer in manuals. You need a practical solution with a clear scope.
The fear
A build without input from its users, agreed controls or a handoff plan can stall before anyone relies on it. Those decisions need to be part of the project from the start.
01 · AI Readiness Assessment · Starts at $5,000
We assess your business and data using Spej’s five-pillar readiness model: Commitment, Guardrails, Data, Capability and Impact. You get a scored readiness profile and a prioritized roadmap.
Review the five pillars together to identify strengths, gaps and the conditions that affect implementation.
Rank opportunities by value, readiness, risk and effort. Agree which priorities warrant the next investment.
AI Readiness Assessment is a separately scoped engagement. The free readiness guide is a self-reported starting point. Design and implementation are agreed separately.
02 · Design & Build · Starts at $25,000
Each phase produces the evidence needed for the next decision.
We agree on the workflow, the stakeholders, the source data, the constraints, the risk and the success measure. Nothing gets built until the problem is worth solving.
Architecture, controls, integrations, testing plan and measures, reviewed with security, finance and the people who will use it. An evidence gate before any spend on build.
Build, test, integrate, launch, document, train and hand over. We build it ourselves, and adoption is part of the definition of done.
What's different
Discovery, Design and Delivery are each scoped and priced. You decide at every gate whether the evidence justifies the next phase.
Data boundaries, access rules and audit trails are part of the Design phase, reviewed with your security and compliance leads before build.
The team that scopes the problem stays accountable through design, engineering, testing and handoff.
Documentation, role-specific training and a transition plan ship with the system. A tool nobody uses is a failed project, whatever the code looks like.
Strategy & governance · Process engineering · Implementation · Training & enablement
Strategy, implementation, process engineering and enablement can each be scoped as a project or delivered through your retained AI Office. Choose the work you need, then the engagement that fits.
Set the direction, ownership and controls for AI across your business.
Deploy enterprise AI, build custom applications and connect systems and knowledge.
Map and redesign workflows, automate the right steps and measure improvement.
Build executive fluency, practical team skills and sustained organizational adoption.
Projects have an agreed scope and deliverables. The AI Office prioritizes work within its retained capacity; larger builds are scoped separately. Plooms is the enterprise software option, with integration and adoption support available through either engagement.
An AI readiness assessment identified six opportunities and delivered a job intelligence prototype. The work gave the business a practical basis for deciding what to pursue next.
Read the case studyidentified through the assessment
No. Bring a business priority or a workflow that needs improvement. Discovery establishes the problem, the opportunity and the scope before you commit to a build.
Yes. Those can be standalone scoped engagements, as well as parts of a larger implementation. We agree the deliverables and completion criteria with you.
The project includes the agreed documentation, training and handoff. You can add an AI Office for ongoing priorities or explore Plooms if you need a secure AI workspace.
A practical first conversation
Use a 15-minute introduction to share the need and arrange the right deeper conversation. You do not need a project brief.