Full-Time

Strategic Account Executive

Posted on 8/21/2026

Paddle

Paddle

201-500 employees

All-in-one revenue delivery for SaaS

No salary listed

Remote in UK

Remote

Category
Sales & Account Management (1)
Required Skills
Sales

Get referred to Paddle

See people who can refer or advise you

Requirements
  • Extensive closing experience in a software or Software as a Service business, including multi-threaded sales processes and enterprise deals.
  • Deep experience in team selling and quarterbacking complex sales processes with high-level stakeholders.
  • Experience with consultative, value-based selling and a proven track record of exceeding quota.
  • Experience selling highly technical products or services.
  • Ability to communicate and influence effectively at multiple levels within prospect businesses, from operators to executives.
  • Experience in the payments space or selling business-to-business Software as a Service.
  • Experience selling to technical stakeholders such as Chief Technology Officers, Heads of Product, and technical founders.
  • Familiarity with e-commerce providers such as Stripe, Braintree, PayPal, and Cleverbridge, and subscription-based services such as Chargebee, Zuora, and Recurly.
  • Strong understanding of the Software as a Service, artificial intelligence, or mobile application market.
  • Ability to operate in an unstructured, self-starting environment.
Responsibilities
  • Own and grow a book of strategic accounts primarily based in Europe, the Middle East, and Africa, with some focus on Asia-Pacific, while developing and executing long-term deal strategies and commercial negotiations.
  • Drive new business by prioritizing target accounts, leveraging Business Development Representative support and Marketing resources, and conducting self-led prospecting to execute account plans and build pipeline.
  • Own the full sales cycle, including discovery, value positioning, objection handling, champion building, and stakeholder influence to progress deal cycles.
  • Use a consultative sales approach to demonstrate Paddle’s impact and align solutions with customers’ long-term company goals.
  • Master Paddle’s product and understand its features, the broader industry, and its value proposition in discussions with Chief Technology Officers, Heads of Product, and Chief Executive Officers.
  • Lead discovery efforts to understand client needs and collaborate with internal teams to develop tailored sales strategies.
  • Collaborate with Product, Customer Success, and Partnerships teams to align on client needs and develop integrated sales strategies for long-term success.
Desired Qualifications
  • Prior experience at a growth-stage internet or software company.
  • An entrepreneurial attitude and enjoyment of solving complex challenges in a fast-growing company.

Paddle is a platform that handles the back-end work for software sales. It combines billing, payments, tax compliance, subscription management, invoicing, and localization into one system so software teams can sell globally without worrying about administrative tasks. It works by processing payments and subscriptions, generating invoices, and ensuring compliance with international tax rules, all accessible through APIs and real-time webhook events for easy integration and up-to-date data. Paddle differentiates itself by offering an all-in-one revenue delivery infrastructure, with built-in tax and localization support, comprehensive documentation, and actionable reporting, so teams can connect payments to growth. Its goal is to help software makers grow internationally and scale their businesses by taking care of the complex back-office work, allowing developers to focus on building products.

Company Size

201-500

Company Stage

Debt Financing

Total Funding

$316.4M

Headquarters

London, United Kingdom

Founded

2012

Get referred to Paddle

See people who can refer or advise you

Simplify Jobs

Simplify's Take

What believers are saying

  • July 17, 2025: Paddle raised $25 million from CIBC Innovation Banking.
  • July 17, 2025: Paddle hired Shopify and Intercom veterans, strengthening enterprise sales and product leadership.
  • Apple’s web-payment shift and AI startup monetization increase demand for Paddle’s MoR platform.

What critics are saying

  • June 16, 2025: FTC permanently banned Paddle from tech-support telemarketers and imposed $5 million.
  • The FTC order hardens monitoring, disclosure, and reporting, raising compliance costs through 2026.
  • A major fraud scandal or card-network offboarding could destroy Paddle’s MoR credibility quickly.

What makes Paddle unique

  • Paddle’s Merchant of Record model removes billing, tax, and compliance complexity.
  • July 17, 2025: Paddle added Vercel and RevenueCat integrations for web and mobile monetization.
  • Paddle serves 6,000+ digital product companies across London, Lisbon, Toronto, New York, and Austin.

Help us improve and share your feedback! Did you find this helpful?

Benefits

Competitive compensation & share options

Private healthcare & mental health coaching

Flexible time off

Learning & development

Family leave

Wellbeing points

Transportation subsidies

Home workstation budget

Growth & Insights and Company News

Headcount

6 month growth

0%

1 year growth

0%

2 year growth

0%
BYOB
Aug 3rd, 2026
Monetizing your app: Paddle payments integration.

Monetizing your app: Paddle payments integration. 2026-08-03 Building the product is only half the battle; getting paid is the other. To help developers monetize their SaaS applications instantly, BYOB provides a deep, native integration with Paddle, a merchant of record that handles global taxes, subscriptions, and invoicing. Tldr. * Automated reconciliation of products, prices, and client tokens. * Secure webhook handling to update durable entitlement state in the database. * Strict separation of Sandbox and Production environments. Idempotent product syncing. Manually copying and pasting Price IDs from the Paddle dashboard into your codebase is tedious and error-prone. BYOB uses an idempotent reconciliation pattern driven by a catalog_key stored in each product's custom_data. You define your products and pricing tiers (amounts, currencies, billing intervals), and the agent automatically lists existing Paddle products/prices, reuses them by matching stable catalog fields, and creates only what's missing. The resulting Price IDs (pri_...) and PUBLIC_PADDLE_CLIENT_TOKEN are written to your project environment through secure env tooling - no manual copy-paste from the Paddle dashboard. Secure webhook automation. When a user upgrades their subscription, the payment happens on Paddle's servers. Paddle then fires a webhook back to your app to grant the user access. BYOB automatically generates the SvelteKit +server.ts webhook endpoints for you. These endpoints: * Securely verify the Paddle-Signature to ensure the payload is authentic. * Parse completion events like transaction.paid, transaction.completed, and subscription.activated - which are the only events that confirm actual payment (note: subscription.created proves provider contact, not customer payment). * Update the durable entitlement state in your database (Cloudflare D1 or Supabase), unlocking premium features for the user instantly. Inline vs. Hosted Checkout. Flexibility is key for conversion rates. The BYOB Paddle integration supports both: * Inline Checkout: Embedding the Paddle checkout UI directly into your pricing page for a seamless experience. * Hosted Checkout: Redirecting users to a Paddle-hosted page, which is ideal for complex invoicing or mobile flows. Environment separation. Mixing test payments with real money is a recipe for disaster. BYOB strictly enforces environment separation. The platform intelligently manages PUBLIC_PADDLE_ENV and your client/secret keys. When working in local development or preview branches, BYOB automatically routes your checkouts and webhooks to the Paddle Sandbox. When you hit production, the real keys take over. Paddle webhook notification settings must use the deployment URL (from byob deployment status), not the preview URL. Preview URLs are tied to the active workspace and are not stable endpoints for incoming webhooks. Summary. Monetization shouldn't require weeks of integration work. With BYOB and Paddle, you can go from free-tier to profitable SaaS in minutes. BYOB team. The creative minds behind BYOB. BYOB is a diverse team of engineers, designers, and AI specialists dedicated to making web development accessible to everyone. Related guides. Ready to start building? Join thousands of developers using BYOB to ship faster with AI-powered development.

Chartsy
Apr 27th, 2026
Stripe vs Paddle: which payment processor is right for your SaaS?

Stripe vs Paddle: which payment processor is right for your SaaS? April 26, 2026 Stripe and Paddle are the two most common payment processors for SaaS businesses - and on the surface they look similar. Both handle recurring billing, both have solid APIs, and both are trusted by thousands of software companies. But they are fundamentally different products, and choosing the wrong one can cost you significantly more than just the processing fee. This guide breaks down exactly how Stripe and Paddle differ on pricing, features, tax handling, and overall complexity - so you can make the right call for your business. The core difference: gateway vs. Merchant of Record. Before comparing features and pricing, you need to understand what each actually is. Stripe is a payment gateway. It processes card transactions on your behalf, but you remain the merchant of record. That means you are legally responsible for collecting and remitting VAT, GST, and US sales tax. Chargebacks, fraud liability, and global tax compliance are your problem. Paddle is a Merchant of Record (MoR). Paddle sells your product to customers on your behalf. You deliver the software; Paddle handles the entire commercial relationship - taxes, compliance, chargebacks, and refunds. From the customer's perspective (and the tax authority's perspective), they bought from Paddle. This distinction explains almost every other difference between them. Pricing. Stripe. | Transaction type | Rate | | Domestic card (US) | 2.9% + $0.30 | | International card | 2.9% + $0.30 + 1.5% surcharge | | Stripe Tax (EU VAT) | ~0.5% additional | | Monthly fee | None | Stripe's headline rate is 2.9% + $0.30. For a $100 transaction, that's $3.20 in fees and $96.80 net. However, if you sell to EU customers and use Stripe Tax to handle VAT compliance, that adds roughly 0.5% per transaction. The real cost for EU sellers is closer to 3.4% + $0.30. For international cards without Stripe Tax, add another 1.5%. Volume discounts are available but require direct negotiation with Stripe. Paddle. | Transaction type | Rate | | All transactions | 5% + $0.50 | | International cards | Same - no surcharge | | Monthly fee | None | Paddle charges a flat 5% + $0.50 regardless of card origin or country. For a $100 transaction, that's $5.50 in fees and $94.50 net. No volume discount tiers are listed publicly - rates are negotiable for high-volume merchants. True cost comparison. The fee gap looks large (2.9% vs 5%) until you factor in what each includes. | Scenario | Stripe true cost | Paddle true cost | | $100 domestic (US only) | $3.20 | $5.50 | | $100 domestic + Stripe Tax | ~$3.70 | $5.50 | | $100 international card | ~$4.70 | $5.50 | | $100 international + VAT | ~$5.20 | $5.50 | For US-only businesses, Stripe is clearly cheaper. For EU-heavy or globally distributed SaaS businesses, the gap shrinks significantly - and at a certain point Paddle's all-in pricing becomes competitive when you account for what you don't have to build or pay for separately. Tax and compliance. This is where the products diverge most sharply. Stripe does not handle tax compliance by default. You are responsible for: * Registering for VAT/GST in each country where you have nexus * Calculating the correct tax rate per transaction * Filing returns and remitting tax to each authority * Staying current with changing thresholds (e.g., EU OSS scheme) Stripe Tax partially addresses this - it calculates and collects the right tax amounts - but you still need to file returns and remit funds yourself, or use a third-party service like Avalara or TaxJar. Stripe Tax costs an additional 0.5% per transaction where it's active. For a US-only SaaS with fewer than ~5 states of nexus, this overhead is manageable. For a SaaS with global customers, it becomes a significant operational burden. Tax compliance is the core reason most founders choose Paddle. Because Paddle is the merchant of record, Paddle is legally responsible for collecting and remitting VAT, GST, and US sales tax globally. You never register for VAT in the EU. You never file a German tax return. Paddle handles all of it as part of the 5% + $0.50 fee. This also means: * Chargebacks are Paddle's legal liability, not yours * Refunds are processed by Paddle * Your invoices come from Paddle (which matters for B2B customers in VAT-registered countries) Subscription management. Both platforms have mature subscription billing, but the approach differs. Stripe Billing. Stripe Billing is a comprehensive subscription engine. It supports: * Free trials, usage-based billing, and metered charges * Proration on plan changes * Multiple currencies with automatic conversion * Smart Retry logic for failed payments (dunning) * Customer portal for self-service upgrades and cancellations * Flexible invoice customisation The API is extensive and well-documented, but implementing a full subscription flow requires engineering work. Most features are configurable, not out-of-the-box. Paddle Billing. Paddle Billing (the current product, distinct from the legacy Paddle Classic) offers: * Subscription management with trials, pauses, and cancellations * A hosted checkout overlay - no PCI scope on your end * Automatic dunning and recovery * A customer portal for self-service management * Localised checkout - prices shown in the customer's currency The main trade-off: Paddle's checkout is a hosted overlay. You have less control over the UI compared to building your own Stripe-powered checkout. This is a deliberate choice - Paddle owns the checkout because they're the merchant of record. Developer experience. Stripe's API is widely regarded as the best in the payments industry. The documentation is thorough, SDKs cover every major language, and the developer dashboard is excellent. Webhooks are reliable and well-structured. The flip side: because Stripe is so flexible, there are many ways to implement any given flow. Getting subscriptions, trials, proration, and tax right often takes longer than founders expect. Paddle's API is good but narrower - you're building within the constraints of Paddle's model. The upside is that many things are handled for you by default: checkout, tax, compliance. Less flexibility, less setup. Paddle's webhooks and API have improved significantly since the Paddle Billing rewrite. Teams moving from Paddle Classic to Paddle Billing should expect a migration effort. Analytics. Neither Stripe nor Paddle was designed to be your analytics platform. Stripe offers a basic dashboard for revenue and transaction monitoring, plus Stripe Sigma - a SQL-based tool for custom reporting. Sigma is powerful but requires SQL knowledge and isn't cheap. Paddle acquired ProfitWell in 2022 and offers ProfitWell Metrics (free MRR reporting) alongside Paddle's reporting dashboard. ProfitWell Metrics is useful for tracking headline numbers but has limited flexibility for custom analysis. For either platform, a dedicated analytics layer gives you visibility that the native tools don't: cohort analysis, LTV by plan, churn by acquisition channel, expansion MRR trends, and custom dashboards you can share with your team or investors. When to Choose Stripe. Choose Stripe if: * You're US-focused and don't have significant EU or global exposure * You have engineering resources to build and maintain the integration * You want maximum control over checkout UX, billing logic, and integrations * You're at a scale where custom pricing negotiations make the lower base rate worth it * You already use Stripe and the switching cost isn't justified When to Choose Paddle. Choose Paddle if: * You sell globally and don't want to deal with VAT registration in 30+ countries * You're a small team or indie developer where compliance overhead is a real constraint * You want an all-in price that covers tax, chargebacks, and compliance * You don't have the engineering resources to build a robust Stripe integration * You want to move fast without a legal or finance overhead Summary. You can also compare Stripe, Paddle, and every other major payment processor side by side - including calculated fees at your exact transaction amount - using its free payment fee comparison tool. | / | Stripe | Paddle | | Type | Payment gateway | Merchant of Record | | Base rate | 2.9% + $0.30 | 5% + $0.50 | | International surcharge | +1.5% | None | | VAT/GST handling | You (via Stripe Tax, paid) | Included | | US sales tax | You (via Stripe Tax, paid) | Included | | Chargeback liability | You | Paddle | | Checkout UI control | Full | Hosted overlay | | Developer flexibility | High | Medium | | Setup complexity | Higher | Lower | | Best for | US-focused / tech teams | Global / lean teams | One more thing: knowing your numbers. Whichever processor you choose, your payment processor is where your revenue data lives - but it's rarely enough on its own to understand your business. Chartsy connects to both Stripe and Paddle and gives you the analytics layer neither provides natively: MRR and ARR calculated from actual invoice data, churn breakdowns by plan and cohort, LTV analysis, expansion and contraction MRR tracking, and an AI-powered interface where you can ask any question in plain English and get an instant chart. Whether you're on Stripe, Paddle, or both, Chartsy turns your payment data into the dashboards and reports that actually drive decisions.

Akamaru
Apr 6th, 2026
Paddle vs Stripe for non-US SaaS in 2026.

Paddle vs Stripe for non-US SaaS in 2026. Stripe is the obvious pick until you realize you have to hand-roll sales tax compliance across 40+ jurisdictions. Here's when Paddle is the better default - and when it isn't. If you're a solo SaaS founder living outside the United States and you default to Stripe, you're also signing up to personally manage sales tax compliance in every jurisdiction where you have a customer. Nobody tells you this up front. I found out the hard way. This post is the billing-processor decision I wish someone had written for me 18 months ago. The core difference, in one sentence. Stripe is a payment processor. Paddle is a Merchant of Record. Everything else - fees, UX, webhook quality, checkout ergonomics - flows from that. Once you understand the MoR model, most of the "which is better" discussion resolves itself. What "Merchant of Record" actually means. When a customer buys from you via Stripe, the legal transaction is: customer | your business. You are the merchant. Your business name on their credit card statement. Your responsibility to file sales tax with 40+ US states, the UK, the EU's OSS scheme, Canada, Australia, Japan, Norway, Switzerland, and so on. When a customer buys from you via Paddle, the legal transaction is: customer | Paddle | your business. Paddle is the merchant. Their name on the credit card statement. Their responsibility to file sales tax everywhere they do business. That's the entire pitch. The math, honestly. Stripe's fee is about 2.9% + $0.30 for standard card payments. Paddle's fee is 5% + $0.50. On a $149 sale: * Stripe: ~$4.62 in fees, you keep $144.38 * Paddle: ~$7.95 in fees, you keep $141.05 Paddle is more expensive per transaction. If you process 100 sales a year, that's $333 extra. Is $333/year worth the sales tax compliance handling? The answer depends on the stack Stripe users actually need to build: * Stripe Tax - $150/mo for the basic tier as of 2026, covers most US states but not all international VAT regimes. You're still on the hook for filing in jurisdictions Stripe Tax doesn't handle. * A tax accountant - €1,000-3,000/year minimum for EU filings, more if you have customers in multiple regions. Plus your time spent gathering data every quarter. * TaxJar / Avalara / Quaderno - $50-500/mo depending on volume, plus annual filing fees per jurisdiction. At realistic solo-founder volume, you spend more hours and more dollars managing Stripe Tax + a filing service than you would on Paddle's 2.1-percentage-point fee difference. And crucially, you trade those extra dollars for zero personal tax liability across 40+ countries. For a US-based founder with a US accountant already on retainer and domestic-only customers? Stripe might still be cheaper. For a solo founder in Lithuania, Georgia, Portugal, Brazil, or anywhere else shipping to global customers, Paddle is almost always the better economic decision. What Paddle gets right (beyond MoR). Beyond the tax thing, a few operational wins I didn't expect: Webhook ergonomics are better. Paddle v2 ships with ~25 event types. Stripe ships with ~200. Most of Stripe's events exist for legacy reasons or features you'll never use. Paddle's event list reads like a product you can actually keep in your head. Idempotency is built into the request primitives. Every webhook has a unique event ID. Deduplication is a three-line database check. Stripe does this too, but the docs bury it; in Paddle it's front and center. Inline checkout without a hosted redirect. Paddle has a JavaScript SDK that opens a checkout modal over your page. Customers stay on your domain throughout. Stripe has Checkout for this, but their "pay in place" option (Payment Element) requires more setup than Paddle's one-line integration. Refunds are a button in their dashboard. Stripe refunds are a button too, but Paddle's default refund flow includes the tax reversal automatically; Stripe leaves tax recovery to your accounting workflow. What Paddle gets wrong. Real weaknesses, in case Paddle marketing makes it sound too perfect: Checkout customization is limited. You can brand colors, logos, and a few text fields. You cannot restructure the checkout flow. If you want a multi-step wizard or deep A/B testing on the checkout page, Stripe gives you more control. Subscription edge cases are thinner. Usage-based billing, mid-cycle plan switches with prorated credits, complex metered pricing - Stripe's API exposes more of this natively. Paddle can do most of it, but you'll hit "not quite what we wanted" walls more often. Payout frequency is slower. Paddle pays out weekly. Stripe pays out daily in most supported countries. Not a dealbreaker, but something to plan your cash flow around. International card acceptance is marginally worse in some regions. Stripe's authorization rates in Latin America and Southeast Asia are a few points higher on average. If those are your primary markets, test both. My rule of thumb. Use Paddle if: * You live outside the US * You sell to global customers * Your product is straightforward to price (flat tiers, per-seat, or simple usage caps) * You'd rather pay 2% more than spend 40 hours a year on tax compliance Use Stripe if: * You live in the US and only sell to US customers * You need subscription mechanics that require Stripe's full API surface * You have an accountant you trust for international filings * You're building something where checkout flow is core to conversion and you need control over every pixel For most solo founders, I think Paddle is the better default in 2026 than it was in 2020, and the gap is widening as global sales tax regimes get more aggressive. The boilerplate angle. Akamaru ships with Paddle v2 wired by default - inline checkout, HMAC-verified webhooks, refund flow, customer portal - because I built it for builders who weren't going to want to hand-roll MoR compliance themselves. If you need Stripe instead, swapping the billing provider is documented as a provider-swap guide in the repo. Paddle is also where most people get stuck during setup - pasting the webhook signing secret into the wrong env var is the single most common failure mode. Akamaru's setup coach catches that exact paste error via prefix regex before it becomes a silent 401 in production. See the 30-second demo on the landing page for what that looks like end-to-end. Either way, don't spend the first month of your SaaS becoming a tax lawyer. The hours compound for the wrong things. Akamaru is a production-ready React + Express SaaS boilerplate. See what's inside

Collectic
Nov 15th, 2025
The Priority Scoring Formula That Changed How We Build

The priority scoring formula that changed how Collectic build. Discover how Collectic uses votes, ARR impact, and effort estimates to automatically prioritize your product roadmap with data instead of gut feeling. Learn how Collectic uses OpenAI embeddings and clustering algorithms to automatically detect and merge duplicate feedback, saving you hours of manual work. Learn why passwordless magic link authentication removes friction for voters while keeping your feedback board secure and spam-free. Stop guessing what to build next. Most founders prioritize features by gut feeling. Which requests are loudest? What seems most important? Which customer complained most recently? This leads to building features that don't move the needle, ignoring high-value requests from paying customers, and wasting time on low-impact work. The priority scoring formula. Collectic uses a simple but powerful formula to automatically score every idea: Let's break down each component and why it matters. Votes: what users want. Every upvote represents a user saying "I want this." More votes mean more people will benefit from the feature. Simple and democratic. With Collectic's public feedback board, users can vote on ideas from any channel. The votes automatically aggregate, even when duplicates are merged. ARR impact: what matters for revenue. Not all votes are equal. A request from a customer paying $10,000/year should weigh more than free trial users. That's where ARR impact comes in. Collectic integrates with Paddle and LemonSqueezy to automatically track the annual recurring revenue of each voter. High-value customers automatically boost the priority of their requests. Effort estimate: what you can build. A feature with 100 votes that takes 3 months might be less valuable than one with 50 votes you can ship in a week. Effort matters. Tag each idea as Small, Medium, or Large effort. Collectic divides by this to surface quick wins - features with high impact and low effort. Real example: making decisions. Here are three real feature requests from a Collectic user: * Dark mode: 45 votes, $12K ARR, Large effort | Score: 180 * CSV export: 12 votes, $8K ARR, Small effort | Score: 384 * API access: 8 votes, $24K ARR, Medium effort | Score: 192 Without data, you'd probably build dark mode first (most votes). But the math shows CSV export has 2x the impact per hour of work. Ship that first, delight users faster, and keep momentum. Automatic updates. The beauty of automated scoring is that it updates in real-time. As more users vote, as paying customers upgrade, as you refine effort estimates - your priorities automatically adjust. Your roadmap stays relevant without manual spreadsheet updates. Just check your Collectic kanban board and work from the top down.

Finovate
Jul 18th, 2025
Paddle Raises $25 Million for Payments Infrastructure

Payments infrastructure company Paddle announced this week it has raised $25 million in debt financing from CIBC Innovation Banking and others.