I just added a new case study, and I’d love to hear your thoughts.

Sometime in September last year, a client reached out to me via Upwork for her Kajabi site redesign project. She explained that she was dissatisfied with her previous developer. Although the developer had created a strong brand identity, a compelling offer, and an aesthetically pleasing website, the workflow created challenges.

The site was built using a Figma-first approach before being implemented in Kajabi. However, whenever the client requested changes, the developer required that all updates be designed externally in Figma, approved, and then manually rebuilt in Kajabi.

This made the process slower, more expensive, and less flexible for quick iterations.

My question is: as a developer, would you follow this approach, or would you prefer to implement changes directly in Kajabi to reduce turnaround time, minimize unnecessary costs, and allow for faster iteration?

Kindly check the full details using the link below: https://contra.com/p/EP3YqURm-kajabi-website-redesign-seo-and-crm-setup?r=sodiq_Alao

looks fantastic 👌

Most of the work I share early in a project is meant to feel a little uncomfortable. Not bad, just bold. Pushed further than the brief asked, into territory the client didn’t quite realise they were ready for. I never go too safe early on. It’s easier to pull things back than it is to start from something that feels soulless. Here’s a glimpse of some early concepts from the Energy Central project. Some bold, some more editorial, all exploratory. A lot of this won’t make it into the final brand, but that’s the point. It’s not wasted work – it’s what leads to a stronger result. The kind you wouldn’t arrive at if you played it safe from the start. This is how a team learns what they’re actually ready to stand behind. The directions you reject are often the ones that lead you to the one you commit to.

looks awesome