Get started
Weeks to value. Not quarters.
Buying Bridge is deliberately simple: a live demo, a short readiness check, a fixed-price pilot - then you pay for what your teams actually use. Here is the whole path - including what needs to be in place on your side.
The path
Four steps from first look to rollout.
Prerequisites
What needs to be in place.
No surprises halfway through: these are the things we check together in step two. Most enterprises already have them.
Commercial
- Every rollout starts with a fixed-scope onboarding package - setup, connectivity, governance baseline and enablement.
- Pricing has two parts: a plan - Bridge Start for the pilot, Bridge M for productive operations, Bridge L for the rollout - with an included unit allowance, and usage beyond it, measured in Bridge Usage Units. For group-wide programs: Bridge Enterprise on request.
- No minimum user count - start as small as a single team.
- Billing is monthly, based on actual usage - at the unit price of your plan.
- The pilot is a fixed-price package - one end-to-end process, a clear scope, a defined end.
- The full price list is public, right on this page - what you see is what you pay.
Technical
- SAP ECC or S/4HANA with the relevant standard services (APIs) enabled for the processes you want to cover.
- Base connectivity between Bridge and SAP - via the Microsoft On-Premises Data Gateway, Azure API Management or SAP BTP.
- A Microsoft 365 tenant with Microsoft Teams; Bridge is delivered through Microsoft 365 Copilot.
- Permissions set up on both sides - in Microsoft and in SAP. Every SAP access runs through the user’s own SAP account: Bridge respects your authorizations and never widens them.
- No modification of your SAP core, no parallel data copy - Bridge reads through the standard.
How pricing works
One onboarding. Three plans. That's it.
Every path starts with a fixed-scope onboarding package - setup, SAP connectivity, governance baseline and user enablement. From there, you pick a plan that grows with you, from pilot to rollout. The whole price list fits on four cards:
Step 1 · one-off
Onboarding
x,x00 EUR* one-off up to 2,500 SAP users. Setup, SAP connectivity, governance baseline, enablement. With Bridge M you receive a x,x00 EUR* Bridge credit after go-live, with Bridge L a x,xx0 EUR* development credit - redeemable for Bridge Functions. From 2,500 SAP users: enterprise readiness and onboarding, xx,x00 EUR*.
Then you choose a plan - the pilot begins with Bridge Start.
Bridge Start
xx0 EUR* per month. Includes 1,000 units, 0.xx EUR* each beyond that. One SAP system, one end-to-end process as the pilot (say, purchase to pay), the full standard catalog - cancel monthly, ends after three months at the latest with a value review: usage, value, next processes.
Bridge M
x,xx0 EUR* per month. Includes 4,000 units, 0.xx EUR* each beyond that. One SAP system included (each additional +x,xx0 EUR*), several end-to-end processes, a dedicated Teams channel, one Bridge development credit per contract year, quarterly value reviews.
Bridge L
x,xx0 EUR* per month. Includes 10,000 units, 0.xx EUR* each beyond that. Two SAP systems included (each additional +x,xx0 EUR*), a named contact, three development credits per contract year, monthly value reviews.
For pilot customers
Early adopter: opening new areas together.
For a small number of pilot customers there is an individual plan: you bring a process Bridge does not cover yet - we open it up together, build the extensions and you keep them. Fixed terms, a direct line to product management, a say in the roadmap. If that sounds like you, ask us about it.
That's the whole price list. No minimum user count - one unit is one answered standard question, document checks and analyses count as small multiples, and follow-ups in the same conversation are free. Custom Bridge Functions from x,x00 EUR*. For group-wide programs across several systems and countries: Bridge Enterprise on request.
| Bridge Start | Bridge M | Bridge L | |
|---|---|---|---|
| Monthly price | xx0 EUR* | x,xx0 EUR* | x,xx0 EUR* |
| Term | 3 months max, cancel monthly | 12 months | 24 months |
| Included units / month | 1,000 | 4,000 | 10,000 |
| Additional unit | 0.xx EUR* | 0.xx EUR* | 0.xx EUR* |
| SAP systems | 1 | 1 included, each additional +x,xx0 EUR* | 2 included, each additional +x,xx0 EUR* |
| Scope | one defined end-to-end process | several end-to-end processes | company-wide rollout |
| Development credits | Functions separately from x,x00 EUR* | 1 per contract year | 3 per contract year |
| Support | email, reply within two business days | dedicated Teams channel, next business day | named contact, four hours on business days, incident line around the clock |
| Value review | at pilot close | quarterly | monthly |
| Onboarding credit | - | x,x00 EUR* after go-live | x,xx0 EUR* development credit |
| Price guarantee | - | across the term | across the full term |
| Not included in Bridge pricing | Runs on |
|---|---|
| Microsoft 365 with Teams | your Microsoft agreement |
| Microsoft 365 Copilot licenses or Copilot Studio capacity | your Microsoft agreement |
| Power Platform environment | your Microsoft agreement |
| Windows server or VM for the on-premises data gateway | your infrastructure |
| Azure resources (such as API Management in the target architecture) | your Azure agreement |
| SAP licenses and SAP named users | your SAP agreement |
Bridge pricing covers Bridge - fully and exclusively. The items above are deliberately excluded; what applies in your environment, we calculate in the readiness check based on your licensing - for users with a Microsoft 365 Copilot license, Microsoft includes the use of internal Copilot Studio agents in the license.
* The amounts on this page are deliberately masked. We name the actual prices in a first conversation, once your use case is clear - in writing, and together with the list of what is not included.
What is a Bridge development credit?
A development voucher: each credit covers one standard Bridge Function - a customer-specific capability worth x,x00 EUR*, built specifically for your processes. Toward an advanced Function it counts as x,x00 EUR*. The Function runs in your SAP and is yours to keep - beyond the end of the contract.
What happens in a value review?
A working session built on numbers, not slides: what was used, what it replaced, and which processes are worth connecting next. After eight to ten weeks in the pilot, quarterly in Bridge M, monthly in Bridge L.
How does the onboarding credit work?
Not a discount - product value: after a successful go-live we credit x,x00 EUR* in Bridge M and x,xx0 EUR* in Bridge L, redeemable for Bridge Functions and extensions.
What does the price guarantee mean?
Plan price and unit prices stay unchanged across the entire term - no index clause, no quiet increases.
How does time saved become money?
Through four mechanisms: time for professional work instead of searching in SAP, faster processes, cash effects from captured discounts, detected duplicates and collected credit notes, and avoided risks around bank details and deadlines. This is why our calculations count only 30 per cent as realised.
What does Microsoft cost on top?
For users with a Microsoft 365 Copilot licence, Microsoft includes the use of internal Copilot Studio agents in the licence. Anything beyond that in your environment we calculate during the readiness check, based on your licensing.
How do we measure whether the pilot paid off?
Before the start we agree a baseline and go/no-go metrics. The monthly report shows every transaction, the value review shows the effect - numbers instead of slides.
Who is liable if an answer is wrong?
We distinguish three levels: displaying information from SAP, assessing a check result, and pointing to a next step. Decisions are always made by people; automated decisions about individuals are excluded.
Full cost control
A usage alert at 80 percent of last month's level, a monthly report by activity type - and an optional soft cap you set yourself.
Included allowance
The base fee includes a monthly allowance of units. Everyday questions cost one unit each - your first team fits comfortably inside the allowance.
Grows with you
Move up to a larger plan any time - and in every value review we show you where Bridge is already creating value and which processes are worth connecting next. Never a hard cutoff mid-work, never an invoice you didn't see coming.
Why this pays off
A question takes seconds. The old way takes minutes - or a ticket.
One Bridge question does not replace an SAP transaction - it replaces a small research chain: three to four transaction types, ten to twenty clicks, ten to twenty-five minutes. Plus the knowledge of which transaction is the right one in the first place. A manually handled request typically costs a company 5 to 15 EUR internally. A Bridge unit costs at most 0.xx EUR* - and the answer arrives where you already work.
| One question to Bridge | Replaces in SAP | Classic effort |
|---|---|---|
| Which purchase orders are overdue? | ME2N, then ME23N per case | 8 to 15 minutes |
| Where are goods receipts still missing? | ME2N, ME23N, material documents | 10 to 20 minutes |
| Which suppliers cause the most delays? | ME2L, ME2N, ME23N plus evaluation | 15 to 30 minutes |
| How has the price of material X developed? | ME1M, ME13 | 10 to 20 minutes |
Do the math
One answered question replaces around 12 minutes of SAP work on average - 12 EUR at typical full staff cost. A purchasing team of 25 asking eight questions a day generates roughly 44,000 questions a year. Even if only a third of the saved time turns productive, that is about 145,000 EUR per year - a multiple of what Bridge costs over the same period. And as usage grows, the value grows with it.
Anyone can ask
The classic route requires an experienced key user - if you do not know ME2N, you never get started. With Bridge, the question is enough: from sales answering while the customer is still on the line, down to the shop floor.
IT says yes faster
Read-only, every access through the asking user's own SAP permissions, no data copy, everything inside your tenant. The questions security and works councils ask are answered before they are asked.