Quick answer: A smart contract audit RFP (request for proposal) is a short brief that describes your code, what's in scope, your deadlines and what you need back from each firm. Sending the same RFP to every firm is what makes their quotes comparable. Copy the template below, fill in the brackets, and send it to your shortlist, or post it on Procur3 to reach matched firms, where a typical request gets around 20 quotes.
Why bother writing an RFP?
Most teams email a few firms, describe the project slightly differently each time, and get back quotes in different formats covering different amounts of work. One firm prices the whole repo, another prices three contracts, a third assumes the fix review is extra. You end up comparing PDFs, not proposals.
A good RFP fixes three things:
- Every firm prices the same code. Same commit, same files, same exclusions.
- Every quote comes back in the same shape. Price, reviewer-days, named team, fix review. That makes quotes easy to compare.
- You get fewer padded estimates. When firms have to guess your code size or how the system works, they add a margin for the unknowns. Tell them, and the margin shrinks.
It also makes the audit itself faster, because the reviewers start with the context they'd otherwise spend the first days reconstructing.
The template
Copy everything in the box. Replace anything in [square brackets]. Delete any line that doesn't apply.
SMART CONTRACT AUDIT: REQUEST FOR PROPOSAL
1. PROJECT OVERVIEW
Project name: [Name]
What it does (2–3 sentences, plain English): [e.g. "A fixed-rate lending
protocol. Users deposit collateral and borrow at a rate fixed at the time
of the loan."]
Chain(s) / network(s): [e.g. Base, Ethereum mainnet]
Stage: [Pre-launch / live with $X TVL / upgrade to a live protocol]
Website / docs: [Links]
Contact: [Name, role, Telegram or email]
2. CODE AND SCOPE
Repository: [Link. Private repos: access granted after NDA or on request]
Commit hash to audit: [Full hash. Code is frozen at this commit.]
Language and version: [e.g. Solidity 0.8.26, Foundry]
Total in-scope size: [X nSLOC]
In scope:
[path/to/Contract1.sol] [nSLOC]
[path/to/Contract2.sol] [nSLOC]
[...]
Out of scope:
[e.g. unmodified OpenZeppelin libraries, test files, deploy scripts,
token contract audited by [Firm] in [Month Year]]
If this is a fork or an upgrade: [What the original is, exactly what changed,
link to the diff]
3. ARCHITECTURE AND TRUST ASSUMPTIONS
How the contracts fit together: [Short description or link to a diagram]
Privileged roles and what each can do: [e.g. Owner (3/5 multisig): set fees,
pause. Keeper bot: trigger liquidations.]
Upgradeability: [None / proxy pattern + who controls upgrades + timelock]
External dependencies: [Oracles, bridges, DEXs, other protocols, and what
happens if one misbehaves]
Tokens supported: [Any ERC-20? Allow-list? Fee-on-transfer or rebasing
tokens supported or not?]
4. WHAT MUST ALWAYS BE TRUE (INVARIANTS)
[e.g. "Total deposits always equal the sum of user balances."]
[e.g. "Only the timelock can change the interest-rate model."]
[e.g. "A healthy position can never be liquidated."]
5. KNOWN ISSUES AND PRIOR WORK
Previous audits: [Firm, date, scope, link to report, or "None"]
Known issues / accepted risks: [List them so firms don't report them again]
Areas we're most worried about: [e.g. liquidation edge cases, oracle
manipulation, rounding]
6. TESTING AND TOOLING
Test coverage: [e.g. 92% line coverage, Foundry]
Fuzz / invariant tests: [Yes/No, where]
Static analysis run: [e.g. Slither and Aderyn, findings addressed]
How to build and run tests: [Commands]
7. SERVICES REQUESTED
[ ] Manual security review
[ ] Fuzzing / invariant testing by the auditor
[ ] Formal verification of: [specific properties]
[ ] Economic / mechanism review
[ ] Fix review (please state how many rounds are included)
[ ] Other: [e.g. frontend or infrastructure penetration test]
8. TIMELINE
Proposal deadline: [Date. We recommend at least 5 days from sending]
Target audit start: [Date or window]
Target report date: [Date]
Planned launch: [Date, if any]
Fix window: [How long you'll need to fix findings before the fix review]
9. BUDGET (OPTIONAL)
[Range or ceiling, or "Open: quote on scope"]
10. CONFIDENTIALITY
NDA required before code access: [Yes/No. Attach NDA]
Can the final report be published? [Yes / No / after launch]
11. WHAT EVERY PROPOSAL MUST INCLUDE
Please answer every point, in this order:
a. Fixed price (USD) and payment terms
b. Reviewer-days (number of engineers × days)
c. Named reviewers, their roles and relevant experience
d. Relevant audits in the last 24 months (protocol type, language, links)
e. Methodology: manual, tooling, fuzzing, formal methods
f. Fix review: rounds included, and the cost of extra rounds
g. Earliest start date and report delivery date
h. Report format and severity classification used
i. Anything you think is missing from this scope
12. HOW WE'LL CHOOSE
Proposals will be compared on:
- Relevant experience with this type of protocol and language: [X]%
- Review team (seniority, named, availability): [X]%
- Review effort and methodology: [X]%
- Fix review and post-audit support: [X]%
- Price: [X]%
- Timeline fit: [X]%
We aim to decide within [X] days of the proposal deadline.
A filled-in example
Here's the template completed for a typical mid-sized DeFi audit. The project is fictional.
1. Project overview. Halden Finance: a fixed-rate lending protocol on Base. Users deposit ETH or USDC as collateral and borrow at a rate fixed when the loan opens. Pre-launch; mainnet planned for late January.
2. Code and scope. Private GitHub repo, access after NDA. Commit
4f2c9e1…(frozen). Solidity 0.8.26, Foundry. 2,400 nSLOC in scope:LendingPool.sol(820),InterestRateModel.sol(310),Liquidator.sol(540),OracleAdapter.sol(290),PositionManager.sol(440). Out of scope: OpenZeppelin libraries (unmodified), tests, deploy scripts, and the HALD token (audited separately in September).3. Architecture and trust. Pool holds all collateral; Liquidator is the only contract that can seize it. Owner is a 3/5 multisig behind a 48-hour timelock, and can set fees and pause new borrowing, but cannot move user funds. Prices come from Chainlink with a 1-hour staleness check. Only ETH and USDC are accepted; no fee-on-transfer tokens.
4. Invariants. Total deposits equal the sum of user balances. A position above 110% collateral can never be liquidated. Interest can never be negative.
5. Known issues. Liquidations can be delayed if the keeper is offline; accepted. Most worried about: liquidation rounding at small position sizes, and stale-price edge cases.
6. Testing. 92% line coverage. Invariant tests for the first two invariants. Slither run, all findings addressed or documented.
7. Services. Manual review, auditor-led fuzzing of the liquidation path, and two fix-review rounds included.
8. Timeline. Proposals by 5 December. Start week of 8 December. Report by 2 January. Two-week fix window.
9. Budget. Open: quote on scope.
10. Confidentiality. NDA required. Report can be published after launch.
11–12. As per the template. Weighting: experience 25%, team 25%, effort and method 20%, fix review 10%, price 15%, timeline 5%.
How to score the proposals
Once the quotes are in, put them in one table and score each on the criteria from section 12. Here's what three quotes for the example above might look like:
| Auditor 1 | Auditor 2 | Auditor 3 | |
|---|---|---|---|
| Relevant experience | Lending, 6 similar audits | Lending, 14 similar audits | DEX/AMMs, 2 similar audits |
| Review team | 2 senior, lead named | 3 senior + lead, CVs attached | 1 reviewer, not yet named |
| Review effort | 12 engineer-days | 18 engineer-days | 8 engineer-days |
| Fix review | 1 round included | 2 rounds included | +$4,000 per round |
| Price | $28,000 | $36,000 | $22,000 |
| Cost per engineer-day | $2,333 | $2,000 | $2,750 |
Auditor 3 has the lowest headline price, but it's the most expensive per day of review, with the least relevant experience and a fix review that costs extra. Auditor 2 is the highest quote, the cheapest per day, and the closest match to the scope. This is why the RFP asks for reviewer-days and fix-review terms: without them, you'd only see the bottom row.
Three questions to ask of every proposal:
- What exactly is included? If fuzzing, formal verification or the fix review isn't listed, assume it isn't included.
- Who is doing the work, and for how long? Named senior reviewers for three weeks is a different product from one unnamed reviewer for one.
- What happens after the report? How many fix-review rounds, how quickly, and at what cost if you need more.
Mistakes that make quotes hard to compare
- No commit hash. Firms quote on whatever's on
mainthat day, and the code keeps changing. - Leaving out what's not in scope. Firms assume everything in the repo is in scope and price it.
- No code size. Firms estimate it, and estimates get padded. Count nSLOC yourself; our audit cost calculator explains how.
- Hiding known issues. You pay reviewers to rediscover them, and they show up in the report.
- A two-day proposal deadline. The best firms are often booked; they need time to look properly. Give at least five days.
- Asking for "a quote" instead of specific answers. If you don't ask for reviewer-days and fix-review terms, you won't get them.
For the full pre-audit checklist, read how to prepare for a smart contract audit.
Sending your RFP
By email: send the same document to every firm on your shortlist on the same day, with the same deadline. Answer questions by replying to everyone, so every firm works from the same information.
On Procur3: the request form follows the same structure, so you can paste straight from your template:
| Template section | Where it goes on Procur3 |
|---|---|
| 1. Project overview | Basics: project title and description |
| 2. Code and scope | Basics (in/out of scope) and Technical (repo links, code size) |
| 3–6. Architecture, invariants, known issues, testing | Technical: attach the completed template as a document |
| 7. Services requested | Basics: service categories |
| 8–9. Timeline and budget | Budget: budget, proposal deadline, start date |
| 10. Confidentiality | Technical: attach your NDA; choose private if needed |
| 11–12. Proposal format and scoring | Built in: every firm quotes on the same fields, side by side |
Your request goes only to firms that work in your language and service, or only to the firms you invite if you make it private. Nothing is ever visible to the public. Posting is free for teams, the first quote usually arrives within 30 minutes, and a typical request gets around 20.
The step-by-step version, with screenshots, is in how to get smart contract audit quotes.
Frequently asked questions
What is a smart contract audit RFP? A request for proposal: a short document describing your code, the scope, your timeline and what you need in each proposal. You send the same RFP to several audit firms so their quotes cover the same work and can be compared directly.
What should a smart contract audit RFP include? At minimum: what the protocol does, the repository and frozen commit, the files in and out of scope with their size in nSLOC, privileged roles and external dependencies, known issues, the services you want (including fix review), your timeline, and the exact information every proposal must contain.
How many firms should I send it to? Three to five if you're running the process yourself. Fewer than three and you have nothing to compare; many more and reading the proposals properly gets hard. On Procur3, the request goes to every matched firm (around 20 quotes on a typical request), or only to the firms you invite.
How long should I give firms to respond? At least five days. Good firms are often booked weeks ahead and need time to read your code before they price it. Rushed deadlines get you fewer quotes and more padding.
Should I include a budget? It's optional. A ceiling helps firms decide whether to quote and pitch the right level of effort. Leaving it open shows you the full range. For typical prices, see what smart contract audits cost in 2026.
Do I need an NDA before sharing my code? Only if your code is private and sensitive. Attach your NDA to the RFP and give repository access only to firms that sign it. On Procur3, firms request access in the app and you approve each one.
Can I use this template for a penetration test or infrastructure review? Yes. Keep sections 1, 8–12, and replace section 2 with the systems in scope (apps, APIs, cloud accounts, wallets), section 3 with your architecture and access model, and section 7 with the testing you need.
Got your brief? Post it once on Procur3 and get comparable quotes from matched firms. Free for teams.
