One of the more interesting projects we’ve taken on recently has been with the founder of Western...One of the more interesting projects we’ve taken on recently has been with the founder of Western...
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
One of the more interesting projects we’ve taken on recently has been with the founder of Western USI, one of Australia’s largest signage installation companies.
When we first started working together, there was definitely some hesitation. And honestly, I don’t blame him. Handing over an important part of your business to a new software team requires a lot of trust.
So we didn’t try to convince him with big promises. We focused on the work.
We built the app, worked through the details, added the admin panel, and kept improving things based on his feedback. Slowly, the conversations changed from “Can this be done?” to “Can we also add this?”
Then we got this message from him, complimenting the app and admin panel and sending over his list of fixes and improvements.
That shift is probably my favorite part of working with founders.
You don’t really earn trust by talking about what you can build.
You earn it by building something that makes the client comfortable enough to trust you with the next thing.
I designed this onboarding experience for Fundify about two years ago, and looking at it today, the thinking still holds up.
The goal was simple: help users understand what the product does before asking them to explore it.
Fundify brings crypto, gift cards, bill payments, and betting wallet funding into one experience, so the onboarding needed to communicate those core values quickly and clearly.
Each screen tells part of that story without overwhelming the user.
Because good onboarding isn't just about showing features.
It's about creating clarity, trust, and enough curiosity to keep going.
Two years later, and I still stand by the decisions behind this one.
A client shouldn’t have to learn Webflow just to publish their next case study.
On a recent build, I spent a lot of time on the CMS: setting up reusable blocks and the logic that lets the team update content without rebuilding pages.
The tricky part is deciding how much control to give them. Too little, and every update becomes a request. Too much, and they’re suddenly responsible for the layout.
I want them to open the CMS, know what to do, and get on with their day. There’s a fair amount of work behind making that feel simple.