30-min call with RobBook a proof-of-concept call
Job 01 · Estimating

// Tank and pressure vessel fabricators · RFQ specification sheets

A customer's RFQ package, read onto one specification sheet your estimator can price from.

An RFQ for a tank or vessel shows up as a requisition, a data sheet, a few specifications and drawings that disagree in small ways. Someone has to pull it all onto one sheet before the estimate starts. A free AI proof of concept has AI build that sheet again from copies of 20 to 30 RFQs your estimators already worked up, showing every field with the page it came from and every item a person must clarify first. Your reviewer, the person who knows these packages best, compares each draft with the sheet your team built.

Book a proof-of-concept call30 minutes with Rob
Past RFQs
20 to 30
Design calculations
None
System access
None

// The one job

From a stack of purchaser documents to one sheet an estimator can trust

The package rarely lands in one format. A process plant sends a requisition, a filled-in vessel data sheet and its engineering specifications. A utility sends a specification section through its engineer. A food maker may send a sketch and a paragraph. Your estimator or applications engineer reads all of it, works out which construction code and edition governs, and writes down the design conditions, materials, nozzles, corrosion allowance and the inspection and stamping requirements that will drive the price.

For the test, AI reads copies of those packages and drafts the specification sheet in the layout your estimators use, with each entry tied to the document and page it came from. Where two documents disagree, both values appear. A field the package leaves blank stays blank and goes on the clarification list. No customer hears about it, and no calculation is run.

RFQ packageRequisition, data sheet, specs
Design code
Design conditions
Materials
Inspection
NozzleSize and classService
Invented package, no buyer's data
Read field by field
with the source page
Draft specification sheetFor your estimator
Code and edition
Corrosion allowance
Stamping
To clarify
FieldAs writtenSource
Invented sheet, for illustration

// What makes it hard

Why two RFQs for the same vessel can need different sheets

ASME publishes the questions. Form U-DR-1, User's Design Requirements for Single-Chamber Pressure Vessels, sits on ASME's forms page, marked as revised for the 2025 edition, with a U-DR-2 for multi-chamber vessels. It runs from owner, operator and city of installation through service and specific gravity to yes-or-no boxes for National Board and Canadian registration and a special service line for lethal, direct firing or unfired steam boiler duty. NB-57, the National Board and ASME guide for certification reviews, asks who in a shop decides whether that form is required and who checks a customer's specification against the scope of the Certificate of Authorization. When a package arrives without the form, the draft borrows its order, so an empty row shows exactly what the customer never said.

One line on a requisition is several boxes on the form. MAWP is either the same as design pressure or calculated by the manufacturer. Minimum design metal temperature gets two cases, each marked process or ambient. Corrosion allowance splits into shell, heads, nozzles, jacket, coil, supports and internals, inside and outside. Post-weld heat treatment is per code or process required, cyclic service brings cycles, design life and a fatigue analysis box, and one box asks whether coating is permitted before the pressure test. On the back, joint categories A, B, C, D and F each take a type of joint and NDE with comments, shell, cone and head thickness each name the joint efficiency they rest on, and body flanges point to ASME PCC-1 for joint assembly. The draft fills in what the package states and computes none of it.

Plants and tank buyers bring forms of their own. Process Industry Practices publishes data forms and instructions for specifying Section VIII vessels as VEDV1003, used with its design and fabrication specification, VESV1002, which reaches through shipping and documentation. A tank RFQ goes another way. A public contents list for API 650, in the 2018 addendum to its 2013 edition, shows Annex L as the Storage Tank Data Sheet and Annex W as Commercial and Documentation Recommendations, with separate annexes for seismic design, internal floating roofs, shop-assembled tanks and austenitic stainless steel. That listing marks the edition as since replaced, so the draft records which edition and which annexes this buyer named and leaves their reading to your estimator.

A public buyer's blanks are part of the specification. The New York State Office of General Services master section on multi-column elevated steel water tanks lists what the purchaser supplies under AWWA D100: capacity, bottom or top capacity level, head range, riser diameter, even the nearest town and railroad siding with their distances from the site. Corrosion allowance is a blank with none required as one choice, earthquake design points to D100's Section 13, and delegated design calculations come signed and sealed by a New York licensed engineer. In a bid set, a bracket nobody chose is a question, and the draft treats it as one.

The clarification list is where a reviewer looks first. A package can name Section VIII with no division or edition, show one nozzle count on the data sheet and another on the sketch, or call for plate as A516 when the NB-57 review asks whether materials are ordered to SA, SB or SFA specifications. Each goes on the list, quoted from both places, for your estimator to take up with the customer. Your reviewer, usually the chief estimator, checks that the governing code was read correctly, that every field traces to the right page, that every conflict was caught, and that the list matches what your team really asked.

// What you send

Packages your estimators already worked up

Copies only
Closed RFQs only
01

20 to 30 RFQ packages

Requisitions, data sheets, specifications, sketches and addenda as they arrived. Mix ASME vessels with API or UL tanks if you build both, and include one you declined to bid.

02

The sheets your estimators built

The internal specification sheet or estimate input for each RFQ, along with any list of questions that went back to the customer.

03

Your exclusions and house defaults

Standard exclusions, clarifications and default assumptions your estimators reuse, as they stood when each RFQ was priced. A page of notes will do.

04

An NDA, then copies only

Signed before any package moves, with customer names masked if you prefer. We never sign in to your estimating, quality or ERP system. If a customer's terms keep a package inside your building, we build look-alikes with you.

// Before it starts

Settled before the first package is copied

The owner puts each of these on paper before anything leaves estimating.

Terms for the specification sheet testOwner decides
Your reviewer
Named by the owner, usually the chief estimator
Sheet layout
Your own, with your own field names
Success criteria
Written first: fields that must match, conflicts that must be caught
Sample
Picked by your reviewer, with one package that names no edition
Who calculates
Your engineers, in the test and live
Price
A range for the live job, given before anything starts

// How it's scored

The sheet your estimator built, beside each draft

RFQ by RFQ
field by field
On the same 20 to 30 RFQsThe sheet your team builtThe AI draft
Governing code, division and edition namedMarked on your RFQsMarked on your RFQs
Design pressure and temperature fields, each with its source pageMarked on your RFQsMarked on your RFQs
Materials carried as the customer wrote themMarked on your RFQsMarked on your RFQs
Nozzle schedule complete: number, size, flange type and classMarked on your RFQsMarked on your RFQs
Corrosion allowance by part, inside and outsideMarked on your RFQsMarked on your RFQs
Examination, registration and stamping requirements listedMarked on your RFQsMarked on your RFQs
Conflicts between documents caught, with both lines shownMarked on your RFQsMarked on your RFQs
Questions for the customer that your estimator also raisedMarked on your RFQsMarked on your RFQs
Blank until your RFQs run. No cell is filled before drafts from your own closed packages have been compared.Your chief estimator marks each row, and that mark decides it.

// After a yes

About 30 days on incoming RFQs

A yes from your reviewer sends new RFQ packages through the same reading for about 30 days.

Your estimator checks and corrects every sheet before a number is worked up, and any question for a customer leaves from your office. The comparison table keeps running on live packages, the next job carries a price of its own, and monthly support comes after that.

// What could follow

Where the estimating desk could go next

Possibilities only
Each priced alone
  1. 01

    Data report packages

    Turnover books assembled from shop records, with every item that has no record listed for your quality manager.

    Next
  2. 02

    Material requisitions

    Plate, heads and forgings from an approved sheet listed for your buyer, with the certificate requirements carried over.

    Then
  3. 03

    Customer drawing comments

    Approval markups listed against the drawing revision they were made on, with open items named for your project engineer.

    After that

// One hard limit

It never performs a design calculation or touches a live quote.

The draft records what the customer wrote. It never sizes a shell, head or nozzle, picks a joint efficiency or a material, or decides that a vessel meets a code, and it signs and stamps nothing. It never opens your estimating, quality or ERP system or a live quote. An estimator checks every specification sheet, and your quality staff and the authorized inspector make every code decision. Defense and aerospace RFQs stay out of the test. Standards and forms named here are described for context, not as legal or engineering advice.

Priced per job. You get a range before the proof of concept and a fixed price before you sign.

What moves the range: RFQs worked up each month, how many construction codes they span, and how many customer data forms your estimators see.

// Questions

Specification sheet questions

Will it calculate shell thickness or check our nozzle reinforcement?
No. It performs no design calculation of any kind. If a package gives a thickness, the draft records it as written, and working out whether it is right stays with your engineers.
Our RFQs often don't name a code edition. What happens then?
The field stays empty and the item goes on the clarification list, with the page where a reader would expect to find it. The draft never assumes the current edition on a customer's behalf.
Customers state the same requirement two different ways. Does it pick one?
No. Both values go on the sheet with their source pages, and the conflict goes on the list for your estimator to settle with the customer.
Can it read scanned data sheets and handwritten markups?
Yes, as copies, and the sample should include them. Anything it can't read clearly stays open for your estimator instead of being filled in with a likely value.
Do API 650 and UL 142 tanks work here as well as ASME vessels?
Yes, if they are in your mix. Each gets the fields its own standard and RFQ call for, so a listed shop tank's sheet looks different from a code vessel's. Your reviewer writes down what each type must contain in the success criteria.
Do you need our estimating or design software?
No. You send copies of packages and the sheets your team made, and drafts come back as files. How a live month would work with your own tools gets decided only after a yes.
Rob Eason

Rob Eason, founder

// Book a proof of concept call

Bring the RFQ package your estimators argued over.

Half an hour with Rob on what you build, your role, the job you'd test and how many RFQs reach estimating in a month. Requisitions, data sheets and drawings stay with you 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.