Vendors & subs

The job pressure

Vendor lists live in spreadsheets while RFQs invent a second roster.

All packages that award trades after winning a job

On the job

Vendor lists should not live in a spreadsheet while RFQs invent a second roster. EstiLumina keeps an org directory and a job roster on the same contacts you invite to a frozen bid package.

Import trades onto a job, issue RFQ from Bids, and award to a commitment without retyping names. Portal links after Issue use the same roster the office already trusts.

That is how award-to-PO stays honest: one directory, one roster, one commitment on the job.

How it works

1. 1

   Maintain an org-wide vendor and sub directory.

2. 2

   Import trades onto a job roster for the RFQ-to-award pipeline.

3. 3

   Issue RFQ from Bids with the same roster contacts.

4. 4

   Award ties the trade back to a commitment on the job.

What you get

• Org directory with trade filters
• Job roster pipeline for RFQ invites
• Trade invites tied to bid packages
• Works with bid portal links after Issue
• Feeds award → PO without retyping contacts

Why teams subscribe

• One vendor directory feeds every job roster
• RFQ invites reuse the same trade contacts
• Award to PO keeps the trade on the commitment

Honest boundaries

• Not a public contractor marketplace.
• Not a claim that every trade already has an EstiLumina login before you invite them.