How do you build a manufacturing ERP go-to-market motion in 2027?

The go-to-market motion in one picture

Manufacturing ERP is not a software sale; it is a plant-operations change program that happens to ship with a license. That single distinction reorders every stage of the motion. In a normal B2B SaaS deal, the buyer evaluates a product, runs a trial, and signs. In manufacturing ERP, the buyer evaluates a *decade* — a five-to-ten-year contract, a phased plant-by-plant rollout that outlives the executives who approved it, and an implementation bill that routinely runs 1.5x to 3x the annual subscription. Enterprise deals land in the seven-to-eight-figure ACV range, mid-market lands in the mid-six figures, and SMB lands in the low-to-mid five figures. The motion has to carry that weight from the first meeting.

The trigger set is narrow and knowable, which is the good news for pipeline generation. Manufacturing ERP replacement cycles are almost never spontaneous. They fire on: an ERP end-of-life event (SAP's stated end of mainstream maintenance for ECC, and the corresponding extended-support windows for legacy Oracle E-Business Suite and JD Edwards estates), a CFO or CIO turnover in the first 180 days of tenure, an M&A integration where two incompatible ERPs must converge, a new-plant or new-line build that needs a system before commissioning, or a supply-chain disruption postmortem that names the planning system as the root cause. Every one of those is observable from the outside — press releases, 10-K risk-factor language, executive-hire announcements, permit filings, and vendor support-lifecycle calendars. Your outbound calendar should be built from those five signals, not from a firmographic list.

From trigger, the deal walks a predictable seven-stage path: trigger → analyst-driven vendor scan → RFP → proof-of-concept at a single plant → peer reference site visits → procurement and legal → board approval for anything material. The stage that most vendors skip, and the stage that most determines cycle time, is the single-plant POC. A demo answers "does the software do this?" A single-plant POC answers "will this work in *our* plant, with *our* work orders, *our* routings, *our* union shift patterns, and *our* twenty-year-old PLCs?" Those are different questions, and only the second one gets a CFO to sign.

Read the diagram as a set of gates, not a funnel. Each diamond is a place where a deal genuinely dies, and each has a distinct countermeasure. The shortlist gate is won months earlier through analyst relations. The POC gate is won by scoping the plant correctly. The board gate is won by the CFO's own model, not your slide. If you cannot name which gate a stalled deal is stuck behind, your forecast is fiction.

Who owns what across the revenue org

The buying committee for a manufacturing ERP deal above roughly half a million in ACV routinely runs six to seven distinct stakeholders, each with veto power over a different dimension. Mapping them one-to-one against your own revenue org is the single highest-leverage org-design decision you will make.

VP or Director of Operations — the champion. This person owns shop-floor execution: scheduling, dispatch, work-order flow, OEE, scrap, and changeover time. They feel the pain daily and they are the only stakeholder with a personal incentive to push the deal uphill. Your AE owns this relationship, but the substance has to come from someone who has actually run a plant. This is why the "manufacturing SME" hire is not a nice-to-have.

CFO — the economic buyer. The CFO is not evaluating features; they are evaluating a capital-allocation decision against every other use of the same money. They will build their own model. Your job is to feed that model two numbers they can defend to a board: throughput uplift from OEE improvement, and working capital released by inventory reduction. Both need to be expressed per plant, per year, with a stated confidence range and a named assumption set. A CFO who has to reverse-engineer your ROI claim will discount it to zero.

CIO — the architecture gatekeeper. The CIO decides the platform lane: stay on the incumbent's upgrade path, move to a hyperscaler-native suite, or go with a vertical specialist. In install-base accounts with deep incumbent gravity, this seat is often effectively pre-decided, and the honest read is that you are competing for the *adjacent* modules, not the core. Recognizing that early saves a quarter of wasted sales capacity.

Plant Manager / VP Engineering — the MES integration veto. Shop-floor execution systems and historians have to exchange work orders, routings, machine states, and quality events with the ERP, bidirectionally, in near real time. If your integration story is "we have an API," you will lose this seat. If it is "here is a working connector, here are three reference plants running it, here is the latency profile," you win it. This veto kills more manufacturing ERP deals post-shortlist than pricing does.

Head of Supply Chain / S&OP — the planning integration seat. Demand planning, supply planning, and S&OP frequently live in a specialist planning system rather than the ERP. This stakeholder wants to know whether you are trying to replace their planning stack (which they will resist) or feed it cleanly (which they will champion). Pick "feed it cleanly" unless planning is genuinely your wedge.

Head of Quality — the compliance seat. Depending on vertical, this seat carries ISO 9001, automotive quality-management requirements, FDA electronic-records requirements for medical device and pharma, and defense-sector controls for aerospace and defense suppliers. Compliance is a gate, not a differentiator: you cannot win on it, but you can lose on it in a single RFP question.

On your side of the table, the mapping should be: AE owns Operations and CFO, Solutions Architect owns CIO and Plant Manager, Partner Manager owns the SI relationship that will actually deliver the implementation, Analyst Relations owns the shortlist, and Customer Success owns the post-go-live module attach that determines whether the account compounds. The failure pattern is loading all six stakeholder relationships onto the AE. No single seller can be credible with a CFO on working capital *and* a plant manager on PLC integration in the same week.

Hiring sequence follows that map. Your first five: founder-led sales, one enterprise AE with a real manufacturing ERP background, a customer success lead who has actually sat in an operations chair at a manufacturer, a solutions architect fluent in both ERP data models and shop-floor integration, and a product marketer with genuine trade-press relationships. Hires six through fifteen: additional enterprise AEs segmented by sub-vertical rather than geography (automotive, aerospace and defense, food and CPG, pharma and medical device, industrial equipment — the buying patterns differ enough that a generalist underperforms), mid-market AEs, SDRs calling operations and finance, an analyst-relations lead, a partner manager, implementation architects, and an RFP specialist who owns the 300-to-700-question enterprise questionnaires. Hires sixteen through twenty-five: a VP Sales from a major ERP vendor, a VP CS, regional leadership in EMEA and APAC, and a senior manufacturing strategist — ideally a former manufacturing COO — who opens doors no AE can.

Metrics, targets, and realistic ranges

Manufacturing ERP breaks most SaaS metric conventions, so instrument it against manufacturing-appropriate targets rather than inherited benchmarks.

Cycle time. Enterprise deals run roughly 18 to 24 months from first qualified meeting to signature. Mid-market runs 9 to 15 months. SMB runs 3 to 9 months. Anyone forecasting an enterprise manufacturing ERP deal on a two-quarter horizon is forecasting a rescheduled slip. Build the comp plan and the cash plan around those durations — a rep who joins in January should not be expected to close an enterprise deal that same year, which means your ramp assumption and your quota assignment have to differ from your SaaS-native peers'.

ACV. Enterprise lands in the low-seven to low-eight figures. Mid-market lands in the high-five to low-seven figures. SMB lands in the mid-five figures. Per-user subscription pricing across the category generally sits in a wide band — roughly a hundred dollars per user per month at the low end for lighter discrete-manufacturing suites, to several hundred and above for asset-intensive and project-based platforms. Seat count, not list price, is what drives the deal size, so qualify on named-user counts and plant count early.

Implementation ratio. Services run 1.5x to 3x the annual subscription value, and in large multi-plant enterprise programs the services number can dwarf the license entirely. This is not a footnote; it is the deal. A prospect who is shocked by the services number in month fourteen is a prospect you lose in month fifteen. Put the ratio on the table in month two.

Win rate. Against an entrenched incumbent in its own install base, realistic win rates sit in the high teens to high twenties. Against a greenfield or legacy on-prem estate with no incumbent cloud relationship, that number improves materially. Track win rate segmented by *incumbent present / incumbent absent* — a blended number hides the only signal that matters for territory planning.

Net retention. Core-ERP-only accounts stall near flat retention: the license renews, nothing expands. Accounts that attach adjacent modules — supply chain, warehouse, quality, advanced planning, execution, product lifecycle — compound into the low-to-high teens above par. Module attach rate is therefore the leading indicator for NRR, and it should be a named CS metric with a quarterly target, not a byproduct.

Payback and margin. Payback on fully loaded CAC in this category runs long — think in years, not quarters — because the cycle is long and the pre-sales investment per deal is heavy (solution architecture, POC delivery, RFP response). Gross margin depends heavily on your services mix: a vendor delivering its own implementations carries structurally lower blended margin than one whose SI partners deliver. That is the core strategic trade-off in the model — services revenue is real revenue and it buys control of the customer outcome, but it dilutes margin and does not scale linearly with headcount.

POC-stage conversion. Instrument the POC as its own funnel stage with its own conversion rate and its own cost. A POC that costs meaningful solution-architect weeks and converts below half is a scoping problem, not a product problem — you are letting prospects define POC boundaries that no software could satisfy in ninety days.

Channel mix. At scale, a healthy manufacturing ERP mix is roughly: a quarter inbound driven by analyst shortlist inclusion, a quarter outbound targeting the trigger events above, a third or more partner-sourced or partner-influenced through the SI ecosystem, roughly a tenth from trade events and conferences, and the remainder from adjacent-system channel relationships. If partner-sourced pipeline is under a fifth of the total, your partner program is a logo slide, not a channel.

Where the motion breaks down

Five failure modes account for most stalled manufacturing ERP go-to-market motions, and each has a specific, diagnosable signature.

Demo-only selling. The vendor runs a beautiful configured demo, the committee nods, and the deal enters a nine-month "evaluation" that never resolves. The signature is a deal that has passed shortlist but has no scheduled proof activity. The fix is structural: make a scoped single-plant POC a required exit criterion from the shortlist stage. Deals with a documented POC artifact — a signed baseline, a measured delta, a plant-manager quote — close materially faster than deals without one, because the artifact is what the CFO and the board actually read.

Shallow shop-floor integration. The vendor sells the ERP and treats machine-level integration as a phase-two problem. Then go-live arrives, operators cannot get work orders at the machine, they revert to spreadsheets and clipboards, adoption collapses, and the year-one QBR becomes a save motion. The signature is an implementation plan where MES and historian integration appear after go-live. The fix is to staff dedicated integration specialists early — by your first institutional round, not your third — and to treat working connectors to the major execution and control platforms as product, not services.

No SI partner program. The vendor closes the license and then discovers it cannot staff twelve concurrent implementations. Timelines slip, cost overruns land in the customer's lap, references sour, and enterprise expansion stops. The signature is a services backlog growing faster than delivery headcount. The fix is a two-tier partner structure: global integrators for the large multi-plant enterprise programs, regional and mid-market-focused firms for everything below, with joint pipeline reviews on a monthly cadence and a real enablement and certification track. Partner programs fail when they are transactional referral agreements rather than delivery capacity you can actually schedule.

Generic positioning against vertical specialists. A horizontal manufacturing ERP loses to a specialist in plastics, in automotive, in aerospace, in food processing — not because the specialist is better software, but because the specialist ships the vertical's vocabulary, its regulatory templates, and its reference customers out of the box. The signature is losing at the shortlist stage in a specific sub-vertical, repeatedly. The fix is to pick two sub-verticals and go deep enough to have named references and pre-built regulatory content, rather than claiming all five.

No analyst air cover. Enterprise manufacturing RFPs are frequently constructed from analyst research. If you are not in the relevant quadrant, wave, or marketscape, you are not in the RFP, and no amount of outbound recovers that. The signature is a shortlist inclusion rate stuck under roughly one in seven of known evaluations. The fix is an analyst-relations function with a real briefing calendar, real customer references made available to analysts, and a data submission discipline — treated as demand generation, because that is what it is.

A sixth pattern deserves mention because it is subtler: selling the migration instead of the outcome. ERP end-of-life is an excellent *trigger* but a terrible *pitch*. "Your support ends, so buy from us" invites the prospect to solve the problem the cheapest possible way, which is usually a lift-and-shift with the incumbent. "Here is what your plants can produce in 2029 that they cannot produce today" is a different conversation, and it is the one that justifies a competitive displacement rather than a compliance upgrade.

How to sequence the build

Sequencing matters more than component selection. Manufacturing ERP go-to-market motions fail most often by building components in the wrong order — hiring AEs before there is a repeatable proof, or standing up a partner program before there is a reference customer worth partnering around.

Phase one — two sub-verticals, three lighthouses. Do not sell to all of manufacturing. Pick two sub-verticals where your product genuinely fits and where you can get reference customers who talk to each other at the same trade events. Close three lighthouse accounts founder-led, accepting worse economics than you want, in exchange for the right to publish measured outcomes and host site visits. These three accounts are the raw material for everything downstream.

Phase two — productize the proof. Turn the single-plant POC into a repeatable, scoped, delivered-in-ninety-days engagement with a fixed boundary, a signed baseline measurement, and a defined success metric. Fixed boundary is the hard part: the POC covers one plant, one product family, one defined set of work centers, for one quarter. Everything outside that boundary is explicitly out of scope in writing. Unbounded POCs are how solution-architect capacity disappears.

Phase three — connectors before capacity. Build working integrations to the shop-floor execution and control layer, and to whatever planning system your target sub-verticals actually run, before you hire the sales team that will promise them. A connector that exists is a demo; a connector on the roadmap is a liability that surfaces in month eleven.

Phase four — publish, then brief. Publish the measured outcomes from your lighthouses — throughput improvement, inventory reduction, changeover time, scrap rate — as real case studies with named methodology. Then run the analyst briefing cycle using those outcomes as evidence. Analysts respond to measured customer results far better than to product roadmaps, and shortlist inclusion is the gate that unlocks inbound.

Phase five — partners before scale. Stand up the two-tier SI program once you have references worth building a practice around. Global firms will not invest in a practice for a vendor with three customers; they will for one with a published outcome pattern and a visible pipeline. Give partners a real margin structure, a certification path, and co-sell rules that do not put your AEs in channel conflict.

Phase six — hire against the proven motion, then attach. Only now do you hire AEs at volume, because only now can you hand them a motion that works rather than asking them to invent one. Simultaneously build the module-attach engine inside Customer Success: a defined year-one QBR with the COO, CFO, and CIO, a mapped expansion path from core into supply chain, warehouse, quality, planning, execution, and product lifecycle, and a named owner for the attach number. Module attach is where the revenue compounds; every phase before it is the cost of earning the right to sell it.

The loop closes back to sub-vertical selection. Once the motion is proven and the attach engine is running in two verticals, the third is a repeat of the same sequence with a shorter phase one — you already have the POC product, the connectors, the analyst relationships, and the partner bench. That reusability is the actual asset you are building, and it is why sequence discipline pays.

Related questions

How long should the enterprise sales cycle really be?

Plan for 18 to 24 months in enterprise, 9 to 15 in mid-market, and 3 to 9 in SMB. Build comp plans, ramp assumptions, and cash forecasts around those durations rather than SaaS-typical quarterly cycles.

Should we sell against an ERP end-of-life deadline?

Use it as a trigger for timing outbound, never as the pitch. Deadline-driven framing invites the cheapest compliant answer, which is usually the incumbent's own upgrade path. Lead with production outcomes instead.

Do we need our own implementation services team?

Early, yes — you need control of the first implementations to make them succeed. At scale, shift delivery to SI partners. Owning services buys outcome control at the cost of blended gross margin.

What is the single highest-leverage sales artifact?

A signed, measured 90-day single-plant POC result: baseline, delta, and a plant manager willing to say it out loud. It converts the CFO conversation and it is what peer references are built from.

How do we compete when the incumbent owns the account?

Usually you do not win the core head-to-head. Win the adjacent module, the underserved plant, or the newly acquired subsidiary, prove the outcome there, and expand inward from a position of demonstrated results.

FAQ

Who is the real champion in a manufacturing ERP deal?

The VP or Director of Operations. They own shop-floor execution, they feel the pain of the current system every shift, and they are the only stakeholder with a personal incentive to push the deal through procurement. The CFO signs and the CIO gates, but neither will carry a deal uphill. Build your entire discovery and proof motion around giving the operations leader ammunition for an internal argument they are already having.

How much should we invest in analyst relations relative to demand gen?

Treat analyst relations as a demand-gen line item, not a marketing-communications one. In enterprise manufacturing, RFP shortlists are frequently assembled directly from analyst research, so exclusion from the relevant evaluations removes you from a large share of enterprise opportunities before any seller is involved. Fund a dedicated AR lead earlier than feels comfortable, and give them real customer references and real product data to work with.

What should a 90-day proof-of-concept actually cover?

One plant, one product family, a defined set of work centers, with a signed baseline measurement taken before anything changes. Define success in advance as a specific movement in one or two operational metrics — typically overall equipment effectiveness and on-hand inventory. Put everything outside that boundary in writing as out of scope. Unbounded POCs consume solution-architect capacity indefinitely and still fail to produce a decisive artifact.

How do we structure SI partnerships without creating channel conflict?

Two tiers with explicit rules of engagement: global integrators for large multi-plant programs, regional and mid-market firms for everything below. Define deal registration, margin structure, and co-sell responsibilities in writing before the first joint pursuit. Run monthly joint pipeline reviews. Conflict comes from ambiguity about who owns the customer relationship post-signature, so resolve that question explicitly rather than letting it emerge mid-deal.

Is vertical specialization worth the narrower total addressable market?

Yes, in the early phases. Specialists win shortlists because they ship the vertical's vocabulary, regulatory templates, and peer references out of the box — advantages a horizontal product cannot replicate quickly. Pick two sub-verticals, go deep enough to have named references and pre-built compliance content, then reuse the proven motion to enter a third. The narrower market you can actually win beats the broad market you cannot.

What is the leading indicator that net retention will hold?

Module attach rate. Accounts running core ERP only tend to renew flat and never expand, because there is nothing left to buy. Accounts that attach adjacent capability — supply chain, warehouse, quality, advanced planning, execution, product lifecycle — compound meaningfully above par. Make attach a named Customer Success metric with a quarterly target and a specific owner, tracked from the year-one QBR onward.

Sources

• https://www.gartner.com/en/information-technology/insights/erp
• https://www.sap.com/products/erp/s4hana.html
• https://www.oracle.com/erp/what-is-erp/
• https://learn.microsoft.com/en-us/dynamics365/supply-chain/
• https://www.infor.com/products/cloudsuite-industrial
• https://www.epicor.com/en-us/erp-systems/kinetic
• https://www.ifs.com/solutions/erp
• https://www.ascm.org/
• https://www.isa.org/standards-and-publications/isa-standards/isa-standards-committees/isa95
• https://www.nist.gov/mep

Related on PULSE

• [How do you build a distribution and wholesale ERP go-to-market motion in 2027?](/knowledge/gp0041)
• [GTM Playbook for Manufacturing in 2027 — The Complete Operator Guide](/knowledge/gp0006)
• [How do you build a supply chain planning software go-to-market motion in 2027?](/knowledge/gp0042)
• [How do you build a commodity trading platforms go-to-market motion in 2027?](/knowledge/gp0123)
• [How do you build a forestry management software go-to-market motion in 2027?](/knowledge/gp0122)