Blog · Guides · 6 min read

How to write an RFP for a smart contract audit

By Kuba Malarczyk, Founder ·

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.

What an audit RFP should contain
SectionWhat to writeWhy it matters
ProjectWhat the program does, who uses it, what funds it holdsLets a firm judge risk and pick the right engineers
ScopeRepository, commit hash, programs, framework, sizeScope is the main driver of effort and quote
Out of scopeFrontend, off-chain services, third-party programsPrevents surprises about what was not reviewed
MaterialsSpec, architecture notes, tests, earlier auditsLess guessing means less time and fewer findings of the wrong kind
TimelineCode freeze, preferred start, hard deadline, launch dateFirms are booked ahead, dates decide who can take you
DeliverablesSeverity-ranked report, fix review, public or private reportDefines what you actually receive
Pricing formatEngineer-days and rate, what the fix review includesLets you compare firms on the same basis

Send the same document to every firm and answer their questions in writing to all of them.

Key takeaways
  • 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

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

6. Ask the same questions of every firm

A short RFP template: project in three sentences; repository, commit hash and framework; programs in scope and out of scope; materials provided; code freeze, preferred start and latest report date; report format, fix review and publication; the six questions above; deadline for replies and the name of the person who answers questions.

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

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

← All posts