Anthropic Co-founder’s “Unusual” Founder Advice: Travel Together First, Then Decide Whether to Build a Crypto Startup

May 12, 2026

In crypto, “choosing a co-founder” isn’t just about complementary skills. It’s about shared risk tolerance, security instincts, and decision-making under pressure—because in a Web3 startup, a small set of humans often are the control layer (treasury signers, upgrade admins, emergency responders, and public-facing credibility).

That’s why a piece of founder advice from outside the blockchain world resonates so strongly: Anthropic co-founder and President Daniela Amodei suggested that before you start a company, you should travel together—ideally long enough (and close enough) to see how you actually operate day-to-day. The idea was covered in Fortune’s report on her Stanford remarks and echoed by Stanford student coverage of her campus talk.

For blockchain founders, this “travel test” maps surprisingly well to what makes (or breaks) a crypto company.

Why the “travel test” fits Web3 better than traditional startups

A normal startup can survive some founder friction if the product is good and the market is forgiving.

A crypto startup often can’t—because the failure modes are harsher and faster:

Security incidents are operational, not hypothetical. When something goes wrong, it’s rarely a calm meeting on Monday. It’s a 2 a.m. call with incomplete information and irreversible transactions.
Public trust is part of the product. Communities, token holders, and partners watch how founders behave under stress.
Governance is human before it’s on-chain. Even in “decentralized” projects, early-stage reality often looks like a small group coordinating upgrades, signers, disclosures, and priorities.

Travel compresses months of working style discovery into a few days: planning, disagreements, fatigue, miscommunication, unexpected problems, and conflict resolution.

If you can’t align on where to eat, who pays, and how to recover from a missed train, it’s worth asking: how will we align on a token launch timeline, an exploit response, or a runway-extending pivot?

Co-founder alignment in crypto is a security primitive

Daniela’s broader point—beyond the travel anecdote—is that stable founding teams tend to have deep prior context and a shared way of giving feedback. That’s visible in how Anthropic formed, with founders who had worked together previously.

In crypto, this matters because “trust” isn’t a vibe; it’s an attack surface.

Recent reports highlight how attackers increasingly target people and processes, not just smart contracts:

The Chainalysis 2026 Crypto Crime Report (scams) describes increasingly industrialized scam operations and projects that 2025 scam revenue could rise as attribution improves.
The TRM Labs 2026 Crypto Crime Report similarly emphasizes how compromising operational infrastructure (keys, signers, orchestration) can be higher ROI than novel contract exploits.

A misaligned or careless co-founder can unintentionally create exactly those weak points: sloppy key handling, risky admin setups, rushed integrations, poor disclosure judgment, or insecure travel habits.

A practical “co-founder offsite” playbook for blockchain teams

Think of this as a structured version of “go travel together”—built for Web3 realities like self-custody, multisig, and adversarial environments.

1) Vision: do you want to build the same kind of crypto business?

Before debating features, align on fundamentals:

Is this DeFi infrastructure, a consumer wallet experience, tokenized real-world assets, or an on-chain game?
Is the goal to be maximally permissionless, or compliance-forward?
Are you building for developers or retail users?
What are your non-negotiables on transparency, custody, and risk?

A simple exercise: separately sketch your “company in 24 months,” then compare. If the pictures look like two different species, you don’t have a “minor disagreement”—you have two companies.

For a timeless warning on founder selection, see Paul Graham’s essay on what founders regret most: character and commitment over raw ability.

2) Roles: who owns what when the market turns and the chain halts?

Crypto teams often fail in the gaps between responsibilities.

On your offsite, write down:

Who is the final decision-maker on security posture?
Who owns smart contract deployment and upgrade processes?
Who handles community communications during incidents?
Who negotiates exchange listings / market makers / partnerships (and what is “off-limits”)?
Who owns compliance and risk (even if you’re early)?

If you can’t assign ownership clearly, your incident response will default to chaos.

3) Security: can you agree on custody, signing, and emergency controls?

This is where many “great on paper” teams quietly diverge.

Do a tabletop session that answers:

Where do keys live: hot, warm, or hardware-isolated?
What requires multisig: treasury moves, contract upgrades, DNS, social accounts?
What’s the policy for approvals: limits, delays, and out-of-band verification?
What’s your plan for travel: device exposure, SIM swap risk, and account recovery?

This matters even more as scams increasingly originate from social platforms. The U.S. regulator community has been explicit that many reported scams begin on social media; see the FTC’s 2026 data release on social media scams.

4) Compliance mindset: can you survive the “rules catch up” phase?

Even teams building open protocols operate in a world shaped by AML expectations, exchange standards, and jurisdictional realities.

At minimum, founders should share a baseline understanding of requirements like the Travel Rule landscape; the FATF’s 2025 targeted update on virtual assets and VASPs is a useful reference for how global expectations are evolving.

You don’t need to agree on every detail today—but you do need the same direction of travel.

Turn the travel idea into a 48-hour “founder compatibility test” (no flights required)

If you want the spirit of the advice without a big trip, run this:

Day 1 (Pressure + clarity)

Morning: hard conversation rehearsal (equity, vesting, token allocation principles, kill switches)
Afternoon: security workshop (signing policy + incident simulation)
Evening: no-work hangout (observe energy, empathy, and conflict style)

Day 2 (Execution + ethics)

Morning: write the 12-month roadmap independently, then merge
Afternoon: define decision rights + escalation paths
Wrap: agree on 3 non-negotiables and 3 “we can compromise” items

If you finish and your honest reaction is “I trust this person more,” that’s signal. If you finish and feel depleted, treat that as data—not drama.

Where OneKey fits: make self-custody part of founder culture

A crypto company’s security is often only as strong as the founders’ daily habits. Using a hardware wallet isn’t just for long-term holders—it can be part of how a team operationalizes private key management, separation of duties, and safer approvals.

If your startup is moving toward multisig treasury workflows or simply wants stronger operational security for founders, OneKey hardware wallets can help by keeping signing isolated from internet-connected environments and making “secure by default” easier to practice consistently—especially when your team is remote, traveling, or operating under time pressure.

In Web3, you’re not only building products—you’re building trust. Test the partnership like it matters, because in crypto, it does.