A product team wants to move a well-loved feature, say audit logs, out of the middle plan and into the top one. The roadmap owner expects upgrades, customer success expects cancellations, and sales expects a week of angry emails. Nobody can say how many customers would do which. Replacing that guess with evidence is why this seat exists. It is one of the remote saas pricing analyst jobs that sits close to product strategy: full-time, on $75,000 a year, paid in USD, and worked from home, whatever country that home is in.
That is the short version of the SaaS pricing analyst job description: you design price policy rather than police it. Deal desk colleagues approve exceptions on individual quotes; you decide what the list prices, plan boundaries and standard discount bands should be in the first place, and you show your working.
Many subscription products sell a small set of plans, and each boundary between them is a fence. A fence can be a usage limit, a seat count, a feature such as single sign-on, or a support level. Your first model is usually a map of which customers sit near each fence and what they actually use. If a large share of mid-tier accounts already touch the feature under discussion every week, moving it upward is a price rise for them, whatever the launch note calls it.
In practice this is a spreadsheet fed by SQL extracts: one row per account, with plan, seats, gated-feature usage, contract value and renewal date. From there you test packaging options side by side. What happens to average revenue per account if the feature moves up? How many accounts would hit the new fence in their first billing cycle? Which value metric, seats or usage, tracks the value customers report most closely?
Discounts drift. An annual-prepay incentive gets stacked with a multi-year discount and a competitive match, and the realised price wanders from list without anyone deciding it should. You model discount policy the way an economist models a tax: who uses it, what behaviour it changes and what it costs.
Much of your week goes into SQL against the warehouse, joining CRM opportunities with billing subscriptions and product usage events. The core cuts sound simple: win rate by plan and deal size, churn by plan and tenure, and expansion through upgrades, seats or overage.
The value lies in the awkward parts. Plan names change, migrated accounts carry legacy prices, and a downgrade followed by expansion counts as one event or two depending on the cohort definition. You document those definitions so everyone argues about the same number, then chart the result: a churn curve per plan, or discount depth plotted against renewal.
Usage data shows what customers did at today's prices. Surveys estimate what they might do at prices you have never charged. The Van Westendorp price sensitivity meter asks respondents four questions about when a product feels too cheap, a bargain, getting expensive and too expensive, and the crossing points of those curves suggest an acceptable range. It is quick to field. Its weakness is that people judge price in isolation, with no alternatives and no money at stake.
Conjoint analysis asks respondents to choose between bundles that vary in features and price, then estimates how much each attribute is worth to them. It captures trade-offs better but needs careful design, a decent sample and statistical modelling, and it still measures stated preference. Respondents can overstate what they would pay, and a survey panel may not mirror your buyers. You run both and say plainly how far to trust them.
Sometimes the best evidence is a live test: a new self-serve price for a share of visitors, a reworded plan page, a different trial length. Pricing tests have their own traps.
Product wants to know what a change means for adoption and the roadmap. Finance wants the effect on bookings, net revenue retention and margin, with downside cases. The format that works is a short memo with one main chart, a clear recommendation, the assumptions it rests on and what would change your mind, with the workbook behind it.
Back to the audit logs. A good answer might move the feature up for new customers only, let existing mid-tier accounts keep it until renewal, and review churn and upgrades after two renewal cycles.
Remote pricing work depends on access. Expect read access to a cloud data warehouse, a BI or notebook tool for analysis, the CRM and billing system for spot checks, and the experimentation or feature-flag platform used for checkout tests. Customer-level and revenue data is sensitive, so access usually runs through company devices, single sign-on and role-based permissions, and you may work mostly with aggregated or anonymised extracts. Survey platforms are usually licensed centrally, so check what exists before suggesting new tools.
You will need a degree in economics, finance, statistics or a related field, backed by two to four years of hands-on pricing, revenue or business analytics work. Strong SQL and Excel modelling are needed, as is hands-on experience with pricing surveys such as Van Westendorp or conjoint, and the ability to present clear recommendations to leadership. Among SaaS pricing analyst skills, presenting gets the least practice, yet it decides whether a model changes anything. The SaaS pricing analyst salary per year attached to this seat is $75,000 USD, full-time.
A SaaS pricing analyst course or certificate can help; read its current syllabus and fees first. A worked case study usually counts for more: a teardown of a public pricing page, a small Van Westendorp study, or a price waterfall from anonymised data.
SaaS pricing analyst interview questions tend to pair a SQL task on subscription data with a packaging case. That same case study is the backbone of a good resume: decisions influenced and results measured, rather than a list of tools.
A revenue analyst usually focuses on reporting and forecasting: bookings, recurring revenue, retention and variance against plan. A pricing analyst uses much of the same data to ask a different question, namely what the company should charge and how plans should be built. The revenue analyst explains what happened; you propose what should change and estimate its effect. People move between the two, but this role is weighted towards packaging, willingness-to-pay research and experiments.
Pricing teams exist at subscription software companies of many sizes, from product-led startups with a self-serve checkout to large enterprise software vendors with complex contracts, and at billing and pricing software providers and consultancies that advise SaaS firms on packaging. A common route is analyst, then senior analyst or pricing manager owning a product line, then director of pricing or monetisation, with head of monetisation covering pricing, packaging and sometimes billing strategy across the business. How quickly anyone climbs depends on the company and on the calls they get right.