When should a brand not touch web3 at all?
Most of the time. A blockchain is worth using when you specifically want to give up control of a record so that other people can verify or transfer it without you, and most brand programmes want the opposite. If the honest reason for the project is that the board asked what the company is doing about web3, the correct output is a memo, not a token. This guide is the argument against, written by people who build these things.
What is the default answer?
A database. It is faster, cheaper, private, correctable, deletable, and it does not require your customers to learn anything. Every marketing capability commonly attributed to web3, including memberships, collectibles, rewards, tiers and digital items, is delivered on ordinary infrastructure daily and has been for decades.
The blockchain earns its place only when the record needs to be outside your control: verifiable by a third party who does not trust you, transferable by the holder without your permission, and durable if you stop operating. Those are real requirements in some businesses, and they are unusual requirements in marketing.
So the framing to bring into the meeting is not what could we do with web3. It is what part of this needs to work without us, and would we accept it working without us. If nobody can answer the second question comfortably, the project is already decided.
Which use cases actively fail?
Loyalty points are the clearest. The entire value of a points scheme to the issuer comes from control: you set the rate, you expire balances, you prevent trading, you adjust when the economics change. Putting points on a chain surrenders every one of those, creates a market price for your own liability, and hands anyone the ability to accumulate points without ever being a customer.
Ticketing is the second, and it is usually pitched backwards. Organisers generally want less transferability, not more, because uncontrolled resale is the problem they are trying to solve. Blockchain ticketing helps when the goal is portability and verifiable resale with rules; it hurts when the goal is stopping touts, because the technology is on the tout's side by default.
Then anything involving customer data. On-chain records are permanent and public, which is incompatible with correcting a mistake, honouring a deletion request or keeping a commercial relationship private. This is not a limitation to work around, it is what the technology is for.
| Proposed use | Why it gets pitched | Usually better | When web3 genuinely wins |
|---|---|---|---|
| Loyalty points | Tokenised rewards, tradable status | A normal points database | Points must be spendable across independent businesses |
| Event tickets | Stops fraud, enables resale royalties | Named-entry tickets with a controlled resale platform | Portability across venues matters more than stopping touts |
| Digital collectibles | Engagement, community, new revenue | In-app items with no resale market | Holders genuinely need to resell or take them elsewhere |
| Product authenticity | Provenance, anti-counterfeiting | A serial number checked on your own site | Resale platforms will verify without asking you |
| Membership and access | Portable, verifiable, tradable | Accounts and entitlements | Other organisations must honour the membership |
| Customer records | Ownership of data, transparency | Anything else at all | Never, in a consumer marketing context |
What costs are missing from the proposal?
Support, first and largest. A customer who cannot access their wallet has lost the asset permanently and you cannot restore it, which turns a routine password reset into an unresolvable complaint. Add sent to the wrong network, transaction failed but the fee was taken, bought from a marketplace and received a counterfeit, and approved a contract that emptied the wallet. Your support team will receive all of these and can fix none of them.
Then key management. Someone has to hold the keys that control the contract and the treasury, forever, including after they leave the company. This is a security and governance obligation of a kind marketing departments have never carried, and the failure mode is total: keys lost means the programme cannot be changed, keys stolen means it can be changed by someone else.
Then the code itself. Contracts are difficult to change after deployment, so a mistake in the rules is often permanent and public. Meaningful audits cost real money and reduce risk rather than removing it. Budget for the audit, the remediation and the possibility of migrating to a new contract, or do not deploy.
What is the reputational exposure?
Association, mainly. Consumers who have encountered crypto have often encountered it through a scam, a collapse or a friend losing money, and a brand entering the space inherits that prior. The response is not defensive messaging, it is either having a use case that survives an unsympathetic explanation in a single sentence, or not doing it.
Energy criticism has moderated as major networks moved to proof of stake, which dramatically reduced their energy consumption, but the perception persists and the correction requires explaining a technical distinction most audiences will not follow. Treat it as a live objection regardless of the current facts.
The exposure people underestimate is inheriting third-party behaviour. Your collectible trades on marketplaces you do not run, at prices you do not set, in listings you cannot remove, next to counterfeits of your own product. Press coverage will attribute all of it to you. That is the price of a public asset, and it should be accepted in advance or avoided.
How do you decide in one meeting?
Four questions, in order. Does the customer need to prove something to someone who does not trust us? Must the thing survive us shutting the programme down? Must the holder be able to transfer it without our permission? And is there a named person willing to own key management for the next five years? If the answer to the first three is no, stop. If the fourth has no name attached, stop regardless of the first three.
Then apply the reversal test, which is more revealing than any of them. Present the identical programme built on a normal database, with accounts instead of wallets, and see what anyone objects to. If the only objection is that it is less exciting or less newsworthy, you have your answer and you have saved a year.
Deciding not to do it is a legitimate output and is easier to defend now than it was a few years ago. The projects that aged worst were the ones commissioned for the announcement, and everyone in the room usually knows at the time which kind they are looking at.
Common questions
- When should a brand avoid blockchain in marketing?
- Whenever the programme does not need the record to work outside the brand's control. A blockchain is worth using when a third party must verify something without trusting you, when the holder must transfer it without permission, or when it must survive the company shutting the programme down. Absent those, a database is faster, cheaper, private, correctable and requires customers to learn nothing.
- Why are blockchain loyalty points usually a bad idea?
- Because the value of a points scheme to the issuer comes from control: setting the rate, expiring balances, preventing trading and adjusting when the economics change. Putting points on a public chain surrenders all of that, creates a public market price for what is accounting-wise a liability, and lets people accumulate points without ever being customers. The exception is points spendable across genuinely independent businesses.
- What are the hidden costs of a web3 marketing programme?
- Support that cannot resolve anything, since a customer who loses wallet access has lost the asset permanently. Key management as a permanent obligation, including after the responsible person leaves. Smart contract auditing and the possibility of migration, because deployed code is hard to change and a mistake in the rules is public and often permanent. None of these appear in a typical campaign budget.
- Is blockchain ticketing better than normal ticketing?
- Only when portability matters more than controlling resale. Organisers usually want less transferability, because uncontrolled resale by touts is the problem they are trying to solve, and a transferable token is on the tout's side by default. Blockchain ticketing helps where tickets should move between venues or platforms with verifiable rules, and hurts where the objective is stopping secondary sales.
- How do you decide whether to do a web3 project?
- Ask four questions: does the customer need to prove something to a party that does not trust you, must it survive the programme being shut down, must the holder transfer it without permission, and is a named person willing to own key management for five years. Then present the same programme built on a database, and see whether any objection concerns substance rather than novelty.
