Direct answer

In your first week as a Founding AE, prioritize three conversations with your founder before you start any sales work. First: a deep walkthrough of their sales history — specific deals, patterns, where deals stall. Second: a precise definition of the ICP and the differentiators that actually drive purchase, in the buyer’s language. Third: explicit alignment on what success looks like in the first 90 days, including the 5 to 8 hours per week of founder coaching time that’s the strongest predictor of Founding AE success. Running pipeline before these three conversations is what gets Founding AEs fired in month four.

You’ve just landed the role. The offer is signed, the comp plan looks good, the product is real. The instinct now is to dive into demo calls and prove you can sell.

Don’t.

Across 250+ founder conversations, the Founding AEs who succeed in this seat all do the same thing in Week One. They have three structured conversations with the founder before they touch the pipeline. The ones who skip these conversations are the ones who end up six months in trying to figure out why deals keep stalling at the same place — without realizing they never aligned with the founder on what the seat was supposed to be.

Week One is not about activity. It’s about pattern transfer. Here are the three conversations to have, what to ask in each, and what to listen for.

The three Week One conversations

Conversation 01
Founder sales history and patterns

Before you build any pipeline, understand how the company has sold so far. Not the aggregate numbers — the patterns behind them. Who has been closing deals. What kinds of customers. What the average deal looks like. Where deals get stuck.

Founders almost always have an incomplete view of their own sales process. They’ve been closing deals as magicians — personal relationships, deep product knowledge, intuition built over years. The deals are real, but the process is in their head. Your job is to find the repeatable patterns and turn them into a motion that scales.

Ask them

“Walk me through the last three deals you closed. What were the key steps? Who was involved? What were the biggest challenges? Where did each one almost die?”

Listen to the founder’s language as they answer. Are they talking about features, or are they talking about what the customer was trying to solve? Do they describe the customer’s pain in the customer’s words? If they can’t articulate the value proposition cleanly when describing a deal they personally closed, you have a message problem to solve in the next 90 days — not a pipeline problem.

Conversation 02
ICP and the differentiators that actually matter

A precise ICP is the foundation of every other sales decision you’ll make. Founders often have a rough one — “we sell to mid-market SaaS companies” — that’s too broad to be operationally useful. Your job in Week One is to push past that.

Ask them

“What are the specific characteristics of your three best customers? What problem were they trying to solve when they bought? What changed for them after they implemented? Why would someone with the same problem choose us over the next-best option?”

Push for specificity in both directions: the customers who fit, and the differentiators that landed. If the founder’s answer is feature-focused (“we have the best dashboard”) instead of outcome-focused (“we cut their reporting cycle from two weeks to two hours”), that’s a message problem you’ll spend the first 30 days untangling. If the founder can articulate the outcome but it doesn’t actually land with buyers, that’s a market problem. Motion is not message is not market. Name which one before you try to fix it — see the framing in the pre-sign checklist.

Conversation 03
Expectations for the first 90 days

Misaligned expectations are the most common source of founder-AE conflict, and they almost always come from things never said out loud in Week One. The founder is quietly hoping for closed revenue by day 60. The AE is quietly assuming day 90+. Neither has said this. Three months later, the disconnect becomes a performance conversation.

Get the targets explicit. Pipeline by day 30. Qualified opportunities by day 60. Closed revenue by day 90 (with realistic acknowledgment of what your sales cycle actually permits). Product feedback cadence. ICP refinement milestones. Write it down. Both of you sign off.

Ask them

“What does success look like at day 30, day 60, and day 90? What pipeline number, what opportunities, what closed revenue? And what do you need from me on product feedback and ICP refinement along the way?”

Be equally explicit about what you need from the founder to hit those targets. Access to specific customers. Founder presence on key calls. Product training depth. Time blocked weekly for shadowing and debrief. Across 250+ founder conversations, the strongest predictor of Founding AE success is founder coaching time in the first 90 days — 5 to 8 hours per week, minimum. If the founder can’t commit that, surface it now. That conversation in Week One is uncomfortable. The same conversation in month four, after deals have stalled, is much worse.

The trap: confusing activity with progress

Once the three conversations are done, the temptation is to start filling the calendar — cold calls, outreach sequences, demo bookings. Resist the part of that instinct that’s about looking busy rather than being effective.

Founders often reward visible activity. They’ll tell you they’re glad to see you’re working hard even when nothing’s closing. Your job is to focus on the activity that’s actually moving you toward repeatable revenue. That means quality over quantity. Ten targeted conversations with people who match the ICP you defined in Conversation 2 beats a hundred unqualified cold calls.

The diagnostic question to run on yourself each week in months one and two: is what I’m doing helping me close a deal, learn more about the ICP, or refine the sales process? If the answer is no on all three, you’re mistaking motion for progress.

The conversations aren’t one-time

The three Week One conversations are the kickoff, not the finish. The deeper work — turning the founder’s tacit knowledge into something you can actually run — happens over the next 60 to 90 days through shadowing, calibration debriefs, and weekly documentation. That mechanism is here.

What Week One does is establish that you’re a founding partner, not an order-taker. The founder doesn’t hand you the playbook because there isn’t one. Your job is to build it with them, starting in your first seven days. The conversations are how you signal what you’re actually there to do.