- BLOCKCHAIN
- ASSESS
- A8 · INTEGRITY FEASIBILITY SCAN™
- 2 WEEKS
Blockchain feasibility scan.Recommended against.Database-based alternative saved AED 8M.
A UAE enterprise evaluated blockchain provenance for a multi-party integrity workflow. The two-week A8 feasibility scan recommended against a blockchain approach, surfacing three structural reasons why the requirement did not need distributed consensus. The alternative — a database-plus-cryptography approach — was implemented at approximately 5% of the proposed blockchain spend, delivering equivalent integrity outcomes.
N=1 ILLUSTRATIVE COMPOSITE — representative pattern for a UAE enterprise operating at scale. Details drawn from patterns across NexITC engagements and market data. Not a specific client narrative.
THE SITUATION
The situation
The client is a UAE enterprise in the commodities sector, operating a complex multi-party workflow involving six categories of counterparties. The core requirement was integrity: a tamper-evident, timestamped record of transaction provenance that could be inspected by third-party auditors and regulators without relying solely on any single counterparty's internal systems.
The internal innovation team and two specialist vendors had proposed blockchain-based solutions. The proposals ranged from AED 4M to AED 8.5M in implementation cost, with significant ongoing operational spend for node maintenance and counterparty onboarding. The strategic thesis was that "only blockchain" could provide the required multi-party trust level.
The CEO had requested an independent scan of the feasibility before committing to the implementation spend. The request was specific: validate the primitive fit — is blockchain the only way, or the best way, to achieve the integrity requirement?
THE SPECIFIC QUESTION
The specific question
The clinic conversation surfaced the structural question. The CEO did not want a vendor recommendation. The CEO wanted a primitive assessment: if we don't use blockchain, what is the gap in integrity? If we do use blockchain, what is the overhead we are buying? The assessment had to be defensible against both the internal innovation team's thesis and the external vendors' proposals.
The Practice Lead's scoping response confirmed A8 as the right shape: a two-week scan focused explicitly on the requirement-to-primitive fit, with a "recommend against" clause in scope if the evidence supported it. The client accepted the scope within 48 hours.
APPROACH AND TIMELINE
Approach and timeline
The engagement ran two weeks against the specific workflow and the vendor proposals in hand.
Week 1 assessed the integrity requirements themselves: what specifically needs to be tamper-evident, at what latency, inspectable by whom, retained for how long, and under what regulatory framework. The requirements were documented against actual counterparty flows — not against generic "provenance blockchain" use case patterns from vendor briefings.
Week 2 assessed the primitive fit: does the requirement set actually need distributed consensus (blockchain's differentiating property), or would tamper-evidence via cryptographic signing on a shared database, combined with third-party notarisation of periodic hash checkpoints, close the requirement at substantially lower complexity? The assessment was structural — comparing what blockchain provides against what the requirement actually needs, category by category.
Practice Lead attendance ran across both weeks. The CEO attended the final readout given the "recommend against" positioning and the aggregate spend implications.
WHAT WE RECOMMENDED AGAINST
What we recommended against
The recommendation the engagement was scoped to be willing to make.
The engagement recommended against blockchain for this workflow. The reasoning ran across three structural findings.
Finding one: the workflow did not require distributed consensus. The integrity requirements — tamper-evident record, timestamped, third-party inspectable — could be satisfied by cryptographic signing on a shared database with periodic hash notarisation to an independent third party. Distributed consensus (the property that distinguishes blockchain from database-plus-signing) was not required by the workflow's actual verification demands. The vendor proposals had assumed distributed consensus was necessary; the requirement evidence did not support that assumption.
Finding two: counterparty coordination overhead exceeded marginal integrity value. Even if blockchain had been the right primitive, the six counterparty categories included several with limited technical readiness for blockchain node operations. The implementation would have required extended onboarding and ongoing coordination overhead that dwarfed the marginal integrity improvement over the database-plus-signing alternative.
Finding three: the vendor proposals conflated blockchain with governance frameworks. Much of what the proposals described as "blockchain benefits" — audit trails, multi-party workflow coordination, defined counterparty roles — were governance and process improvements that could be implemented alongside the database alternative at equivalent value.
The recommended alternative: shared database with cryptographic signing, third-party notarisation for periodic hash checkpoints, and the governance framework the vendor proposals had bundled with blockchain, implemented against the database alternative.
OUTCOMES
Outcomes
The board accepted the recommendation. The blockchain evaluation process was closed. The database-plus-signing alternative was scoped as a separate initiative and implemented by the client's internal engineering team with third-party notarisation contracted from a specialist provider. Total year-one implementation and operational cost of the alternative was approximately AED 400K — approximately 5% of the aggregate blockchain proposal spend the recommendation avoided.
The tamper-evidence, third-party inspectability, and workflow coordination outcomes the blockchain proposals had targeted were achieved through the alternative, with year-one operational cadence in place within four months of the A8 engagement close.
The A8 engagement fee was recovered many times over in the avoided spend on day one of the board decision.
WHAT COMES NEXT
What comes next
The client's follow-on relationship with NexITC subsequently expanded into a scoped advisory checkpoint on the database-plus-signing implementation acceptance criteria — a limited scope engagement rather than a full B13 ChainProof Build, appropriate to the alternative's technical shape. No blockchain work has been re-opened.
Adjacent SKUs: A8 · B13 ChainProof™ Build
Considering blockchain for a multi-party integrity workflow?
Book a clinic. Practice Lead attends. Roughly half of A8 engagements end with a "no-go" or "redesign" recommendation — because most integrity requirements don't need distributed consensus.