// HVAC equipment manufacturers · Quote requests
A rep's request and an equipment schedule, read line by line into a quote sheet for your applications engineer.
Your rep forwards a job: an engineer's equipment schedule, a specification section and a note about bid day. Someone on your applications desk has to read every tag against what you build before a selection run can start. A free AI proof of concept does that reading again on copies of 20 to 30 requests you already quoted, and drafts the quote sheet tag by tag, with every line a person must select or resolve listed. Your reviewer, the colleague who knows this desk best, holds each draft against the quote that went back.
- Past requests
- 20 to 30
- Units selected by AI
- None
- Logins needed
- None
// The one job
From a forwarded schedule to a quote sheet your engineer can start from
A request comes in from the rep agency as an email with attachments: the schedule page from the mechanical drawings, the spec section for that equipment, sometimes an addendum and a list of approved alternates. Your applications engineer pulls each tag's airflow and static, coil and fan data and electrical data, notes the construction options and tests the section adds, and only then opens the selection program.
In the test, AI reads the same copies and drafts the quote sheet: unit tag, airflow and static as scheduled, coil and fan fields, voltage, phase and ampacity fields, the construction options the spec calls for, the testing or certification it requires, and the lines a person has to select or resolve, each with the page or clause it came from. It runs no selection, prices nothing and sends nothing to a rep.
for your engineer
// Where it gets hard
Where a schedule and a section stop being one request
The tag is the key, and owners don't write the line the same way. The University of Georgia's standards, dated July 1, 2026, make every schedule give each piece of equipment a unique identifier, rule out a single type standing in for several units and say a building can't hold two AHU-1s. They also want the basis of design by make and model with all options, once the designer has verified the model is still in production. Old Dominion University goes the other way: it discourages designers from printing a manufacturer's cooling, heating and efficiency data on the schedule, so makers compete on calculated values and code minimums, and it allows manufacturer values only for custom and specialty equipment. One request names a competitor's model with every option. The next gives only the duty. The draft carries each line as written and says which kind it read.
Static pressure depends on who added what. Old Dominion has every scheduled fan with filters state its dirty filter pressure drop allowance. Georgia bases fan static on filters half loaded, plus system effect, internal cabinet losses, external duct losses and the drops through coils, dampers and humidifiers. The University of Houston's section for custom air handlers then moves the target: the fan has to run stably at half an inch above the scheduled static, and the motor can't overload a half inch below or above it. Old Dominion even fixes elevation, letting design calculations use sea level or 17 feet. So the draft records external or total static as the sheet states it, the filter condition, any margin the spec adds and any elevation it gives, and leaves a question where the request is silent.
Coil and fan lines go well past the schedule. Old Dominion wants each designed coil's entering and leaving air and water conditions, air and water pressure drop and tube velocity on the schedule, with fouling factors alongside. AHRI's coil program certifies average total capacity, air pressure drop and fluid pressure drop, so the rest is your own construction data. Houston's master section offers bracketed choices of 8 or 12 fins per inch, tube walls of 0.020, 0.024 or 0.035 inch and 304 or 316L stainless casings, and tests coils by air pressure under water at one and a half times the pressure on the drawings, never below 250 psig or above 500. A bracket left unedited is a question, not a value. On the air side, Houston's fan array paragraphs call for a backdraft damper on each fan and one complete spare fan and motor assembly with every unit, while Georgia specifies direct drive fans with variable speed drives and puts belts behind a written variance.
Certification lines look alike and aren't. AMCA warns that a product tested to an AMCA standard isn't necessarily certified, that certified makers aren't required to show the seal, and that a requirement to bear the seal can be met with literature showing it in a submittal. Houston wants fans that bear the seal for air and sound. A 2023 elementary school section from Massillon City Schools in Ohio wants air handlers cETLus listed to UL 1995 and CAN/CSA C22.2 No. 236, and certified under AHRI's Standard 430 program with a note excepting fan arrays. Its filter line says UL 900 listed, Class I or Class II, where Houston's says Class 1. The same Massillon section limits casing leakage twice, once per square foot of casing and once as a share of supply air, at different test pressures. On a California hospital, certain equipment needs a Certificate of Compliance for special seismic certification, which the state's voluntary OSP program reviews and preapproves. The draft lists each requirement in the owner's words, takes no position on whether a unit meets it, and marks any two that conflict.
The expensive sentences sit away from the schedule, and your reviewer watches for them. Houston has the owner's representatives witness factory vibration, acoustical and unit run tests, with the contractor paying air fare and lodging for two of them. Old Dominion asks for factory and field leak testing on air handlers above roughly 10,000 cfm, with witness testing coordinated through its facilities office. Massillon says that if a submitted unit differs from the design basis in size, capacity, connections, electrical needs, weight or pad requirements, the manufacturer bears the cost of the changes and of coordinating the other trades. Your reviewer, usually the lead applications engineer, checks that every tag came across, no scheduled number changed, no value was invented for a blank or a bracket, every test and listing the section names landed on a line, and every clause like these reached the list a person has to resolve.
// What you send
Requests your applications desk already answered
20 to 30 closed requests
Each one as the rep forwarded it: the email, schedule pages, specification section and any addendum, plus the quote that went back. Include jobs you won, jobs you lost, one you declined and a custom unit if you build them.
The selections behind them
The selection output or internal quote sheet for each request, as it stood at the time. It is the answer key for the comparison and is never rerun.
Standard options and exceptions
Your construction options, test offerings and the exception wording your engineers reuse, as PDFs or a workbook dated to match those quotes.
Copies, once the NDA is signed
Rep, contractor and owner names can be masked. Nobody here signs in to your ERP or selection program, and if a customer's terms keep a drawing inside your building, we build look-alikes with your reviewer.
// Before it starts
Decided before the first schedule is copied
The owner fixes these in writing before anything leaves the applications desk.
- Your reviewer
- Named by the owner, usually the lead applications engineer
- Success criteria
- In writing: which fields must carry over exactly, how open lines are scored
- Sample
- Your reviewer's pick, catalog and custom units both where you build both
- Who selects
- Your engineer, during the test and after it
- Price
- A range for the live job, given up front
- NDA
- Signed before any file is copied
// How it's scored
The quote your desk returned, beside the draft, tag by tag
| On the same 20 to 30 requests | The quote that went back | The AI draft |
|---|---|---|
| Unit tag and basis of design, as scheduled | Marked on your own requests | Marked on your own requests |
| Airflow and static, with filter condition and elevation where stated | Marked on your own requests | Marked on your own requests |
| Coil and fan fields carried from the schedule and the section | Marked on your own requests | Marked on your own requests |
| Electrical fields: voltage, phase, ampacity, disconnect, drive | Marked on your own requests | Marked on your own requests |
| Construction options the spec calls for | Marked on your own requests | Marked on your own requests |
| Testing, listing and certification lines | Marked on your own requests | Marked on your own requests |
| Lines held for a person, each with its clause | Marked on your own requests | Marked on your own requests |
// After a yes
About 30 days on new rep requests
A yes from your reviewer moves the same reading onto new rep requests for about 30 days.
Every quote still leaves from your own system after your applications engineer has selected, checked and approved it, and the scoring table keeps running on live requests. Anything further is a separate decision with its own price, with monthly support after that.
// Jobs that could follow
What could come after the quote desk
- 01Next
Warranty claim files
A field claim put together from its form, serial number, ship date and start-up report for your warranty administrator to decide.
- 02Then
Submittal packages by tag
Certified drawings, fan curves and coil data gathered for each tag against what the section lists.
- 03After that
Replacement part quotes by serial
A failed component traced through that serial number's build record and drafted for your aftermarket desk.
// One hard limit
It never selects equipment and never touches a live quote.
The draft reads what the schedule and specification say and lists what a person must decide. It runs no selection and doesn't say a unit meets a duty, a listing or a rating. It never opens your ERP or selection program, never touches a live quote and never writes to a rep or a customer. An applications engineer approves every quote. This page describes public specifications and rating programs and isn't engineering or legal advice, and defense and aerospace jobs stay out of the test.
Priced per job. You get a range before the proof of concept and a fixed price before you sign.
Rob gives the range on the call, once he knows how many rep requests your desk answers in a month and how many product families your schedules cover.
// Questions
Quote request questions
Will the AI pick the unit or run our selection program?
Our schedules arrive as scanned drawings, PDFs and spreadsheets. Does that work?
What if the schedule and the specification disagree?
Can it tell us whether we meet a listing or rating the spec names?
Do our reps have to change how they send requests?

Rob Eason, founder
// Book a proof of concept call
Bring a bid day's worth of forwarded schedules.
Half an hour with Rob about what you build, your role, the job you'd test and roughly how many rep requests arrive each month. Keep every schedule and spec section until the NDA is signed.
- Co-owned a 60-employee financial services firm and sold his share to his partner.
- Ran GOSO Technologies, a Boston solar company rated 5/5 across 24 Google reviews.
- 5/5 across 83 reviews in HighLevel's Certified Admin Directory.
- 4.3/5 from 6 Google reviews of Massmarket AI.
- Every directory and Google review, critical ones included, is shown word for word at massmarket.ai/reviews.
- Takes every proof-of-concept call himself.
