MCP / SAP
Bring SAP work into the assistant
Completed MCP integration connecting a compatible assistant to a defined SAP scope. The client works from the assistant.
Read the SAP integration ↗
Hunter BI / Applied enterprise intelligence
Corporate AI Deployment Pilot · Claude & ChatGPT
AI assistants. Connected to your business.
Hunter BI connects Claude or ChatGPT to approved business information and tools. Start with one departmental workflow, test the value with your team and plan the next integration from the results.
Fixed-fee implementation. Client-owned environment.
Integration experienceBusiness software. Connected to an AI assistant.
Hunter BI has completed MCP integrations for SAP and Sage X3. The reported benefit: clients work from their AI assistant, with a qualitative improvement in productivity.
Hamza EL HINANIAI consulting & integration · CasablancaMeet Hamza EL HINANI ↗MCP / Sage X3
Use the ERP from the assistant
Completed MCP integration for Sage X3. The reported benefit is a more direct way for the client to work from an AI assistant.
Read the Sage X3 integration ↗Client identities and implementation details remain confidential. No quantified productivity result is published.
Start with a task your team recognises.
These are candidate pilot workflows, not results from the projects above. Choose one and agree what a useful outcome looks like.
Operations / internal support
Find the right procedure
Help staff locate an approved answer and its source instead of searching across documents.
Measure during the pilotTime to a verified answer, correct source version and escalation when information is missing.
Management / knowledge teams
Prepare a sourced summary
Prepare a first synthesis of an authorised document set for a named reviewer.
Measure during the pilotTotal preparation and review time, source coverage and corrections required.
Engineering / industrial teams
Use technical documentation
Help teams retrieve relevant instructions from the approved technical corpus.
Measure during the pilotCorrect document retrieval, answer usefulness and respect for access permissions.
What the workflow looks like
Illustrative document workflow · not a client screenshot
Ask
An employee asks for the approved procedure.
Retrieve
The assistant uses the authorised source set.
Check
The answer includes references to inspect.
Approve
A person reviews the answer before acting.
What is included in the pilot?
One department, one primary AI platform and one agreed workflow. Your proposal specifies users, sources, included connectors, acceptance criteria and a fixed implementation fee.
- One department & named sponsor
- One defined workflow
- Authorised sources & users
- Measurable acceptance criteria
What does your team receive?
Scope & test plan
The workflow, sources, access matrix, responsibilities, baseline and acceptance criteria.
Configured pilot
The agreed configuration and workflow, with business tests, access checks and documented limitations.
Training & handover
The agreed team sessions, user and administration guides, configuration transfer and access review.
Results & next decision
An acceptance report and a recommendation to extend, adjust or stop. Wider deployment is a separate engagement.
The base pilot uses the document sources and existing connectors agreed in the proposal. A new ERP connection or custom MCP server is a separately scoped engineering engagement.
How we agree acceptance criteria
Choose the test set, baseline, thresholds and acceptance owner before configuration. The example below is an evaluation framework, not a client result or a promised productivity gain.
- End-to-end task time
- Preparation, answer checking and corrections against the current process on comparable tasks.
- Evidence quality
- Whether each material claim is supported by the right source and document version.
- Access boundaries
- Whether authorised users can use the agreed sources and excluded users or groups are denied.
- Errors and uncertainty
- How the workflow handles missing, contradictory or insufficient evidence and escalates to a reviewer.
A fixed fee. A defined boundary.
Implementation fees · USD
Your scope. A written fixed fee.
After scoping, your proposal sets out the implementation fee in USD, milestones and acceptance criteria. Software licences, usage charges and additional work are itemised separately.
Discuss your use caseWhat your proposal will specify
- Workflow, users, source volumes and included connections
- Fixed implementation fee in USD and separate vendor costs
- Milestones, client inputs and acceptance owner
When does delivery start?
Your proposal includes a schedule and the inputs needed from your team. The start date is confirmed once procurement, payment conditions, licences and authorised access are ready.
Outside the base pilot
- Additional departments, workflows or source systems
- Custom API/MCP development and substantial data preparation
- Special hosting, infrastructure, certification or legal advice
- Ongoing operations, support retainers and on-site work unless agreed
Delivery and eligibility for your organisation
A small scope. A serious implementation.
A corporate pilot is not an unrestricted trial account. It is a bounded implementation with named owners, authorised data and a documented decision at the end. Select one primary platform during scoping; deploying both is not automatically included.
Start with a workflow
Choose a document task such as finding an approved procedure or preparing a sourced internal summary. Define the output, its reviewer and the work it replaces.
Establish a fair comparison
Use an agreed test set to compare the current process with the assisted process. Count human review time and corrections, not just how quickly the model answers.
Make the next decision
The final report supports a decision to extend, adjust or stop. New departments, systems and users require a separate scope; they are not an automatic commitment.
Scoping → agreed proposal → procurement & contract → payment → implementation → acceptance. Payment is arranged after scope approval, including Stripe where agreed with procurement.
The Hunter BI approach
Think enterprise AI.Think Hunter BI.
The value is not in another AI account. It is in connecting intelligence to the way your business works. Hunter BI brings strategy, integration and adoption into one scoped engagement.
- Strategy
- Integration
- Adoption
01 / Frame
One workflow. A clear direction.
Start with the work, not the model. Align the business sponsor and IT around a defined task, an authorised source set and a result your team can evaluate.
What moves forwardAn agreed scope, access matrix and acceptance plan.
02 / Connect
Your intelligence. Your working environment.
Bring Claude or ChatGPT into a client-owned environment. Qualify the right sources and connectors, define the permissions and keep people in control of consequential decisions.
What moves forwardA configured pilot with tested access boundaries. Custom MCP work scoped separately.
03 / Advance
Prove the workflow. Plan the next move.
Test with your business team, train the people who will use it and transfer the configuration. Decide what to extend from observed results, not a demonstration alone.
What moves forwardA results report, team handover and a scoped recommendation for expansion.
Conceptual visuals created for Hunter BI. Not photographs of client infrastructure.
Clear ownership, from setup to handover.
Confirm the named delivery team and responsibilities during scoping. The engagement separates what Hunter BI delivers from the approvals and operating decisions that stay with your organisation.
Hunter BI
Agreed configuration, integration work, business tests, training and delivery documentation.
Your business sponsor
Select the workflow, provide representative tests and accept the business result.
Your IT & security team
Approve accounts, source access, vendor requirements and the operating owner.
After handover
Your team receives the agreed configuration and guides. Ongoing support, incident response and maintenance are defined in a separate agreement if needed; they are not assumed to be included in the pilot.
Access controls and security review
We agree the required controls against the chosen product, licence and architecture. The handover distinguishes available, configured, tested and unsupported controls.
Identity and permissions
Named users, roles and source permissions; SSO or provisioning only when included and supported by the selected licence and identity provider.
Human approval
A defined reviewer and approval step. The base pilot does not make external commitments or change business records autonomously.
Source boundaries
Permitted documents and actions, negative access tests and escalation when evidence is missing. Confidential data is not requested in the initial enquiry.
Retention and traceability
Record the retention settings, available logs, authorised reviewers and any gaps in the selected environment. Your security team reviews the actual processing chain.
Client ownership is not on-premise hosting. Processing location, retention and third-party services must be reviewed for the actual deployment.
Before you commission a pilot
Does the pilot include both Claude and ChatGPT?
No. We select one primary platform during scoping, based on the workflow, licences and requirements. A comparison or a second deployment needs its own agreed scope.
Are licences included in the fixed fee?
No. Software subscriptions and consumption are separate from implementation fees. The client owns its environment and its vendor agreements.
Can you connect our ERP or internal tools?
We first check the system, version, interfaces and permitted actions. A connector is included only when explicitly agreed. A new MCP server or custom integration is not automatically part of the pilot.
Do you guarantee a productivity improvement?
No predetermined gain is promised. We agree the measurement method and acceptance criteria, then document the result, including review time, errors and limitations.
What happens after acceptance?
Your team receives the agreed configuration, documentation and training. Any extension is scoped separately using the pilot findings; there is no automatic group-wide commitment.
What would you like your team to do better?
Tell us the task and the tools your team uses. You do not need a finished brief. The first conversation helps identify a useful starting point and what needs to be checked before a proposal.
Our first conversation
- Identify one useful workflow and the people involved
- Check the main data, access and platform dependencies
- Agree the next scoping step before a written proposal
Do not send confidential documents, personal records, passwords or API keys. Source access is arranged only after authorisation.
Prefer email? contact@hunterbi.com
Or contact us on WhatsApp ↗Platform documentation
Features depend on the selected plan and agreement. These vendor guides do not certify a Hunter BI deployment.