Smart contract development typically costs from a few thousand euros for a standard token to more than 100,000 EUR for a lending protocol or a bridge. The price depends first on the type of project, which sets the number of developer-days, then on the options, the target chains and the day rate of the vendor, which varies widely by region. The figures below come from the public indicative model used by the smart-contract.com calculator: they are orders of magnitude, not quotes, and an audit must always be budgeted on top of development.
Indicative ranges by project type
The type of project is the main driver of cost, because it determines how much logic has to be designed, written and tested. The model expresses this as developer-days for the contracts and their tests, on an EVM chain, before options and overhead.
| Project type | Developer-days (contracts and tests) |
|---|---|
| Token | 5 to 12 |
| NFT collection | 8 to 18 |
| Staking or vesting | 12 to 25 |
| DAO or governance | 15 to 35 |
| Real-world asset tokenization | 25 to 55 |
| DEX or AMM | 40 to 90 |
| Lending protocol | 60 to 130 |
| Bridge | 70 to 150 |
Converted into a budget with a Western European vendor, on an EVM chain and without any option, the model gives for example:
- Token: 3,900 to 15,000 EUR (6 to 14 days including overhead).
- DEX or AMM: 30,000 to 114,000 EUR.
- Lending protocol: 45,000 to 165,000 EUR.
The width of each range reflects real differences in scope. A token with a fixed supply and no special rules sits at the bottom; a token with vesting schedules, transfer restrictions and role management moves toward the top. To estimate your own project, combine type, options, chains and region in the development cost calculator. Real quotes always depend on the scope you describe.
What adds effort
Options, additional chains and project overhead add developer-days to the base estimate. They are often underestimated at the start of a project because they sit outside the core contracts.
Options
Each option in the model adds a range of developer-days:
- Upgradeability: +3 to 6 days. Upgradeable contracts allow fixes after deployment, but add design constraints and a governance question: who can upgrade, and with what safeguards.
- Oracle integration: +3 to 8 days. Using external data such as prices requires handling stale, missing or manipulated values.
- Web front end (dApp): +15 to 40 days. The interface through which users connect a wallet and interact with the contracts.
- Back end or indexer: +10 to 25 days. Services that read on-chain events, store history and feed dashboards or notifications.
The front end is frequently the largest option. For a small token project, it can cost more than the contracts themselves.
Chains
Deploying on several chains, or on a non-EVM chain, increases effort in two ways.
- Each additional chain: +3 to 6 days for configuration, deployment scripts, testing and chain-specific differences.
- Chain factor: EVM 1.0; Solana 1.25; Move-based chains 1.2; other chains 1.3. This multiplier applies to the whole estimate, because tooling, libraries and experienced developers are less abundant outside the EVM ecosystem.
Project management and QA
The model adds 15% to the development effort for project management and quality assurance: meetings, specification reviews, test campaigns, deployment preparation and handover. A quote without any time for these activities is either absorbing them in its day rate or leaving them out.
The effect of the vendor's region
For the same project and the same number of days, the vendor's region can change the budget by a factor of two or more. Senior day rates in the model, in EUR:
- North America: 800 to 1,400
- Western Europe: 650 to 1,100
- Eastern Europe: 400 to 750
- Latin America: 350 to 650
- Asia: 300 to 650
The day rate is only part of the equation. Seniority, experience with your type of protocol, language skills, time zone overlap with your team and the quality of tests delivered all affect the final cost, because a cheaper team that needs more days or produces code that requires heavy fixes after audit is not cheaper in the end. Compare the total effort and the deliverables, not only the day rate.
How long development takes
Developer-days measure effort, not calendar time. The calendar duration depends on how many developers work in parallel and on how quickly decisions are made on your side.
As an order of magnitude, a simple token (6 to 14 days including overhead) can be delivered by one developer in a few weeks. A DEX or a lending protocol, at several dozen to more than a hundred developer-days, usually involves a small team over several months. Adding developers shortens the schedule only up to a point, because smart contract logic is tightly coupled and must stay consistent.
Plan the calendar backward from your launch date and leave room for:
- A specification phase before any code is written.
- A code freeze before the audit.
- The audit itself, the fixes and the re-audit.
- Testnet deployment and final checks before mainnet.
Hidden costs to budget
The development quote rarely covers everything a project needs to go live. The following costs are the ones most often missing from the initial budget.
- Audit: a separate engagement with an independent auditor, which never replaces the developer's own tests. Its price depends on code size and complexity; the guide on smart contract audit cost gives indicative ranges.
- Re-audit: after the audit, the developer fixes the findings and the auditor verifies the fixes. In the site's audit model, this adds about 20% to the first audit price. The developer's time to fix findings must also be planned.
- Front end: if it is not in the quote, add 15 to 40 developer-days in the model.
- Maintenance: monitoring, responses to incidents, dependency updates, upgrades if the contracts are upgradeable, and support for new chains.
- Deployment gas: deploying contracts and configuring them on mainnet costs transaction fees (gas), paid in the chain's native token. The amount depends on the chain, the size of the contracts and network conditions at the time of deployment.
Other items can apply depending on the project: a bug bounty program after launch, legal review for tokenization projects, and key management tools such as a multisig wallet for administrative roles.
How to get comparable quotes
Quotes are comparable only when every vendor answers the same brief. If each vendor interprets the need differently, the price differences reflect different scopes, not different efficiency.
- Write a precise brief. Describe the project type, the features, the target chains, the options (upgradeability, oracles, front end, back end), the expected tests and documentation, and the deadline. The brief generator produces a structured specification from your answers.
- Impose a quote format. Ask every vendor for the same breakdown: developer-days by component, team composition and seniority, day rate, duration, deliverables, test coverage and what is excluded.
- Check the assumptions. Make sure each quote covers the same chains and options, and states how fixes after the audit are handled and billed.
- Separate development and audit. Request audit quotes from independent auditors, never from the development vendor or a company tied to it.
- Compare effort, not only price. A quote far below the others often means fewer days, a narrower scope or missing tests. The guide on how to compare smart contract quotes explains how to read them side by side.
Key takeaways
- In the site's indicative model, smart contract development ranges from 5 to 12 developer-days for a token to 70 to 150 for a bridge, before options and overhead.
- Options (front end, back end, oracles, upgradeability), additional chains, non-EVM chains and 15% of project management and QA add significant effort.
- Senior day rates range from 300 to 1,400 EUR depending on the vendor's region, but total effort and code quality matter more than the day rate alone.
- Budget the audit, the re-audit, the front end, maintenance and deployment gas on top of the development quote.
- Comparable quotes require one precise brief, one imposed quote format and an audit by a provider independent of the developer.