Short answer: A specification manager works to get a building product named or approved in construction project documents — before the tender, and usually with someone who will never place an order. The role sits between technical advice and sales: they talk to architects and specialist planners about performance requirements, supply specification text and technical data, and try to shape the criteria before they are fixed. They are measured on specifications won, not on revenue booked.
The role in one sentence
Field sales sells to the buyer. The specification manager sells to the person who decides what the buyer is allowed to buy.
That distinction explains almost everything else about how the role works, and why it is so frequently mismeasured.
What the job actually involves
Building relationships with specifiers. Architecture practices, specialist planners, engineering consultancies. These are long relationships, often spanning many projects. A practice that has specified you three times is a materially different prospect from a new one.
Technical consulting on live projects. An architect at design stage has an unsolved problem and a deadline. The specification manager's value is helping solve it — which means knowing the product deeply enough to say where it does not fit.
Supplying specification text and data. Ready-to-use wording, current technical data sheets, test reports, declarations of performance, and product data in the formats specifiers actually work in. Friction here costs specifications quietly.
Shaping criteria, not just naming products. Sole specification is rarely achievable. The realistic goal is often performance requirements your product meets comfortably and competitors meet marginally — a structural advantage that survives the tender.
Defending the specification at procurement. Winning the specification is not winning the order. Contractors substitute on price, lead time or habit. Someone has to notice when a specified project reaches award and reach the winning contractor before purchasing decisions are made.
Feeding the pipeline back. Which criteria keep appearing, which certifications specifiers ask for, which competitor is winning which segment. This is market intelligence that should reach product management, and usually does not.
How it differs from field sales
Specification manager | Field sales | |
|---|---|---|
Talks to | Architects, specialist planners | Contractors, distributors, purchasing |
Project phase | Planning and design | Tender through procurement |
Decides | What is acceptable | Who supplies it |
Time to revenue | 6–24 months | Weeks to months |
Measured on | Specifications won | Orders booked |
Main risk | Substitution at procurement | Price competition |
Companies that run both roles need them connected. The most common failure is that the specification manager wins a specification, nobody tells field sales, the project goes to tender, and a competitor is substituted without anyone noticing until the order does not arrive.
The measurement problem
This role produces no revenue for a year. In a standard sales report, a specification manager doing excellent work looks less productive than a rep chasing tenders. That is a reporting failure, and it is why the function gets cut first when budgets tighten.
The metrics that actually reflect the work:
Specification rate — share of pursued projects where your product is named or approved
Sole versus "or equal" split — quality of the specifications won, not just quantity
Average project stage at first contact — are you inside the influence window
Time from project identification to specifier contact
Specification-to-order conversion — how much survives procurement
Influenced project volume — total value of projects where you are in the specification, by stage
None of these appear in a default CRM report, because a default CRM records orders, not specification milestones. Making them visible requires the project to be the CRM object and specification to be an explicit pipeline stage.
What makes the role hard in practice
Finding the projects. A specification manager can only influence projects they know about while the window is open. Tender portals are structurally too late. Early signals sit in planning applications, permits, design competition results, developer announcements and trade press — high volume, fragmented, and hard to work manually.
Finding the right person. Knowing that a practice is the architect is where research begins. Practices rotate project teams, and the name on the planning application is often not the one writing the specification.
Remembering to come back. Projects go quiet for months and then move in a week. Follow-up triggered by a calendar reminder set eight months earlier is not a system.
These are the three places where the role loses most of its time, and none of them is the part of the job that requires a specification manager.
How the work changes with project intelligence
Building Radar is built around this pattern. Projects are detected at planning and design stage across more than 50 countries and scored against the manufacturer's own portfolio, because Jeane, the intelligence inside Building Radar, reads your website, product catalogues and technical data sheets. The deciding role per project arrives with reachable contacts rather than a firm name. Project stage changes are monitored continuously, so follow-up is triggered when a project moves — including when a specified project enters procurement and substitution risk begins.
Holcim, whose specification managers work this way, reports a 400% increase in sales meetings. The mechanism is straightforward: more projects reachable while still open, and less time spent on research.
Frequently asked questions
What is a specification manager? A role at a building product manufacturer responsible for getting products specified in construction projects, working primarily with architects and specialist planners during the design phase.
Is a specification manager a sales role? It is a sales role with a technical core. The output is commercial — a specification that leads to orders — but the daily work is technical consulting rather than negotiation.
How is a specification manager measured? On specification rate, the sole-versus-equivalent split, project stage at first contact, and specification-to-order conversion — not on booked revenue, which arrives much later and through a different party.
Do you need a specification manager if you have field sales? If your product is decided at design stage by an architect or planner, yes. If it is decided at procurement by a subcontractor, field sales covers it.
How many projects can one specification manager handle? Typically forty to eighty active projects, depending on product complexity and cycle length. Beyond that, follow-up quality degrades.
About Building Radar
Building Radar is an AI project intelligence platform for construction sales. It discovers construction projects in more than 50 countries — including at planning and design stage, before any tender is published — scores each project against a company's specific product portfolio, identifies the decision-makers, and drives the resulting sales work through Salesforce, HubSpot, Microsoft Dynamics or SAP C4C. Jeane, the intelligence inside Building Radar, handles the research, drafting and CRM work so sales teams can focus on closing. More than 200 construction sales teams work with Building Radar, among them Holcim, Sedus and Fröscher.
Ready to make specification work visible?
Find out how Building Radar's revenue engineering solution puts specification managers in front of the right projects earlier.
Schedule an initial consultation