2 minute read

Introduction

www.restauranttechnologynetwork.com

Current Request for Proposal (RFP) processes are cumbersome, time-consuming, and complex, even for the most sophisticated buyers & suppliers. It is common for this process, or parts of this process, to be outsourced due to the time commitment and risk associated with strategic decision-making. The RFP process should be simple and streamlined for non-mission critical applications. While individual organizations prioritize certain systems, most companies would benefit from a normalized, clearly defined plan, adaptable to specific needs.

The RTN Buyer’s Guide and RFP Best Practices will help buyers and sellers accelerate the procurement process by:

Identifying what constitutes a quick decision vs. full-fledged RFP process

Ensuring clear objectives for buyers and suppliers

Creating a framework to prioritize requirements

Increasing buy-in from stakeholders and executive teams

Defining clear communications with vendors

Simplifying the selection and proof of concept test process

Staff

ABBY LORDEN VP and Brand Director, HT Co-Founder, RTN 973.607.1358 alorden@ensembleiq.com

ANGELA DIFFLY Co-Founder, RTN 404-550-7789 angela@restauranttechnologynetwork.com

PATRICK DUNPHY CIO, HTNG & RTN 312.690.5039 patrick@restauranttechnologynetwork.com

ROBERT FIRPO-CAPPIELLO Editor in Chief, HT 917.208.7393 rfirpo-cappiello@ensembleiq.com

ANNA WOLFE Senior Editor, HT 207.773.1154 awolfen@ensembleiq.com

MICHAL CHRISTINE ESCOBAR Managing Editor, HT 224.632.8204 mescobar@ensembleiq.com

KATHERINE WARE Senior Account Executive, HT & RTN 785.424.7392 kware@ensembleiq.com

NOELL DIMMIG Account Executive, HT & RTN 973.607.1370 ndimmig@ensembleiq.com

LEAH SEGARRA Senior Account Executive, HT & RTN 973.610.8391 lsegarra@ensembleiq.com

Table of Contents

Introduction.......................................................................................................................................2

Do You Really Need an RFP?.................................................................................................... 4

Internal Stakeholder Management ......................................................................................... 6

Needs vs. Wants vs. Wish List.................................................................................................. 8

Identifying Vendor Candidates................................................................................................ 9

Communicating with Vendors................................................................................................. 10

Evaluation Criteria ....................................................................................................................... 12

Lab & Pilot Programs.................................................................................................................. 13

Appendix A: Sections of the RFP .......................................................................................... 16

Appendix B: Stakeholder Questionnaire............................................................................ 20

Key Contributors

CHRIS HEARD CEO & Co-founder

NIKO PAPADEMETRIOU Vice President, Major Accounts & Business Development

JOE TENCZAR Co-Founder

Our Mission

The Restaurant Technology Network (RTN) is a membership community solely dedicated to the restaurant technology industry. Through access to valuable benefits and powerful connections, our members shape industry standards and share technical guidance to help restaurateurs run successful businesses and better serve their customers.

Copyright 2020 Restaurant Technology Network (RTN). All rights reserved. No part of this publication may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopy, recording or information storage and retrieval systems, without express written permission from the publisher. RTN is a wholly owned subsidiary of EnsembleIQ, with principal headquarters at 8550 W. Bryn Mawr Ave., Suite 200, Chicago, IL 60631.

This article is from: