Runway vs Credit Repair Cloud
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.
Credit Repair Cloud goes mobile-first for end-clients and rips Zapier out of the GoHighLevel sync.
Three substantive releases anchor the period: the Secure Client Access mobile app moved from beta (March) to GA (April) with onboarding, credit tracking, in-app messaging, and push notifications; native two-way GoHighLevel sync replaced the Zapier-based workaround in the Marketing Hub; and PDFs can now be attached directly to dispute letters across every send path. Inquiry matching during credit-report re-imports also got tighter, cutting duplicate inquiries and unexpected mass deletions. Each release shows up twice in the feed due to a publishing-side encoding issue.
The product is shifting two channels at once — client-facing communication is moving onto a mobile app that competes for attention against any consumer fintech, and operator-facing integrations are being pulled in-house away from brittle Zapier glue. Combined with PDF-native dispute letters, the work targets the two pain points that hold mid-market credit-repair shops back: client engagement and integration reliability.
The mobile app will likely sprout payment collection and document upload next, since onboarding and messaging are already there. Expect more native integrations to follow GoHighLevel — Twilio, Stripe, or major email senders are obvious candidates given the marketing/operations focus.
See more alternatives to Runway →
See more alternatives to Credit Repair Cloud →