To onboard a Founding Account Executive with no existing sales process, start by giving them structured access to customers, context, and the founder, not a playbook that doesn’t exist yet. The founding AE’s job is to build the process, not follow one, which means onboarding looks fundamentally different from a standard AE hire. The questions below break down exactly what that looks like in practice.
What should a founding AE do in their first 30 days?
In their first 30 days, a Founding Account Executive should focus entirely on learning the business from the inside out: talking to existing customers, shadowing the founder in sales conversations, reviewing any deals that have closed or been lost, and forming a clear picture of what’s actually working. No quota. No pipeline pressure. Just discovery.
This matters because a founding AE who skips this phase tends to default to habits from their last company, which may have nothing to do with your buyers, your product, or your market. The first 30 days are about building conviction and context, not closing.
Concretely, that means:
- Five to ten customer interviews to understand why people bought and what they value
- A review of lost deals to understand where the pitch breaks down
- Deep product immersion, including hands-on time with the tool
- A first draft of the ICP based on what they’re hearing, not what the deck says
By day 30, a strong founding AE should be able to articulate the value proposition in their own words and have a point of view on what a repeatable sales motion could look like. If they can’t, that’s a signal worth paying attention to.
How do you build a sales process when there isn’t one yet?
You build a sales process from the ground up by starting with what’s already worked, even informally. Look at every deal that has closed and map the steps that actually happened: how the conversation started, what objections came up, what moved it forward, and what the buyer needed to say yes. That pattern is your starting point.
From there, the founding AE should document as they go, not in retrospect. Every call, every email sequence, every demo structure gets written down in real time. The goal isn’t perfection. It’s repeatability. A rough process that gets tested and refined beats a polished one that never gets used.
The founder plays a critical role here. They typically hold tacit knowledge about why customers buy that has never been written down. Getting that out of their head and into a shared document is one of the most valuable things that can happen in the first 60 days.
What does a good founding AE onboarding plan actually include?
A good onboarding plan for a Founding Account Executive includes four core elements: structured access to customers and stakeholders, a defined discovery period before pipeline pressure kicks in, clear ownership of what the AE is expected to build, and regular check-ins with the founder to align on direction. Without these, the hire drifts.
The plan should be time-boxed. A common structure that works well in practice looks like this:
- Days 1 to 30: Discovery mode. Customer interviews, product immersion, deal review, no quota.
- Days 31 to 60: First pipeline. The AE starts running their own conversations with the founder’s support. They’re testing their early hypotheses about the sales motion.
- Days 61 to 90: Process documentation. The AE formalizes what’s working into a repeatable framework, including talk tracks, objection handling, and qualification criteria.
What good onboarding does not include is a stack of internal decks, a product certification course, and a target date to be “fully ramped.” That’s how you onboard a New Business Account Executive at a company with an established motion. A founding AE hire needs space to think, not just content to consume.
How long does it take a founding AE to ramp without a sales process?
Without an existing sales process, a founding AE typically takes three to six months to reach meaningful productivity, and that’s normal. The extended ramp is not a performance problem. It reflects the reality that this person is doing two jobs simultaneously: selling and building the infrastructure to sell at scale.
That said, you should start seeing early indicators of success well before the six-month mark. By the end of month two, a strong founding AE will have run enough conversations to have a clear hypothesis about the sales motion. By month three, they should have a documented process, even a rough one, and early pipeline moving through it.
Where companies go wrong is applying the same ramp expectations they’d use for an Expansion Account Executive or a Channel Account Executive joining an established team. Those roles inherit a process. A founding AE builds one. The timeline reflects that difference, and setting the wrong expectations is one of the fastest ways to lose a great hire early.
Should the founding AE or the founder own the sales process?
The founding AE should own the sales process, but the founder must co-create it. This distinction matters. If the founder retains ownership, the AE becomes an executor rather than an architect, which defeats the purpose of the hire. If the AE operates in isolation, they build something disconnected from the founder’s hard-won knowledge about what actually resonates with buyers.
The most effective setup is a deliberate handover. The founder shares everything they know, including the unwritten stuff: how they open conversations, what language buyers respond to, which objections are real versus smoke screens. The founding AE takes that input, tests it, and starts formalizing it into a process they own and can improve over time.
This also has a practical implication for how you hire. A Partner Account Executive or someone who has only operated within structured sales organizations is often a poor fit for this role. You need someone with the confidence to make decisions without a safety net and the discipline to document what they learn.
What are the biggest mistakes companies make when onboarding a founding AE?
The biggest mistakes companies make when onboarding a Founding Account Executive are setting quota too early, providing too little founder access, and hiring the wrong profile for the role. Any one of these can derail an otherwise good hire within the first 90 days.
Setting quota in month one is the most common error. It forces the AE into short-term selling mode before they’ve had time to understand the buyer, which usually results in a fragile pipeline built on assumptions rather than insight. The pressure to hit a number prevents them from doing the discovery work that makes everything downstream better.
Insufficient founder access is the second major failure point. The founding AE needs to shadow real sales conversations, ask questions that would seem basic to anyone else, and get honest feedback on their early attempts. Companies that treat onboarding as an HR process rather than a founder-led partnership tend to produce AEs who are technically active but strategically lost.
Finally, hiring the wrong profile. A founding AE role is not a standard New Business Account Executive position with an ambiguous job title. It requires a specific combination of entrepreneurial mindset, comfort with ambiguity, and the discipline to build systems while also closing deals. Hiring someone who thrives in structured environments and then expecting them to build from scratch is a setup for disappointment on both sides.
At Nobel Recruitment, we speak to hundreds of GTM candidates and hiring managers every week. Curious what we’re seeing in the market right now? Reach out, we’re happy to share, or take a look at how we approach GTM executive search.
Frequently Asked Questions
How do you know if your founding AE hire is the right fit within the first 30 days?
The clearest early signal is whether the founding AE is asking the right questions — about buyers, lost deals, and the product — rather than waiting to be told what to do. A strong fit will proactively seek out customers to interview, synthesize what they’re hearing into a coherent point of view, and push back constructively when something doesn’t add up. If by day 30 they’re still waiting for a playbook to appear, that’s a meaningful red flag about whether you have the right profile for the role.
What should the founder actually do during the founding AE's onboarding period?
The founder’s primary job during onboarding is to be accessible and to externalize their tacit sales knowledge — the instincts, language, and patterns they’ve developed through direct selling that have never been written down. Concretely, that means co-running sales calls, debriefing after every conversation, and making time for regular one-on-ones where the AE can ask questions that might feel basic but are actually critical to building the right foundation. Founders who treat onboarding as the AE’s problem to solve alone almost always end up with a disconnected sales process that doesn’t reflect how the company actually wins deals.
How do you set fair performance expectations for a founding AE when there's no historical benchmark?
Instead of setting revenue-based targets in the first 90 days, define success around process milestones: a completed set of customer interviews by day 30, a documented first draft of the sales motion by day 60, and a live pipeline being actively worked through a repeatable framework by day 90. These output-based expectations give you something meaningful to evaluate without forcing the AE into short-term selling behavior before they’ve earned the context to do it well. Once the process exists, you can layer in pipeline and revenue targets that are grounded in actual data rather than guesswork.
What does a good ICP (Ideal Customer Profile) look like when a founding AE builds it from scratch?
A founding AE’s first ICP draft should be built entirely from primary research — customer interviews, deal reviews, and direct sales conversations — not from the company’s existing marketing deck or assumptions about the target market. It should capture not just firmographic data (company size, industry, geography) but behavioral signals: what triggered the buying decision, what internal pain made the problem urgent, and what the buyer needed to believe in order to say yes. Expect this document to evolve significantly over the first six months as the AE tests hypotheses in real conversations and refines what actually predicts a closed deal.
When should a founding AE start hiring or building out a sales team beneath them?
A founding AE should not start hiring until the sales process is documented, repeatable, and has been validated across a meaningful number of deals — typically somewhere in the range of 10 to 20 closed wins following a consistent motion. Hiring before that point means onboarding new reps onto a process that doesn’t yet exist, which compounds the chaos rather than solving it. The founding AE’s job is to build and prove the model first; scaling it is the next phase, and conflating the two is one of the most common ways early-stage sales teams stall out.
What's the difference between a founding AE and an early AE hire, and does it matter for onboarding?
A founding AE is specifically hired to build the sales process from scratch — they are the first sales hire and operate without an established motion, manager, or playbook. An early AE, by contrast, might be the second or third sales hire joining a team where a founding AE has already laid the groundwork. The distinction matters enormously for onboarding: a founding AE needs a discovery-first, builder-oriented ramp with heavy founder involvement, while an early AE can be onboarded more conventionally onto the process the founding AE has already created. Treating these two hires the same way is a common and costly mistake.
What tools or systems should a founding AE set up during their first 90 days?
The priority in the first 90 days is capturing information, not optimizing tooling — so keep the stack minimal and practical. At a baseline, a CRM (even a lightweight one) to log deal activity and track pipeline stages, a shared document for building out the sales process in real time, and a call recording tool to review and learn from conversations are sufficient to start. Resist the temptation to over-engineer the tech stack before the process itself is defined; the right tools become obvious once you know what you’re actually trying to measure and repeat.
Related Articles
