The Perfect Landscaping RFP Template

Posted by Joseph Barnes on Jun 26, 2012 12:00:00 AM

Is it Apples-to-Apples? You’ve been there; you’re in a meeting reviewing several different bids - they range from $120,000 to $250,000 and you wonder how that can possibly be.

RFP for LandscapingChances are, it's probably not the result of the many well-thought out pricing strategies of landscape companies. This is the result of a poorly administered RFP that lacks detailed, specific or accountable scope of work. It may not have had a clear and simple bid form either. 

In service industries like the landscape maintenance industry, specifics are everything. There are maps and specifications that help identify the tangible, but let’s say you request 38 mowings on a property. This isn’t exactly how it has to be. One landscaper may predict an early winter and budget for 36 cuts, despite what’s being presented. It's also entirely possible that contractors are including (or excluding) different areas. On a sizable property, that could be thousands of dollars difference. These types of “strategies” from landscape maintenance companies affect how you need to put a landscape maintenance RFP together.

We want to give you the tools to make your life easier. If you're concerned that creating an awesome RFP is too much work but you want to get the right landscape contractor on your property, you've come to the right place.

The following Landscaping RFP Template is just what you'll need to work from when you're looking to get some new proposals. We've even added comments to help guide you on what sections you'll need, and what sections you might do without.

Click on the RFP template below to download this awesome resource!

RFP Template

Meet with Us

Are you ready to discuss your property's specific challenges?

Request Quote
Joseph Barnes

About The Author

Joseph Barnes

Joseph Barnes has served as Marketing Manager of Yellowstone Landscape since 2013. He writes on a variety of topics related to the commercial landscaping industry.