The Market Intelligence Report (Version 1)

A few weeks ago I sent an early version of my business to 44 people that I trust.

One aim: tell me why this won’t work.

Well over twenty people have replied thus far. Some loved it. Some challenged it. One of my friends literally told me to get a job.

What I didn’t realise at the time was that I wasn’t collecting feedback. I was accidentally building a market intelligence database.

That distinction sounds small. It isn’t.

Opinions vs patterns

One person’s opinion is interesting. Five independent people saying the same thing is a pattern. Patterns become evidence. Evidence changes decisions.

That’s the framework I’m now building the Bitcoin Custody Architect around. Not intuition. Not assumption. Repeated market signals.

Here’s what Version 1 of that intelligence looks like.

Insight 1: Recovery beats sovereignty

My original hypothesis was that people care about sovereignty. The offer was called “The Sovereign”. I believed in sovereignty deeply and assumed others did too.

But nobody talked about sovereignty…

They talked about losing access to their Bitcoin. They talked about their spouse not understanding their setup. They talked about inheritance, continuity, recovery, what happens if something unexpected occurs. Then I ran a public poll on X: Bitcoin falls 50% versus you lose access to your Bitcoin. The responses weren’t close. Losing access won decisively, with comments like “that’s a hundred percent loss” and “the thing of nightmares.”

Decision: recovery becomes the centre of the business. Bitcoin Custody Architect replaces The Sovereign.

Insight 2: Confidence, not documentation

I assumed people were buying architecture. Plans. Frameworks. The deliverable.

What I got instead was story after story. My Ledger died and I panicked. My wife wouldn’t have a clue where to start. I nearly lost everything when I forgot my passphrase. I sent Bitcoin to a wallet and it didn’t show up for three days.

People aren’t buying the plan. They’re buying the feeling of knowing the plan exists and works.

Decision: the real product isn’t documentation. The real product is confidence.

Insight 3: Architect, not provider

I had considered becoming a custody provider of some kind. The market talked me out of it.

Multiple people independently said the same thing: don’t compete with hardware wallet companies or collaborative custody providers. Sit above them. Help people choose. Help people understand trade-offs. Help them ask the right questions before they ever pick a tool.

How old are you? How many dependents do you have? How meaningful is it if this disappears? Does someone need to inherit this when you’re gone? These questions need answering before anyone touches a hardware wallet.

Decision: the architecture layer is the business.

Insight 4: Distribution comes through advisers

I assumed this was a direct-to-consumer business. Create content, build trust, convert readers to clients.

Nobody asked about distribution. But multiple people independently pointed toward financial advisers, family offices, and professional referral partners. Unprompted. In response to an offer I sent about Bitcoin custody.

Financial advisers can’t advise on Bitcoin. But their clients are already holding it. There’s a gap there that an architect who doesn’t hold keys and doesn’t give financial advice can sit inside cleanly.

Decision: the adviser referral channel becomes a strategic priority.

Insight 5: The relationship doesn’t end at delivery

My initial thinking was straightforward. Deliver the plan, job done, off you go.

Multiple people told me otherwise. Families change. Technology changes. The tools available for self-custody change. A plan built in 2024 may have gaps by 2026. A setup that made sense for two people may not make sense for two people and a child.

I actually found evidence of this in my own setup recently. Years into this. Still had a gap.

Decision: the annual review becomes part of the core customer journey from day one. Not an afterthought, not an optional upsell.

Insight 6: Stories, not specifications

Nobody in any of these conversations remembered technical details. Descriptor paths. Derivation standards. Backup verification procedures.

But everyone remembered stories. The time their Ledger died. The moment they realised their wife had no idea where the seed phrase was. The three days they spent sweating while a transaction failed to arrive.

Stories carry emotion. Emotion reveals what people actually value.

Decision: stories become the primary teaching mechanism for everything I produce.

What surprised me most

The biggest lesson from all of this had nothing to do with Bitcoin.

It was about me.

I’d been spending more time creating than listening. I built what I personally would have bought, which is the most natural thing in the world to do as a founder. It’s also a trap.

The better question is: what does the market actually want built?

That requires putting the ego down. It requires sitting with feedback that challenges your assumptions rather than reinforcing them. It requires noticing when five independent people are all saying the same thing you weren’t expecting to hear.

I wasn’t listening closely enough. I’m trying to change that.

This is Version 1

This market intelligence report is built from warm outreach, founder conversations, adviser discussions, public polls, social media responses, and competitor observations.

I expect Version 10 to look very different. That’s exactly the point.

The goal isn’t to be right from the start. The goal is to keep learning faster than everyone else. Because if I consistently understand what Bitcoin holders actually worry about, better products emerge. Better content emerges. Better decisions get made. And better outcomes follow for families trying to hold Bitcoin across generations.

If you have a custody story, a recovery experience, an inheritance challenge, or a mistake you learned from, I’d genuinely love to hear from you. Every conversation improves the next version of this report.

jakewoodhouse.io/bca or reach out on X.

This is Version 1. Looking forward to what Version 2 teaches us.