Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages

Help for owners

An investor wants a technical review of my code

Short answer

A technical review before funding or a sale checks whether the product is owned, maintainable and safe: who owns the code, whether it builds, how it is hosted, what depends on one person and where the security gaps are. You can prepare first. An independent engineer can find and fix the obvious problems before the investor's reviewer does.

  • Written for business owners
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Does this sound like your situation?

  • An investor asked for technical due diligence and I am nervous.
  • I am not sure the company, not a freelancer, owns the code.
  • Only one developer understands how it works.
  • There are no tests, no documentation and no record of how to release it.
  • I want to know the weak points before someone else finds them.

Why does this happen?

  1. Investors are buying a future, not a demo

    They want to know the product can grow, that it can survive a person leaving and that it will not become a liability.

  2. Ownership gaps are common in young companies

    Code written by contractors, store accounts in someone's personal name and servers on a founder's card are all frequent findings. Several are about the stores, covered on the transfer page.

  3. Security is a standard question

    A reviewer will often use a published checklist. OWASP's mobile standard, for example, groups checks into storage, cryptography, authentication, network communication, platform interaction, code quality, resilience and privacy.

  4. Nobody wrote it down

    Without a short guide to how the product is built, hosted and released, the reviewer has to guess, and guesses tend to be pessimistic.

What can I do about it today?

  1. Ask the investor what they want to seeA list of questions, the format and the deadline. It saves time and avoids surprises.
  2. Write one page about the productWhat it does, what it is built with, where it runs, who built it and who can change it.
  3. Put every account under the companyCode repository, store accounts, hosting, domain and key services, each with a company email.
  4. Gather the contractsAgreements with developers that show the company owns the code. A lawyer should check them.
  5. Do not rush a cleanup that changes the live productQuick fixes made in panic can break the product the week of the review.

When should I bring someone in?

  • The review is within a few weeks and nobody has read the code with an investor's eye.
  • The only person who knows the system is leaving or unreliable.
  • You suspect secrets or customer data are exposed.

How do I handle it?

  1. Read it as the reviewer wouldStructure, tests, dependencies, build and release process, hosting, and how data is stored.
  2. Check the ownership pointsI list every account and credential the product depends on and who holds it.
  3. Run a security passSecrets in the code, outdated libraries and obvious access problems, against a recognised checklist.
  4. Give you a ranked listWhat to fix before the review, what to explain and what to leave.
  5. Fix what is quick and safeWith a backup and a rollback each time. I do not rewrite the product the week before a review.

The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.

What do owners ask about this?

Can you make the review pass?

No. I can find and fix the weak points and help you explain the rest honestly. The investor decides.

Is this the same as due diligence for a startup?

Close. This page is for the founder preparing for the investor's questions. The reviewer's own report is the investor's affair.

Do I have to give you all our code?

I need read access to the repository. I will sign a confidentiality agreement if you want one.

Will you speak to the investor?

I can answer their technical questions with you present, if you both want that.

Sources

How was this page made?

I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.

For your developer: the technical fixes

Next step

Want this off your desk?

Send me a few lines on where things stand. I reply within 24 hours.