Skip to main content

Blockchain Strategy and Use-Case Design

An honest read on whether blockchain fits your business, where value sits, and the simpler option.

The problem we solve

The pressure usually comes from outside the technical team: a board asking for a position, a vendor demonstrating a platform, a competitor announcing an initiative. Projects then start on enthusiasm and stall on a question nobody answered — why would a shared database not do this, who else joins the network, and what keeps them there. Legal and regulatory questions surface after the build has begun, which is the most expensive point to discover them. The result is a proof of concept that never reaches production. We move those questions to the front, where answering them is cheap.

Expected outcomes

  • A documented go, defer or do-not-build decision with reasoning your board can review.
  • The highest-value, lowest-complexity use case identified as a realistic entry point.
  • Clarity on which parties participate and what makes each of them join and stay.
  • A specific position on what belongs on the ledger and what stays in your own systems.
  • A grounded view of build and running costs before any budget is committed.
  • A defined list of legal and regulatory questions to put to your counsel before development.
  • A phased roadmap starting with a proof of concept that has measurable acceptance criteria.

Who this is for

  • Boards and executives being asked to take a position on distributed ledger technology.
  • Logistics and supply chain operators working across many parties and conflicting paperwork.
  • Issuers of documents or certificates that third parties need to verify independently.
  • Organisations exploring digitised assets or ownership records who need a realistic read first.
  • Innovation teams holding an early idea that needs either scoping or an early exit.

Use cases

  • Pressure-testing an existing idea before development budget is allocated.
  • Designing a supply chain traceability model spanning suppliers, carriers and inspectors.
  • Designing a verification mechanism for documents your organisation issues to others.
  • Choosing between a permissioned network among known partners and a public network.
  • Assessing digitisation of an asset or ownership record, including the legal path required first.
  • Reviewing a vendor pitch or ready-made platform before signing.

Deliverables

  • A feasibility report with an explicit verdict: build now, defer, or use a simpler alternative.
  • A use-case document covering parties, data flow, and what is and is not recorded on-ledger.
  • An architecture comparison of the shortlisted options against stated, written criteria.
  • An initial cost model that can be updated as assumptions change.
  • A risk register combining technical, operational and regulatory risks with proposed mitigations.
  • A proposed proof-of-concept scope with measurable acceptance criteria.
  • A short decision briefing built for a non-technical audience.

Project phases

Framing

A working session with decision-makers on the commercial problem, the parties involved, and what success means in business terms.

Necessity test

Test the conditions that justify a shared ledger against simpler alternatives, documenting why each option is ruled in or out.

Model design

Map participants and their incentives, the data flow, and what sits on-ledger versus staying in your systems behind a verification reference.

Architecture and cost

Compare network options and operating models, and build an initial view of capital and running costs.

Risk and regulatory path

A technical and operational risk register, plus the specific legal questions to settle with your counsel before any build.

Roadmap

Sequence the phases, define the proof-of-concept scope and acceptance criteria, and present the decision for sign-off.

Estimated timeline
3 to 6 weeks
An estimate that depends on scope and how quickly reviews come back — not a contractual commitment in itself.
Pricing
After scoping
Starts from a defined scope covering a single use-case assessment, and expands with the number of use cases, participating parties, and the depth of cost modelling required. Final scope is set after the framing session.

Scope and working details

What is in and out of scope, how we work, and what we need from you.

What is included

  • A framing workshop with decision-makers on the commercial problem and success criteria.
  • A necessity test: multiple parties, incomplete trust, and genuine need for a shared record.
  • An explicit comparison with alternatives: shared database, API integration, or a trusted intermediary.
  • Governance design: who joins, who operates nodes, and how upgrade and exit decisions are made.
  • Architecture decisions: permissioned or public, and what is recorded on-ledger versus off.
  • Integration points with your existing systems and the data flow between them.
  • Estimates for build, running costs, network fees and the operational risks attached.
  • A defined list of legal and regulatory questions to resolve with your counsel before building.
  • A phased roadmap opening with a narrowly scoped proof of concept and its acceptance criteria.

What is not included

  • Legal, tax or regulatory advice — we identify the questions for your qualified counsel to answer.
  • Investment advice, promotion of digital assets, or any assistance with fundraising — entirely outside our scope.
  • Smart contract or application development, which is a separately scoped later stage.
  • Handling client funds, custody of digital assets, or operating wallets on your behalf.
  • Any promise of regulatory approval, listing, or acceptance by any authority or platform.

How we work

The engagement opens with a necessity test, not a platform discussion. If the conditions are absent — multiple independent parties, incomplete trust, a genuine need for a shared record — we say so and point to the simpler option, and we treat that as a successful outcome because it saves you an entire programme. Where the conditions do hold, we design the smallest scope that proves value rather than a full platform built before a single user exists. Anything touching financial assets or funding instruments is subject to independent legal and regulatory review before execution, and we make no investment or financial promises of any kind.

What we need from you

  • Decision-makers present in the framing workshop, not delegates without authority.
  • A description of the current process, the parties in it, and where it repeatedly breaks down.
  • Information on existing systems and realistic integration points.
  • A line to your legal counsel for the specific regulatory questions we surface.
  • Candour about budget and timeline so the recommendation is practical rather than theoretical.

Methodology and technology

We apply an explicit necessity test before any platform conversation: independent parties without full mutual trust, a genuine need for a shared record, and no acceptable single trusted intermediary. Where those conditions fail, we recommend the simpler alternative. Where they hold, we compare permissioned networks built on Hyperledger Fabric with public networks compatible with the Ethereum Virtual Machine, and define precisely what is written on-ledger versus held in your systems behind a verification reference. Proofs of concept are designed on test networks first. Any work touching financial assets, funding instruments or token issuance is subject to independent legal and regulatory review before execution, 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

Part of these solutions

Frequently asked questions

Might you conclude that we should not use blockchain at all?

Yes, and it happens. Plenty of cases resolve with integration work or a shared database at far lower cost and complexity. When that is the answer we write it plainly with the reasoning behind it — the value of the assessment lies as much in stopping the wrong programme as in starting the right one.

Why not simply use a shared database?

In most situations you should. A distributed ledger earns consideration when independent organisations must share a record that none of them can alter unilaterally, and where none of them will accept that record sitting under a single party’s control. If either condition is missing, the simpler option is the better engineering answer.

Do we need to issue a token or a coin?

The large majority of enterprise use cases do not. Anything touching financial assets, funding instruments or digital issuance carries legal and regulatory consequences that must be settled with your counsel before design begins. We do not provide investment advice and make no financial promises; we identify the questions and who is qualified to answer them.

What is the regulatory position in this market?

Regulation in this space continues to develop, and we do not offer legal interpretation or speak on behalf of any authority. What we hand over is a specific list of questions and which body each one belongs to, so your legal counsel can resolve them before any execution commitment.

Are we committed to building with you afterwards?

No. The report is written to be executable by any competent team, including your own or another supplier. If you do want us to build, the proof-of-concept phase is quoted separately with its own scope and acceptance criteria.

How will we know whether the proof of concept worked?

Because acceptance criteria are agreed before the build rather than after: which commercial transaction runs through the model, which parties actually use it, and what measurable difference it makes against the current process. Without that, a proof of concept becomes a technical demonstration that leads to no decision.

Have an idea, or a system that needs work?

Start with a short session to understand where you stand and what the next step should be. If the scope is clear, a written proposal follows.