Project Details
CVS Land/Snow Pricing
RFP
Completed
Won
Green
100%
06-29-2022
07-22-2022
Project Log Items
 
Date
Type of Note
Type of Service
Due Date
Status
Note
Resolution
 
12-15-2022 General Note       •    Matt Young just met with corporate team yesterday. They anticipate awarding the land/snow bid first week of January with the goal of having contracts executed for 2/1 start date  
08-25-2022 Lever LandSnow     Sean offered a discount where we already had 1 of the 2 trades to incentivize the consolidation award of the other.  
08-25-2022 Lever LandSnow     Work with the Field to find margin for locations near Walgreens, DG and other small box accounts  
07-20-2022 Agenda LandSnow     Discount strategy finalization  
07-20-2022 Question Snow     How do we differentiate City/Store sidewalks with CRM specs? Speak with Jason  
07-20-2022 SOW Snow     Parking Lot Push, Full Salt, Partial Salt, Store Sidewalks, City Sidewalks  
07-20-2022 SOW Land     Mowing every 10 days, weeding every visit, Spring and Fall cleanup  
07-20-2022 SOW Land     Fertilization and irrigation are the only 2 differences between base scope and the THH scope. Does not impact snow at all.  
07-20-2022 Meeting LandSnow     Met with Gabe and Vince to walk through pricing for land. Missing specs for ~20 locations the PI team missed. Went off averages for those locations. The type of scope per store was missing from the document sent to us, so we'll need to ad that into our model. Sean sent it over.  
07-20-2022 Key Assumption       Assuming 50% of the locations have functioning irrigation in our pricing.  
07-20-2022 Pricing Strategy Land     CVS does not know which locations have irrigation and which do not. We want to go low in on the stores for irrigation costs to not inflate our overall price.  
07-08-2022 Meeting LandSnow     Sean spoke with the customer. They are fine with us submitting pricing on Fri. 7/22 by EOD. Specs are being captured and the PI team has started.  
07-01-2022 Pricing Strategy Snow     Eastern NE and ND is per event snow. IN has 2 different RFMs- 1 Southern and 1 Northern. Southern RFM likes us and Northern doesn't like anybody. We were fired previously in Fort Wayne, IN.  
07-01-2022 Risk LandSnow     Northern IN customer does not like us  
07-01-2022 Risk LandSnow     Locations where we're not doing land and we have snow, we'll be bidding against that vendor. Same for snow but we don't have land.  
07-01-2022 Agenda LandSnow     What's our strategy here?  
06-30-2022 Pricing Strategy LandSnow     Target locations we are currently doing snow for but not land. Same for snow but not land. We are viewed very positively for snow, so we should be able to pickup some locations here. We received a 5% snow price increase last year that we are locked into for 2-years. We never increased provider pricing there and we have healthy margins.  
06-30-2022 Agenda LandSnow     Specs- how many do we have? What's our trust in those?  
06-30-2022 General Note LandSnow     Locations by State
DC    16
ID    1
IN    199
KY    15
MI    130
MT    8
ND    5
NE    21
OH    58
OR    1
TN    85
VA    181
WA    9
Grand Total    729		  
06-30-2022 Competitor Battle Card LandSnow     MaintenX, Brightview, Case Snow and Regional providers  
06-30-2022 Pricing Strategy LandSnow     Price more aggressive at the locations within a quarter mile of a Walgreens we're contracted at  
Postmortems
 
Date Modified
Question
Answer
Action to What We Learned
 
No Postmortem records found
Show fields from Show fields from Show fields from a related table
Report Name *
Description
Reports and Charts Panel
Each table has a panel listing its reports and charts, organized in groups.
Please wait while your new report is saved...
Field label
Column heading override
Justification
What does auto mean?
Fields in:

Fields to Extract:
Name for the new table:
Items in the new table are called:

When you bring additional fields into a conversion, Quickbase often finds inconsistencies. For example, say you're converting your Companies column into its own table. One company, Acme Corporation, has offices in New York, Dallas and Portland. So, when you add the City column to the conversion, Quickbase finds three different locations for Acme. A single value in the column you're converting can only match one value in any additional field. Quickbase needs you to clean up the extra cities before it can create your new table. To do so, you have one of two choices:

  • If you want to create three separate Acme records (Acme-New York, Acme-Dallas and Acme-Portland) click the Conform link at the top of the column.
  • If the dissimilar entries are mistakes (say Acme only has one office in New York and the other locations are data-entry errors) go back into your table and correct the inconsistencies—in this case, changing all locations to New York. Then try the conversion again.

Read more about converting a column into a table.