For the company’s principals
Register your management company.
Four steps. You tell us the size of the company, the states you cover, and the community sizes you take on. Then put up to 3 communities on the platform free. What you get back is an operator’s account. Your managers work from one dashboard, and you hold the controls.
Registering creates your company account immediately. VendoRFP still verifies every company by hand before your listing publishes or a single community lead reaches you.
The company
Four answers, two of them taps. The domain and the website are optional.
As a board would see it on your listing.
How big is the company
Communities you run today
Two-letter codes. This is what you advertise. VendoRFP sets the states you receive community leads in, at verification. You cannot widen that from here.
Optional, and worth doing. Claiming reserves the domain to you: VendoRFP approves one domain for one company. Publishing the TXT record we give you is what switches auto-join on. After that, anyone who signs up at your address joins as a manager once they confirm it, with no invite. Two proofs are at work here. The record proves the domain belongs to your company. Confirming the address proves the person can read mail at it. Your domain is on your website, so knowing it proves nothing on its own. New managers arrive with the standard permissions and no team or portfolio administration. Inviting managers by name works from the moment you register.
Optional. Shown on your listing.
VendoRFP reaches you on the address you sign in with. A phone number is only ever used for two-factor sign-in, once you have an account.
The control suite
What a company account gives you over your managers.
| Permissions per manager | 11 permission switches, on or off per manager. Two of them decide who may see money and who may award work. Awarding work and approving a work order are enforced on the server, so a switch you turn off holds even against somebody going straight at the URL, and every switch says right beside it what it covers. |
|---|---|
| A record of every control change | Permissions toggled, seats invited, suspended or removed, communities added, domains claimed. All of it goes to a log that only ever gets added to. Day-to-day work inside a community is stamped on its own records instead, so this log holds what was decided. |
| Seats and logins | Invite, edit, suspend and remove managers. Suspending a seat revokes every permission on it, and has to carry a reason the manager can read. |
| Your mail domain joins your managers | Claim your company’s mail domain and prove it with one DNS record. After that, anyone who signs up at that address joins your roster as a manager on their own, the moment they confirm the address. The proof is yours to give and yours to revoke, and team and portfolio administration stays yours to grant. |
A new manager seat starts with the day job switched on and money switched off. Billing and awarding work are switches you grant on purpose.
A manager seat is 11 switches. These are all of them.
Two proofs do two different jobs before anybody joins on a claimed domain. The DNS TXT record proves the mail domain belongs to your company. Confirming the address proves the person typing it can read mail there, which matters because anyone can read your domain off your website. Both have to hold — and the grant that follows carries no team or portfolio administration.6 of the 11 are on when a seat is created; the rest, marked below, you switch on yourself.
See RFPs
Create RFPs
Select winning proposal — off until you grant it
Approve work orders
See billing and spend — off until you grant it
See vendors and compliance
Message vendors
Use the estimate engine
Invite and manage other managers — administration, yours to grant
Assign communities to managers — administration, yours to grant
Reveal and set lockbox codes — off until you grant it