What you’ll do
As an Enterprise Client Sales Executive, you’ll own a portfolio of high-value accounts within Brex’s Enterprise segment. Your role will be pivotal in fostering business expansion and ensuring sustained client success through disciplined execution, strategic influence, and consultative engagement.
Where you'll work
This role will be based in our San Francisco office. We are a hybrid environment that combines the energy and connections of being in the office with the benefits and flexibility of working from home. We currently require a minimum of three coordinated days in the office per week, Wednesday and Thursday. We currently require three days per week in office - Monday, Wednesday and Thursday. As a perk, we also have up to four weeks per year of fully remote work!
Responsibilities
Drive revenue growth across your book by strategically increasing card adoption and expanding client use of Brex’s Spend Management suite (Expense Management, Bill Pay, Travel, and global payments)
Drive long-term retention by understanding client health and business needs, proactively developing and executing strategies to mitigate churn risk and solidify partnerships
Proactively identify and prioritize expansion opportunities by analyzing account performance, usage headroom, and competitive signals
Lead renewal and expansion cycles end-to-end, from early account strategy through negotiation and close, ensuring strong commercial outcomes
Build executive-level relationships and multi-thread across stakeholders (finance, procurement, and operations) to strengthen account resilience, act as a trusted advisor, and uncover new areas for adoption and growth
Operate with ownership, anticipating client needs, addressing risks early, and taking accountability for revenue and retention outcomes
Partner cross-functionally with Customer Success, Solutions Consultants, Underwriting, RevOps, and Product to deliver unified client outcomes
Maintain rigorous sales discipline with consistent pipeline hygiene, accurate forecasting, and comprehensive account planning.
Surface insights and advocate for clients internally, influencing product roadmap and operational improvements
Solve complex problems with judgment and creativity, converting competitive threats or risks into opportunities for retention and expansion
Requirements
10+ years of B2B closing experience in SaaS, payments, or financial technology
Proven success managing enterprise-level accounts with complex deal cycles, executive engagement, and multi-threaded relationships
Consistent record of exceeding quota and delivering top performance in competitive sales environments
Demonstrated mastery of renewal and expansion cycles, including high-value negotiations and competitive displacements
Track record of driving net revenue growth through upsell, cross-sell, and adoption of multi-product solutions
Proficiency with sales tools and systems such as Salesforce, Outreach, and Gong, with strong pipeline and forecast discipline
Preferred qualifications
Deep knowledge of corporate cards, underwriting, rewards, or credit risk management
Experience selling financial operations platforms (expense, travel, AP, or global payments)
Recognition as a top performer (President’s Club, top stack rank, etc.) in prior roles
Exposure to enterprise procurement processes and competitive SaaS/fintech sales cycles
Compensation
The expected OTE range for this role is $250,000 - $315,000. The starting wage will depend on a number of factors including the candidate’s location, skills, experience, market demands, and internal pay parity. The OTE figure listed here includes base salary and commissions, which may or may not be earned depending on performance. Depending on the position offered, equity and other forms of compensation may be provided as part of a total compensation package.
Please be aware, job-seekers may be at risk of targeting by malicious actors looking for personal data. Brex recruiters will only reach out via LinkedIn or email with a brex.com domain. Any outreach claiming to be from Brex via other sources should be ignored.
