Technology
Pendo consulting and implementation
We help organisations see what people actually do inside their software, and then change it. Five is a Pendo partner working across New Zealand and Australia.
Why you'd want this
The organisations we work with can usually tell you what their software cost and how many people have logins, and then it gets vague, because what happens after somebody signs in has never really been anybody's job to find out.
The behaviour is being recorded anyway. It sits there in the product, every click and every journey somebody gave up on halfway, and it doesn't get turned into a decision, so roadmaps get built out of opinion and releases go out without anyone having agreed beforehand what they were meant to change.
Pendo makes that behaviour visible. We spend our time on what to do about it, which means agreeing with you what needs to shift and how you'll know it has, and then tagging and building against the measures we've agreed. If we get into it and Pendo turns out to be the wrong fit we'll say so, and we don't make margin on your licences so there's nothing in it for us either way.
Where we support
One method underneath everything, and four ways to start with us.
- Measures first: We agree the outcomes and how you'll know they've happened before anything gets tagged, so there's something to judge the work against later on.
- Software experience review: A fixed-scope diagnostic covering where the friction sits, what people genuinely use, and whether Pendo suits what you're trying to do.
- Instrument and baseline: Pendo deployed and tagged properly, so you've got an honest picture of how the software gets used before anybody designs a guide.
- Design and build: In-app guidance, support and sentiment, shaped around the behaviour you're trying to shift.
- Adoption and ongoing support: Super users, operating rhythm, leadership alignment, and set hours each month once you're live.
How it will benefit you
- Roadmap conversations get easier: When the behaviour is visible, priorities get argued from what's happening in the product.
- A straight answer, including no: We don't make margin on your licences, so we've no reason to talk you into more of them than you need.
- You can tell whether it worked: The measures are agreed before the work starts, so afterwards there's something to check it against.
- Fewer repeat questions: The things people keep getting stuck on become guidance inside the product, at the moment they're stuck.
- Your team can run it: Julius leads our digital adoption delivery, and we build the capability in your team while we go so you aren't tied to us afterwards.

