How to Write a Great Mobile RFP for Responsive Web & Apps

Every week, hundreds of mobile app RFPs hit the market for website redesigns or native mobile app development. We’ve put together a “best practices” summary and template highlighting questions your company can ask to get the best possible responses and pricing estimates for your mobile development project.

Of course, these are guidelines first. Any mobile app RFP should be customized for each project you might be considering in order to choose the best development agency. This mobile RFP template will provide you with a helpful starting point to find your top development and design team. If you don’t have your Mobile or Digital Strategy locked down, take a look at our Mobile and Digital Strategy RFP Template.

To receive a copy of this Sample RFP in Word format, please send a request using our contact form, and we’ll be happy to send it to you.

Notes and prompts are in italics and are intended for the Issuer of the RFP. They should be removed prior to distribution of RFP to potential Responders.

1. Define your Project Strategy & Purpose

In this section, the Issuer’s goal is to give Responders sufficient context to propose real and complete solutions. If this information cannot be completed, a mobile strategy project may be a required first step, prior to a Design & Development project. Please see the Mobile Strategy RFP template for more information.

Summary of Business Problem

What core business problem is the mobile or digital solution designed to address? What are the KPIs (Key Performance Indicators)? What was the origin of the concept and how has it evolved?

Stakeholders & Decision Makers

Who is leading the project? Who are other stakeholders and what is their level of involvement? Whose budget will this come out of? Who are the final decision makers?

Scope

Is this a mobile- or digital-only solution or part of a larger project that includes non-digital components? Does this product establish a new line of business or enhance an existing one?

Users

Provide the Responders all available information/research regarding the end users of the app, including

Features

What analysis/ranking of features has been conducted? What methodologies were used?

Competitive Overview

Do the Issuer’s competitors have solutions in the market? What are their strengths and weaknesses? Are there non-competing but analogous experiences that inspire the solution?

Design Direction

Issuers should provide Responders with current style guides as well as examples of apps/websites that the Issuer feels are indicative of their design direction, including descriptions of what specific attributes the Issuer likes/dislikes?

Operating Systems (OS) & Devices

Which devices and Operating Systems will be supported? If yes, what drove those selections? If mobile, how has the decision of native apps vs. mobile web vs. both been considered? Are these decisions final or still open?

Architecture / Integration

How will the overall system be architected? What back end systems/data sources will the mobile apps be interfacing with? Do these systems currently exist? If so, Issuers should provide access for Responders to review the APIs/feeds as part of the mobile RFP process. If not, what is the timeline/process for building them? Will the Responding agencies be asked to assist in the architecture and/or development of the APIs/feeds?

Prototypes

Provide Responders any prototypes developed to date.

Marketing / Distribution

How will this product be promoted and distributed to end users? What will drive engagement and ongoing repeat usage?

Target Timeline & Drivers

What is the target launch date and what drives that date as the target (e.g. a certain event)? Are there other dependencies required to hit this date (e.g. APIs/feeds that need to be built)?

Goals & Ideal Outcome

What is the financial model? What other quantifiable goals are there? What are the soft/qualitative goals (e.g. supporting a certain brand image)? What are the potential costs of failure (i.e. delivering a poorly designed, slow or buggy app, or missing timelines)? How and with what frequency will goals be measured?

2. Request Mobile or Digital Agency Background & Capabilities

The Issuer’s main goal here is to ensure finding an Agency who will help solve business problems creatively, propose incredible design options, and deliver a stable, fast, elegant mobile experience, within timelines/budgets. Also, Issuers should make it a priority to find partners who are easy to work with. The questions below are designed to help Issuers pinpoint real differences among responding Agencies, which is often difficult to do:

Summary/History

How did the agency start? Who is the executive team and what is their background? What is the mission of the agency?

Differentiators

How does the company differentiate itself vs. competitors?

Portfolio

Please summarize your top mobile app development projects, the problem you were trying to solve, and provide a link to each (if publicly available).

Awards

Please summarize your top awards or other examples of thought leadership in the space.

HR & Hiring Processes

Please provide highlights of your work culture, any ratings/awards in this area and please summarize your hiring process. [Since the Issuer is ultimately buying the capabilities of the agency’s team, it’s important to understand how the team has been created].

Mobile Design & Technology Assessments

[This is an absolutely critical part of the RFP as it will give the Issuer insight into how the agency thinks and approaches projects]:

Design Capabilities:

Development Capabilities:

Security / Intellectual Property:

QA Process:

Project Management Process:

References

Please provide three references of similar projects. Interviews with the references will be limited to 10 minutes.

3. Clearly Outline Project Proposal

The Issuer’s goal here is to ensure the mobile agency understands the business needs, has enough of an interest to put real thought into a proposal, and can meet timelines and budgets. In addition, the Issuer will get insight into how the Agency approaches these types of problems, and how seriously the Agency is taking this potential project.

Project Concept & Recommendations

What do you most like about our app/mobile web concept? What are you most concerned about and would change if you could? Would you suggest we do native applications, web applications, or both?

Other App Projects

Can you tell us about other apps that you have deployed and describe some great mobile experiences in the space we are in (or a related space)? What made them great?

Work Examples

Please provide an example of previous work for each major functionality of the project. If there are proposed functionalities that you have no previous examples for, please explain your approach and why you believe you will be able to perform.

Project Approach

Please summarize your approach to the project, and what you believe will be major variables/risks that will drive success/failure based on our goals. What will drive consumer adoption and use? How can those risks best be managed on our side and your side?

Timeline/Budgets:

Measurement, Analytics and Ongoing App Improvement and Management

[Mobile projects are no longer about launching an app or mobile website, and going back and doing an update every 6 months. Mobile is about constant and never-ending analysis and improvement. A mobile project is NOT an upfront project followed by “maintenance” – instead it is a long-term engagement with a partner/agency during which time the goal is to work together to constantly revise and improve].

4. Define RFP Process: Budget, Decision Criteria, & Timelines

Budget

Being open about budget ranges will significantly improve the responses the Issuer will receive. Every project has a range of options and degree of polish/customization that significantly impacts the final price. By leaving the budget open, Issuers run the risk of receiving a wide range of responses and possible project solutions, and being left without a true a basis for making apples-to-apples comparisons. The Issuers goal should be to determine who is best positioned to do the work within a certain budget range, not to let the Responders define the budget. For example, two versions of the same app could cost $200K and $500K, with one using out of the box OS-supplied design paradigms and the other being highly customized with amazing polish and motion design. If the budget range is set, the Issuer will learn how far each agency will push within that range, whereas if the Issuer leaves budgets open, the proposals will range from $200K and some for $500K but not really be bidding on the same project. It’s analogous to comparing offers for a Toyota Camry and a BMW 5-series. Best practice is for Issuers to set a budget range and push for the best app within that budget, and let Responders know that coming in with a solution at the bottom of or below the range would positively impact their chances.

Decision Criteria

How will the Issuer choose whom to work with? What will be the criteria and how will they be ranked?

Establish Timeline For

(1) Initial RFP Distribution (2) Responder Submission of Questions (and QA session if applicable) (3) Question Replies (4) Final Submissions

You can download a copy of this Sample RFP, or if you have questions please use our contact form and we’ll be happy to assist you!