The problem we solve
The issue is rarely a lack of systems. It is that every party has its own system and its own version of events, exchanged through files, email and phone calls. Manual reconciliation repeats every cycle, proving who changed what and when is difficult, and any dispute turns into a long search through records the other side does not trust. When a shared network is proposed, it usually stalls on governance rather than technology: who joins, who sees what, who runs it and who pays. We work on both sides at once — and if a distributed ledger is not the right answer, we say so before budget is committed.
Expected outcomes
- One shared record, visible to each party according to its role, replacing exchanged files with no authority.
- A tamper-evident history of who entered what and when, without depending on one party's word.
- Less effort spent reconciling records manually between partner systems.
- Written joining and permission rules that participants agree before the network runs.
- The ability to evidence a sequence of actions to an auditor or requesting authority.
- A defined route for adding new participants without rebuilding the network.
Who this is for
- Groups of companies or bodies that share one process while remaining independent of each other.
- Supply chains that need reliable traceability across organisational boundaries.
- Financing and insurance providers whose decisions rest on documents issued by third parties.
- Large enterprises seeking a single record across business units running different systems.
- Teams evaluating a shared-network idea who want a neutral technical verdict before investing.
Use cases
- Tracing product origin and condition across supply chain parties to the final recipient.
- Sharing certificates and documents in a form any counterparty can verify independently.
- Recording assets and transfers of custody within a known set of participants.
- Reconciling records between partners on different systems and different closing cycles.
- A shared audit trail for sensitive operations that face periodic inspection.
- A contained pilot that tests viability with real parties before committing to a full network.
Deliverables
- A viability report with a clear recommendation — including not proceeding, where that is right.
- A governance document agreed by participants before go-live.
- A working permissioned network with separated test and production environments.
- Documented transaction logic and integration-ready APIs.
- An integration package per agreed participant system, with test data.
- An operations plan covering responsibilities, monitoring, backup and restore.
- Technical documentation and knowledge transfer for each participant operations team.
Project phases
Viability assessment
Analysis of the problem, the parties and the trust boundaries, ending in a reasoned decision on whether a distributed ledger is warranted.
Governance and data model
Agreeing joining rules, permissions and dispute handling, and settling what is written to the ledger versus held outside it.
Network setup
Standing up the permissioned network, its environments, and participant identities, permissions and keys.
Transactions and integration
Building the shared transaction logic and access interfaces, and connecting each participant system through a documented integration layer.
Contained pilot
Running one real process with actual participants and measuring what changed in reconciliation effort and cycle time.
Operations and expansion
Handing operations and monitoring to each participant team, then adding processes and members in stages.
- Estimated timeline
- 10 to 18 weeks
- An estimate that depends on scope and how quickly reviews come back — not a contractual commitment in itself.
- Pricing
- After scoping
- Scope depends on participant count, how many systems need integrating, and how intricate the agreed governance is. You can start with a short viability assessment priced separately before committing to delivery.
Scope and working details
What is in and out of scope, how we work, and what we need from you.
What is included
- A straight viability assessment: does this need a distributed ledger, or a database and integration.
- Defining participants, trust boundaries, and what each party must see or must not see.
- Governance design: joining, permissions, dispute resolution, operating responsibility.
- Data modelling, including what is written to the ledger and what stays outside it.
- Network setup, environments, and participant identity and key management.
- Development of the shared transaction logic and the interfaces that reach it.
- Integration with each participant system through documented APIs and an integration layer.
- An operations, monitoring, backup and tested-restore plan.
- Running a contained pilot with real participants before any expansion.
What is not included
- Issuing or promoting any token, investment offering or fundraising activity.
- Legal or regulatory advice, or representation before any authority.
- Drafting the agreements between participants — we prepare the technical basis, your counsel drafts.
- Operating the network on participants' behalf after handover, unless separately arranged.
- Changes to each participant's internal systems beyond the agreed integration points.
How we work
The first session is a blunt assessment: what the problem is, who the parties are, and where trust actually breaks today. If the parties already trust one operator and integration would solve it, we say so and save you a project you do not need. Where a shared ledger is warranted, governance is settled before technology, because these networks fail on who decides far more often than on which platform. We then prove it with a contained pilot — one real process, real participants — and expand only once it holds up in day-to-day operation.
What we need from you
- An executive sponsor with the authority to convene participants and make decisions.
- Initial commitment from the other parties to take part in design, not only in the pitch.
- A description of the current process and the documents exchanged between parties.
- A technical contact at each participant with authority over their integration.
- Legal review on your side of the participation agreements before go-live.
Methodology and technology
We work on permissioned platforms such as Hyperledger Fabric, or Ethereum Virtual Machine compatible networks operated under closed permissions, choosing between them on data sensitivity, participant count and what the operating teams can realistically maintain. Only what genuinely needs to be shared and evidenced goes on the ledger; sensitive detail stays off it, bound by a verification hash. Integration with participant systems runs through documented APIs and an integration layer. Operations use containers and reproducible infrastructure with monitoring, backup and tested restore. Anything touching payments or financial assets is subject to legal and regulatory review by your advisers, and we make no investment or financial promises.
How this connects to the rest of our work
A service rarely works alone. These come before it or alongside it, and these are the solutions it forms part of.
Services that work with it
Blockchain Strategy and Use-Case Design
An honest read on whether blockchain fits your business, where value sits, and the simpler option.
Web2 and Blockchain Integration
Bring on-chain activity into the systems you already run — one reconciled, monitored record.
APIs and Systems Integration
Documented APIs and an integration layer that keeps your systems in step — and alerts you when it cannot.
Tokenization Technology Architecture
Architecture for tokenising an asset or right: lifecycle, controls and an auditable record.
Solutions close to it
Frequently asked questions
Do we actually need blockchain, or would a shared database do?
We raise that question before you do. If every party trusts one organisation to run the system, a central database with integrations and an audit log is simpler, cheaper and faster to operate. A distributed ledger earns its place when no party will accept the record sitting under another party’s control. Settling that is the entire purpose of the viability assessment, and we write the recommendation even when it says do not proceed.
Who operates the network and who pays for it?
Decided in the governance document before go-live, not afterwards. Common arrangements are each participant running its own node, a neutral operator funded jointly, or the lead sponsor operating initially with an agreed path for others to join. We lay out the options with their operational and cost implications; the choice belongs to the participants.
Will our data be visible to competitors on the same network?
Not by default. Permissioned platforms let you control which parties see which data, and sensitive detail can stay off the ledger entirely with only a verification hash written to it — enough to prove a record exists without revealing it. That separation is designed during data modelling and signed off by each participant before anything runs.
What happens if a participant leaves?
The answer belongs in writing before anyone joins, not at the moment of departure. Governance covers revoking permissions, what happens to historical records, how the network continues with the remaining members, and the departing party’s right to a copy of its data. We prepare the technical basis; your counsel drafts the terms.
Does this involve issuing a coin or token?
No. The enterprise networks we build require no tradeable token or currency, and we make no investment offering or financial promise. If your case does involve payments or assets with financial value, that is a different route and is subject to legal and regulatory review by your advisers before any implementation.
What is the lowest-risk way to start?
A short viability assessment that settles the decision either way, followed by a contained pilot covering one process with a small set of parties. That surfaces the real obstacles early — usually regulatory and operational rather than technical — before you commit to a full network and a long budget.