You need to stop waiting for the AE to drive pipeline growth and immediately redefine your role from technical mouthpiece to account owner. Start by running a 2-hour exercise this week: map every stakeholder in your top 3 accounts (technical buyers, economic buyers, end users, champions), identify their individual pain points and business priorities, and list 3-5 potential expansion opportunities per account based on what you already know technically. Don't wait for perfect information—use what you've observed in technical conversations about their infrastructure gaps, complained-about workflows, or mentioned future initiatives. Then, within 48 hours, directly schedule 30-minute conversations with 2-3 technical champions under the premise of "quarterly technical check-in" or "ensuring you're getting maximum value." In these conversations, ask business-outcome questions ("What's your team being measured on this quarter?" "Where are the bottlenecks costing you the most?") instead of purely technical ones, and end each conversation with a specific next step: "Based on what you've shared about X problem, I'd like to bring our team back next week with a specific proposal for how we could address that—does Thursday at 2pm work?" Simultaneously, build a peer relationship with your AE's manager by bringing them a solution, not a complaint. Schedule 20 minutes with them this week and come prepared: "I've identified $X in expansion opportunity across these accounts based on technical conversations. Here's my plan to drive three discovery meetings in the next two weeks. I'd like your perspective on how to position these internally and whether you want me to loop in [AE name] as I execute or run point myself given bandwidth." This frames you as someone taking ownership while respecting the political reality. Set a forcing function by committing to specific dates for these discovery meetings in that conversation—make them real calendar commitments, not hypotheticals. Follow up 48 hours later with a one-line email confirming the commitments and deadlines you discussed. You're not asking permission to drive outcomes; you're demonstrating you already are and inviting them to optimize how you do it. The key belief to challenge here is that your role definition limits your agency. Test this directly: your first "experiment" is whether customers actually care about your title when you bring them valuable business insights. The answer will almost certainly be no—technical champions are desperate for vendors who understand their business context, not just their tech stack. Once you run 3-4 of these expanded conversations and see positive responses, you'll have both proof that your belief was limiting you and concrete pipeline progress to show. This isn't about working around the AE; it's about demonstrating what's possible and creating a new normal where you're a revenue driver who happens to have technical depth, not a technical resource who occasionally helps with deals. Move fast—every week you wait is pipeline that doesn't exist in Q4.

Tacit Knowledge Revealed

Expert decision-making relies on recognizing subtle cues and applying practiced mental patterns. Here's what an expert notices, thinks, and does at key moments: