An audit RFP is a one-to-two page brief that you send unchanged to every firm you consider. It names the code and commit to review, what is out of scope, the documents you will provide, the dates you need, and what the report must contain. With the same brief, quotes become comparable.
| Section | What to write | Why it matters |
|---|---|---|
| Project | What the program does, who uses it, what funds it holds | Lets a firm judge risk and pick the right engineers |
| Scope | Repository, commit hash, programs, framework, size | Scope is the main driver of effort and quote |
| Out of scope | Frontend, off-chain services, third-party programs | Prevents surprises about what was not reviewed |
| Materials | Spec, architecture notes, tests, earlier audits | Less guessing means less time and fewer findings of the wrong kind |
| Timeline | Code freeze, preferred start, hard deadline, launch date | Firms are booked ahead, dates decide who can take you |
| Deliverables | Severity-ranked report, fix review, public or private report | Defines what you actually receive |
| Pricing format | Engineer-days and rate, what the fix review includes | Lets you compare firms on the same basis |
Send the same document to every firm and answer their questions in writing to all of them.
- Freeze the code and pick a commit hash before you write the RFP, so the scope cannot drift.
- List what is out of scope as clearly as what is in scope.
- Ask every firm for engineer-days, rate, named reviewers and an example report.
- Ask whether fix review is included and how long the firm will check your fixes.
- Give the real launch date and the code freeze date, because availability decides the shortlist.
Asking five audit firms for a quote usually produces five different numbers, and it is hard to tell whether the difference is price or scope. The cause is often your own message: each firm saw a slightly different description. An RFP (request for proposal) fixes that. It is a short, structured brief that every firm gets word for word, so their answers can be placed side by side.
1. Describe the project in a few lines
Say what the program does, who uses it and what it controls: user funds, an admin key, an oracle feed, a token mint. Firms use this to judge risk and to decide which of their engineers fit. Keep it factual. Marketing language tells a reviewer nothing about the code.
2. Define the scope exactly
- Repository and commit: link the repository and give one commit hash. Freeze the code first, because a moving target is the most common reason a quote changes later.
- Programs and files: name the programs to be reviewed, the framework (for example Anchor or native Rust) and the approximate size in lines of code.
- Dependencies: say which libraries or other programs you call, and whether the firm should review how you use them or only your own code.
- Out of scope: list what you do not want reviewed, such as the frontend, backend services or deployment scripts, so nobody assumes otherwise.
3. List the materials you will provide
A short specification, an architecture diagram, a list of privileged roles, test instructions and any earlier audit reports all save review time. If some of these do not exist yet, say so. The audit readiness checklist shows what to prepare before you send the RFP.
4. Give real dates
State the code freeze date, your preferred start, the latest acceptable report date and the launch date if there is one. Good firms are often booked for weeks, so an honest timeline decides who can take the work. Do not invent urgency. If the launch date can move, say that too.
5. Say what you want to receive
- Report: findings ranked by severity, with a description, impact and a recommended fix for each.
- Fix review: ask whether checking your fixes is included, whether it is one round or more, and how long the firm will accept fixes after the report.
- Publication: say whether you want the report public, and whether you need a shorter summary for users or partners.
- Communication: a kickoff call, a private channel, and how critical findings are reported during the review rather than only at the end.
6. Ask the same questions of every firm
- Team: who will review the code, how many engineers, and how much Solana experience do they have?
- Method: manual review only, or also testing tools such as fuzzing? What will not be covered?
- Sample: an example report from similar work, with client details removed if needed.
- Effort and price: engineer-days, day rate and total. A fixed price is fine if it comes with the engineer-days behind it.
- Availability: earliest start and expected duration.
- Conflicts: any relationship with competing projects or with the providers of your dependencies.
How to read the responses
Compare engineer-days first, then rate. Two quotes with the same total can hide very different effort. Check that each firm describes the same scope you wrote, and be careful with a quote that is much lower than the rest: it may cover less. Then look at the named team, the sample report and the dates. The full process is in how to compare audit firms, and what to check about the firm itself is in choosing a Solana auditor.
Mistakes to avoid
- Changing the code after quotes arrive: it invalidates every quote. Freeze first.
- Sending different briefs to different firms: you lose the main benefit of an RFP.
- Choosing on price alone: a cheaper quote often reviews less or uses less senior time.
- Leaving fix review unspecified: ask about it before you sign, not after the report arrives.
- Starting too late: asking three weeks before launch limits you to whoever has a free slot.
For an idea of the range, use the audit cost calculator and read what a Solana audit costs. The glossary has a short definition of an audit, and the Solana smart contract audit providers page lists firms we have checked.
Frequently asked questions
What is an RFP for a smart contract audit?
A short written brief that you send unchanged to every audit firm. It names the code and commit to review, what is out of scope, the materials you provide, your dates and the deliverables, so the quotes can be compared.
What should I include in an audit RFP?
The project and what it controls, repository and commit hash, programs and framework, what is out of scope, specs and tests you will provide, code freeze and launch dates, report format, fix review terms and questions about the reviewing team and price.
How do I compare audit quotes?
Compare engineer-days and day rate, not only the total. Check that each quote covers the same scope, who the named reviewers are, whether fix review is included and when the firm can start.
When should I send the RFP?
Once the code is frozen and the specification exists, and early enough to fit the firms booking time. Good firms are often booked for weeks, so asking only a few weeks before launch narrows your choice.
Skip the writing, get a shortlist
Describe your program and timeline. We read it and suggest providers that fit your scope, with a reason for each. Free for teams.
Get matched →Looking for help with this? Browse Solana smart contract audit providers, or describe your project and get matched for free.
Related reading
- Solana audit readiness checklist: 12 things to prepare before the audit startsWhat to prepare before a Solana audit: a frozen commit, a short spec, invariants, tests that run in one command, agreed scope and a developer on call.
- Where to find Solana auditors, developers and agenciesIs there a marketplace for Solana service providers? The main places teams look: ecosystem directories, bounty boards, audit contests, freelance sites and vetted marketplaces.
- How to compare Solana audit firms: a neutral frameworkCompare Solana smart contract audit firms on evidence you can check yourself: public Solana reports, Anchor or native Rust experience, engineer-days, fix review and timing.