Skip to content

← All case studies

Property management · Live deployment

Eleven vendor bids collected, compared and reported in eight days

One request from the manager sent the RFQ emails, booked a route of site walks, pulled every bid out of the inbox and put a side by side report in the owner's hands. The figures show a typical bid round.

Illustrative example: property manager, 6 communities · October 2026

Vendors invited
14
Bids compared side by side
11
Request to owner report
8 days
How it unfolded

From benchmark to rollout.

Day 1
The request

The manager asks for bids on seal coat and restriping at six communities plus next year's landscape contract, and the assistant drafts one RFQ email per vendor with the scope, unit counts, site maps and a bid due date.

Days 1 to 2
Site walks on the calendar

Vendors pick a walk time by reply, and the assistant groups the walks by property and drive time so the maintenance supervisor covers nine walks in two mornings.

Days 3 to 7
Bids pulled from the inbox

Each bid that arrives as a PDF, a spreadsheet or a line in an email body goes into one comparison sheet, and vendors who miss the due date get a polite follow-up the next morning.

Day 8
The owner report

The owner gets a two page report with price per property, scope gaps, exclusions, insurance status and start dates, with the manager's recommendation on top.

This is an illustrative engagement. The workflow is the one we set up for property teams, and the figures describe a typical bid round for a manager running six garden communities, so no single client’s numbers appear here.

A bid round touches more people than any other task on a property manager’s desk. The scope has to go out to a dozen vendors, each vendor wants to walk the site, the bids come back in every format a contractor can think of, and the owner wants one page that makes the choice easy. The manager in this example runs two or three of these a quarter on top of everything else, and each one takes a few weeks of email.

What we set up

We connected Claude to the manager’s Outlook inbox, the team calendar, the approved vendor list and the property files that hold unit counts and site maps. The manager starts a round with a single message that names the work, the properties and the due date.

From there the assistant drafts every RFQ email with the scope written the same way for each vendor, so the bids come back comparable. It suggests a few new vendors near each property when the approved list is thin, with their license and insurance checked against public records before anyone is invited. The manager reviews the batch and approves it, and the emails go out from the manager’s own address.

How the site walks get scheduled

Vendors reply with the times that work for them, and the assistant books each walk onto the maintenance supervisor’s calendar in route order, so the drives between properties stay short. Every vendor gets a confirmation with the address, the gate code instructions and the supervisor’s name. In this example fourteen vendors were invited and nine asked to walk, and all nine walks fit into two mornings.

How the bids get collected

Bids arrive as PDFs, spreadsheets, photos of handwritten quotes and a few lines typed into an email. The assistant reads each one, pulls out the price per property, the scope items, the exclusions, the warranty and the proposed start date, and adds a row to the comparison sheet with a link back to the original email. When a vendor leaves out something the RFQ asked for, the assistant drafts a short note asking for it.

Three vendors missed the due date, and each got a follow-up the next morning. Two of them sent bids that day, which is how the round ended with eleven bids from fourteen invitations.

What the owner receives

A two page report in the owner’s inbox on day eight. Page one is the manager’s recommendation and the three strongest bids with price per property. Page two is the full comparison, with every exclusion and every missing insurance certificate flagged so nothing surprises anyone after the contract is signed.

What stayed human

The manager approves every email before it goes out. The supervisor walks the sites and talks with the vendors. The owner makes the call on who gets the work, and the manager signs the contract. The assistant handles the sending, scheduling, chasing and assembling that fills the weeks between those decisions.

Guard rails

Nothing goes to a vendor without the manager’s approval, and the assistant never accepts a bid, negotiates a price or commits the owner to anything. Vendor pricing stays inside the comparison sheet and the owner report, which live in the owner’s own files.


Book the audit