Blockchain & Web3
Token launch support
Tokenomics written down and signed off, contracts that enforce what the deck promises, liquidity locked, and someone awake on launch night.
- From
- $5,000–$50,000
- Typical time
- 1–4 months
- Usually bought by
- Crypto founders
What this actually solves
A token launch is the point where a private project becomes a public one, and it is almost entirely irreversible. The supply is the supply. The allocations are on-chain and readable by anyone who cares to look. If the vesting schedule in your deck says the team is locked for three years and the contract lets the owner move those tokens on day one, somebody will notice, publish it, and no amount of explanation afterwards will undo the damage. Every promise made in the run-up becomes a claim that the code either enforces or contradicts.
What you are really buying is the gap between those two things being closed, in the right order. The contracts have to say what the marketing says. The liquidity has to be locked before anyone is asked to buy into it. The legal position has to be settled before the contracts are final, not after, because it determines who can participate and therefore what the sale mechanics look like. And on the day itself there has to be a written plan rather than a group chat, because launch nights go wrong quickly and improvisation on-chain is expensive. None of that is glamorous, and all of it is what separates a launch that survives scrutiny from one that becomes a cautionary link.
How the launch runs
- Tokenomics on paper, signed before any Solidity. Total supply, every allocation bucket, cliffs, vesting curves and the emission schedule, in one document you sign off. Nothing gets written in code until the numbers stop moving, because each change rewrites contracts and tests. This document is also the reference the launch is later judged against. One to three weeks, driven by how settled your plan is.
- Legal and jurisdiction, in parallel and before code freeze. Your counsel produces a written opinion on how the token is characterised and which markets you can and cannot sell into. We build to that answer — geographic gating, sale mechanics, disclosure requirements. We do not proceed to final contracts without it. Runs alongside, typically 2 to 6 weeks on your lawyer's clock.
- Contracts, tests and independent review. The token itself, the vesting and cliff contracts, and where relevant a sale contract, built on OpenZeppelin implementations with tests that assert the schedule from your signed sheet — including tests proving the owner cannot pull team tokens forward. Then an external security review, quoted separately, because these contracts will hold other people's money. Three to six weeks.
- Testnet rehearsal that you personally run. Everything deployed to a testnet and driven by your team from your own wallets — claim, vest, transfer, and deliberately attempt the things you would rather nobody could do. Design changes that come out of this are cheap now and impossible after launch. Five to ten days.
- Liquidity, lock and the launch window. Mainnet deployment from a written runbook, contracts verified, every parameter read back off the chain, ownership on your Safe multisig, liquidity provided, and the liquidity position locked for a stated term with the lock contract and its public link published as part of the delivery. Then the monitoring window, staffed. Two to five days plus the agreed support hours.
- After the noise, the reporting. On-chain dashboards so you can see holder distribution, vesting releases and liquidity depth without asking anyone, plus a handover listing every owner power that still exists and what its misuse would do to holders. Three to five days.
Two habits shape how we work here. Everything that will be publicly checkable is published by us rather than described — the lock link, the verified contracts, the vesting addresses — because a claim anyone can verify for themselves is worth more than a paragraph. And there is a written list of contract features we decline to build, shared before engagement, so nobody discovers it halfway through.
What moves the price
Whether we run the process or write the contracts. Being the contract engineer inside a team you have already assembled sits at the bottom of the range. Coordinating tokenomics, counsel, liquidity, listing preparation and launch operations across several parties sits at the top, because most of that cost is sequencing and chasing rather than code.
How many jurisdictions are involved. One market with one clear legal opinion is straightforward. A launch that has to gate several countries differently multiplies the sale mechanics, the front-end work and the number of times contracts get revised.
How much support you need after the day. Launch-night hours, the following weeks of monitoring, and later vesting or parameter operations are all real work with real risk attached. The range is $5,000–$50,000 over 1–4 months, and the top of it is almost always an operated launch rather than a delivered one.
What usually goes wrong
Liquidity is provided and never locked. The pool goes live, trading starts, and the LP position sits in a wallet the team controls, meaning the entire market can be removed in one transaction. Buyers ask about this before they ask about anything else, and the absence of a lock is read as an answer. The lock has to be a contract with a stated term and a public link, done at launch, not promised for later.
The vesting in the deck is not the vesting in the code. The presentation says a one-year cliff and three-year linear release for the team. The contract has the schedule but also an owner function that can reassign or accelerate a beneficiary. Both statements are true and only one of them is enforceable, and the contract is the one strangers will read. Every line of the signed tokenomics sheet needs a test proving the code enforces it and proving the owner cannot bypass it.
Marketing gets ahead of the contracts. Somewhere in the run-up, a post promises a listing, a return, a partnership or a price floor. That promise does not stay in marketing — it attaches to the code and to everyone whose name is on the project, and it converts a technical launch into a set of claims somebody may later be asked to justify. The remedy is boring and works. Every public claim about supply, unlocks or liquidity is checked against the signed sheet and the deployed contracts before it is published, and anything about price or returns does not go out at all.
See where the site stands before you brief anyone.
If the site is already live, start from what it scores rather than from a guess. The audit reports what it checked, what it found, and — the part most tools leave out — what it could not check, and why.
Questions people ask before they commit.
- Do you give legal or investment advice?
- No to both, and we are strict about it. Whether your token is treated as a security in a given country is a legal opinion that has to come in writing from your own counsel in that jurisdiction, before contracts are finalised, because the answer changes what we build and who you are allowed to sell to. We are engineers. We will tell you what the code does and what it cannot hide, and we will not tell you or anyone else what a token is worth.
- Will you build a token that can pause transfers or blacklist addresses?
- Not as a hidden power, and usually not at all. A mint function that is not on the public page, a transfer pause, an address blacklist, a fee switch the owner can move after launch, or anything marketed as sniper protection that in practice stops specific holders from selling — these are declined regardless of the fee. They are indistinguishable from the mechanics of a trap, and once they are on-chain under your project's name that is what they look like to anyone reading the contract.
- Can we pay you in the token instead of cash?
- No. If we hold your token we stop being your contractor and become a participant in your project, which changes our incentives, your disclosure position and our ability to give you an unwelcome answer. Invoicing is in normal currency through normal channels, with contracts and records, which is also what your bank will want when it asks where the money came from.
- Do you handle exchange listings?
- We prepare everything a listing team asks for and run the decentralised exchange side end to end, including liquidity provision and the lock. Centralised listings are a commercial negotiation between you and the exchange, their fees are theirs and can be very large, and nobody can honestly promise you one. Any project telling you a listing is guaranteed is telling you something they do not control.
- What actually happens on launch day?
- A written runbook, executed in order — deploy, verify, read every parameter back off the chain, provide liquidity, lock the liquidity position, publish the lock link, then monitor. Somebody stays online for the whole window, watching transactions and holder behaviour and ready to stop rather than improvise if something looks wrong. That window is a named line item in the quote with defined hours, because it is real work, and it is the part most easily assumed to be free.
- Why does this take one to four months when the contracts are the small part?
- Because everything around them is the large part. The time goes into settling tokenomics that stop moving, waiting on legal counsel, vesting schedules that have to match what has been promised publicly, liquidity arrangements, listing preparation and a proper testnet rehearsal. If your allocations change every week you are not being difficult, but each change rewrites the vesting contract and the tests behind it.
Often taken together.
Start with the brief, not the invoice.
Send what you are trying to achieve. You get a written scope, a price and a date — or an honest “this is not the right service for that”.
Talk about Token launch support All Blockchain & Web3 services