The Community's Buying Journey

Every community’s buying starts on one screen — the Buyer Dashboard. In a single glance the board sees how many procurements are active, how many contracts are running, what is expiring in the next ninety days, and the total dollar value under management.

In this walk-through the community is Palmetto Lakes HOA — demonstration data, not a real association — with one active procurement worth an estimated $285K. Anything a board is likely to let slip (a contract quietly expiring, a rebid coming due) is surfaced here before it becomes a scramble.

Starting a procurement begins with one plain question: what does the community need to buy? The board chooses the category — Landscape Maintenance or Roofing & Roof Maintenance — and CPI shapes the rest of the intake around that trade.

The promise is printed right on the screen, in the community’s own words: “We’ll match qualified vendors on capability alone — never on who pays.” That is not marketing copy; it is the rule the matching engine actually follows in Stage 6.

The scope step is where a vague “we need landscaping” becomes a precise, biddable request. CPI pulls the community’s known facts from its association profile — landscaped acreage, number of lakes, irrigation zones, tree inventory, building count, roof types — so the board is confirming, not re-keying.

The board then states the required services, any optional services, the desired frequency, the current deficiencies to fix, and the improvements it wants. That is the RFQ every qualified vendor will bid against — identical scope, so the proposals that come back are genuinely comparable.

What each vendor sees, and what stays with the board

• Shared with invited vendors The scope of work, service frequency, and the property facts a vendor needs to price the job accurately.
• Shared once a vendor qualifies Detailed site plans and the full deficiency list — released to vendors the engine has already matched as qualified.
• Board only — never shown to vendors Your budget posture, internal evaluation priorities and weighting, board deliberations, and every other vendor’s pricing. Nobody bids against your number, and nobody sees a rival’s.

Before the request goes out, the board sets the bar every vendor must clear — applied equally, no exceptions. These are the insurance floors (a general-liability minimum, workers’ compensation, an additional-insured requirement) and the classification standards (worker classification, E-Verify, background checks) the community expects.

Then the board sets the process: how many bids it wants to see, the decision date it is working toward, and what it will weigh most — price, quality, responsiveness. For a large or complex scope, it can also flag that an independent Verified Assessment is needed before award.

Once the board confirms, the opportunity goes live and gets its own record. From this moment every step is time-stamped: when it opened, which vendors were matched, what each proposed, how they scored, and — in the end — why the winner won.

The opportunity page organizes the whole procurement into tabs — Overview, Matches, Proposals, Comparison, and Decision — so the board always knows where things stand.

Now the engine does the work a busy board cannot. It scores every qualified vendor against the community’s actual RFQ across eight capability factors: Geography, Service fit, Size, Experience, Capacity, Qualifications, Verification, and the community’s stated Preferences.

The banner on this screen states the rule in plain words: “Membership, verification, and payment status are not inputs to this score. The platform’s compensation is identical regardless of which vendor is selected.” A Listed vendor and a Premier member are scored by the exact same yardstick.

A high score gets a vendor onto the shortlist; proof keeps it there. Before a large award, an independent verifier confirms each shortlisted vendor’s license, current insurance certificates, workers’ compensation, and track record against the documents on file. The “Verify 10/10” only lands when those documents actually check out.

For the largest or most complex scopes — a full reroof, a multi-year grounds contract — the board can commission an independent Verified Assessment (an arm’s-length, third-party review) so the winning bid is backed by more than a proposal.

Proposals never arrive in the same shape — one bundles emergency calls, another prices them separately; one inspects weekly, another monthly. CPI normalizes them all to the community’s one scope so the numbers finally mean the same thing.

The comparison lays it out side by side: annual base price, a normalized total (so $248K and $272K are a real comparison), the account-manager model, inspection cadence, escalation, emergency response, and every scope line item marked included or not — with its price.

With capability scored, credentials verified, and proposals normalized, the board records its award and the reason for it. The whole trail is preserved — who was invited, who bid, how each scored, and why the winner won.

That record is the community’s protection. When an owner asks “why did we pick them?” or an auditor reviews the file, the answer is one clean, neutral document — not a folder of emails and a fading memory.

The award is the start of the relationship, not the end of the work. The signed contract and its term live in Contracts, and the dashboard’s expiring-in-90-days tracker makes sure a renewal never lapses by accident.

Performance is tracked against the scope the community actually bought, so the next rebid starts from evidence, not impressions. And because the RFQ is saved, the whole request becomes a reusable template — the next procurement takes a fraction of the time.