Free template · code audit proposal

Technical audit proposal template

A proposal for reviewing someone else's codebase: what you'll check, how each finding is rated, how you get access without touching production, what the client receives, and what an audit is not. Written out in full for a fictional health-tech client.

Sections
11
Estimate
8 lines, 59 hours
Example total
$7,670.00
Payments
50% / 50%
Proposal

Brightline Health: technical audit of the scheduling platform

Prepared for Brightline Health

Investment
From $7,670
Payments
2 stages

What you asked for

Your scheduling platform has grown for five years on Django, pages have slowed down, and a hospital customer has sent a security questionnaire you need to answer with confidence. Before hiring, you want an outside view of what to fix first, how urgent each item is, and roughly what it will take.

We propose a two-week, fixed-price audit that ends with a ranked plan your team can start on the next Monday.

What we'll look at

  • Security: sign-in and sessions, who can see which patient's appointments, input handling, secrets in code or settings, and known vulnerabilities in your dependencies
  • Performance: the ten slowest pages and API calls, profiled; database queries, indexes and repeated queries; caching
  • Code health: test coverage of the booking flow, structure, and the upgrade path to supported Django and Python versions
  • Infrastructure and costs: hosting, backups (and whether a restore has been tested), monitoring, error tracking and monthly spend

How each finding is rated

Every finding in the report has: what we saw (the file and line, or the request that shows it), what it means in plain words, how to fix it, and the effort in hours.

  1. Critical: data is exposed or the site can be taken down now. We tell you the same day, not at the end.
  2. High: a real risk or a visible slowdown; fix within the month.
  3. Medium: worth fixing as part of normal work.
  4. Low: good practice, no urgency.

What you get

Review

  • A kickoff call to agree priorities and the pages that matter mostS-1
  • The review itself, with read-only access throughoutS-2

Report

  • A written report with every finding rated, evidenced and estimatedS-3
  • A 30/60/90-day plan: what to fix first and in what orderS-4
  • Draft answers to the security questions the report coversS-5
  • A one-hour walkthrough with your team, recordedS-6

Investment

A fixed price for a fixed two weeks. The re-check after your fixes is optional.

TaskHoursRateAmount
Review · 45 h$5,850.00
Kickoff, access and set-up3$130.00$390.00
Security review14$130.00$1,820.00
Performance profiling10$130.00$1,300.00
Database and query review6$130.00$780.00
Code health and upgrade path8$130.00$1,040.00
Infrastructure and costs4$130.00$520.00
Report · 14 h$1,820.00
Report, plan and draft questionnaire answers12$130.00$1,560.00
Walkthrough with your team2$130.00$260.00
Optional extras
Re-check after your fixes (within 60 days)6$130.00+$780.00
Subtotal$7,670.00
Total$7,670.00

Timeline

Two weeks from the day access is in place: review in week one, report and walkthrough in week two.

Payments

  1. To startOn approval$3,835.0050%
  2. Report deliveredEnd of week 2$3,835.0050%

Access, data and limits

  • Read-only access to the code repository, the staging site, logs and the hosting console. We change nothing in production
  • An anonymised copy of the database, or a read-only replica; we don't need to see real patient details
  • This is a review, not a penetration test: we don't attack the live system. It's also not a compliance certification (such as SOC 2 or HIPAA), though the report helps with both
  • An audit lowers risk but can't prove no problem remains

Questions you might have

Will you change our code?

No. Everything is read-only; the report tells your team (or us, if you'd like a separate quote) what to change.

What if you find something critical?

We tell you the same day, with the fix, so you're not waiting for the report while a risk is open.

Who sees the report?

Only you. Findings are confidential, and we're happy to sign your NDA before access is granted.

Terms

Invoices are due within 14 days. The report is yours to use and share as you wish. Access is removed at the end of the audit and any copies of data are deleted. Work outside the agreed scope is quoted in writing before it starts.

Next step

Approve below and we'll send the deposit invoice, an NDA if you need one, and a short list of the access we need.

A worked example for a fictional client. Every word and number is yours to change.

How to write each part

  1. Name the decision the audit supports

    Clients rarely want “an audit” for its own sake. They want to know what to fix before hiring, how to answer a customer's security questionnaire, or whether to rebuild. Say which, and the rest of the proposal has a yardstick.

  2. List the areas, and how deep you'll go

    Security, performance, code health, infrastructure: name what you'll look at under each (“the ten slowest pages, profiled”) so the client can see the depth. A vague scope invites the question “did you check X?” after the report lands.

  3. Show what a finding looks like

    Describe the severity scale and what every finding contains: the evidence, the impact in plain words, the fix and its effort in hours. This is what the client is buying, so let them see its shape before they pay.

    Promise to raise anything critical the same day. It costs you nothing and removes the worry of waiting two weeks with a known hole.

  4. Be precise about access and data

    Ask for read-only access, say you change nothing in production, and avoid real personal data where an anonymised copy will do. For regulated clients, this paragraph often decides whether the proposal gets past their security team.

  5. Say what it is not

    A code review isn't a penetration test, and neither is a compliance certification. Saying so up front sets the right expectation and protects you if something is found later that was outside the scope.

  6. Fix the time, fix the price

    A time-boxed audit at a fixed price is easy to approve. Offer a re-check after fixes as an optional extra; it's useful to the client, and it often turns into the follow-on work.

Questions people ask

What does a technical audit include?

Usually a review of security, performance, code health and infrastructure, ending in a report where each finding has evidence, a severity, a recommended fix and an effort estimate, plus a prioritised plan. The proposal above lists exactly what's covered.

How much should I charge for a code audit?

Price the time box, not the codebase: estimate the hours for each area and the report at your normal rate, then quote it as a fixed price. One to two weeks suits most small to mid-sized applications.

Is a code audit the same as a penetration test?

No. An audit reads the code, configuration and infrastructure to find problems; a penetration test actively attacks the running system. Say which one you're offering, and refer the other out if the client needs it.

What access do I need to audit a codebase?

Read-only access to the repository, a staging environment, logs and the hosting console, plus an anonymised copy of the database or a read-only replica. You shouldn't need write access to production or real personal data.

How long does a technical audit take?

One to two weeks for most small to mid-sized apps: about a week reviewing and a week writing the report and plan. Larger systems are better split into areas and audited one at a time.

Can I download this audit proposal template?

Yes: download it as Markdown for Google Docs, Notion or Word, or save it as a PDF with your browser's print. Or open it in Devposal and send it as a link your client approves online.

Related