Identify workflow processes
As they are actually executed, not as documented.
How it works
The process, end to end
Staged, with a decision point at every step. You can stop at any of them.
STEP 1
Intro call
30 minutes on your current setup, and whether this is a fit at all.
STEP 2
Data collection
Documents and system exports. Nothing installed on your side, no agents, no downtime.
STEP 3
Model & interviews
We build the model and sit down with the people doing the work. Their input is the part everyone else skips.
STEP 4
Findings
Where your record goes dark, what it is costing, and what we recommend — with the evidence behind each finding.
STEP 5
Your decision
Our systems, connectors for yours, or neither. The findings are yours either way.
STEP 6
Live & improving
The model keeps running, widening its coverage, and surfacing what to fix next.
Steps 5 and 6 only happen if the findings earn them.
The method
Documents are the event log for companies that don't have one
Products are traced start to end through the documents that moved with them: purchase order, order confirmation, ASN or DESADV, CMR, packing list, goods receipt, customs declaration, invoice. Each carries a reference, an activity and a timestamp — everything an event log requires.
Identify gaps
Where the record goes dark, which events have no capture point, which identifiers fail to reconcile.
Implement event logs & workflows
Event logs suited to your organisation, and workflows built where none existed. This is the core sale.
It does not stop at a report
Core keeps running after adoption, widening its coverage as gaps are closed and surfacing further improvements. The model improves because its inputs improve.
The same trace enumerates the external parties in your chain, and where responsibility and risk sit between them. That is how the Network layer is derived rather than separately built.
The four parts
One thing you always get. Two ways to act on it. One layer underneath.
Bridge HUB Core
The living model
We trace how your products move through the documents that travel with them — PO, ASN, CMR, goods receipt, customs, invoice — and combine that with what your people tell us.
Core is what every customer buys, and it is bought first. You are not buying a diagnostic tool; you are buying a continuously updated model of your own operation.
Documents in. A live picture of your operation out. It keeps running.
Bridge HUB Systems
If you want ours
WMS and inventory first, then asset management, freight forwarding and customs broker. Already configured from your own data by the time you decide.
WMSIMSAMSFreight forwardingCustoms broker
Configuration already exists by the time you decide, because our systems have been running against your data throughout the diagnosis. Rollout is days, not months.
Bridge HUB Connectors
If you keep yours
Dynamics, Oracle, SAP, HubSpot and others. Built from your measured workflow and managed for you, so your existing systems finally talk to each other.
Microsoft DynamicsOracleSAPHubSpotCRM
We will never compete on catalogue size. Each connector is built from your measured workflow and managed on your behalf — because you do not employ an integration engineer, and integration is a permanent operational commitment.
Bridge HUB Network
Included with everything
Suppliers, carriers, forwarders and customers on shared dashboards. Each party holds its own key.
Included with every product, never sold separately. Encrypted data aggregation, key management, and shared dashboards with external stakeholders — each party controlling what it exposes. Built to be compatible with the European data-space standards rather than a rival to them.
The pilot
What you get, what we ask
A design partnership, stated plainly.
What you get
- A model of how your operation actually runs, and a map of where its record goes dark
- Event logs and workflows built where none existed
- Role-specific live visibility — customer service sees order status without calling the warehouse
- Findings with the evidence and confidence level behind each one, including what we could not see
- Advisory throughout, at no charge
- No obligation to take any Bridge HUB product at the end of it
What we ask
- Access to operational documents and system exports
- Time with the people doing the work
- Honest feedback, including when we are wrong
- Permission to use what we learn to improve our own systems
- A reference case, if the results earn one
Pricing
How it is priced
A fixed monthly subscription. No implementation fee, ever.
| Element | Price |
|---|---|
| Advisory | Free |
| Pilot | Your team's time only. No deployment footprint. |
| Diagnostic report | One-off, or free as advisory |
| Event logs and workflows implemented | Included in the Core subscription |
| Bridge HUB Systems | Monthly, per system |
| Bridge HUB Connectors | Monthly, per connector |
| Bridge HUB Network | Included — and your counterparties are never charged |
| Instrumentation hardware | Pass-through plus monthly, only where a physical event has no capture point |
Subscription bands are set per team size rather than per user, so the price does not rise every time you hire. We will quote yours on the intro call.
Instrumentation
Where a physical event has no capture point
Sometimes the diagnosis finds a step no system could have recorded, because nothing was there to record it. Where that happens we instrument it — RFID readers and tags, and sensor tags for temperature and humidity where storage conditions carry liability. This is one option among several, applied where the model shows it is needed, and never the starting point.
EU band 865–868 MHz, RED 2014/53/EU and ETSI EN 302 208, CE marked
EPC Gen2 / ISO 18000-63 tags, GS1 EPCIS event model
Cryptographic tag authentication and TLS-secured reader backhaul