A quote and proposal request portal is where customers request a quote with the details and photos a job needs, the business sends back a price, and the customer accepts or declines it on the same record.
Pattern: RequestsDescribe it to Pory
“We're a custom woodworking shop. Customers request a quote with photos and measurements, we send a price, and they accept or decline it online.”
My quote requests
Vikram replies to every request within two business days. Small jobs are priced from your photos; anything bigger than a shelf gets a measuring visit first.
We have your request, photos and measurements.
Vikram is measuring or pricing it, and may ask for another photo or measurement.
The quote and drawing are on your request. The price holds for three weeks.
We order the wood and book your installation date, usually six to eight weeks out.
In plain English
Pory gives every customer and estimator a sign-in of their own. Each customer sees only their own quote requests. It covers request → send → accept. Quote requests, photos and measurements, visits, invoices, drawings and quotes, our work and oakline team live in Pory's own database, so there's no spreadsheet to keep in sync.
What it does
Quote requests used to start as a phone call, continue by text with blurry photos, and end with the estimator asking for measurements again. In Pory a customer describes the job, picks the service, gives a needed-by date and uploads photos and measurements in one request. They can see where each request stands, so "did you get my photos?" stops being a text.
Accepted quotes used to be a "yes go ahead" buried in an email chain, which made start dates guesswork. The customer opens their quote, checks the price, the drawing and the attached quote document, and accepts or declines, adding a note if the price or timing doesn't work. The estimator knows which jobs are real without chasing anyone.
Every person signs in to their own view. This is what each role in the demo gets.
Sees only their own quote requests.
Sees every quote request in the portal.
The tables and fields Pory sets up for this portal. Describe your own version and change any of them in the editor.
Each one reads and writes the same records, so a form, its approval and the status page someone checks are one system. How Pory builds a portal
Signed-in or public, with typed fields and file uploads. A form files a record; it doesn't start an email thread.
Decision buttons for whoever may edit the status. Who decided, when, and why stays on the record.
Each person sees their own records, the ones assigned to them, or the ones they manage. Fields can be hidden per role. Pory sets this up from your description, and you can adjust it in the editor.
A sign-in link by email, by default. Password sign-in if you'd rather.
Your domain, your colors, your logo. Members see you.
Describe who signs in and what each person needs, and Pory builds it. Join the waitlist while signups open; paid plans are a flat price with unlimited customers.
