To help an architect specify your windows, doors, or millwork, make three things easy. They need to see if the product fits the project, find the current documents, and reach a person who can answer what the documents cannot. A project photo can get an architect's attention. To write your product into a spec, they need current details and someone who can answer questions.
Your job is to make those steps easier. A brochure cannot approve a product for a project, so do not let yours pretend to.
Ask Where the Project Stands
"Can I send you our catalog?" is a weak opener. Try this instead: "What are you trying to settle on this project?"
An architect early in design may need a sample and a sense of what is possible. One writing the specification needs exact information. One reviewing a proposed swap needs to know what is different, not hear that it is "basically the same."
Before you send anything, learn:
- Which product or opening is being considered?
- What decision is due next, and when?
- Is the question about looks, fit, performance, installation, or availability?
- Who will review the answer?
Ask only for the project details your team needs. No one should have to send a full set of plans to ask a basic product question.
Build a Packet Around One Product
The packet should let someone check one product without digging through five unrelated lines. Here is what to put in it and who owns each piece.
| Include | Who owns it |
|---|---|
| The exact line, model, and options covered | Product manager |
| Current drawings, with the file type, date, and the setup they cover | Technical team |
| A spec the architect can edit, if you have one | Spec support |
| Test results or ratings, with where they came from and the setup they cover | Technical reviewer |
| Current install and warranty sheets from the maker | Product support |
| How to get a sample, and what the sample shows | Sample coordinator |
| A technical contact, plus a backup | Sales or technical lead |
Not every project needs every item. Find out what the architect needs before you build a giant download bundle.
Dealers and reps need the same pieces. For Architectural Door & Millwork, a distributor serving dealers in Michigan, Ohio, and Indiana, Grit Blueprint made product flyers, specifications, size charts, and a print and digital sales catalog. Whoever is answering the architect should be working from the same current files.
Put the basics on your website, too. A product page with clear document names saves an architect a phone call. See what belongs on a building product page.
What a Drawing Does Not Prove
A nice detail drawing is not a project review. A file may show a product without covering every size, assembly, or condition. A sample may show a finish without showing the whole installed system. A photo of a big opening does not prove your proposed setup meets this project's needs.
Have the right technical person explain what your files cover, what they do not, and what still needs review. Leave design and code calls to the pros who are responsible for the project.
It is fine to say, "We need to check that."
Carry the Question Through the Handoff
Here is a made-up example. An architect asks a regional window brand if a proposed opening will work with a certain wall assembly. The rep sends a catalog and copies a dealer. The dealer asks which opening. The architect has to ask the same question again.
A better handoff carries the product, the drawing, the open question, and the person who owns the answer. The rep stays responsible for getting the answer back, even when someone else has to produce it.
Put five lines on a question card that travels with it.
- Project question: What are we trying to confirm?
- Product and document: Which exact item and revision are we reviewing?
- What we do not know yet: What have we not confirmed?
- Owner: Who will answer, and who is the backup?
- Next update: When will we report back, even if the review is still open?
Promise an update your team can keep. Do not let that update date turn into a promised approval.
If the architect will end up buying through a dealer, the handoff also has to reach the right dealer. That routing choice is covered in dealer locator or get a quote.
Follow Up With Help
After you send the packet, ask if it answered the question and what is still missing. If the project changes, check that your documents still apply. If your product cannot do the job, say so before the team builds its plans around it.
Try It on One Line This Week
Ask someone outside your product team to find one line's current drawing, specification, and technical contact. Fix the first place they get stuck. Then run one real question through the handoff and see if the answer gets back without the architect starting over.
If you make the product and need your dealers and reps to explain it well, see how Grit Blueprint works with building product manufacturers.
Questions and Answers
They need to see whether the product fits the project, find the current drawings and specs, and reach a person who can answer what the documents cannot. Ask what they are trying to settle on the project before you send a catalog.
The exact line, model, and options covered, current drawings with revision dates, an editable guide specification where you have one, performance documents with their source, current installation and warranty documents, how to request a sample, and a technical contact with a backup. Not every project needs every item.
No. A drawing may not cover every size, assembly, or condition, and a sample may not show the whole installed system. Have a technical person explain what your information covers and what still needs review, and leave project design and code decisions to the responsible professionals.
Send a short note with the project question, the exact product and document revision, what is still unknown, who owns the answer and a backup, and when you will report back. The rep stays responsible for getting the answer to the architect.
Ask someone outside your product team to find one line's current drawing, specification, and technical contact, and fix the first place they get stuck. Then run one real question through the handoff and see if the answer gets back without the architect starting over.
Want Help Putting It to Work?
A free call with Stefanie Couch. About 30 minutes.
Not ready to talk? Get the Built to Win Newsletter


