Leading PreSales | The Solution Engineering Leadership Show

Leading PreSales | The Solution Engineering Leadership Show

By Jan-Erik Jank & Tim BrömmeBusinessCareersManagement
Download on the App Store

Leading PreSales | The Solution Engineering Leadership Show episodes

  • Dream Big, Then Pull the Brake [83]
    Lead build-vs-buy calls: outcome first, then one hard bottleneck question

    Ava's team kept duct-taping workarounds onto a bought POC platform until one SE built the tool she actually wanted in an afternoon. Nate pushes back on skipping constraints, and together they work out how to pair unconstrained dreaming with a named brake so build ideas don't turn into distractions.

    What Nate and Ava discuss
    • Why opening with security and data-protection constraints kills good tool ideas, and how to treat them as problems to solve instead
    • Pairing a builder with one named 'brake' and timeboxing the no-limits phase to one or two hours
    • Spotting when 'buy' is really failing: repeat workarounds and a weekly log of customer asks you couldn't deliver
    • The move

      Give the next build idea a one-to-two-hour session with no constraints. Then have one named person ask whether this is your biggest bottleneck right now. If it's not, park it, and keep a weekly log of 'we couldn't do it' moments so it comes back with evidence.

      🔗 Resources & Links: paths.to/presales

      📅 Book a Discovery Call: calendly.com/serockstars-tim/discovery-call

      7 min
    • Stop Waiting Weeks: Make Your SE Team AI-Self-Sufficient [82]
      Find the work your SEs queue weeks for, then let them ship it in thirty minutes

      Ava watched one of her SEs go from webinar idea to live landing page before lunch, work that once took her weeks of cross-team waiting. Nate pushes back on brand risk, shadow IT and customer legal. Together they work out which dependencies AI can remove and which ones are real.

      What Nate and Ava discuss
      • Moving approval upstream: other teams approve a template once, and SEs self-serve every instance inside it
      • Where the real delay sits: the hands-on work versus weeks of handoffs, inboxes and chasing
      • Guardrails at scale: shadow IT, brand consistency, and why customer legal can't be prompted away
      • The move

        Run a dependency audit: ask every SE when they last waited more than a week on another team, then check whether a template plus an AI tool could make that work self-serve. Take the list to the other team's leader before you build anything, and pitch it as fewer tickets in their queue.

        🔗 Resources & Links: paths.to/presales

        📅 Book a Discovery Call: calendly.com/serockstars-tim/discovery-call

        7 min
      • Hours Saved Is Not Money Saved [81]
        Why 'admin hours times rate' collapses in front of a CFO, and what to say instead

        Ava's SE brought a business case built on hours saved times an hourly rate, but the people were still on the payroll after go-live. Nate and Ava work out how to coach SEs to turn freed capacity into revenue, error cost, or avoided hiring that finance will actually believe.

        What Nate and Ava discuss
        • Why freed capacity isn't cost savings unless a real cost line shrinks
        • Error and risk cost as the lever that beats time saved, with a pricing-sheet example
        • When avoided hiring holds up, and why it has to match the customer's budget cycle
        • The move

          Pull every business case your team sent last quarter and ask one question wherever you see hours times rate: which cost line shrinks? If none does, rewrite it as freed capacity and get the buyer to say what those hours turn into.

          🔗 Resources & Links: paths.to/presales

          📅 Book a Discovery Call: calendly.com/serockstars-tim/discovery-call

          7 min
        • The €1,000 Contradiction: Don't Promise Enablement You Haven't Funded [80]
          When your job posting hands out a mandate your budget can't possibly pay for

          Nate reads a Head of SE posting that makes the new leader responsible for training, tools and feedback — then funds it with €1,000 a year, less than the same company gives people for donating to open-source projects. He and Ava dig into why that gap is read as a culture signal, and what to do before pay transparency makes every line comparable.

          What Nate and Ava discuss
          • Why a mandate without a matching budget line is the loudest thing in your job ad
          • How to win enablement budget by making already-spent shadow money visible to finance
          • Region-honest benefits, remote-first, and why every work-model rule needs a stated reason
          • The move

            Open your live posting and write the euro figure next to every 'you will own / build / equip' line. If there's no number — or the number embarrasses you — fix the budget before you post, or cut the sentence.

            🔗 Resources & Links: paths.to/presales

            📅 Book a Discovery Call: calendly.com/serockstars-tim/discovery-call

            7 min
          • Head of SE or Jack-of-All-Trades? Scope-Test the Role Before You Sign [79]
            Eleven mandates, fifteen SEs: how to split the operating year from the three-year list

            Nate breaks down a second-line Head of Solution Engineering ad that quietly bundles five go-to-market motions, post-sales and partner building into one job. He and Ava work out how to scope-test a mandate like that — as the candidate and as the hiring manager.

            What Nate and Ava discuss
            • Reading the org math: fifteen SEs with two team leads means the people job is developing the leads, not running deals
            • Why 'partner closely with Sales, CS, Partnerships, Product' is the tell that decides whether a broad mandate is attractive or a trap
            • The seniority mismatch hiding in the nice-to-haves — and who you should actually hire instead
            • The move

              Before you accept (or post) a second-line SE role, split the responsibility list in two with the hiring manager in the room: what must be true in twelve months, and what belongs on a three-year list with a date. Then write the name of the peer who owns each long-term item today — no name means it's yours by default.

              🔗 Resources & Links: paths.to/presales

              📅 Book a Discovery Call: calendly.com/serockstars-tim/discovery-call

              6 min
            • Your Job Ad Is a Sieve With No Holes [78]
              Why binary requirements and a 12-month success line beat adjectives

              Nate tears apart a publicly posted Head of Solution Engineering ad from a fast-growing automation vendor — two things it does brilliantly, two it gets badly wrong. Ava pushes back on publishing comp bands and on asking candidates to sign up for a number before they know the territory.

              What Nate and Ava discuss
              • Publishing the salary band as a filter in both directions — and what it costs you internally
              • Killing unmeasurable must-haves like 'AI curiosity' and replacing them with observable evidence
              • Adding the one sentence almost no job ad contains: what success looks like after twelve months
              • The move

                Open your current req and add a single line describing what success looks like twelve months in. Then walk your must-have list and delete anything a candidate can't answer with a plain yes or no.

                🔗 Resources & Links: paths.to/presales

                📅 Book a Discovery Call: calendly.com/serockstars-tim/discovery-call

                7 min
              • The 18-Month Goodbye: Why Your Best SE Leaves a Team They Love [77]
                Ambitious SEs don't quit over dissatisfaction. They quit over a timeline nobody named.

                Ava's strongest SE left after eighteen months from a team she loved, because the path to leading anything was never made concrete. Nate and Ava dig into why silence about timelines costs you your best people, and what an honest version of that conversation sounds like.

                What Nate and Ava discuss
                • Why great culture, comp and training don't retain someone whose next step is invisible
                • The arithmetic problem: more aspirants than seats, and what happens when you never say the real number
                • Giving real accountability with a date attached instead of a 'lead' label with nothing behind it
                • The move

                  Book thirty minutes with everyone who has hinted they want to lead — outside the pipeline 1:1. Ask what they want to be responsible for and by when, then say the honest timeline out loud, even when it's ugly, and set a date to revisit it.

                  🔗 Resources & Links: paths.to/presales

                  📅 Book a Discovery Call: calendly.com/serockstars-tim/discovery-call

                  7 min
                • Hire the Slope, Not the Checklist [76]
                  Which candidate gaps you fund with budget and time \u2014 and which ones actually disqualify

                  Ava almost passed on her best hire because a scripted demo in his second language buried him. She and Nate work out how to separate fundable gaps from structural ones \u2014 and how to attach a remedy, a budget, an owner and a date before day one.

                  What Nate and Ava discuss
                  • Redesigning an interview so the format stops hiding the candidate \u2014 and how to standardize that at scale
                  • Naming the gap out loud in the offer call and funding the fix before day one
                  • Which gaps you personally over-weight, and what it costs to push a hire past a skeptical sales leader
                  • The move

                    Before the offer goes out, write one sentence naming the gap, then attach the remedy, the budget, the owner and the date. If you can't fill all four, you're not funding a gap \u2014 you're hoping.

                    🔗 Resources & Links: paths.to/presales

                    📅 Book a Discovery Call: calendly.com/serockstars-tim/discovery-call

                    7 min
                  • The Long Leash: Why Great SEs Drown After Promotion [75]
                    Promoting your best SE without a ramp isn't confidence -- it's an unmanaged risk

                    Ava tells the story of her own first leadership job: the title, the bigger number, and a comp plan she couldn't read. She and Nate work out what a real promotion ramp looks like -- and why the new leader's silence is the least reliable signal you have.

                    What Nate and Ava discuss
                    • Why confident self-presenters hide their gaps for months, and what to assume instead
                    • Screening motive without making it a pass-fail test
                    • Pairing new leaders with a mentor who has nothing left to prove
                    • The move

                      Before anyone gets promoted, have them draft a 90-day phase plan with named milestones -- including one session on the commercial model -- and let them pick their own mentor from two or three people who have nothing left to prove.

                      🔗 Resources & Links: paths.to/presales

                      📅 Book a Discovery Call: calendly.com/serockstars-tim/discovery-call

                      6 min
                    • Your Best SE Won't Leave Over Money — They'll Leave Over the Ceiling [74]
                      Why great SEs quit when everything is fine — and the one question that surfaces it

                      Nate brings an exit interview where nothing was wrong: good product, good team, good manager — and the best SE in the region still left after five quarters. He and Ava dig into the invisible ceiling on scope and progression, and what leaders can actually do about it.

                      What Nate and Ava discuss
                      • Why comp is the story people tell afterwards, not the reason they left
                      • How to name a ceiling honestly when there's no management seat to offer
                      • Sponsorship vs. criteria — and why a career grid on its own promotes nobody
                      • The move

                        Twice a year, ask each SE what they're optimizing for right now, then answer honestly whether it exists here in the next eighteen months. If it's a yes, sponsor one concrete thing within ninety days — otherwise the yes is just a nicer no.

                        🔗 Resources & Links: paths.to/presales

                        📅 Book a Discovery Call: calendly.com/serockstars-tim/discovery-call

                        6 min

                      About Leading PreSales | The Solution Engineering Leadership Show

                      From the publisher's feed

                      Two voices. Two perspectives. One goal: making you a better PreSales leader.