What's changing in RunwayCal.

• Product
• Integrations
• Data

True Cash Position, tax obligations, and reviewed Stripe inputs

Mission Control added True Cash Position beside held-cash and recorded-obligation context. The same release period introduced tax-obligation tracking and the restricted Stripe connection documented in the product today.

What changed

• True Cash Position became a separate planning metric rather than another name for a bank balance.
• Recorded tax obligations became part of the financial context visible to the user.
• The Stripe path used restricted access and review boundaries instead of claiming a general bank feed or automatic reconciliation.

Why it matters

The release made it easier to distinguish cash held from the wider obligations and timing that shape a financial decision.

• Website
• Billing

Website redesign and a new pricing structure

RunwayCal rebuilt its marketing website, expanded its product and solution explanations, and introduced the pricing structure available at that time.

What changed

• The website moved toward a broader product, persona, industry, and financial-needs architecture.
• Pricing and plan packaging were revised for the release period.
• Product and solution pages began carrying clearer decision and capability boundaries.

Why it matters

The update gave buyers more context about the product before entering the application or choosing a plan.

• Planning
• Reporting
• Product

Scenarios, Board Access, and deterministic financial signals

RunwayCal added scenario modeling, a bounded read-only Board Access path, and an expanded set of rules-based financial signals.

What changed

• Scenarios made it possible to compare hypothetical changes without silently rewriting recorded financial reality.
• Board Access provided a focused read-only reporting window with user-controlled sharing and revocation.
• The supported rules-based signal set expanded to 23 insights, including runway, revenue-concentration, and cash-flow milestone context.

Why it matters

Planning alternatives, reporting access, and operating signals became separate product jobs instead of being presented as one undifferentiated dashboard.