What Makes a Great App RFP?

WHAT and WHY instead of HOW

Product owners tend to skip the whole-picture level and go straight into details. Instead of describing the desired features and colors, answer the most important questions first: what kind of product do you need? Why do users need it? 

How to describe HOWs

If you already shared your business goals and still want to give some feature requirements — refer to other products or competitors. For example, ‘I want a virtual card as in PayPal, booking as in Airbnb and Headspace-like design’.

Technical requirements aren’t a must

There’s no need to get started with a Technical Requirement Specification, better provide the manager with some document that answers the question ‘Why and for whom do we build this app?’. It’s best to keep it within 2 pages.

About money

How to save time when choosing a contractor? Frankly share your budget expectations right from the start. If an agency works in a different price segment — you won’t waste time on them. Plus, an agency can offer you an optimal option to fit your budget.

I have filled a brief, will it work?

Agencies usually offer to fill out a brief. Basically, it’s useful but ONLY for the agency that asked you to fill it out. Remember that all agencies have different specializations and working approaches.

Be ready for calls

You described the concept of the future product and shared budget expectations. Good — the next step is to get in touch personally. The development studio is your long-term partner, so it’s crucial to filter out anyone you don’t like. Communication is key.

Real people — real language

The best way to write a clear and understandable RFP is to use simple words. Talk with the manager just like you talk with your family or colleagues. No need to hide the context behind long and complicated words.

Perfect app development RFP

To write a perfect app development RFP, use this structure:

1. context (WHAT)
2. purpose (WHY)
3. HOW through references
4. budget expectations
5. contacts

You can attach a business requirements document (2 pages max)