About Wingback
Wingback provided tools and APIs for SaaS pricing and packaging. The idea was simple to state: a SaaS company should be able to ship any set of features of its product under any pricing model, and changing pricing should not require engineering work. Yann and I started Wingback in 2021.
After 1aim was acquired, I was not really sure what to do next. I helped a few founder friends with their companies and traveled for a while, but I wanted to build something myself again. In late 2020 I joined On Deck, which was a genuinely outstanding program. Through it I met a lot of founders, most of them building software. I spent months talking with them about what was actually hard in their businesses, and pricing and packaging kept coming up. Everyone had a view on what their pricing should be. Almost nobody had a way to implement it without pulling engineers off the roadmap for weeks. It was an interesting, unsolved, and massive problem, and that is why I started Wingback.
It was a very different company from 1aim. There was no hardware and nothing to install in a building. It was just software, sold to other software companies. It was also a huge step. We got into Y Combinator, raised a seed round with exactly the investors we had hoped for, and brought together a team of great people. YC was an incredible experience. For three months we were part of a batch with some of the best founders in the world. When the batch ended, we were on a high. Turning that into as much growth as we expected was another story, and what followed was a rollercoaster.
Wingback was founded during COVID, so we built it remote-first. That was a bigger shift than it sounds. At 1aim we had been in the office 100 percent of the time, no hybrid, no working from home, and we considered that essential to how we worked. We worked with Marissa Goldberg, who knew remote companies well, and rebuilt the way we worked around it. The team ended up spread across five continents. We hired most of them without having met in person, and some of them I never met in person at all. It worked better than I expected. Bringing so many great people together from all over the world was one of the best parts of Wingback.
What we built
Pricing in most SaaS companies is sort of an afterthought. Someone decides on the plans, and an engineer builds them into the product. From then on, every change goes back to that engineer: a new tier, a discount for one customer, a feature that should move from one plan to another, a usage limit that turned out to be wrong. Each one becomes a ticket, and each ticket competes with the roadmap for actual product features. So most companies focus on product and then leave pricing alone for years.
The cost is easy to miss, because it is revenue that never shows up. Different customers are willing to pay very different amounts for the same product, and three fixed plans do not let them. We used to say the goal was to go from product-market fit to product-market-pricing fit.
The layer in between
We called what we built SaaS Growth Infrastructure. In practice it was a layer between a company’s features and its billing processor, usually Stripe. Every feature of a customer’s product was mapped into Wingback once. A plan was a set of those features with a pricing logic attached. Instead of carrying the rules for the pricing logic in its own code, the product asked Wingback what a given customer could access. Usage was metered against the same plans, and billing was generated from the same data.
Our product was a plan editor, entitlement management with usage metering, self-serve signup components and billing, with APIs underneath. Feature definition all the way through to accurate invoicing.
Mix and match
There is no pricing model that fits every customer, so we did not make anyone pick one. Feature sets, packages and pricing logics could be combined freely, and several could run at the same time. A plan could be a flat fee, per seat, usage based, tiered, or any combination of those. That included combinations such as per seat and usage-based pricing in the same plan.
Add-ons were a big part of it. SaaS features are like burrito toppings, and everyone wants to add guac. So let them. With Wingback, a customer could add the features they wanted, when they wanted them, without anyone on the vendor’s side writing code for it.
A plan could also be built for exactly one customer. For an early-stage company, that could be the difference between closing a deal and explaining why the product could not be sold that way. A new plan went live in minutes rather than weeks, so testing a pricing idea stopped being a project. Finding the right pricing for a market can take months. Our job was to make sure the engineering was not the bottleneck for finding the right pricing anymore.
Built for non-engineers
Wingback was designed so that anyone on a SaaS team could use it. Sales, ops or growth could change pricing themselves, and the engineers could get back to the product. Most of that happened in three places.
Plan Editor: This was where plans were created and changed, in an interface rather than in code.
Customer Management Portal: This was for everything after a sale: customer data and payment options, additional services, and fine-tuning a plan that had already been sold.
Billing Portal: This was for the end customer, with signup, payment tracking and the option to manage their own payment details.
We sold to SaaS companies at very different stages, early and late, self-serve and sales-led, and the problem looked different in each. An early-stage company did not have the time or the engineers to build a custom plan for one customer, even when that customer was ready to sign. A late-stage self-serve company wanted to run product-led growth campaigns and found its pricing could not keep up. A late-stage company with a sales team lost time on every non-standard deal, because sales had to wait for engineering, and it frustrated everyone involved. The product was the same for all of them. What it fixed was not.
Timing
Timing was not our friend. When we started, pricing and packaging was near the top of the list for SaaS companies, because getting more out of every existing customer was where growth had to come from. Then the market turned. The funding environment tightened in 2022, and our customers went into survival mode. Some of them did not make it. We had built a product for a market that looked very different by the time the product was ready. For a startup to work, a lot of things have to come together at the same time.