KraftHub and SAP.
Your SAP stays the system of record. KraftHub is the layer in front of it: enquiry, quote, appointment, site.
The problem SAP does not solve
SAP is in your business because finance, purchasing, stock and people have to run in one place. That is exactly what it is built for. What it is not: the surface where a customer enquiry at 6:40 in the morning becomes a quote, where a fitter dictates a variation report wearing gloves, where moving an appointment sends a confirmation email.
That work happens anyway. Mapping it into SAP means a customising project; leaving it outside means the numbers in SAP are always a day old.
- OutlookEnquiries and confirmations
- ExcelCosting per branch
- PaperReports in the van
- WhatsAppArrangements with the fitter
Who stays responsible for what
No judgement, just the allocation. On the left what stays in SAP. On the right what runs beside the system today and gets a surface in KraftHub.
- Financial accounting, consolidation, close
- Purchasing, creditors, framework agreements
- Stock, materials, dispatch
- People, time, payroll
- Controlling, cost centres, reporting
- Compliance and audit
- Customer enquiry from email, phone and web form
- Quote with AI from text, voice, photo, plan and PDF
- Appointment, scheduling, customer confirmation
- Site: hours, photos, daily and variation reports, signature
- Project file with an AI answer and its source
- Create e-invoices, capture and file incoming documents
KraftHub does not replace your SAP. It takes the work it was never meant for — and hands the documents back cleanly.
How the two systems come together
Three routes, from least effort to most. Route 1 needs no project on the SAP side.
Documents back to finance
Outgoing invoices, debtors and documents leave KraftHub in the formats your finance department already accepts. After the export KraftHub locks the invoice against later changes.
Master data and transactions over the SAP APIs
Reconcile customers and suppliers, return the awarded transaction, post hours and material against the right project. Every connection runs over SAP's documented interfaces, never the database. Which of them your business needs is settled in the project — nothing here is prebuilt, and that is deliberate.
KraftHub as a tool inside your SAP AI
Your assistant asks KraftHub directly — over the Model Context Protocol, the same standard SAP builds its agent world on. This is the part no other trade software vendor offers.
KraftHub as a tool for Joule and your agents
SAP's own reference architecture describes Joule as an MCP client, and the MCP Gateway in SAP Integration Suite as exposing SAP and non-SAP interfaces as “governed, MCP-compliant tools”, consumable by any AI agent. For external MCP servers SAP publishes a reference pattern of its own, with requirements for authentication, token exchange and logging.
Translated into your business: your SAP assistant asks which fitter is free on Thursday, which quotes are open for a customer, or what report exists for a site — and gets the answer from KraftHub without anyone switching windows.
We set the connection up with your IT: which access your assistant gets, and how it authenticates, is your decision, not ours.
“Which fitter is free in Kassel on Thursday?”
- Access chosen per connection
- revocable at any time
- every access is logged
- change or delete: no
Four reasons your audit will back
No second ERP
You introduce no parallel world for the numbers. The data your audit checks stays one set.
The gap is closed, not moved
What happens in Outlook and Excel today gets structure, history and reporting — in the same place it arises.
AI without an SAP project
Quoting, inbox, project questions and site documentation run with AI from day one — independent of your ERP's release cycle.
One more tool for your agents
If you are building on Joule and your own agents, KraftHub becomes part of that landscape over MCP instead of standing beside it.
What your IT and data protection need to sign off
The documents exist already — no special round, no asking sales.
From first call to rollout
- 01
First call — management, IT, or both
- 02
Agree the scope and direction of the interface
- 03
Test tenant with your master data
- 04
Pilot with one team
- 05
Rollout
What businesses running SAP ask first
Sources for the SAP interfaces named here: the SAP Business Accelerator Hub (API_BUSINESS_PARTNER, A_BusinessPartner, API_SALES_ORDER_SRV) and SAP's reference architecture on Joule as an MCP client and the MCP Gateway in SAP Integration Suite. Vendor statements are quoted, not assessed.
A conversation, not a pitch.
45 minutes, with or without your IT. For management we work out what changes day to day and what a move actually involves; for IT, which of the three routes fit your business and what runs without a project on the SAP side. Come alone or bring whoever you need.