How to make a launch plan for your token

Token creators: write the audience, the documents, the launch-day sequence, and the first four weeks before you sign. The plan does not name a future price.

A launch plan is a list in three parts: what you finish before you sign, what you do on the day you sign, and what you repeat for four weeks after the address exists. You can write all three today, before a wallet is connected.

The list does not say what the token will be worth, and it does not tell anyone to buy. This is not financial advice. A signature creates a contract on one network. The plan is the work around that signature: who the token is for, which papers you finish, what you will say, and which counts you will keep.

What the three parts are

People treat the launch as the moment of the signature. The costly mistakes are already in the sentence, the network, the supply, and a promise the chat heard. Write those down first. A plan does not make the token a good idea. It makes the day of the signature a day you already described.

PartWhenDone when
Before you deployBefore any signatureAudience, documents, and the message are written
Launch dayThe day you signNetwork, contract address, and transaction hash saved together, then posted in the one place you named
First four weeksAfter the address existsThe same facts repeated, one use someone can finish, and a note of who did it or that nobody did

The ten points from a purpose sentence to the contract address are in how to launch a token step by step. The month after the address exists, including liquidity basics, is in what to do after you deploy a token. This page is the plan that points at both. It is not a tour of a form.

Before you deploy: audience and documents

An ERC-20, on this page, means a fungible token: each unit is the same type as another unit of that token, with a name, a symbol, and a total supply. That is the ERC-20 token standard (Ethereum.org, page last update 9 July 2026). The plan does not change what the standard counts. It records who should hold a balance, and why.

Write the audience before you write a crowd. A person in the plan has a wallet on the network you will sign, and can say what the token is for. Your own signing wallet is the supply, not the audience. How that person receives a transfer is in how to get the first holders for your new token. Do not buy a list of wallets. Do not put a holder target in the plan as something the signature will produce.

Finish these documents before you connect a wallet. Each one is a few lines.

DocumentWrite thisLeave out
PurposeWho uses the token, and what they do with itA future price, a date, or a multiple
Supply noteThe supply starts on the wallet that signs. Who you will transfer to, and why. Name, symbol, and supply stay as you sign them.A split you have not written, or a line that says you can edit them later
NetworkOne of five live networks: Ethereum, Polygon, BNB Chain, Arbitrum, or Base. The people you named can open that network. There is no testnet. A second network is a second contract, a second fee, and a second address.A ranking of the five, or a practice deploy
FeesService fee $6 on Ethereum and $3 on Polygon, BNB Chain, Arbitrum, and Base, plus gas in that network’s coin. The fee is not refundable. Checked on this site’s Learn pages on 14 October 2026. Gas changes.Treating the fee as an audience, as gas, or as a certificate
MessageThe one place people can reply, and the post you will put there: purpose, network, and contract address togetherThe token name alone, or a chat you bought
Price answerWhat a person can do with the token. You do not set a price.A number, a date, or a multiple

You can finish the table today. None of it requires a signature. If the purpose sentence is a future price, rewrite it before you fill anything else.

Launch day

Launch day is the sequence you already wrote. It is not a speech you invent in the chat after the signature.

  1. The wallet you control holds that network’s coin, enough for gas. You hold the keys. The plan does not ask for the seed phrase. A private message that asks for the phrase is not part of the plan.
  2. Sign on the one network in the plan. Assume name, symbol, and supply stay as signed.
  3. Save the network, the contract address, and the transaction hash in one note.
  4. Post the purpose, the network, and the address in the one place you named. Do not post the name alone.
  5. Transfer only to a person who asked and who fits the sentence.

The signature is one line in that list. Future Constructor deploys a standard ERC-20 from your wallet on the network you already chose. It does not write the audience, the documents, or the four-week schedule. It does not open a pool, lock an LP token, or collect money before launch.

The first four weeks

These rows are a schedule of work. They are not a forecast. You can do every row and still have no users. Skipping a row does not break the contract. The longer month after the address exists, including how a pool works, is in what to do after you deploy a token.

WeekPut this in the planLeave out
1Post the purpose, the network, and the address in the one place. Talk to the people you named. Transfer only if they asked.A bought chat. A future price. A second network “to restart”.
2Post the same facts again. Publish the token source on the block explorer, or write down that you have not.A claim that someone reviewed the project. A follower count as proof.
3One action a person can finish with the token: access, a credit inside a product you run, or a community action you host. Write who finished it, in words a stranger can check.A chart. A second token. A use you cannot point at.
4Read the three counts in the next section. If the people who finished the action need a swap, write that the pool is a later step you take yourself. If they do not, write “no pool”.A pool as proof the token is used. A size you copied from someone else.

Say the same facts in that one place each week you show up. A quiet week is a result. Fill the next row. Do not fill it with a bought crowd, and do not paste the seed phrase into a tool that offers to fill it for you.

The liquidity line is a decision, not a pool. A pool is two coins on a swap site. You choose both, and you choose the size, only if people who already use the token need to swap. The signature does not open a pool, and it does not lock the LP token. Whoever holds that LP token can remove their share. Write that in the plan before you tell anyone the pool will stay.

What you count

Pick counts you can check by naming a person. This page does not give you a target number. It does not have a success rate to quote.

  • People who can repeat the purpose without you writing it for them.
  • People who finished the one use in week 3.
  • Replies in the one place you named, from people you can name.

Do not enter these as results of the plan:

  • A price or a chart.
  • A holder count you bought, rented, or dusted onto strangers.
  • A follower count.
  • The service fee. It was the charge for the deploy.

Write the empty count down. Zero people who finished the use is a result you can read. It is not a reason to invent holders, and it is not a reason to name a future price.

What can go wrong

You can pay the service fee and the gas and still have no users. The token can sit unused. The plan does not reverse a wrong network, and it does not edit a name, a symbol, or a supply you already signed. This page does not tell anyone to buy.

If the sentence you posted is a future price, people will repeat it. Rewrite it before launch day. If you take money from the public for the token, securities laws and other rules may apply where you live. This is not legal advice. You are responsible for those laws.

Built on OpenZeppelin Contracts v5; factory source code is verified on Sourcify; no independent audit. That sentence is about the factory’s published source and the factory code on the network. It is not a review of your plan, your token, or what you tell people. The risk stays with you.

Sources

  • Ethereum.org, “ERC-20 Token Standard”, page last update 9 July 2026, read for this guide on 14 October 2026: ethereum.org/developers/docs/standards/tokens/erc-20/. Used for what “fungible” means: each unit is the same type as another unit of that token. This page does not repeat other figures from that article.
  • Service fee and networks: $6 on Ethereum and $3 on Polygon, BNB Chain, Arbitrum, and Base, plus gas, on five live networks, with no testnet. These are the terms already stated on this site’s Learn pages, checked for this guide on 14 October 2026. Gas is separate and changes. This page does not add a holder count or a success rate.

Checklist for the launch plan

  1. Write the purpose sentence. If it names a future price, rewrite it.
  2. Name the people who already fit that sentence, and the one network they can open. There is no testnet.
  3. Write the supply note: it starts on the signing wallet. List who you will transfer to, and why.
  4. Write the fee line: $6 on Ethereum, $3 on the other four, plus gas. It is not refundable. It is not an audience.
  5. Name one place people can reply, and the post: purpose, network, and address together.
  6. Write the price answer in advance: what a person can do with the token. No future price.
  7. On launch day, save the network, the contract address, and the transaction hash together. Transfer only to someone who asked.
  8. For four weeks, repeat the same facts, run one use a person can finish, and write down who did it or that nobody did.
  9. A pool is optional and later. You open it yourself, and only if people who already use the token need a swap.
  10. Count people who can repeat the purpose and people who finished the use. Do not count a bought list.
  11. Say that there has been no independent audit. Do not hand anyone your seed phrase.

Where to go next

The other guides are on Learn. The first person who holds the token is in how to get the first holders for your new token. The route from the sentence to the address is in how to launch a token step by step. The month after that address exists is in what to do after you deploy a token.

Ready to deploy a token under this plan? Deploy an ERC-20 on 5 networks, service fee $3 ($6 on Ethereum) plus gas.

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

Does a launch plan set a price?

No. The plan names who the token is for and what they can do with it. It does not name a future price. This page does not tell anyone to buy. This is not financial advice.

What do I finish before I deploy?

The audience, the purpose sentence, the supply note, one of the five live networks, the fee line ($6 on Ethereum or $3 on the other four, plus gas), the one place you will post, and the sentence you will use when someone asks the price. None of that needs a signature. There is no testnet.

What do I do on launch day?

Sign on the network you wrote down, from a wallet you control. Save the network, the contract address, and the transaction hash together. Post the purpose with those facts in the one place you named. Transfer only to someone who asked. You hold the keys.

What belongs in the first four weeks?

The same facts, posted again. One use a person can finish. A note of who finished it, or that nobody did. A pool only if those people need a swap, and you open it yourself later. The schedule is not a forecast. You can do every week and still have no users.

Does the plan include a pool?

Only as a decision you write down. If the people who already use the token do not need a swap, the line says no pool. If they do, you open it yourself, later, on a swap site, with two coins, and you choose the size. The signature does not open a pool and does not lock the LP token.

What should I measure?

People who can repeat the purpose without you writing it for them. People who finished the one use. Replies in the one place you named, from people you can name. A price, a bought holder count, a follower count, and the service fee are not those measures.

Does the $6 or $3 fee buy the plan’s results?

No. The service fee is $6 on Ethereum and $3 on Polygon, BNB Chain, Arbitrum, and Base. It is the charge for that deploy. It is not refundable. Gas is separate and changes. Neither amount buys an audience, a pool, or a user.

Does the plan mean the token was reviewed?

No. Built on OpenZeppelin Contracts v5; factory source code is verified on Sourcify; no independent audit. A written plan is not a review of the token or of what you tell people. The risk stays with you.