TriaChain Solutions / due diligence

Technical due diligence, in language you can act on.

Every pitch deck says the platform is proprietary technology. Sometimes it is. Sometimes it is a thin layer over somebody else's API, held together by one contractor who has stopped answering. We read the code and tell you which one you are looking at, before the money moves.

// what we take on

Four reasons people ask us to look

[01] investment

Before you invest

You are putting money into a company whose main asset is software you have never seen. We tell you what the repository supports, what the deck claims, and where those two disagree.

[02] acquisition

Before you buy

An acquisition where the technology is the point. We look at what you are actually acquiring, what it depends on, and what it will cost to run once the founders leave.

[03] your own

Your own product, honestly assessed

Delivery has slowed and nobody can tell you why. We read the code and the process, then give you a straight answer, including when the answer is that the code is fine and the problem is elsewhere.

[04] cto

Technical judgement when you need it

Fractional CTO work for board meetings, hiring decisions and vendor choices. You get a direct technical view instead of relying on a supplier's version of what is possible.

// how it works here

How we work on this

  • Plain language, no theatre. You get a written report a non-engineer can act on: what works, what will break, what it costs to fix, and which risks are worth living with. Technical detail goes in an appendix for your own engineers.
  • We say when it is fine. A review that always finds catastrophe is a sales pitch. Sometimes the honest answer is that the code is ordinary, the team is competent, and your risk sits somewhere else entirely.
  • Contract audits stay with auditors. For code that will hold money on chain, our review is not a substitute for a specialist security audit, and we will tell you to commission one.
  • We do not bid on the rebuild. If we recommend replacing something, we are not the ones quoting for it unless you ask us to be. It keeps the assessment honest.
// questions

What clients ask first

What do we get at the end?

A written report: an honest summary in plain language, a list of risks ranked by what they would actually cost you, and a technical appendix for your engineers. Plus a call to go through it.

How long does a review take?

Usually one to two weeks depending on the size of the codebase. If you are under an offer deadline, tell us and we will say honestly whether we can do it properly in the time.

What do you actually look at?

The code and its history, the architecture, the dependencies, how it is deployed and monitored, how many people understand it, and how much of the value sits in systems the company does not own.

Can you review a blockchain project?

Yes. The team's experience includes core protocol work on Polkadot at Parity Technologies and the Forest Filecoin node at ChainSafe, so we know what to look for beyond a fork with a new logo.

What is fractional CTO work?

A few days a month for architecture decisions, hiring, vendor calls and board questions. Useful when the company needs ongoing technical judgement but not a full-time CTO.

Do you sign an NDA?

Yes, before we look at anything, and we work with whatever data room arrangement the deal requires.

// contact

Tell us what you are about to sign

Write in plain words: what the company claims to have built, what you are considering, and by when you need an answer. One of the three of us answers, usually the same day.

info@triachain.com