Runway

Name: Runway
Brand: Runway
Rating: 1.5 (222 reviews)

AI Native

FP&A that drives better decisions, faster

Est 2020|Valuation $117.5M|Raised $47.5M|56 Ref Customers

LinkedIn 17K|Web traffic 73K|FTEs 26|HQ San Francisco, California, US

MarketsFP&A Management Reporting Budgeting & Forecasting

Published Oct 15, 2026

01Common complaints

- Organizations with a single-person finance function seeking an out-of-the-box solution requiring minimal configuration and internal effort; community feedback indicates a substantial learning curve in some deployments. - Organizations that require transparent, published pricing to support procurement or budgeting decisions. - Organizations whose primary requirement is to remain entirely spreadsheet-driven with minimal behavior change; spreadsheet-first vendors may be more appropriate. - Buyers seeking the longest-established enterprise vendor footprint and partner ecosystem for very large-scale deployments; incumbents may offer broader enterprise maturity for certain requirements. - Organizations that cannot tolerate potential brand confusion during evaluation between runway.com (FP&A) and runwayml.com (creative AI).

Deal disqualifiers (poor fit)

Very small finance teams lacking time to implement or administer a new platform.
Requirements for fully transparent, published pricing during initial vendor shortlisting.
Environments with unusually complex legal/entity/accounting structures where extensive customization and pilot validation are required.

Publicly observable limitations / gaps

Public pricing is not available, which limits quick benchmarking and creates procurement friction.
Some reviewers report that ongoing changes can be challenging without vendor involvement; this suggests potential dependency on customer success for certain change scenarios.
Brand and review confusion between runway.com (FP&A) and runwayml.com (creative AI) complicates third-party review interpretation.

Roadmap / future features

No detailed public roadmap with release dates was located in the reviewed sources. Buyers should request the vendor’s roadmap, release notes, and product development cadence during commercial diligence.

02Why they buy

Observed / partially validated from vendor content and customer narratives: - Cross-functional self-service planning where departmental stakeholders can build scenarios and collaborate without constant finance-led consolidation. - Rapid scenario planning capabilities and support for multi-scenario comparison. Vendor-claimed unique selling points that require validation during procurement: - Large efficiency multipliers reported in vendor case studies; buyers should request measurement methodology and baseline comparisons. - Vendor-reported integration counts and available connectors; buyers should confirm connector availability and any tier-based limits relevant to their needs. - AI-labeled features for variance explanations and workflow acceleration; buyers should test these features in pilot workflows to understand practical utility. Balanced view: - The combination of structured modeling, collaborative inputs, and integrated actuals is the core value proposition, but realizing this value typically requires configuration, data cleanup, and internal ownership.

Why customers chose Runway (patterns)

From customer stories and review summaries, common selection drivers include:

Reducing spreadsheet versioning and manual consolidation.
Faster scenario planning.
Live actuals syncing via integrations.
Enabling self-service visibility for non-finance stakeholders.

Vendor-claimed unique selling points that require validation during procurement:

Key Differentiator

03Field reports

Review platforms (G2)

There is a notable risk of review conflation between the FP&A product and the creative AI product on review sites. - On G2, separate listings can reflect different products: a Runway FP&A listing and other Runway listings that refer to creative AI/video generation. - Review content that refers explicitly to video credits or generative video output appears to relate to the creative AI product rather than the FP&A product. #### Representative positive feedback (Runway Financial on G2) A G2 reviewer in a mid-market finance role described the customer success organization positively and reported the product scaled to their needs, while noting onboarding complexity. #### Representative negative or cautionary feedback (mixed listings on G2) Some reviews refer to problems with video output, credit usage, and refunds; those items appear to pertain to the creative AI product rather than the FP&A offering. The existence of such reviews is operationally relevant because it can cause confusion for buyers searching Runway reviews.

Community discussions (Reddit)

A Reddit thread in r/FPandA included: - Positive comparisons to Adaptive Planning: one commenter stated that Runway felt substantially more flexible in cube modeling and praised available documentation. - A cautionary report for very small teams: a commenter reported a steep learning curve for a single-person accounting team and described support as insufficient to complete implementation; this commenter suggested that the organization might have been better served by remaining with spreadsheet workflows. Another Reddit post comparing Runway to other FP&A entrants raised skepticism about feature completeness in newer vendors, which is a common buyer concern when evaluating newer providers.

Why customers may leave or not purchase (patterns)

If implementation requires extensive vendor involvement or a dedicated FP&A owner, smaller teams may find the solution unsuitable.
Lack of public pricing can complicate ROI justification.
Expectations that the platform will match simple spreadsheet workflows may lead to dissatisfaction when a learning curve exists.

1) Developer-focused platform (vendor customer story)

Stated outcomes:

Replaced multi-tab spreadsheets used for consolidation.
Reduced monthly manual update effort.

Critical evaluation:

These outcomes are plausible following migration from manual spreadsheet consolidation to integrated reporting.
The metrics are vendor-published and lack independent validation.
Success appears to depend on source data quality and having clear internal ownership over the model.

2) Large talent/investment platform (vendor customer story)

Stated outcomes:

Single source of truth and reduced time validating metrics.
Enabled cohort-based predictive modeling and faster business reviews.

Critical evaluation:

Multidimensional cohort modeling is typically challenging in spreadsheets; dedicated FP&A tools can materially improve this capability.
The case study outcomes are largely qualitative and lack disclosed measurement methodology.

3) Email/productivity company (vendor customer story)

Stated outcomes:

A large efficiency multiplier is reported in the vendor material, along with broader departmental self-service for scenario building.

Critical evaluation:

Large multipliers can occur when the baseline process is highly manual; without specifics on which tasks were measured and the measurement approach, reported multipliers should be treated as directional and vendor-provided rather than independently validated.

04Best fit

Company size

A practical fit is often mid-sized to larger organizations with an established planning cadence that incorporates cross-functional inputs.

Industries / verticals

SaaS / technology
Fintech
High-growth consumer and marketplace businesses

Roles and personas

Decision makers: CFO, VP Finance, Head of FP&A, Head of BizOps
Champions/admins: FP&A manager/analyst, finance systems owner
End users: department heads (Sales/Marketing/Ops), executive leadership

Key pains addressed

Spreadsheet sprawl and version-control challenges
Manual monthly updates and reconciliations
Slow scenario planning cycles
Finance bottlenecks where stakeholders await updated numbers

Qualification criteria (indicative)

Presence of at least one dedicated owner to build and maintain the model.
Source systems (accounting, HR, CRM, data warehouse) that are reasonably accessible for integration.
A need for cross-functional planning rather than finance-only budgeting.

05The pitch

What the product does (objective value proposition)

Runway is a cloud FP&A platform intended for collaborative budgeting, forecasting, scenario planning, and interactive reporting. The vendor presents the product as an alternative to spreadsheet-centric planning by providing a centralized, structured financial model that syncs with actuals from accounting, HR, CRM, and other data systems and supports multi-scenario what-if analysis. Key product capabilities described by the vendor include: - Scenario planning and rapid what-if simulation (for example: hiring changes, funding delay, marketing spend shifts). - Collaborative budgeting with structured inputs (intended to reduce spreadsheet versioning and manual consolidation). - Revenue planning tied to CRM/pipeline and operational drivers. - Forecasting that updates with actuals through integrations. - Variance analysis (Budgets vs Actuals), reporting dashboards, and narrative/board-ready reporting. - AI-labeled features described by the vendor as workflow accelerators (for example, variance drill-down/explanations); some of these features are described as Beta. Important ambiguity / brand collision: “Runway” is also widely known as RunwayML, a separate company offering AI creative/video generation tools. Some review platforms and search results conflate these entities or display profiles that refer to the creative AI product rather than the FP&A product. This report focuses on Runway FP&A; buyers should verify that third-party content applies to the FP&A product before using it in procurement decisions.

Target market and positioning

Runway is positioned toward companies seeking faster planning cycles, improved collaboration across departments, and automation of forecast and reporting updates—particularly organizations moving beyond Excel/Google Sheets. Vendor messaging highlights rapid simulation, collaboration, and a user interface described by the vendor as similar to recent assistant-style finance tools. Evidence from customer stories and vendor materials suggests typical targets include: - Tech/SaaS and venture-backed companies - Finance and BizOps teams modernizing planning - Cross-functional stakeholders (Sales/Marketing/Ops) who require self-service financial visibility

Get a comprehensive analysis of Runway including market position, competitive landscape, adoption trends, and peer benchmarks.

Download full report →

Published Oct 15, 2026

01Common complaints

Organizations with a single-person finance function seeking an out-of-the-box solution requiring minimal configuration and internal effort; community feedback indicates a substantial learning curve in some deployments.
Organizations that require transparent, published pricing to support procurement or budgeting decisions.
Organizations whose primary requirement is to remain entirely spreadsheet-driven with minimal behavior change; spreadsheet-first vendors may be more appropriate.
Buyers seeking the longest-established enterprise vendor footprint and partner ecosystem for very large-scale deployments; incumbents may offer broader enterprise maturity for certain requirements.
Organizations that cannot tolerate potential brand confusion during evaluation between runway.com (FP&A) and runwayml.com (creative AI).

Deal disqualifiers (poor fit)

Very small finance teams lacking time to implement or administer a new platform.
Requirements for fully transparent, published pricing during initial vendor shortlisting.
Environments with unusually complex legal/entity/accounting structures where extensive customization and pilot validation are required.

Publicly observable limitations / gaps

Public pricing is not available, which limits quick benchmarking and creates procurement friction.
Some reviewers report that ongoing changes can be challenging without vendor involvement; this suggests potential dependency on customer success for certain change scenarios.
Brand and review confusion between runway.com (FP&A) and runwayml.com (creative AI) complicates third-party review interpretation.

Roadmap / future features

02Why they buy

Observed / partially validated from vendor content and customer narratives:

Cross-functional self-service planning where departmental stakeholders can build scenarios and collaborate without constant finance-led consolidation.
Rapid scenario planning capabilities and support for multi-scenario comparison.

Vendor-claimed unique selling points that require validation during procurement:

Large efficiency multipliers reported in vendor case studies; buyers should request measurement methodology and baseline comparisons.
Vendor-reported integration counts and available connectors; buyers should confirm connector availability and any tier-based limits relevant to their needs.
AI-labeled features for variance explanations and workflow acceleration; buyers should test these features in pilot workflows to understand practical utility.

Balanced view:

The combination of structured modeling, collaborative inputs, and integrated actuals is the core value proposition, but realizing this value typically requires configuration, data cleanup, and internal ownership.

Why customers chose Runway (patterns)

From customer stories and review summaries, common selection drivers include:

Reducing spreadsheet versioning and manual consolidation.
Faster scenario planning.
Live actuals syncing via integrations.
Enabling self-service visibility for non-finance stakeholders.

Vendor-claimed unique selling points that require validation during procurement:

Key Differentiator

03Field reports

Review platforms (G2)

There is a notable risk of review conflation between the FP&A product and the creative AI product on review sites.

On G2, separate listings can reflect different products: a Runway FP&A listing and other Runway listings that refer to creative AI/video generation.
Review content that refers explicitly to video credits or generative video output appears to relate to the creative AI product rather than the FP&A product.

Representative positive feedback (Runway Financial on G2)

A G2 reviewer in a mid-market finance role described the customer success organization positively and reported the product scaled to their needs, while noting onboarding complexity.

Representative negative or cautionary feedback (mixed listings on G2)

Some reviews refer to problems with video output, credit usage, and refunds; those items appear to pertain to the creative AI product rather than the FP&A offering. The existence of such reviews is operationally relevant because it can cause confusion for buyers searching Runway reviews.

Community discussions (Reddit)

A Reddit thread in r/FPandA included:

Positive comparisons to Adaptive Planning: one commenter stated that Runway felt substantially more flexible in cube modeling and praised available documentation.
A cautionary report for very small teams: a commenter reported a steep learning curve for a single-person accounting team and described support as insufficient to complete implementation; this commenter suggested that the organization might have been better served by remaining with spreadsheet workflows.

Another Reddit post comparing Runway to other FP&A entrants raised skepticism about feature completeness in newer vendors, which is a common buyer concern when evaluating newer providers.

Why customers may leave or not purchase (patterns)

If implementation requires extensive vendor involvement or a dedicated FP&A owner, smaller teams may find the solution unsuitable.
Lack of public pricing can complicate ROI justification.
Expectations that the platform will match simple spreadsheet workflows may lead to dissatisfaction when a learning curve exists.

1) Developer-focused platform (vendor customer story)

Stated outcomes:

Replaced multi-tab spreadsheets used for consolidation.
Reduced monthly manual update effort.

Critical evaluation:

These outcomes are plausible following migration from manual spreadsheet consolidation to integrated reporting.
The metrics are vendor-published and lack independent validation.
Success appears to depend on source data quality and having clear internal ownership over the model.

2) Large talent/investment platform (vendor customer story)

Stated outcomes:

Single source of truth and reduced time validating metrics.
Enabled cohort-based predictive modeling and faster business reviews.

Critical evaluation:

Multidimensional cohort modeling is typically challenging in spreadsheets; dedicated FP&A tools can materially improve this capability.
The case study outcomes are largely qualitative and lack disclosed measurement methodology.

3) Email/productivity company (vendor customer story)

Stated outcomes:

A large efficiency multiplier is reported in the vendor material, along with broader departmental self-service for scenario building.

Critical evaluation:

Large multipliers can occur when the baseline process is highly manual; without specifics on which tasks were measured and the measurement approach, reported multipliers should be treated as directional and vendor-provided rather than independently validated.

04Best fit

Company size

A practical fit is often mid-sized to larger organizations with an established planning cadence that incorporates cross-functional inputs.

Industries / verticals

SaaS / technology
Fintech
High-growth consumer and marketplace businesses

Roles and personas

Decision makers: CFO, VP Finance, Head of FP&A, Head of BizOps
Champions/admins: FP&A manager/analyst, finance systems owner
End users: department heads (Sales/Marketing/Ops), executive leadership

Key pains addressed

Spreadsheet sprawl and version-control challenges
Manual monthly updates and reconciliations
Slow scenario planning cycles
Finance bottlenecks where stakeholders await updated numbers

Qualification criteria (indicative)

Presence of at least one dedicated owner to build and maintain the model.
Source systems (accounting, HR, CRM, data warehouse) that are reasonably accessible for integration.
A need for cross-functional planning rather than finance-only budgeting.

05The pitch

What the product does (objective value proposition)

Key product capabilities described by the vendor include:

Scenario planning and rapid what-if simulation (for example: hiring changes, funding delay, marketing spend shifts).
Collaborative budgeting with structured inputs (intended to reduce spreadsheet versioning and manual consolidation).
Revenue planning tied to CRM/pipeline and operational drivers.
Forecasting that updates with actuals through integrations.
Variance analysis (Budgets vs Actuals), reporting dashboards, and narrative/board-ready reporting.
AI-labeled features described by the vendor as workflow accelerators (for example, variance drill-down/explanations); some of these features are described as Beta.

Important ambiguity / brand collision: “Runway” is also widely known as RunwayML, a separate company offering AI creative/video generation tools. Some review platforms and search results conflate these entities or display profiles that refer to the creative AI product rather than the FP&A product. This report focuses on Runway FP&A; buyers should verify that third-party content applies to the FP&A product before using it in procurement decisions.

Target market and positioning

Evidence from customer stories and vendor materials suggests typical targets include:

Tech/SaaS and venture-backed companies
Finance and BizOps teams modernizing planning
Cross-functional stakeholders (Sales/Marketing/Ops) who require self-service financial visibility

Get a comprehensive analysis of Runway including market position, competitive landscape, adoption trends, and peer benchmarks.

Download full report →