What an investor will ask about your token

Before the first call, an investor asks what a person can do with the token, where the contract is, who holds the supply, what the code can still do, and who will answer. Write those five answers down. If you cannot answer one, say so. This page does not find an investor, and it does not tell anyone to buy. This is not financial advice.

You can answer every line and still receive nothing. A finished sheet is not a commitment from the other person. The costly miss is a promise the contract does not store: a future price, a yield, or a line that someone reviewed the project.

What the first call is

The call is a conversation about facts you can point to. It is not a sale. It is not a promise that the token will later trade on an exchange. The call can drift toward a future price, a place on an exchange, or a review. Those three are the lines to leave out. What you prepare is the part a person can check without taking your word.

What the token is for

One sentence is enough: who holds the token, and what they can do with it. Access, a vote, points inside a product, or a record of something they already did can fit that sentence. A sentence that fits: “People who use the booking app hold this token, and one token is one booking credit.” A sentence that does not: “The price will rise after the call.”

If the sentence is a future price, a yield, or any profit, rewrite it. An ERC-20 contract keeps a balance and a total supply. It does not keep a price. How to say the use, and what a stranger already checks, is in how to make people trust your new token.

If you do not have the sentence yet, the call is early. Write it before you book the time. The written plan for the audience, the documents, and the first four weeks is in how to make a launch plan for your token.

The contract and what it can still do

Send the network, the contract address, and the transaction hash of the deploy together. A shared name is not a shared contract. Another network is another address. If you do not have an address yet, write that in the same place. Do not invent one for the call.

The ERC-20 standard, as Ethereum.org lists it, exposes a name, a symbol, decimals, the total supply, the balance of an account, and transfer. That list does not include a price. The page was last updated on 9 July 2026. Read it for the method names, not for a value.

Then read the rest of your code, or say that you have not. If the code can create more tokens, pause transfers, or change a fee, name that in the same sentence as the supply. If it cannot, say that too. A person who finds a function you never mentioned will treat the silence as the problem.

If the explorer has not published the source, say so. Published source means a person can read the code. It is not a review of the project. If nobody independent has reviewed the contract, say that in one sentence. Do not say the project was reviewed.

Who holds the supply

Write the total supply and the wallet that holds it. If one wallet holds all of it, say so. Do not hide that. Name any transfer you have already made, and to whom. Do not describe a team share, a reserve, or a lock that is not on the chain yet.

The people you can name as holders are people who chose to hold the token. A bought count, a rented wallet, or dust sent to strangers is not that list. How to tell those apart is in how to get the first holders for your new token. If nobody has used the token, say so. Zero is an answer you can defend. An invented number is not.

Who answers, and what you send

Name the person who will be on the call, and what that person can actually answer. If that person is you, say so. A wallet address is not a team. A logo is not a name.

Until they ask for more, send only this:

• The purpose sentence: who uses the token, and what they do with it.
• The network, the contract address, and the transaction hash. Or the fact that there is no address yet.
• Where the supply sits, including a wallet that holds all of it.
• What the code can still do, or that you have not read it.
• Who has used the token, by name or by the action they finished. If nobody has, say so.

Leave out a future price, a yield, a profit, and any line that says the project was reviewed. Do not promise a place on an exchange. Do not pay a stranger who writes first and asks for a fee, or for your seed phrase, in exchange for an introduction. Do not send the seed phrase to the person on the call.

The month after an address already exists — a use, a community, and a partner note that is still facts — is in what to do after you deploy a token. This page is the sheet you write before the conversation. It does not replace that month of work.

What can go wrong

You can prepare every answer and still hear no. This page does not find investors, and a no does not mean the contract failed. Do not fill the silence with a price.

If you take money from the public for the token, securities laws and other rules may apply where you live. This page does not say which rule applies to you, and it does not tell you how to step around one. This is not legal advice. You are responsible for those laws.

Hiding a function that creates more tokens, inventing holders, or handing over a seed phrase costs the conversation and can cost the wallet. The risk of what you say, and of whom you send the phrase to, stays with you.

Sources

• Ethereum.org, “ERC-20 Token Standard”, page last update 9 July 2026, read for this guide on 15 October 2026: ethereum.org/developers/docs/standards/tokens/erc-20/. Used for the methods an ERC-20 contract exposes: name, symbol, decimals, total supply, balance, and transfer. The standard does not include a price. This page does not repeat other figures from that article.

Checklist before the first call

1. Write the purpose sentence. If it names a future price or a yield, rewrite it.
2. Save the network, the contract address, and the transaction hash together. If there is no address yet, write that.
3. Write the total supply and the wallet that holds it. Mark any split you have not signed as not signed.
4. Write what the code can still do: more tokens, a pause, a fee — or that it cannot, or that you have not read it.
5. Say whether the source is published. If nobody independent has reviewed the contract, say that. Do not say the project was reviewed.
6. Name the person who will answer. If it is only you, say so.
7. List who has used the token. If nobody has, say so. Do not buy a holder count.
8. Write the lines you will not say: a future price, a yield, a profit, a place on an exchange, a review that did not happen.
9. Do not send a seed phrase. Do not pay for an introduction.
10. Read the sheet aloud. If a sentence is a promise the contract does not store, delete it.

Where to go next

The other guides are on Learn. What a stranger can check is in how to make people trust your new token. The first person who holds the token is in how to get the first holders for your new token. The written plan before you sign is in how to make a launch plan for your token. The month after the address exists is in what to do after you deploy a token.

This page does not need a new contract. If you still have to deploy one, that step is separate: an ERC-20 on 5 networks, service fee $3 ($6 on Ethereum) plus gas. There is no testnet.

Create the token

Author: Future Constructor, a technical tool. It deploys a standard ERC-20 from your own wallet on Ethereum (service fee $6) or on Polygon, BNB Chain, Arbitrum and Base (service fee $3). Network gas is extra and changes. You hold the keys. Built on OpenZeppelin Contracts v5; factory source code is verified on Sourcify; no independent audit. Nothing on this page is financial, investment, or legal advice. You are responsible for the token’s purpose and for the laws that apply to you. Service fees are non-refundable. Transactions are final.

FAQ