Founder guide · Build

How to write app requirements before hiring a developer (with a fill-in checklist)

By Jayden Sue Jun Hong · Updated 2026-11-15

Short answer

Before you hire a developer, write a short requirements document (often called a PRD, product requirements document). It should cover the problem, the users, what each user must be able to do, which features are in the first version and which can wait, the screens, integrations such as FPX, DuitNow or WhatsApp, how you handle personal data under the PDPA, your budget range, timeline and how you will judge success. Two to five pages is enough for most MVPs. It makes quotes comparable and protects you from scope creep.

Why a requirements document saves you money

When three developers give wildly different quotes for "an app like Grab", they are usually not quoting the same thing. Each has guessed what you want. A requirements document removes the guessing, so you can compare quotes line by line.

It also becomes part of the contract. When a feature is missing or works differently from what you expected, the document is what you both point to. Without it, every disagreement turns into "that's a change request".

You don't need technical language. Plain sentences, simple sketches and examples of apps you like are enough. A good developer will turn them into a technical plan.

The fill-in checklist

Copy these headings into a document and fill in each one. If you can't answer something yet, write "unknown"; that is useful information for the developer too.

  1. 1. Problem

    In one or two sentences: who has the problem, how often, and what it costs them today. Fill in: "[User] struggles to [task] because [reason], which costs them [time/money]."

  2. 2. Users and roles

    List every type of user and what they are allowed to do. Example: customer, workshop staff, workshop owner, your own admin team.

  3. 3. User stories

    For each role, write what they need to do in the format "As a [user], I want to [action] so that [outcome]." Keep each one to a single action.

  4. 4. Must-have vs later features

    Sort every feature into "must have for launch" and "later". Be ruthless: if the first users can live without it, it goes into "later". See what an MVP is.

  5. 5. Screens

    List the main screens (sign-up, home, search, booking, checkout, profile) and sketch them on paper or with a tool like Figma. Add two or three apps whose look or flow you like, and say why.

  6. 6. Integrations

    Which outside services must the app connect to? Common Malaysian examples: payment gateway with FPX, cards and DuitNow QR; WhatsApp for notifications; SMS or WhatsApp OTP for login; Google Maps; accounting software; e-invoicing through MyInvois (see MyInvois for apps).

  7. 7. Data and PDPA

    What personal data you collect (names, IC numbers, phone numbers, locations, health data), why, who can see it, and how long you keep it. This drives consent screens, security and hosting choices. See PDPA for apps.

  8. 8. Admin needs

    What your team must do behind the scenes: approve users, edit content, issue refunds, view reports, export data, handle support tickets. Admin panels are often forgotten and can be a large part of the build.

  9. 9. Platforms and languages

    iOS, Android, web, or a combination? Which devices must it work on? Which languages: English, Bahasa Malaysia, Chinese, Tamil?

  10. 10. Budget range

    Give a range, not a single number. It lets the developer suggest what fits, rather than designing something you can't afford. Check typical ranges on our app cost guides.

  11. 11. Timeline

    Your target launch date and why it matters (a trade show, a grant deadline, a season). Note any fixed dates.

  12. 12. Success metrics

    How you will know the first version works: for example, 100 paying users in three months, 50 bookings a week, or a 30% repeat rate. These guide what gets built first.

  13. 13. Acceptance criteria

    For each must-have feature, the conditions it must meet to count as done. Example: "A customer can pay by FPX, receives a WhatsApp confirmation within one minute, and the booking appears in the admin panel."

  14. 14. Ownership and handover

    State that the code, designs and accounts belong to your company, and that you expect source code and documentation at each milestone. See how to protect your startup idea.

Writing good user stories

User stories keep the document focused on what people need to do, not on technical solutions. Keep each one small enough to build and test on its own.

  • As a patient, I want to book a clinic slot on my phone so that I don't have to call during office hours.
  • As a workshop owner, I want to see tomorrow's bookings in one list so that I can plan my mechanics' day.
  • As an admin, I want to refund a cancelled booking so that the customer gets their money back without a bank transfer.

For each story, add acceptance criteria in plain language: "Given [situation], when [action], then [result]." For example: given a slot is already booked, when a second patient tries to book it, then the app shows the next available slot.

Gaps that blow up quotes later

These items are often missing from a founder's first draft and appear later as change requests:

  • Roles and permissions: who can see and edit what.
  • Notifications: push, email, SMS and WhatsApp, and what triggers each one.
  • Payment edge cases: failed payments, refunds, partial refunds, payouts to vendors.
  • Empty, error and loading states: what users see when there is no data or the network drops.
  • Content: who writes the text, photos and product data, and who enters it.
  • Data migration: moving existing customers or records from spreadsheets or an old system.
  • Ongoing costs: hosting, APIs and maintenance after launch. See app running costs.

How to use the document with developers

  • Send the same document to every developer you are considering, so quotes are comparable.
  • Ask each one to list their assumptions and to price features separately.
  • Invite questions. A developer who asks good questions about your users is usually a better sign than one who quotes instantly.
  • If the scope is unclear, consider a short paid discovery phase in which the developer turns your document into wireframes and a detailed estimate.
  • Attach the final version to the contract, and agree how changes will be requested, priced and approved.

Not sure which kind of developer to approach? Compare the options in freelancer vs agency vs in-house.

Frequently asked questions

What is a PRD?

A PRD (product requirements document) describes what a product must do: the problem, the users, the features, and the conditions for each feature to count as done. For a startup MVP it can be a few pages, not a formal specification.

What should I prepare before hiring an app developer?

A problem statement, a list of user types, user stories, a must-have vs later feature list, rough screen sketches, required integrations, how you handle personal data, a budget range, a target launch date and how you will measure success.

Do I need wireframes before getting a quote?

No, but simple sketches help a lot. Hand-drawn screens or screenshots of apps you like are enough. Many developers produce proper wireframes as part of a paid discovery or design phase.

Can the developer write the requirements for me?

Yes, many agencies run a paid discovery phase to do this. You still need to supply the business knowledge: who the users are, what problem they have and what success looks like. Nobody can write that for you.

Should I tell developers my budget?

Yes, as a range. It lets them propose a scope that fits instead of quoting for everything. A developer who knows your limits can suggest what to cut or phase.