Runway vs Shift4
Side-by-side trajectory, velocity, and editorial themes.
Steady polish for collaborative financial planning — chart clarity, scenario branching, layout control.
Runway is in steady incremental mode for its collaborative financial planning canvas. Recent work focuses on the everyday ergonomics: 100% stacked charts now consistently display percentages, scenarios can be duplicated or locked as point-in-time versions from Activity History, table and database blocks are resizable per page, and formula editing has gotten cleaner (context menus, an 'f' indicator, sturdier draft history). Earlier entries added customizable fiscal year labels and Last close in formulas.
The cadence is small, focused improvements across the modeling and presentation surfaces — no directional pivot visible. The duplicate-and-lock-scenario primitive is the most strategically interesting recent addition; it suggests Runway is investing in version-control-style collaboration patterns familiar to engineers, not just spreadsheet users. Formula editing depth keeps getting attention, signalling power-user retention is a priority.
Expect continued refinement of scenario management (likely scenario comparison views or merge-style workflows), more chart-type polish, and probably an AI-assisted formula or modeling helper in the next quarter or two given how much editor surface area is being polished.
Shift4 absorbs the SkyTab and Lighthouse sub-brands — one parent brand across POS, venue, and merchant hub.
Shift4 is mid-rebrand consolidation. SkyTab POS has become Shift4 Dine, SkyTab Venue has become Shift4 Venue, and Lighthouse Business Manager has become the Shift4 Customer Hub. Recent communications are dominated by the rollout: update notices, required version bumps, and post-rebrand feature drops in the Customer Hub for both Dine and Venue.
The product strategy is moving from a portfolio of acquired sub-brands toward a single Shift4-branded merchant stack covering payments, POS, venue, and the merchant back office. The merged Customer Hub is the connective tissue — once everything carries the Shift4 name, cross-sell across payments, POS, and back-office tooling becomes a much shorter conversation.
Expect the immediate post-rebrand period to bring feature parity passes across Customer Hub for Dine and Venue, plus a v1.124-equivalent required update for Venue. Net-new functionality is likely to be paused until the rename and required-update cycle completes.
See more alternatives to Runway →
See more alternatives to Shift4 →