Last updated: September 2026
A specification sales manager gets a building product written into the design, then keeps it there. The job is to educate architects, engineers and specifiers on the product, consult on how it fits the project, and stay engaged from design through tender and procurement so the specification is not swapped out before the order lands. Unlike a BDM, the win happens months, sometimes years, before an order is placed.
Key responsibilities of a specification sales manager
Day to day, a specification manager builds and defends relationships with the people who choose products at design stage, mainly architects, engineers and specification consultants, rather than the builders and contractors who eventually place the order. Compliance and code literacy matter most where the product, the application and the buyer demand it. A fire-rated facade system is a different conversation to a design-led interiors product, and the National Construction Code is applied through each state and territory, so the amount of code work in the role depends on what is being sold and where.
- Educate architects, engineers and specifiers on the product through CPD sessions and technical presentations
- Consult on product selection, samples and technical submissions while the design is still open
- Research live and upcoming projects and get in front of the right people early
- Write or influence the specification wording so it holds up when someone tries to swap it
- Track every project through the CRM as it moves from design toward tender
- Defend the specification when a cheaper substitute is floated at procurement or fitout
- Hand off, or carry, the commercial work once the specification is won
Specification is invisible until someone makes it their job to be in the room when the decision gets made. On a role I briefed this year, the first specification hire in the company's history, the job was to build everything: CPD, collateral, spec clauses, pipeline, the function itself.
CPD has moved from a nice-to-have to a standard ask. At least half the specification briefs I take now ask whether the candidate has run CPD presentations. Two years ago that question was not on the brief. More clients want to build out a CPD programme because the demand from architects is there. One specification manager I interviewed this year was running four or five CPD sessions a week.
How much of the job is winning the spec and how much is holding it? My view is that winning it is somewhere between a third and half of the job, depending on the product and the project. People doing the job in lighting put it lower. Three of them, independently, said the same thing: winning the specification is about 20 percent of the job, holding it through to delivery is the other 80, and most people underestimate the second bit. Another put defending and attacking competitor specs as a huge part of the role, especially in the current climate.
Holding it comes down to being findable when the project moves. One specification manager told me: I always made sure my details were on the plans. So when a project moved stages, they could call me directly, and we knew through the CRM where everything was at and could go back to the architect before the spec fell.
The job also means defending the spec once it's written. A product gets specified, but between design and construction it can be swapped out for a cheaper substitute at the procurement or fitout stage. A specification manager's real value is stopping that substitution from happening, not just winning the initial spec.
The cycle from specification to order is not one length. From what I hear across the roles I recruit it runs anywhere from a few months to three years, by product and project. One person in the role put it this way: specifications might not happen in the first month or two, they might happen six months to two or three years down the track, and his owner was happy with that. Set ramp expectations against that cycle. A manager who expects orders in the first quarter is measuring the wrong thing, and both sides end up frustrated.
What skills does a specification sales manager need?
Product and market knowledge first. A good spec rep knows the market, the competitor products and where their own product wins, which is why they are usually easier to place into an aligned product than a new category. They are the technical expert in the room. That said, transferable skills matter more here than in most sales roles. Some of the strongest waterproofing specification people I have placed were structural engineers or chemists first. In my experience it is more often the spec rep who rejects a role than the other way round, and it is usually on product fit.
On top of that: technical credibility with engineers and specifiers, CRM discipline, access to the decision-makers on live projects, and the patience to work a long cycle without a monthly number to hide behind. A pure spec role is top of funnel. Architects, engineers, designers. CPD sessions, working a room, knowing the product inside out. No monthly number off a builder.
A note on titles, because they are used loosely. Architectural rep and A&D rep usually describe the same job, more often on decorative products. Spec manager and spec rep turn up across every product and sector. Treat the title as a hint and read the scope. The map of how the common titles collapse into a handful of real jobs is in the Eleven Titles, Four Jobs taxonomy, and the two-role diagnostic is in Specification Manager vs BDM.
How is a specification manager different from a BDM?
A specification manager sells to the people who design the building, a BDM typically sells to the people who build or buy for it, and the two roles get confused constantly in job briefs. A BDM's activity is usually visible fast: calls made, quotes sent, orders won within weeks or months. A specification manager's activity is invisible for a long time before it shows up as revenue, because the win happens at design stage and the order doesn't land until the project reaches site.
This distinction causes real hiring problems. Companies write a "BDM" job ad expecting fast order-taking, then hire someone whose actual skill set is long-cycle relationship building with architects and engineers, and both sides end up frustrated. I've gone deeper on this distinction, including a 20-minute diagnostic for checking which role you're actually briefing, in Specification Manager vs BDM.
How is a specification manager different from an account manager?
An account manager manages existing customer relationships and repeat revenue, while a specification manager is building new relationships with a design community who rarely buy anything directly. They choose what gets written into the plan. The confusion between BDM, account manager and specification manager comes from all three being labelled "sales" when the actual buyer, sales cycle and skill set are different for each.
| Specification Manager | BDM | Account Manager | |
|---|---|---|---|
| Sells to | Architects, engineers, specifiers | Builders, contractors, distributors | Existing customers |
| Sales cycle | Months to years, by product and project | Weeks to months | Ongoing, repeat |
| Core skill | Technical credibility, code fluency, spec defence | New business hunting, relationship speed | Retention, account growth |
| Activity visibility | Delayed, hard to measure early | Fast, easy to measure | Steady, recurring |
A full breakdown of the eleven job titles that actually collapse into four distinct jobs in this market, including where account manager sits, is in the Eleven Titles, Four Jobs taxonomy.
What do specification sales managers earn in Australia?
From the specification roles I have briefed and placed this year, a base of $120,000 to $140,000 is typical, plus superannuation, plus a car or car allowance of $15,000 to $25,000 quoted separately, sometimes with a fuel card or etag. National specification roles can run to $150,000 to $160,000 base. That sits above a standard BDM, which I see at $100,000 to $130,000 base. These are my own figures from live briefs, current at September 2026, not a survey. For how packages are structured across building products sales, see the Building Products Sales Salary Guide.
Where does a specification manager sit in the buying chain?
The role works at the early end of a long chain. A building product runs through a series of decisions before it is installed, and the specification manager does most of their work near the front while the order is placed much later, usually by other people.
I use one framework for this across every role I recruit. I call it the Building Products Decision Chain. The role hub maps these stages across every building products sales role:
Need → Influence → Specify → Approve → Fund → Price → Purchase → Install → Operate → Replace
This is a simplified decision path, not a perfectly linear process. Stages can overlap, repeat or happen in a different order depending on the project and the procurement model. Most of the specification manager's work sits in Influence and Specify. On hybrid or smaller-project roles the same person may also support pricing, procurement and conversion further along the chain.
Who specifies the product, and who approves and buys it?
The split is not always clean. On some projects the specifier is also the approver, the funder or the buyer: an owner-developer, a commercial owner-occupier, a government asset owner, or a homeowner working with a designer. On others, the product is assessed and paid for by people the specification manager never meets in the design room. Read each project to see where those roles actually sit, because it changes who the hire has to reach to protect the specification.
Why does winning the specification not guarantee an order?
Winning the specification puts the product in a strong position, and holding it to an order is a separate job. Once the design is set, a contractor or subcontractor can propose an alternative during design review, pricing or procurement. Whether that alternative can actually be used depends on the contract, the specification wording, the approvals required, and the evidence of suitability the project and the National Construction Code call for. A technical assessor, engineer or certifier judges whether the alternative performs and complies. A separate party, usually the client or the superintendent under the contract, holds the authority to accept or reject the change. Some products are tightly documented and hard to swap without a formal equivalence assessment. Others are written loosely and move easily. The variable is how well the performance is specified and evidenced, which applies to technical and decorative products alike. A specification manager whose relationships stop at the architect can win the specification and still lose the order, because the people who assess, price and buy the product sit further down the chain.
Which relationships keep a specification alive?
A specification survives to an order when someone holds a relationship at each stage where it can be challenged. The table below maps the stages of the Building Products Decision Chain, the stakeholders who typically shape each one, the decision they influence, and what a strong candidate should be able to show for it. On larger or more complex projects, few stages are settled by one person alone. It is a map of the network a specification hire has to reach, and a way to read whether they have actually held it or only met the architect.
| Decision stage | Typical stakeholders | Decision they influence | What a strong candidate should demonstrate |
|---|---|---|---|
| Need | Developer, homeowner, government agency, asset owner or end user | Project need, performance brief, constraints and owner standards | Can show, without confidential detail, how they turned an owner or user need into a product requirement |
| Influence | Architect, designer, engineer or consultant | Initial product category and the shortlist | How they created early access, identified the decision-makers and changed or narrowed the shortlist |
| Specify | Architect, engineer or specification writer | Product wording and the alternatives allowed | A specification they influenced, the wording or performance requirement, the alternatives permitted, and how they tracked it after issue |
| Approve | Technical assessor, engineer, building surveyor or certifier for suitability, and the client, superintendent or contract authority for acceptance, depending on the project and jurisdiction | Whether the evidence satisfies the technical and compliance assessment, and whether the party authorised under the contract accepts the change | Technical credibility, compliance literacy, and knowing who signs off the change |
| Fund | Owner, developer, government client or finance authority, depending on the project | Whether the project and the product position fit the approved capital and delivery case | Understands the commercial approval constraint and whether they influenced it directly or through the client team |
| Price | Quantity surveyor, estimator or contractor | Cost pressure and value-engineering options | Can compare price, installation, availability, performance and warranty without claiming an equivalence they cannot support |
| Purchase | Builder, subcontractor, procurement team, distributor or client | Supplier selection and any proposed substitution | How they identified the purchasing route, supported the bid or channel partner, responded to a proposed alternative, and confirmed the order was placed |
| Install | Installer, applicator or specialist subcontractor | Buildability, system compatibility and site acceptance | A site issue, training need or installation constraint they resolved |
| Operate / Replace | Asset owner, facility manager, government operator or end user | Maintenance, warranty, spares, future standards and replacement choice | Post-installation feedback or repeat-specification evidence |
Practitioner note: this framework reflects my first-hand experience recruiting specification, technical and project-sales roles across Australian construction chemicals, building envelope, civil and infrastructure, interiors and architectural lighting. It is how I test candidates. It is not a survey. Which stakeholder carries the most substitution influence varies by product, project and procurement model.
How can you test this network in an interview?
The framework is only useful if you can test it. Ask the candidate to walk one real project the whole way, using a non-confidential example:
- Take me from the project need to the product that was ordered or installed. What was your part in it?
- Who shaped the design, the technical assessment, the price, the purchase and the installation, and how did you identify them?
- Where was the specification challenged, who proposed the change, and who decided whether it was acceptable?
- What product evidence, performance comparison or commercial case did you contribute?
- Which relationships and actions were yours, which belonged to colleagues or channel partners, and how did you confirm the outcome?
A weak answer stops when the architect writes the product into the specification. A strong one follows the project through pricing, substitution review, procurement and installation, and separates what the candidate personally did from what the team or channel did.
What should hiring managers look for when hiring a specification manager?
Look for genuine technical fluency, not just a sales track record. A specification manager who can't hold a conversation with a design engineer about code compliance loses credibility with the specifier community fast, and that community is small enough that reputation damage travels. Look for evidence they've defended a spec against substitution, not just won one, since spec defence is where most of the real commercial value sits. And set ramp-time expectations against the actual sales cycle. If you're measuring a specification manager on 90-day order volume, you're measuring the wrong thing. I've written more on what good looks like in this role, including how the role gets misread in job briefs, in Why Your Reps Win the Spec But Lose the Sale.