Who owns the intellectual property in the work you deliver?

You own everything. Full assignment of all work product on final payment, written into the master agreement.

Will you sign an NDA before we discuss the project?

Signed before the first call if you want one. We'll work under yours rather than ours.

Are there taxes or surcharges added to the quoted price?

No tax added to your invoice. The number in the proposal is the number you pay — no surcharges, no adjustments at the end.

What time zones do you overlap with?

Working-day overlap across five regions. Full overlap with the Middle East and South East Asia, most of the day with the UK and EU, and four hours with US Eastern.

What happens to our code and infrastructure if we stop working together?

No lock-in. Your repository, your infrastructure, your accounts, from the first commit.

← All notes

Web3 product architecture

Why most Web3 products fail at the lifecycle level

The contracts are audited, the math is elegant, and a month after launch the funnel is dead at “Connect Wallet”. The problem is almost never the protocol — it is treating UX as a skin applied at the end rather than an architectural constraint set in week one.

Product funnel optimisation · architecture-led UX · smart contract co-design

Stondel28 July 20269 min read612 views

If you have spent time building or investing in decentralised applications, you know the standard Web3 post-mortem. The team raises a seed round, hires a top-tier contract shop, passes two independent audits and launches on mainnet. The protocol is secure. The math is elegant. The contracts are verified on Etherscan.

Then comes the quiet part. A month later the dashboard shows thousands of visits, a cliff at "Connect Wallet", and almost no daily active users. The post-mortem blames market conditions or a lack of crypto-native awareness. Inspect the product closely and the real diagnosis is duller: user experience was treated as a frontend skin to be applied at the end, rather than an architectural constraint engineered in week one.

The onboarding math is brutal

SaaS teams obsess over friction. Add two clicks to a checkout and conversion drops measurably. Standard Web3 onboarding does not add two clicks — it introduces an entirely foreign mental model, and it does so before the user has seen any value.

A non-crypto-native user landing on a typical dApp hits four cognitive walls in sequence:

The extension barrier — "install a browser plugin, leave this tab, configure a vault." Drop-off around 40–50%.
The key custody panic — "write down twelve random words. Lose them and your assets are gone forever." Drop-off around 15–30%.
The on-ramp tax — "go to an exchange, pass KYC, buy native tokens, wait for withdrawal, bridge across chains." Drop-off around 60–80%.
The calldata blind sign — "approve this unreadable hex blob." Drop-off around 10–20%.

Abstracting infrastructure with embedded accounts

To stop the decay, UX decisions have to dictate protocol architecture from day one. Rather than requiring users to bring an externally owned account from a browser extension, modern products use embedded wallets backed by MPC or account abstraction — ERC-4337 today, EIP-7702 as it lands.

TRADITIONAL WEB3 FLOW
[User] ──► [Install Wallet] ──► [Seed Phrase] ──► [Buy Gas] ──► [Sign]

MODERN STONDEL STACK
[User] ──► [Passkey / Social Login]
              │
              ▼
[Smart Account (ERC-4337 / 7702)] ──► [Paymaster (sponsors gas)]
              │
              ▼
[Session Keys (auto-signed)] ──► [Instant chain execution]

Co-engineering contracts with the interface

The costliest mistake in legacy Web3 development is treating contract engineering and frontend engineering as sequential, isolated tasks. When contracts are designed in a silo, bad UX gets hardcoded into the blockchain — where it is expensive and sometimes impossible to fix.

Take a classic ERC-20 deposit into a yield vault. Call approve(). Wait for confirmation. Call deposit(). Wait again. Two transactions and two gas payments for one intention, and a drop-off cliff in the middle of it.

Co-designing the contract with the people building the interface produces a different shape: ERC-2612 permit for signature-based off-chain approval, and atomic multicall batching. Approve and deposit collapse into a single signature.

When contracts are designed in a silo, bad UX gets hardcoded into the blockchain.

What that looks like across a build

Phase	Engineering focus	UX deliverable
Architecture	Contract design, state machine logic, account abstraction choices	Zero-seedphrase auth mapped out; gas sponsorship logic defined
Core build	Solidity logic, Foundry invariant testing, off-chain indexing	Multicall batching implemented; human-readable error mappings
Integration	viem/wagmi integration, optimistic UI layer, custom indexer pipelines	Real-time transaction step-trackers; sub-second state reconciliation
Mainnet launch	Audits, paymaster monitoring, fallback RPC configuration	Onboarding verified frictionless; wallet flows hold under load

None of this is exotic. It is ordinary product discipline applied to a backend that happens to be adversarial, public and expensive to change — which is exactly why it has to happen in week one rather than week twenty.