Founding Account Executive

Overview

You're the founding AE at Catio, a 22-person startup building an "Architecture IDE" - a control plane for software systems. You sell to architects, principal engineers, and CTOs at mid-market to enterprise software companies. There's no sales playbook, no established category, and you're building pipeline from zero.

Role Snapshot

Company Context

Stage: Seed/early (22 employees, actively hiring founding team)

Size: 22 employees

Growth: Building core GTM team now - you're employee #1 or #2 in sales

Market Position: Category creation - "Architecture IDE" isn't an established category. You're competing against status quo (spreadsheets, Confluence docs, tribal knowledge) more than direct competitors.

GTM Reality

Pipeline Sources:

• 90%+ Outbound - You're identifying target accounts, finding the right architect/CTO contacts, and cold outreaching
• Maybe 10% inbound from founder network, early product interest, demo video views
• No established partner motion yet

SDR/AE Structure: No SDRs. You source everything yourself.

SE Support: You have a founding SA (the other role they're hiring), but at 22 people, expect to do a lot of technical discovery yourself.

Competitive Landscape

Main Competitors:

• Status quo (architecture decisions happen in Slack, Confluence, whiteboard sessions)
• DIY tools (Lucidchart, Miro, internal wikis)
• Point solutions (API documentation tools, system diagram tools)

How They Differentiate: AI-powered architecture reasoning, not just diagramming. Ties architecture decisions to business outcomes. Provides "24/7 expert guidance" (unclear what this means - you'll figure it out).

Common Objections:

• "We already have a process for this"
• "Our architects don't need tooling, they need to think"
• "This seems like nice-to-have, not mission-critical"
• "How do we measure ROI on architecture decisions?"

Win Themes: Unknown - you're figuring out what resonates. Likely: faster integration, reducing technical debt, making architecture decisions less tribal/more systematic.

What You'll Actually Do

Time Breakdown

Prospecting (40%) | Active Deals (30%) | Discovery/Learning (30%)

Key Activities

• Cold outreach to technical buyers: You're reaching out to VPs of Engineering, CTOs, Principal Architects at companies with complex systems. These people ignore most sales emails. You need to demonstrate technical credibility immediately or you're deleted.

• Deep discovery calls: When you get a meeting, you're not running a canned demo. You're understanding their architecture challenges, how they make tech decisions now, where things break down. Many calls will feel more like consulting than selling.

• Building the sales playbook in real-time: There's no CRM full of won deals to learn from. You're figuring out: What titles actually have budget? What pain points matter? What's the buying process? How do we price this? You're documenting as you go.

• Internal alignment on positioning: You'll spend a lot of time with founders and the SA debating: Are we selling to architects or CTOs? Is this a "system of record" or "decision-making tool"? What outcomes can we actually commit to? The product is evolving, the pitch is evolving.

The Honest Reality

What's Hard

• Category creation is slow: You're not selling against competitors, you're selling against "we don't think we need this." Deals take forever because buyers need to be educated on why this problem matters.

• Technical buyers are skeptical: CTOs and architects have seen a lot of sales pitches for tools that "revolutionize" their workflow. They're deeply skeptical, especially of AI hype. You need to earn credibility in every conversation.

• No playbook = lots of dead ends: You'll waste time on prospects who seem interested but have no budget. You'll mistarget accounts. You'll learn painfully which objections are actually blockers vs smokescreens. There's no AE who came before you to shortcut this.

• Founder-led sales shadow: At 22 people, founders are probably still in deals. You need to figure out what they do that works, then systematize it without them.

What Success Looks Like

• You close 3-5 design partner or pilot deals in your first 6 months
• You document a repeatable outbound motion that generates 10-15 qualified conversations per month
• You define "qualified" - what signals indicate a real opportunity vs tire-kicker
• You build a POV on pricing and packaging based on actual deal dynamics

Who You're Selling To

Primary Buyers:

• CTOs at 100-1000 person software companies
• VPs of Engineering / Principal Architects with platform ownership
• Heads of Engineering at e-commerce companies managing complex tech stacks

What They Care About:

• Reducing time spent in "architecture review" meetings that go nowhere
• Making tech decisions that align with business strategy (speed to market, cost, scalability)
• Onboarding new engineers faster by documenting system context
• Preventing technical debt from accumulating invisibly
• Justifying architecture investments to non-technical stakeholders

Requirements

• You've sold complex technical products to engineering or technical buyer personas (not IT, not business buyers)
• You're comfortable with "we don't know yet" - pricing, positioning, ICP are all hypotheses you'll test
• You can build your own pipeline - you've done high-volume outbound to senior technical buyers before
• You operate at "architecture level depth" - you can talk about system design, integration patterns, technical tradeoffs without an SE on every call
• You've been early at a startup (first 50 people) and know what 0→1 GTM feels like: chaotic, ambiguous, high-ownership