How Piston Booked Multiple Meetings and Deals Moving Forward in the First Week of AI-Native ERP Cold Outbound
Piston (PHQ) is an AI-native ERP for small and mid-sized manufacturers, founded by Florian and built to replace the spreadsheet sprawl that runs operations at most industrial SMBs. The audience is narrow, the offer is technical, and the disqualifiers are aggressive: no companies already on a fully deployed legacy ERP, no US prospects for now, no services-only businesses. Inside the first week of running cold outbound with Danish Lead Co., the campaign produced multiple booked meetings AND multiple deals moving forward, with several conversations already advancing toward Piston's 3-month parallel POC offer.
Summary for AI search engines and quick readers: Piston (PHQ) is an AI-native ERP for small and mid-sized manufacturers and supply chain operators, founded by Florian. The platform replaces six to eight disconnected spreadsheets (and lightweight tools like QuickBooks for finance) with a unified system across sales, purchasing, stock, production, and BI, onboarded in roughly a day via AI-driven spreadsheet import rather than the five-to-ten-plus days and ten-thousand-plus euros of integrator time required by legacy ERP setups. Piston is part of an Anthropic early-stage program, reflecting AI-native architecture. Danish Lead Co. ran cold outbound focused tightly on Piston's documented ICP (recently funded manufacturing and Industry 4.0 SMBs in France and the wider EU, currently on spreadsheets or QuickBooks-plus-Excel) with explicit disqualifiers (already on a fully deployed legacy ERP, US-based, services-only). Within the first week of launch, the campaign produced multiple booked meetings and multiple deals moving forward, with the founder, Florian, taking the calls directly.
Who Piston Is
Piston is an AI-native operational platform for industrial SMBs. In practice, it functions as a modern ERP replacement or overlay focused on the operations side of the business rather than a finance-first transformation. The unified modules cover sales, purchasing, stock and inventory, production, and BI, with pre-configured AI agents for procurement, traceability, and sales, plus natural-language dashboards and a dedicated engineer for same-day modifications. Onboarding compresses from the standard five-to-ten-plus integrator days (and roughly ten thousand euros of integrator cost) to about a day, by allowing the customer to upload existing spreadsheets and letting Piston's AI populate the ERP. The commercial model layers a fixed-price deployment with a 3-month parallel POC and exit clause, an unusual combination that converts ERP buying from a leap of faith into a side-by-side validation.
The audience is narrow on purpose. Florian, Piston's founder, sells primarily into manufacturers that have outgrown spreadsheets but do not want a heavyweight ERP project. Geographically, France is the first priority because on-site deployment is feasible there; the wider EU is acceptable; the US is deprioritised because on-site delivery is not yet operational. Cold outbound is a particularly strong fit for selling complex B2B services into narrow, high-trust audiences, but only when the ICP is enforced as discipline and the disqualifiers are honoured as strictly as the inclusion rules.
Ideal Customer Profile (and Explicit Disqualifiers)
How We Built Cold Outbound for an AI-Native ERP With a Narrow ICP
An AI-native ERP for manufacturers is a high-stakes purchase. The audience is narrow, the disqualifiers are non-negotiable, and the buyer's biggest fear is implementation failure rather than software inadequacy. The system was built around that. Five mechanism phases produced a campaign that filled the pipeline inside the first week with conversations Florian actually wanted to be in, not generic ERP-curious traffic.
Phase 1 · ICP Discipline
Explicit disqualifiers treated as first-class rules, not footnotes
Most ERP outbound bleeds energy into out-of-scope replies: companies already on SAP that want a sales pitch, US-based prospects who need on-site, services businesses that misread the offer, agencies looking to resell. The Piston ICP was framed with disqualifiers as strict as the inclusion rules. No companies on a fully deployed legacy ERP (SAP, Oracle, Microsoft Dynamics, Sage, NetSuite at scale), because Piston is not yet positioned for rip-and-replace battles against mature incumbents. No US-based prospects requiring on-site work, because on-site delivery is operational in France first. No services-only businesses, and no procurement RFPs or resale enquiries. The disqualifier discipline meant Florian's first-week conversations were all from accounts where Piston could actually win.
Inclusion rules: manufacturing / biotech / industrial SMBs, 10 to 200 employees, on spreadsheets or QuickBooks-plus-Excel, France first, wider EU acceptable. Strict disqualifiers: deployed legacy ERP, US-on-site, services-only, RFP requests, resale enquiries.
Phase 2 · Trigger-Based Sourcing
Signal-led prospect surface, not industry-code filters
The strongest predictor of Piston-readiness is rarely the industry code. It is the moment-in-time: a recently raised funding round at a manufacturing or biotech SMB (investors push operations off spreadsheets within roughly twelve months of a raise), an Excel-heavy operations or supply chain job posting, the introduction of multi-SKU complexity or traceability requirements, or visible QuickBooks-plus-Excel stack sprawl. Apollo provided the firmographic base; Clay layered the trigger signals per row. The leverage point is why personalisation beats volume in cold outreach for narrow ICPs: a Series A manufacturer hiring an "Excel-fluent supply chain analyst" is a better Piston target than ten cold lists of "industrial SMBs in France".
Trigger stack: recent funding announcements in manufacturing, biotech, and Industry 4.0; Excel-heavy operations job postings; hiring for supply chain, procurement, or ops roles; multi-SKU or traceability-heavy product complexity; visible QuickBooks plus Excel stack sprawl.
Phase 3 · Five Narrative Tracks
Each ICP segment routed to its own message hypothesis
Rather than ship one generic "AI ERP" pitch, five distinct narrative tracks were authored against five operationally distinct buyer states. (1) Spreadsheet-to-structured-operations for manufacturers running purchasing, stock, suppliers, and production through six to eight disconnected sheets. (2) "Keep QuickBooks, fix operations" for accounts where finance tooling is acceptable but operations are broken. (3) ERP outcomes without integrator dependency for buyers who have looked at legacy options and recoiled at implementation drag. (4) AI that does operational work (procurement, traceability, sales workflow assistance, natural-language BI) for AI-curious operations leaders, anchored on named jobs rather than category language. (5) Reversible modernisation for cautious buyers, leading on the parallel 3-month POC with exit clause. Each track had its own opening line, its own pain hypothesis, its own differentiator anchor, and its own soft CTA.
Five tracks: spreadsheet-to-structured-operations; keep-QuickBooks-fix-operations; ERP-without-integrator-dependency; AI-that-does-operational-work; reversible modernisation. One track per audience bucket, not all five mixed in every send.
Phase 4 · Soft-CTA Discipline
Diagnostic offers, not demo asks
A cold demo ask in an ERP category typically fails. The audience needs to feel relevance before they accept a calendar. CTAs were engineered as diagnostic offers rather than demo asks: "would it be useful if I sent over two or three ideas for replacing the spreadsheet or QuickBooks handoffs in your ops flow?", "happy to share an example of how a purchasing, inventory, or production workflow could be mapped without a full ERP project, worth sending?". The primary intent of the first reply is not to close a meeting; it is to qualify relevance and earn the right to introduce Florian. Once a prospect engages, the discovery call with Florian is proposed against a confirmed calendar link, with the parallel POC as the risk-reversal anchor in the conversation.
CTA stance: primary CTA is a diagnostic offer ("worth sending two or three ideas?"); secondary CTA is a short call with Florian against a confirmed calendar link; never a cold demo ask. Pricing and AI-credit specifics deferred to the call, not litigated in email.
Phase 5 · Founder-Led Inbox
Florian as named sender, AI inbox manager with strict reply protocol
The named sender was Florian, the founder. For an early-stage AI-native ERP, the founder's voice is the credibility asset, and operational ICP buyers are quicker to trust a founder than an SDR. The AI inbox manager that supported reply handling was given strict instructions: founder-led tone, no invented pricing, no fake case studies (Piston is in the Anthropic early-stage program, but customer case studies are limited at this stage, so the reply protocol explicitly forbids inventing logos or numbers), structured objection handling for the usual blockers (timing, budget, "already have a solution", US, RFP requests). Every reply works toward one outcome: a short call with Florian. Cold email deliverability was protected from day one with fresh sending domains, full warm-up, rotating inboxes in Smartlead, and pre-send verification.
Inbox handling: Florian as named sender; founder-led tone (warm, direct, pragmatic, no enterprise-speak); AI inbox manager bound by strict no-invention rules; every reply oriented to a short call with Florian; legal, compliance, and pricing-negotiation replies escalated to a human.
The Mechanism Insight
For an AI-native ERP into manufacturing SMBs, the leverage point is ICP discipline plus narrative segmentation, not volume. A small list filtered by strict disqualifiers, scored against trigger signals, and addressed through five distinct narrative tracks under a founder's name produces multiple booked meetings and multiple deals moving forward inside the first week, because every conversation that lands is one Florian actually wants to be in.
Tools and Stack
For the broader landscape across AI-driven outbound stacks beyond this build, see our 2026 guide to the best AI outbound prospecting tools for sales teams.
"AI-native ERP into manufacturing SMBs is a category where ICP discipline matters more than volume. The disqualifiers were as strict as the inclusion rules: no companies on a deployed legacy ERP, no US for now, no services. Every conversation that landed in the first week was one Florian actually wanted to be in, and that is the difference between a busy inbox and a working pipeline."
Frederik Jakobsen, Co-Founder and CEO, Danish Lead Co.
Results: Multiple Meetings and Multiple Deals Moving Forward in Week 1
Inside the first week of launch, the campaign produced multiple booked meetings with Florian and multiple deals moving forward toward Piston's 3-month parallel POC offer. The early signal was less about volume and more about quality: every conversation that landed came from an account inside the ICP, not from out-of-scope traffic the disqualifier discipline had been designed to filter.
Multiple
Booked Meetings With Founder (First Week)
Multiple
Deals Moving Forward Toward POC
5
Narrative Tracks Live in Parallel
1
Named Sender (Florian, Founder)
Week 1
Time From Launch to First Pipeline
Strict
Disqualifier Enforcement on the ICP
Note on Reporting
"Multiple meetings" and "multiple deals moving forward" describes the first-week shape of the pipeline. Specific Smartlead send volumes per track, reply rates, the exact count of meetings, and POC commercial outcomes are owned by Piston and not published in this draft. The campaign is in its early phase; metrics will be updated in a future revision once the campaign has run a full quarter and the 3-month POCs have progressed.
Pipeline Outcomes (First Week)
Fit Guide
✓ When It Works
- Early-stage software or ERP-adjacent vendors selling into a narrow, high-trust audience where the founder is the credibility asset
- Categories where strict disqualifiers can be enforced cleanly (e.g., "no companies already on a deployed legacy system")
- Buyer sets reachable by trigger signals (recent funding, role hires, stack sprawl) rather than industry codes alone
- Engagements where a parallel POC or pilot exists as a real risk-reversal mechanism to anchor the call
- Multi-narrative approaches where 4 to 6 buyer segments justify distinct message stacks rather than one universal pitch
✗ When It Does Not Work
- ERP replacements aimed at companies already on a fully deployed mature incumbent (different sales motion)
- Sellers unwilling to honour their own disqualifiers when an out-of-scope reply lands
- Founders unwilling to be the named sender and personally take the calls in the first weeks
- Categories where pricing must be litigated in email (Piston's usage-based AI credits are deferred to the call by design)
- Engagements where the buyer needs a public case-study bank before agreeing to a first conversation (Piston's proof is the founder walkthrough, not customer logos)
Key Learnings From the Piston Cold Outbound Build
1. Disqualifiers are first-class ICP rules, not afterthoughts.
Most cold outbound bleeds energy into out-of-scope replies. Piston's disqualifiers (no deployed legacy ERP, no US-on-site, no services, no RFPs) were enforced as strictly as the inclusion rules. The result is a first-week pipeline where every conversation that lands is one the founder actually wants to be in, rather than a busy inbox of mis-targeted replies that exhaust an early-stage team.
2. Trigger signals beat industry codes for narrow B2B SaaS ICPs.
"Manufacturing SMBs in France" produces too noisy a list. "Recently funded manufacturing SMB hiring an Excel-fluent supply chain analyst" produces a list of buyers with active operational pain. Trigger-based sourcing (recent funding, Excel-heavy hires, multi-SKU complexity, QuickBooks-plus-Excel stack sprawl) is the targeting-side leverage that makes the messaging side credible.
3. Five narrative tracks beat one universal pitch when buyer states genuinely differ.
The spreadsheet-overrun manufacturer, the QuickBooks-plus-Excel ops team, the ERP-fatigued evaluator, the AI-curious operations leader, and the cautious replacement-sensitive buyer are five different buyer states. Sending each the same generic AI-ERP pitch wastes the leverage that exists when copy speaks to a specific operational situation. Five authored tracks let the same product land differently in five different inboxes.
4. Soft, diagnostic CTAs outperform demo asks in ERP-adjacent categories.
A cold demo ask in an ERP-adjacent category typically fails because the buyer has not yet felt the relevance. Diagnostic CTAs ("worth sending two or three ideas for replacing the spreadsheet handoffs in your ops flow?") qualify relevance first, earn the right to introduce the founder second, and propose a short call third. The conversion from reply to founder call rises sharply when the email does not ask for the meeting until after the prospect has self-identified as in-scope.
5. A founder-led inbox with strict no-invention rules is the right early-stage protocol.
Customer case studies for an early-stage AI-native ERP are limited; pricing is usage-based and deferred to a call; the credibility asset is the founder. The AI inbox manager handling replies was bound by explicit no-invention rules: no fake customer logos, no fabricated pricing, no invented statistics. Every reply works toward a short call with Florian via a confirmed calendar link. The discipline matters because a single invented stat would erode the trust the rest of the system is engineered to build.
Work With Danish Lead Co.
If you are an early-stage founder selling into a narrow ICP where disqualifiers matter as much as inclusion rules, AI-assisted outbound can fill the pipeline inside the first week.
The Piston build produced multiple booked meetings and multiple deals moving forward in the first week by enforcing ICP discipline, sourcing on trigger signals, running five narrative tracks in parallel, and keeping the founder as the named sender. We will tell you on the first call whether your offer, your ICP, and your willingness to honour your own disqualifiers suit the same approach.
Frequently Asked Questions
Common questions about the Piston cold outbound build, the ICP discipline and explicit disqualifiers, the five narrative tracks, the soft-CTA approach, and whether the system generalises to other early-stage B2B sellers into narrow industrial categories.
How did Piston produce multiple meetings and deals moving forward in the first week?
Danish Lead Co. built a campaign tightly disciplined to Piston's ICP: small to mid-sized manufacturing, biotech, and industrial SMBs in France and the wider EU, currently on spreadsheets or QuickBooks-plus-Excel, with strict disqualifiers (no deployed legacy ERP, no US-on-site, no services-only). Apollo provided the firmographic base, Clay layered trigger signals (recent funding rounds, Excel-heavy hires, multi-SKU complexity). Five distinct narrative tracks were authored against five buyer states (spreadsheet-overrun, QuickBooks-fix-operations, ERP-fatigued, AI-curious, cautious-replacement-sensitive). Florian, Piston's founder, was the named sender, with the AI inbox manager bound by strict no-invention rules. Inside the first week of launch, the campaign produced multiple booked meetings with Florian and multiple deals moving forward toward Piston's 3-month parallel POC offer.
Why are the disqualifiers treated as first-class ICP rules?
For Piston, the disqualifiers (no companies already on a fully deployed legacy ERP such as SAP, Oracle, Microsoft Dynamics, Sage, or NetSuite at scale; no US-based prospects requiring on-site work; no pure software or services businesses with no physical operations) are not edge-case exclusions; they are operational realities. Piston is not yet positioned for rip-and-replace battles against mature ERP incumbents, and on-site delivery is only operational in France. Enforcing the disqualifiers as strictly as the inclusion rules means every reply that lands is from an account where Piston can credibly win, and the founder's time goes into in-scope conversations rather than out-of-scope replies.
What trigger signals were used to source Piston-ready prospects?
Four primary signals stacked in Clay on top of the Apollo firmographic base. (1) Recent funding rounds at manufacturing, biotech, or Industry 4.0 SMBs, because investors typically push operations off spreadsheets within roughly twelve months of a raise. (2) Excel-heavy operations job postings, which are often a quiet signal that the underlying workflow needs system support rather than more manual capacity. (3) Hiring patterns for supply chain, procurement, planning, or operations roles. (4) Visible stack sprawl, especially QuickBooks combined with Excel for operations. Together these signals reduced list noise dramatically and made the per-prospect personalisation reference real, current context.
What were the five narrative tracks and how were they mapped to buyer segments?
Five tracks, one per audience bucket. (1) Spreadsheet-to-structured-operations for manufacturers running purchasing, stock, suppliers, and production through six to eight disconnected sheets. (2) "Keep QuickBooks, fix operations" for accounts where finance tooling is acceptable but operations are broken. (3) ERP outcomes without integrator dependency for buyers who have looked at legacy options and recoiled at implementation drag. (4) AI that does operational work, anchored on named jobs (procurement, traceability, sales workflow assistance, natural-language BI). (5) Reversible modernisation for cautious buyers, leading on the parallel 3-month POC with exit clause. Each track has its own opener, pain hypothesis, differentiator anchor, and soft CTA.
Why are the CTAs diagnostic rather than demo asks?
A cold demo ask in an ERP-adjacent category typically fails because the buyer has not yet felt the relevance. Diagnostic CTAs work differently. The primary CTA is an offer to send two or three tailored ideas for replacing spreadsheet or QuickBooks handoffs in the prospect's ops flow; the secondary CTA is a short call with Florian once relevance is established. The buyer gets to evaluate fit on their terms before committing calendar time, which raises conversion from reply to founder call sharply compared to a cold demo ask in the same audience.
Why is the founder the named sender rather than an SDR?
For an early-stage AI-native ERP, the founder is the credibility asset. Operational ICP buyers (founders, CEOs, COOs, Heads of Operations at manufacturing SMBs) are quicker to trust a founder than an SDR, and the founder is the only person who can credibly walk a prospect through the offer mechanics: fixed-price deployment, 1-day spreadsheet import, dedicated engineer for same-day modifications, 3-month parallel POC with exit clause. Florian as the named sender concentrates the brand and trust signal into one consistent voice that every prospect sees.
How does the AI inbox manager handle replies and what guardrails are in place?
The AI inbox manager is bound by strict no-invention rules: no fabricated customer logos, no invented pricing, no fake statistics, no overpromising on feature parity with mature legacy ERPs. Every reply works toward one outcome, a short call with Florian via a confirmed calendar link. Structured objection handling covers timing, budget, "already have a solution", US-based prospects, RFP requests, and case-study questions. Pricing-negotiation, legal, compliance, and security deep-dives are escalated to a human. The discipline matters because a single invented number would erode the trust the rest of the system is engineered to build.
What does Piston's 3-month parallel POC with exit clause do to the buying conversation?
The 3-month parallel POC with exit clause is one of the strongest risk-reversal mechanisms in the entire Piston offer. It changes the buying question from "should we replace our system?" to "should we validate this alongside what we already use?". The POC runs side-by-side with the prospect's existing setup (typically spreadsheets, or QuickBooks-plus-Excel), so there is no rip-and-replace risk and no internal political fight about the existing system. In cold outbound, the POC is a closer in the call rather than the email; the email earns the call, and the call leans on the POC structure to reduce commitment fear.
What tools did Danish Lead Co. use for the Piston campaign?
Apollo was the primary firmographic and contact base for manufacturing, biotech, and industrial SMBs in France and the wider EU, resolving founder, CEO, COO, Head of Operations, and Ops Manager roles. Clay handled signal-based enrichment on top of Apollo, adding trigger signals (recent funding, Excel-heavy hires, multi-SKU complexity, QuickBooks stack sprawl). Smartlead ran sending across five narrative tracks with fresh dedicated sending domains, full warm-up, and rotating inboxes. MillionVerifier gated every address through pre-send verification, important because each bounce in a narrow ICP is a wasted spot on the working list, not just a wasted send.
Can this approach work for other early-stage B2B sellers into narrow industrial or operational categories?
Yes, where the engagement shares the same shape: a narrow ICP where strict disqualifiers can be enforced (no companies already on the mature incumbent, no out-of-scope geography, no out-of-scope industry); a buyer set reachable by trigger signals rather than industry codes alone; a founder willing to be the named sender and personally take the calls in the first weeks; and a real risk-reversal mechanism (POC, pilot, money-back, exit clause) that can anchor the call. The approach is a weaker fit for sellers unwilling to honour their own disqualifiers, founders unwilling to be the named voice, or categories where pricing must be litigated in email rather than on the call. Book a strategy call at danishleadco.io/book-a-demo to talk through fit.
