Client stories
Notes from product, success, and release owners who booked assessments, path reviews, and working sessions.
Feature Adoption Assessment
“We knew our reporting module was opened often and still underused. Portal Cypress Core walked our product and support leads through the first thirty days of events and support themes, then left us with a ranked list we could actually schedule. The workshop days felt dense — useful, if a little relentless — and the written brief matched what we had discussed.”Helena Croft · Head of Product, Edinburgh
Onboarding Path Review
“The onboarding review caught a setup step our analytics never labelled as a failure. New accounts were skipping a permissions screen and never returning to the feature we cared about. Helena’s reservation about our sparse session recordings was fair; we still got a clear map and three path changes to test.”Marcus Adeyemi · Customer Success Lead
Release Adoption Brief
“I needed a post-ship story for leadership within a week. The release adoption brief was short, specific, and tied to the accounts we had targeted — not a generic health score.”Priya Nair · Release Owner
Adoption Working Session
“Our half-day session forced product, design, and support to agree what ‘adopted’ meant for one feature before we argued about charts. We left with owners and a small experiment list rather than another shared dashboard link.”Tom Gillespie · Founder, B2B tools company
Feature Adoption Assessment
“They asked for anonymised exports and release notes up front, which kept the assessment grounded. I would have liked one more readout call than the package included, but the final recommendations were concrete enough to put into the next sprint planning.”Sophie Lang · Product Operations
A Midlothian B2B product team shipped a reporting enhancement that showed strong first-week reach. Return use lagged. During a Feature Adoption Assessment we paired funnel steps with support phrases about export formats and shared ownership of saved views.
The brief ranked three changes: clarify who owns a shared view, surface export options earlier, and delay a promotional prompt that interrupted setup. The team scheduled two of the three in the following sprint and kept the third for a later release.
Instrumentation was thinner than ideal on one secondary path — we said so in the brief rather than stretching the sample.
An onboarding path review for a signup redesign found accounts skipping a permissions step that analytics never marked as failed. The annotated map became the shared artefact for design and product owners.
Discuss a similar engagement