Insights / Web3
Do I Need a Token? A Decision Framework for Web3 Founders
Default to no. A token is a job, not a fundraising costume. If Stripe, a membership, or equity already runs the business, you do not need a ticker.
Do I need a token? Default to no. A token, here, is a digital unit on a ledger that people hold, spend, or transfer. Most teams asking the question already have a product that can charge, a company that can issue equity, or a membership that can gate access. They want a ticker because a round, a competitor, or a conference made a ticker look like progress. A token is a job. If you cannot name the job in one sentence, you do not have utility. You have a costume.
Utility is the job the token does in the product — a job a user must hold or spend the token to complete. Tokenomics is the spreadsheet: supply, unlocks, and incentives. Fix the job first. If the token is optional in the product, the spreadsheet is fan fiction. See Tokenomics for Founders after this filter, not before it.
As GM at ChrysusDAO and founder of BlocksGenie Technologies LLC, I have watched this decision from the operator side of DeFi (decentralized finance) and from the advisory side of teams who were told to “add a token.” The teams that survive are the ones who can delay the ticker until a job appears. The teams that struggle are the ones who mint first and invent the job in public.
This brief is a commercial filter. It is not a legal conclusion. Tokens may be securities depending on facts and jurisdiction. Licensed counsel answers that. I will not.
Do I need a token? Default to no
Start with the existing rails. Payments: cards, invoices, ACH, Stripe, a bank. Access: accounts, licenses, API keys. Ownership of the company: equity, options, a shareholder agreement. Ownership of a cash-producing asset: a fund interest, a note, a contract. If those rails already do the work, a token adds wallets, listings, market structure, and a new way to fail.
The burden of proof is on the token. It must do a job those rails cannot do, or cannot do at a cost you will actually pay. “Our category has tokens” is not proof. “We need a community” is not proof. Communities exist around products that charge in dollars. Discord is not a protocol.
Defaulting to no is not hostility to crypto. It is respect for the cost. Once a token exists, you have holders with expectations, a price someone will screenshot, and a support burden that looks like customer service plus investor relations plus amateur market making. You opted into that. Be sure.
If the honest motive is fundraising, say so internally. Then call counsel. Do not ask a tokenomics vendor to turn a round into a “utility” story. That move has a long, public history. It is also outside what I will help you write.
A token is a job, not a fundraising costume
A fundraising costume is Web3 language wrapped around a round that could have been equity. The product works in dollars. The deck leads with a TGE (token generation event — a public token launch). The utility section is a list of future maybe’s. Do not put that in the same paragraph as a real job.
Jobs I will take seriously, in commercial language:
- Access — the token is how a defined set of users unlock a defined function, and cash cannot do it without breaking the design.
- Work — the token pays for a unit of work in a network of providers who will not invoice one company.
- Settlement — counterparties need a shared unit that is not one firm’s IOU.
- Coordination — many independent parties must vote or stake on rules they will not let a CEO change by email.
Jobs I will not take seriously without more evidence:
- “Rewards” that are a discount by another name, with a price chart attached.
- “Governance” over a product the team will keep operating regardless of the vote.
- “Alignment” with no mechanism except hoping holders tweet.
- “Liquidity” for an asset that has no natural counterparties.
If the token is optional in the product — users can do everything with a login and a card — then the token is a side bet. Side bets can be a business. They are not utility. Do not put them in the same paragraph.
Costume fundraising looks like this: the product works in fiat, the deck leads with a TGE, the utility section is a list of future maybe’s, and the team cannot describe what happens if the token price goes to zero. If the product still works at zero, you did not need the token for the product. You needed it for the round. Say that to counsel. Do not say it to Twitter.
A six-step filter before you mint
Work through these in writing. Not in a war room with a vendor. On paper.
- What does the user do today, in the product, without a token?
- Which of those actions fails if we never mint?
- Who must hold the token to do that action — and why will they hold it when the price is ugly?
- What happens to the product if the token cannot be transferred, listed, or sold?
- Who is the operator when something breaks — a company, or “the DAO” as a slogan?
- What will you tell a holder who asks whether this is an investment? (Draft it. Then take the draft to counsel. Do not publish my or your amateur version.)
If step 2 is empty, stop. You have your answer. Ship the product. Charge money. Issue equity if you are raising for a company. Come back to a token when step 2 is not empty.
If step 2 is full, you still may not need a public token. Points, a closed ledger, a permissioned instrument, or a simple API credit can do network accounting without a ticker. Public tokens are for when the public is actually a party to the job. Most B2B products do not have that party. They have customers.
| If this is true | You likely need | You likely do not need |
|---|---|---|
| Users pay you for software | Billing and a product | A ticker |
| You are raising for a company | Equity and counsel | A “utility” cover story |
| Many independent parties must settle | A shared unit and rules | A points program called a token |
| You have an off-chain asset to service | A structure — see RWA tokenization | A public memecoin wrapper |
| Someone asked for a TGE date | A written job, then counsel | A countdown on a landing page |
What a commercial “yes” still does not decide
A commercial yes — “this product has a job for a token” — is not a legal yes. It is not a listing. It is not a design for supply, unlocks, or market making. It is permission to continue the work with the right professions in the room.
Counsel decides how the instrument is offered, if it is offered, and what you may say about it. I will repeat the only sentence that belongs in a commercial brief: tokens and tokenized assets may be securities depending on facts and jurisdiction. Do not ask a strategist to bless a structure. Ask a lawyer.
Engineering decides how the job is encoded after the job is specified. Spec first. If you hire engineers to discover the job, you will discover it on-chain, in public, with holders. That is a hard classroom.
Go-to-market decides who must hold the token and how they get it without turning every user into a bagholder (someone stuck holding a token they did not need for the product). Distribution is part of the product. Airdrops — free token distributions — are not a strategy. They are a distribution tactic with a long memory.
If you want an outside commercial read on whether the chain belongs at all, that is blockchain consulting as I practice it — product first, ticker last.
How teams talk themselves into a bad yes
Competitor has a token. So will we. Competitors also have debt, lawsuits, and dead Discord channels. Copy the product if it works. Do not copy the ticker as a superstition.
Community wants a token. Which community — users who pay, or spectators who want a chart? Pay the first with a better product. The second will not save a weak one.
Exchanges will not talk to us without a token. Then you are buying a listing process, not a product feature. Price that as a listing process. Put counsel on it. Do not redesign the software around a listing questionnaire.
Employees want tokens instead of cash. That is compensation design. Compensation design is legal and tax work. It is not a reason to invent utility in the app. If the app does not need a token, do not add one so you can pay people in it. Find another way, with advisors who do employment and securities work.
The round is easier with a TGE story. Maybe, in some rooms, in some years. Easier is not the same as cleaner. You will live with the holders after the round. Plan for that life, not for the announcement.
A 30-minute internal exercise
Put the founding team in a room. Ban the words ecosystem, alignment, and community for thirty minutes. Describe the product as if to a customer who will never own a token. Then add one sentence: “The token exists because ___.” If the sentence is embarrassing, believe the embarrassment. Kill the ticker. Ship the product.
If the sentence is specific and survivable when the price is down 80%, you have a candidate. Write it. Take it to a commercial session if you want pressure on it. Then take it to counsel. In that order.
Getting an outside yes or no on the token
These packages are a commercial filter. They do not include tokenomics modeling, whitepapers, legal opinions, investor introductions, or a claim that a token is or is not a security. I will not help you dress a round as utility.
| Package | Price | What you receive | Best for |
|---|---|---|---|
| Web3 Strategy Session | $249 · 60 min | A yes or no from the conversation. No homework. No written document. | Whether to keep working the token idea or put it down for a defined period |
| Project Review | $499 · up to 3 materials | Up to 60 minutes of review, then 90 minutes in the room, then a short action summary. I will mark costume language. I will not rewrite your whitepaper. | When you already have a deck, a site, or a utility note |
| Web3 Strategy Blueprint (featured) | $999 | Up to five materials, two hours of review, a 5–8 page 30/60/90-day plan, and a 45-minute follow-up within 30 days | When several people must share the same plan — including a plan that says “no token this quarter” |
BlocksGenie can build the software when the commercial design is settled. A token is not a prerequisite for that build. Many of the best builds never have one.
Questions people ask
Do startups need a token?
Usually no. You need a product, distribution, and unit economics first. A token is for a job that a normal payment, membership, or equity instrument cannot do.
When does a token make sense?
When many parties must be paid, accessed, or coordinated without a single company’s database as the source of truth — and when those parties will actually use the token for that job. Not as a fundraising costume.
What is the difference between token utility and tokenomics?
Utility is the job. Tokenomics is the spreadsheet. Fix the job first. If the token is optional in the product, the spreadsheet is fan fiction.
Can I use a token to raise?
Fundraising is a legal and commercial process. A token does not make it simpler. Whether a token is a security depends on facts and jurisdiction. That is for licensed counsel, not a blog post or a strategy session.
What if investors asked us to launch a token?
Treat it as a request to examine, not as an order. Write the job. If there is no job, the honest conversation is equity, revenue share, or a delayed decision — with counsel in the room for the structure.
Should I hire a tokenomics consultant first?
No. Decide whether you need a token. Then decide what it does. Modeling without a job is decoration. See Tokenomics for Founders.
Do your packages include a token design?
They include a commercial filter: yes or no, what stays off-chain, and a 30/60/90 if you buy the Blueprint. They do not include tokenomics modeling, whitepapers, or legal opinions.
Not legal or investment advice. Tokens and tokenized assets may be securities depending on facts and jurisdiction.