# Get advice or a code review

> An advice or code review is a short, focused job where an independent developer reads your plan or your code and tells you plainly what is good, what is risky and what to do next. It does not change your product.

Canonical: https://erdibuilds.app/help/advice-review
Last updated: 2026-11-06 (November 6, 2026)

## When a second opinion helps

You do not need to be stuck to ask for a review. It is often an inexpensive way to avoid a bigger mistake. People ask for reviews when they cannot judge what they are paying for, or when something feels wrong but nobody can explain it.

- You received proposals that differ a lot, and you want help comparing them.
- You are about to launch and want a check on security and performance.
- A developer says you need a rebuild, and you want another view.
- You are buying a product or taking over a team, and want to know what is inside.
- You wonder if your chosen technology fits your plans.

## What a review can cover

**Common review topics**

|  | What the reviewer looks at | What you get |
| --- | --- | --- |
| Plan or architecture | Your brief, the technology and how the pieces fit together | A written opinion with risks and alternatives |
| Code quality | Structure, readability, tests and how easy it is to change | A list of findings sorted by importance |
| Security | Secret keys, user access, login and data protection | Problems found, with a suggested order to fix them |
| Performance | Speed, load and the cost of running the product | Where it is slow, and why |
| Proposal check | A quote or milestone plan from another developer | Whether it is realistic and complete |

## What to prepare

- Say what you want to decide: launch, buy, continue, rebuild or switch technology.
- Read only access to the repository (The place where the code is stored) is enough. Do not share passwords or secret keys.
- A short description of the product and who uses it.
- Any existing documents, quotes or proposals you want reviewed.
- A list of your worries, even vague ones.

## How it runs in milestones

A review is a small project, often one or two milestones. Each milestone is funded before work starts and runs 1, 2, 3, 4, 6 or 8 weeks. Milestones are from 50 to 2,000 each in your project currency. Agree on the format of the answer before you start, for example a written report plus a call to go through it.

**Example review plan**

|  | What you get | Example timing |
| --- | --- | --- |
| Phase 1: Kick off | A short call to set the questions and share access | A few days |
| Phase 2: Review | The reviewer reads the material and tests the product | For example, 1 to 2 weeks |
| Phase 3: Report and call | A written report with clear priorities, plus a talk about next steps | For example, 1 week |

Example only: the weeks are for illustration. Developers set the length of each milestone in their proposal, and each real milestone runs 1, 2, 3, 4, 6 or 8 weeks.

## Questions to ask the reviewer

- Have you reviewed code or plans in this technology before?
- Will the report be written in language I can pass on to others?
- Do you rank findings by how much they matter?
- Can you tell me what is good about the work as well as what is wrong?
- Will you be available for follow up questions about the report?

> A reviewer who also hopes to win the repair job has a reason to find many problems. Ask whether the review is independent, and decide on the next step separately.

After the review, you might continue with [bug fixing](https://erdibuilds.app/help/fix-bugs), a [rescue](https://erdibuilds.app/help/rescue-project) or the guide on [questions to ask before hiring a developer](https://erdibuilds.app/guides/questions-to-ask-before-hiring-a-developer).

## Frequently asked questions

### Does the reviewer change my code?

No. A review produces advice. Any changes are a separate piece of work that you agree on afterwards.

### Do I need to share passwords?

No. Share read access to the code, and keep secret keys out of it. A review can flag where secrets are stored without seeing them.

### Can I understand the report without technical knowledge?

Ask for a summary in plain words at the top, with details below for the next developer.

### Can I use a review before buying a product?

Yes. It is a common reason. Make sure the seller allows access, and agree on confidentiality. This is general information, not legal or tax advice.

### Is a review the same as a security audit?

No. A review gives a broad opinion. A formal security audit goes much deeper and is a specialist job. State clearly what you expect.

## Related

- [Rescue a Stuck App or Software Project](https://erdibuilds.app/help/rescue-project): Your developer disappeared or nobody can change the app anymore. See the first steps, a milestone plan and what to ask a rescue developer.
- [Hire a Developer to Fix Bugs in Your App](https://erdibuilds.app/help/fix-bugs): Your app crashes, loads slowly or does the wrong thing. See how to describe problems, plan fixes in milestones and find a developer.
- [Take Over an Existing Codebase Safely](https://erdibuilds.app/help/take-over-an-existing-codebase): Moving code from another developer or agency? Use this handover checklist for access, documents and a first audit milestone.
- [Questions to Ask Before Hiring a Developer](https://erdibuilds.app/guides/questions-to-ask-before-hiring-a-developer): Twenty plain questions for a first call with a developer, grouped by experience, process, handover and money, and what good answers sound like.
- [How to Hire an App Developer, Step by Step](https://erdibuilds.app/guides/how-to-hire-an-app-developer): A clear process for hiring an app developer: define the job, choose where to look, compare proposals, check fit and start with a small milestone.
- [Upwork alternatives for app and SaaS builds](https://erdibuilds.app/compare/upwork-alternatives): Upwork alternatives for app, SaaS, website and game projects: ErdiBuilds, Fiverr, Toptal, Malt, Freelancer.com and Contra, with sourced facts.