Wingback

Name: Wingback
Brand: Wingback

AI Native

B2B SaaS pricing and billing platform - ship the right products to the right customer at the right price. YC W22, ODF.

Est 2021|Valuation $9.3M|Raised $2.4M

LinkedIn 384|Website|FTEs 14|HQ Remote, Oregon, US

MarketsDynamic Pricing & Subscription Management Subscription Management & Recurring Billing

01Competitive Landscape

Narrative analysis

- Wingback vs Stripe Billing - The vendor presents Wingback as an alternative to Stripe Billing for billing feature management while continuing to use Stripe for payment processing. The vendor differentiates on hybrid pricing support, a low-code plan iteration interface, and packaged customer-facing components. - Stripe's advantages are its payments ecosystem maturity, broad adoption, and extensive third-party integrations and documentation. - Wingback vs Chargebee - The vendor publishes a comparison against Chargebee that highlights differences in pricing model flexibility and MRR calculation methods; these vendor-provided comparisons should be validated against current Chargebee documentation and independent benchmarks. - Chargebee emphasizes billing, invoicing, CPQ, and usage/hybrid billing options and has an established market position. - Other alternatives - Recurly: positions on transparent starter pricing and subscription growth tooling. - Orb / Metronome: frequently evaluated when teams prefer engineering-first, developer-centric usage metering and billing approaches.

	Wingback	Stripe Billing	Chargebee
Starting Price	Third-party reporting lists "Early" and "Growth" tiers at published monthly prices; vendor also references a transaction-based fee (structure unclear)	Usage-based pricing; published vendor pricing available	Public pricing includes tiered plans with thresholds and overage models; details vary by plan
Best For	B2B SaaS teams seeking hybrid/feature-based billing with built-in customer-facing components and lower-code plan iteration	Teams already standardized on Stripe requiring payments + billing integration with broad PSP capabilities	Mid-market and enterprise subscription businesses that need billing, CPQ, and revenue recognition features in a single suite
Key Strength	Hybrid pricing and non-technical plan management plus built-in self-serve components (vendor positioning)	Mature payments ecosystem, extensive documentation, and broad adoption	Comprehensive monetization suite with established market presence and billing/CPQ-focused features
Key Weakness	Limited independent review footprint; security and compliance posture not clearly documented publicly; transaction-based fee structure is not public in accessible sources	Complexity can increase with custom pricing/entitlements and advanced usage-based models	Some users report workflow and support friction in community discussions; complexity in specific pricing models may require workarounds

01Competitive Landscape

Narrative analysis

Wingback vs Stripe Billing
- The vendor presents Wingback as an alternative to Stripe Billing for billing feature management while continuing to use Stripe for payment processing. The vendor differentiates on hybrid pricing support, a low-code plan iteration interface, and packaged customer-facing components.
- Stripe's advantages are its payments ecosystem maturity, broad adoption, and extensive third-party integrations and documentation.
Wingback vs Chargebee
- The vendor publishes a comparison against Chargebee that highlights differences in pricing model flexibility and MRR calculation methods; these vendor-provided comparisons should be validated against current Chargebee documentation and independent benchmarks.
- Chargebee emphasizes billing, invoicing, CPQ, and usage/hybrid billing options and has an established market position.
Other alternatives
- Recurly: positions on transparent starter pricing and subscription growth tooling.
- Orb / Metronome: frequently evaluated when teams prefer engineering-first, developer-centric usage metering and billing approaches.

	Wingback	Stripe Billing	Chargebee
Starting Price	Third-party reporting lists "Early" and "Growth" tiers at published monthly prices; vendor also references a transaction-based fee (structure unclear)	Usage-based pricing; published vendor pricing available	Public pricing includes tiered plans with thresholds and overage models; details vary by plan
Best For	B2B SaaS teams seeking hybrid/feature-based billing with built-in customer-facing components and lower-code plan iteration	Teams already standardized on Stripe requiring payments + billing integration with broad PSP capabilities	Mid-market and enterprise subscription businesses that need billing, CPQ, and revenue recognition features in a single suite
Key Strength	Hybrid pricing and non-technical plan management plus built-in self-serve components (vendor positioning)	Mature payments ecosystem, extensive documentation, and broad adoption	Comprehensive monetization suite with established market presence and billing/CPQ-focused features
Key Weakness	Limited independent review footprint; security and compliance posture not clearly documented publicly; transaction-based fee structure is not public in accessible sources	Complexity can increase with custom pricing/entitlements and advanced usage-based models	Some users report workflow and support friction in community discussions; complexity in specific pricing models may require workarounds