CRM Software for NDT Inspection Companies: Turning RFQs Into Booked Jobs

Every NDT company owner has lived this moment: an RFQ lands at 4:45 PM on a Friday for a weekend emergency callout on a leaking exchanger, and somewhere between the quote going out, the PO coming back, and the crew walking through the gate Monday morning, something gets dropped — a certificate of insurance nobody caught was expiring, a QA contact never looped in on a procedure revision, a technician double-booked on two turnarounds the same week. That isn't really a technology problem. It's a tracking and hand-off problem, and most CRM software marketed to service businesses was never built for an operation that runs on RFQs, vendor pre-qualification, and Master Service Agreements instead of a marketing funnel.

The RFQ Is Not a "Lead": Why Off-the-Shelf CRMs Fit Awkwardly

Salesforce, HubSpot, and most of the CRM category were architected around an inbound, marketing-driven sales motion: a visitor fills out a form, gets scored as a marketing-qualified lead, a sales rep works it into a sales-qualified lead, a demo gets scheduled, a proposal goes out, and the deal closes. That model assumes a buyer who starts anonymous and has to be found and nurtured. It's the right architecture for a SaaS product — and close to useless as a mental model for how NDT inspection work actually gets sold.

An NDT services company — running UT, RT, MT, PT, VT, ET, TOFD, or phased array crews — wins almost all of its revenue through RFQs issued by procurement departments at refineries, petrochemical plants, fabrication shops, power generation facilities, and EPCs, supplemented by a smaller but often more profitable stream of emergency call-outs and referrals from existing site relationships. There is no cold top-of-funnel visitor converting into an opportunity; the deal starts the moment a buyer who has already screened the company for capability and certifications sends a bid package. And the relationship rarely ends at "closed-won" — a plant that awards a turnaround inspection contract this spring starts a repeat cycle tied to outage schedules, API 510, API 570, and API 653 mandated reinspection intervals, and emergency callouts that can land on any week of the year.

Force this pattern into Salesforce or HubSpot out of the box and the mismatch shows up fast. "Leads" don't really exist because there's no inbound funnel generating them — every opportunity gets created manually the moment an RFQ arrives. Default stage names like "Qualification" or "Needs Analysis" don't correspond to anything an NDT company actually does before quoting, which is a scope review against a bid package, sometimes a mandatory site walk, and a hard check on whether crew and calibrated equipment are available in the window the client needs. Larger inspection companies rebuild this inside a generic CRM with custom objects and workflow automation, but it means paying for, and configuring around, a sales architecture that doesn't match the business.

Mapping the Pipeline NDT Companies Actually Run

A far more useful starting point is to define the pipeline stages the way inspection work really moves, then build (or buy) a system around that sequence instead of bending a generic template to fit:

• RFQ received — via an ISNetworld or Avetta-connected procurement portal, direct email from a known contact, or a phone call for an emergency callout.
• Scope review / site walk — for complex work (a confined-space vessel inspection, a piping circuit with unknown wall-loss history, a shutdown with overlapping trades), many clients require a pre-quote site visit before a firm number goes out.
• Quote submitted — priced against scope, method mix, crew-day estimates, and any client-specific rate schedule already on file.
• Client evaluation — the buyer is often comparing the quote against two or three other qualified vendors on price, certifications, capacity, and prior performance.
• Award / PO issued — referencing contract terms, often tied back to an existing MSA rather than negotiated fresh.
• Job scheduled and mobilized — technicians, equipment, and any subcontracted specialty methods assigned to dates that reconcile against every other commitment on the books.
• Job complete — field data collected, reviewed, and turned into a finished report.
• Invoiced — against the PO, the rate schedule, and any change orders for scope that grew once the vessel was opened.

Notice how little of that sequence resembles a generic CRM's default stages. There is no "discovery call" — the scope is usually already defined in the bid package. There is no "negotiation" stage in the SaaS sense — pricing is a straight comparison against competing quotes, sometimes with a follow-up round. And the stage most CRMs treat as an afterthought — scheduling and mobilization — is often where the real risk lives, because a won job with no available Level II technician or equipment overdue for calibration isn't actually a won job yet.

One Client Account, Three Contacts Who Rarely Talk to Each Other

A single industrial client account typically has at least three distinct contact types, each caring about a different thing, and each needing a different kind of follow-up:

• Procurement / purchasing — issues the PO, negotiates rate schedules and payment terms, cares primarily about price and contract compliance, and usually receives the RFQ and awards the job.
• Site / operations contacts — the maintenance planner or outage coordinator who needs the inspection performed, cares about scheduling around the turnaround window, site access, and crew headcount.
• QA / engineering contacts — the inspection engineer or quality manager who cares about technician certifications, written procedures, ASME Section V compliance, and whether the final report meets the client's documentation standard.

A generic CRM built for a single-buyer B2B sale — one champion, one economic buyer — tends to collapse this into a single "primary contact" field, which is exactly how companies lose track of who needs what. A quote can be fully approved by procurement on price and terms, but stall for two weeks because nobody sent the written procedure to the QA contact for review before mobilization. Or a job gets scheduled with the site contact, but the PO never gets cut because purchasing was never looped back in. Tracking three contact roles per account, and which one is waiting on a response, is the difference between a quote that dies quietly and one that converts.

RFQ Response Time Is a Scored Metric, Not a Courtesy

Operators and EPCs that maintain multiple qualified NDT vendors frequently shortlist, in part, on responsiveness — not just price. A maintenance planner scrambling to fill an unplanned outage window won't chase a vendor who takes three days to quote when a competitor answers in four hours. Some clients formalize this: internal vendor scorecards used by refineries and large EPCs often track quote turnaround alongside safety statistics and on-time performance, feeding into who gets invited to bid next time.

This is exactly the kind of metric a CRM should surface and rarely does out of the box: time-to-quote measured from RFQ receipt to submitted price, broken out by source (a portal, a repeat client's direct email, a referral, a cold RFQ from an unfamiliar EPC), and win rate calculated against each source. A company that discovers its portal-sourced RFQs run twice the response time of its repeat-client RFQs, with a matching gap in win rate, has found an actionable lever — resource the fast-turn quoting process better, or stop chasing a channel where speed alone won't win the work.

Approved Vendor List Status: The Gate Before the Gate

Before an RFQ ever gets sent, most industrial clients require a company to already be sitting on an approved vendor list. Getting onto that list typically means clearing a formal pre-qualification process — often run through a third-party platform such as ISNetworld or Avetta — covering safety statistics (TRIR, EMR), insurance minimums, and increasingly a documented quality system with evidence of ASNT SNT-TC-1A personnel qualification and, where relevant, familiarity with codes like API 510, API 570, and API 653.

AVL status is not permanent. It has to be renewed — annually in many cases, sometimes every two years — and that renewal is effectively a mini-audit: updated insurance certificates, a refreshed safety record, sometimes a repeat of quality system documentation. A company that lets requalification lapse doesn't get a rejection notice explaining why RFQs stopped arriving; it just quietly falls off the list, invisible until months later when someone asks why a longtime client hasn't sent an RFQ in two quarters. A CRM or ERP that treats AVL status as a tracked field with an expiration date and an automated reminder ahead of the deadline turns that silent risk into a scheduled task, the same discipline an ASNT Level III applies to a written practice review. Firms building that audit-readiness muscle sometimes bring in outside ASNT Level III consulting to get quality documentation in shape before a requalification cycle.

MSAs, Rate Schedules, and the COI That Can Bench a Crew Overnight

Repeat industrial clients almost always operate under a Master Service Agreement rather than negotiating fresh terms on every job. The MSA sets contract duration and renewal date, liability and indemnification terms, and — critically for margin — a negotiated rate schedule: day rates by method and technician level, per diem, and overtime multipliers. Losing track of which rate schedule applies to which client is a quiet way to underbill a job or quote a number that doesn't match what's on file.

The sharper risk sits with certificates of insurance. Almost every MSA specifies minimum coverage — general liability, umbrella coverage, auto liability, workers' compensation — and the COI on file has to stay current for the life of the contract. When a policy renews and the updated certificate doesn't get sent, or simply lapses between renewals, most industrial sites won't let a contractor's crew badge in; security or the contractor management platform checks insurance status at the gate, and an expired COI can turn away a fully staffed, fully certified crew that showed up ready to work — a failure that has nothing to do with technical capability and everything to do with a document nobody was tracking. A CRM or ERP that ties COI expiration dates to each account, with alerts well before the renewal deadline, closes that gap.

Win/Loss Tracking: Where BD Time Actually Pays Off

Most small NDT companies can say roughly how many RFQs they quoted last quarter. Far fewer can say, with precision, which categories of work they actually win versus quote-and-lose, and why. That distinction matters more in a services business than a product business, because BD hours chasing unwinnable RFQs are hours not spent nurturing the relationships and vendor qualifications that produce repeat business.

Structured win/loss tracking — logged against every closed opportunity, not reconstructed from memory months later — should capture why a quote was lost (price, schedule availability, missing certification or method capability, incumbent relationship, stronger AVL standing at a competitor), sliced by job type (turnaround versus new construction versus ongoing plant maintenance), by method, and by client. A company that finds it wins the large majority of RFQs from clients where it already holds an MSA, but only a small fraction of cold RFQs bid on price alone, has learned something concrete: BD effort is better spent deepening existing relationships than fighting price wars where an incumbent already has the edge.

The Gap Between "Job Won" and "Job Actually Staffed"

Marking an opportunity "closed-won" in a CRM and having a job that is actually staffed, equipped, and mobilized are two different facts, and the space between them is where many small NDT companies quietly drop the ball. A won job needs a technician with a current, applicable certification for the method and level — not just any available body — equipment inside its calibration interval and not already committed elsewhere, and a schedule slot that doesn't collide with a turnaround commitment three states away.

When the CRM and the system running field operations are two disconnected tools, that reconciliation happens manually — a spreadsheet, a whiteboard, a group text — and it works until it doesn't: a technician gets double-booked, or a job gets confirmed before anyone verified the required PAUT probe was back from a competing job site. The fix isn't more diligence, it's connecting the two systems so a won opportunity converts directly into a job record already carrying certification status and calibration data, inside a platform like Atlantis NDT ERP, instead of requiring someone to re-key the same information twice.

Spreadsheets, a Bent CRM, or an ERP That Already Knows Your Techs and Equipment

Most NDT companies pass through three stages of BD tooling:

• Email and spreadsheets. Nearly every company starts here, and it works fine at low volume with a single founder or BD person tracking everything as backup. It breaks down once two people touch the pipeline, once RFQ volume climbs past what one person can hold in memory, or the first time a COI lapses silently because no one was watching a spreadsheet column for a date that quietly passed.
• A generic CRM adapted to fit. Salesforce and HubSpot both offer serious pipeline management, reporting, and automation — and both require real customization to represent RFQ stages, AVL status, MSA terms, and COI expirations, none of which exist as native concepts in either platform. The higher tiers with the automation and custom-object features this use case needs carry real per-seat cost for a small BD team, and even after that investment the CRM still knows nothing about technician certifications, calibration status, or the field schedule — that data lives elsewhere, so someone re-enters the same client and job information twice.
• CRM functionality built into an operations ERP. The advantage isn't a longer feature list — it's that a won opportunity is the same record as the job that gets scheduled, staffed with certified technicians, and invoiced, with no export/import step and no risk of two systems drifting out of sync. That's the model behind Atlantis NDT ERP: RFQ tracking, AVL and MSA/COI monitoring, and win/loss reporting sit in the same system as technician certification tracking, equipment calibration schedules, and job dispatch, so the handoff from "we won the bid" to "the crew is on site" doesn't depend on updating a second tool. Completed jobs flow into NDT reporting software for the field data and final report, closing the loop from RFQ to invoice inside one platform.

None of these three approaches is wrong at every stage of a company's growth — a two-person shop chasing a dozen RFQs a month may genuinely be fine on a spreadsheet. But the transition point is predictable: once a company is juggling multiple client MSAs, tracking AVL requalification deadlines, and fielding RFQs from more than one BD staffer, the cost of a dropped COI renewal or a missed requalification deadline outweighs the cost of a system built to track it automatically.

The right tool for an NDT services business reflects how the business actually sells: RFQ-driven, relationship-heavy, and inseparable from the certifications, calibrations, and scheduling that determine whether a won bid ever becomes a completed, invoiced job.

Atlantis NDT Products & Services

Atlantis NDT pairs field expertise with software: NDT inspection management software — Atlantis ERP, a digital twin platform for asset integrity, and NDT reporting software. Build your team with NDT training & certification (ASNT SNT-TC-1A) and ASNT certification pathways, or bring in ASNT Level III consulting. Affordable, accessible, fully customizable — book a free consultation.