Skip to content
AppDues
Log in
Contact salesSign up

Val Agostino on Monarch Money, subscription models, and building for the long haul

Building a subscription app takes time, skill, and capital. Val Agostino, a co-founder of Monarch Money, argues that another ingredient matters just as much: sustained passion for the problem. In a Sub Club podcast conversation, he explains how that passion shapes the choice of customer, the way a team validates product decisions, and the ability to look past a feature request to the need underneath it.

Choose your customer wisely

A monetization decision is also a customer decision. In an ad-supported app, the people paying are advertisers, and the product must keep generating ad revenue. Val Agostino describes the result as a worse experience for users because the revenue team and the product team end up pulling in different directions. He points to Mint as an example: the financial app was ad-supported from the start, and that tension showed up in questions about how many offers could be placed in front of a user in a single session.

A subscription model changes who the business answers to. Users pay directly, so their experience becomes the commercial priority. After Mint was acquired and shut down in 2024, Monarch Money had an opening to attract former Mint users with a subscription-based product built around the user rather than around ad inventory.

Use this as a decision checklist when choosing a model:

  • Identify who actually pays you. If advertisers pay, their goals will shape the product.
  • Ask whether your team can resolve conflicts between revenue targets and user experience without constant internal friction.
  • Consider whether your audience expects a direct, paid relationship with the product.
  • Check whether a subscription price can support the experience you want to deliver.
  • Treat a competitor's shutdown or model change as a moment to examine user expectations, not as an automatic growth opportunity.

Raising the bar for MVP

The familiar startup advice to ship quickly and iterate has limits. Agostino describes the usual loop: launch something, watch how people respond, adjust, and launch again. That loop is slow. Several cycles can pass before the product lands where the team intended, and each cycle costs calendar time.

Monarch Money tried to reduce that waste by doing more work before release. The team built clickable prototypes of requested features and asked customers a direct question: would this feature solve your problem? Feedback on a prototype is faster and cheaper than feedback on shipped software, and it lets the team release a stronger product in fewer iterations.

A practical validation loop looks like this:

  1. Capture the request in the customer's own words.
  2. Build a clickable prototype that shows the proposed behavior.
  3. Ask whether the prototype solves the stated problem.
  4. Revise or discard before committing engineering time.
  5. Ship only when the prototype has answered the question.

This does not mean avoiding release forever. It means spending upfront effort on the decisions that are expensive to reverse later.

Going beyond app features

A sticky app solves a real pain point, and the pain point is not always the same as the feature request. Agostino and his team use the Jobs to Be Done framework and the Five Whys to reach the underlying reason. The Five Whys method asks why repeatedly until the root cause becomes clear.

Monarch Money's due dates on bills feature shows how this works. Customers wanted to see when upcoming bills were due. One reason was practical: users with ADHD needed all upcoming expenses in one place. Another benefit was knowing there was enough cash in the bank to cover those bills. The deeper reason was peace of mind.

Once a team understands that emotional reason, it can build a more complete feature and may add capabilities customers would not have thought to request. Agostino has said that his motivation behind better financial health tools is partly personal: he has been through periods when money was tight and his family benefited from financial planning tools. He also cites a wider need, quoting the claim that finances are the number one source of stress in American families, and points to the real impact such products can have on people's lives.

A useful distinction for product teams:

  • A feature request describes a proposed solution.
  • A job describes the progress the customer wants to make.
  • An emotional reason explains why the job matters.
  • A robust feature addresses all three, not just the first.

Frequently asked questions

Why does Val Agostino prefer a subscription model over an ad-supported one?

He argues that an ad-supported model makes advertisers the real customer. The product then has to keep increasing ad revenue, which can degrade the user experience. A subscription model makes users the paying customer and aligns the product with their experience.

What is the difference between shipping fast and validating with prototypes?

Shipping fast moves a version into the world and learns from usage data. Prototype validation asks customers whether a proposed feature solves their problem before engineering work begins. Both involve feedback, but prototypes reduce the cost of a wrong turn.

How does the Five Whys method help with feature requests?

It pushes past the requested feature to the reason behind it. In the Monarch Money example, a request to see bill due dates led to practical needs and, ultimately, to peace of mind. That deeper understanding can shape a better feature.