Architecture of Sales · 2026-06-04 · 5 min
Key moments - from our scoring
Substance score
15 / 100
Five dimensions, 20 points each
Dominik van Tuch of Architecture of Sales explains why assigning engineering staff to prospect for technical B2B sales is inefficient and how to structure a sustainable alternative. The core problem: product engineers excel at explaining technology but lack sales skills like prospecting, qualification, and discovery - sending them to cold outreach wastes their expertise and burns them out. Van Tuch advocates for a sales tandem model pairing native Polish-speaking SDRs (who handle initial outreach, qualification, and discovery) with technical experts (who join once real opportunity exists). This structure protects engineer bandwidth, increases deal velocity, and improves prospect perception - prospects understand technical experts' time is scarce and valuable. Implementation requires structured SDR onboarding covering product documentation, ICP, buyer personas, pain points, and USPs, so SDRs can identify fit without explaining architecture. Two working models emerge: SDR plus presales engineer (presales owns technical discovery), or SDR plus sales executive (executive leads full conversation while technical staff answers hard questions). Critical for companies selling complex software or hardware into Poland's market who currently rely on engineer-led prospecting.
Engineers excel at explaining products but lack training in prospecting, qualification, and closing. When sent to cold outreach, they disappear into unqualified calls, waste their high-value time, and lose sharpness on deals that actually matter - like using a Formula One engine to deliver pizzas.
Build a tandem: a native Polish-speaking SDR handles initial outreach, qualification, and discovery to identify real opportunities; a technical expert (presales engineer or sales executive) enters only after prospects are qualified and have sufficient data, then runs demos and technical discussions.
Option one pairs an SDR with a presales engineer who takes over after first meetings and owns the technical process. Option two pairs an SDR with a sales executive who runs the full conversation, highlighting value and pain points, while a technical person defends architecture and answers hard questions.
SDRs don't need to explain technology - they need to identify customer problems, confirm fit to ICP, and schedule next steps. This requires structured onboarding covering product documentation, ICP, buyer personas, pain points, and value proposition, which is learnable and doesn't require technical background.
When prospects see a technical expert only appears for important conversations - not every call - it immediately signals that person's time is valuable and the opportunity matters, raising perceived value of the conversation itself.
Our reviewer’s read on each dimension, with quotes from the episode.
The core idea - don't use engineers as cold-callers, use an SDR to qualify then bring in the technical expert - is restated repeatedly across 5 minutes with very little net-new information added. The advice is basic sales-ops 101 padded with analogies and no depth beyond the surface claim.
When you send your presale engineer to do code outreach and prospecting, you are using a formula one engine to deliver pizzas.
The SDR doesn't need to explain the technology. They need to identify the problem, confirm the fit and schedule the right next steps. That's all.
The SDR-plus-solutions-engineer tandem is a decades-old, textbook enterprise B2B sales motion with zero contrarian or first-principles framing. The Poland-specific angle is the only differentiator, but even that is not developed into any original insight.
Native Polish speaking SDR who opens the conversations, qualifies the prospects and run the discovery. And a technical expert who can be English speaking who enters the process once there's real opportunity
Option number one SDR plus pre sales Engineer SDR prospects and qualify pre sales, takes over after the first meetings
There is no guest - this is a solo promotional monologue by the host, a founder of a lead-gen agency. No scale of operations, client outcomes, or practitioner depth is demonstrated anywhere in the transcript; the episode functions as a service pitch.
I am Dominik van Tuch, founder of Architecture of Sales, a lead generation and sales outsourcing agency that helps companies enter the Polish market with native Polish speaking SDRs.
If you want to know how this looks for your specific product and team structure, book a call with me.
There are zero named clients, zero metrics, no pipeline numbers, no conversion rates, no timelines, and no case studies anywhere in the episode. Every claim is purely abstract and hypothetical.
Engineers who spend their days on unqualified calls stop being sharp on the ones that matter.
That positioning alone raises the perceived value of the conversation.
This is a scripted solo monologue with no interviewer, no questions, no follow-ups, and no pushback possible. There is no conversation to evaluate; the format is a short promotional video pitch from start to finish.
By the end of this video, you will know how to build a sales tandem that closes more deals without burning out your engineers
Most companies answer the questions the wrong way.
Computed from the transcript - who did the talking, and the words that came up most.
Your best salesperson is often your product engineer. And that's exactly the problem. In this episode, Dominik Wantuch - founder of Architecture of Sales - breaks down one of the most common mistakes technical companies make when entering a new market: sending their engineers to do cold outreach and prospecting. Engineers are brilliant at explaining products. They are not trained to prospect, qualify leads, or navigate a sales process. When you put them on cold calls, you are using a Formula One engine to deliver pizzas. It works - but at enormous cost in wasted time and burned-out talent. The solution Dominik outlines is the sales tandem: A native Polish-speaking SDR who opens conversations, qualifies prospects, and runs discovery A technical expert - who can be English-speaking - who enters the process once there is a real opportunity and enough data to run a meaningful demo This model protects your engineers from dead-end calls, raises the perceived value of every technical conversation, and builds a qualified pipeline your team can actually close.
Transcribed and scored by The B2B Podcast Index.
Speaker A: Your best salesperson is your product engineer. And that's exactly the problem. They know everything about the product and nothing about how to prospect, qualify, open or close a deal. By the end of this video, you will know how to build a sales tandem that closes more deals without burning out your engineers or wasting their time on calls that go nowhere. This video is for companies that sell technical products, software or hardware where engineering knowledge is required to close deals. I am Dominik van Tuch, founder of Architecture of Sales, a lead generation and sales outsourcing agency that helps companies enter the Polish market with native Polish speaking SDRs. Uh, today I want to talk about one specific challenge. Selling technical products where the sales process requires real engineering knowledge. What do you do when your product is complex? Your buyer is an engineer engineer. And your sales process requires someone who actually understands the technology. Most companies answer the questions the wrong way. They send their engineer to prospect and watch them disappear into dead end calls for weeks. Technical people are brilliant at explaining products. They are not trained to prospect, navigate the sales process or close. When you send your presale engineer to do code outreach and prospecting, you are using a formula one engine to deliver pizzas. It works, but it's not what it was built for and it costs you a fortune in wasted time. And worth it builds frustration. Engineers who spend their days on unqualified calls stop being sharp on the ones that matter. Good solution for this situation is tandem. Native Polish speaking SDR who opens the conversations, qualifies the prospects and run the discovery. And a technical expert who can be English speaking who enters the process once there's real opportunity M and enough data about customers to run the demo and discussions. Here's why this works. When a technical expert join a meeting, the prospect immediately understands that this person's time is valuable. Cover multiple projects, they don't show up for every call. That positioning alone raises the perceived value of the conversation. The SDR saves the engineer from dead end calls the engineer, close the deals, the SDR opens. The most common fear I hear is this. Your sdr, uh, won't understand our product. They will make a bad first impression. That's a legitimate concerned. Here's how we solve it. Before any call is made, we run a structured onboarding process. We document the product, the icp, the buyer Personas, the pain points, the unique selling points and the market value proposition. The SDR doesn't need to explain the technology. They need to identify the problem, confirm the fit and schedule the right next steps. That's all. That's a skill and it's learnable. The technical conversations happen at the first or second second meeting when it actually matters. What you end up with is qualified pipeline prospects who have a real need, match your ICP and are ready to talk to your technical team. Your engineers spend their time on conversations that are worth having, not on cold calls that go nowhere. That's not just more efficient. That's how you scale a technical sales process in a new market. Depending on your team structure, there are two ways to build it. Option number one SDR plus pre sales Engineer SDR prospects and qualify pre sales, takes over after the first meetings and owns the technical process. Option number two SDR uh plus sales executive. The sales executive runs the full conversation. Highlight the value in excelling points, pain points, the technical person, defense, the architecture, and answers the hard questions. Either a model works. What doesn't work is one engineer doing all of it alone. If you sell a technical product and you are entering Poland, don't make your engineer your prospector. Build the tandem Polish SDR opens the door. Your technical expert walks through it. That's the model that works. If you want to know how this looks for your specific product and team structure, book a call with me. I, uh, will tell you exactly how we would build it.
Other episodes covering the same guests and topics, from across The B2B Podcast Index.
I asked 5 brands why they sponsored this 30,000 person eventSponsor Magnet · on ICP (Ideal Customer Profile)92 / 100
CRO Role Hot Takes with Bridget WinstonThe CRO Spotlight Podcast · on ICP (Ideal Customer Profile)88 / 100
The Rise and Fall of the MQL - Live Workshop Recording with Jon MillerGTM Live · on Sales Development Representatives (SDRs)80 / 100
What I Wish I’d Known About Sales With Tom HappeB2B Sales Playbook · on ICP (Ideal Customer Profile)79 / 100
Best of Build Mode: Think like a VCEquity · on ICP (Ideal Customer Profile)78 / 100
How Splunk Scaled to a $10B IPO: Tom Schodorf’s GTM Playbook for FoundersBuilt Not Born: The Startup Go-To-Market Podcast · on ICP (Ideal Customer Profile)78 / 100
Foreign Companies Keep Losing Polish Deals They Should Win. 3 Reasons Why.62 / 100From Cold Call to Closed Deal: The Full Architecture of Sales Process Explained by Dominik Wantuch65 / 100Cold Calls, Clay & Claude: Inside the B2B Sales Process at Architecture of Sales | Polish Market Entry with Szymon Dąbrowski & Ewelina Piechota49 / 100How Much Does Sales Outsourcing in Poland Actually Cost? Lead Generation vs Full Sales Outsourcing in Poland63 / 100The Polish Market Entry Checklist: 9 Points That Separate Success from Failure