A Cinderella Story
KindredCloud was looking for a new brand identity and a responsive web platform that matched the values of a lean startup looking to make a big impression, which led to EditorX being the best solution. It wasn't luck that the client was a good fit, we knew what to ask before offering X as a product because, well, beta in Wix terms could last years. So we tested X and we tested again. And again. Each time noting its limitations or buggy boundaries. Once we knew what we could offer, it became a matter of finding the right fit for this glass slipper of a platform. Thankfully, our client was thrilled with the process and their final product and we learned a lot about tailoring products in the process.
Video Wins, Every Time
Before offering X to clients Slake researched the classic pitfalls of trying to develop this platform in the same nimble way the Wix Classic editor and was able to apply a different approach to development that reduces overall drag.
This was our second X website delivered to a high-level client with our 30 Day Production Timeline and so far it has been relatively smooth sailing. Long story long, offering X as a product meant not just being able to sell it, that's the easy part. We first had to internally know what we were capable of offering successfully in a sprint production timeline (ie very few delays). When we stick to that system things work great. We tested the waters recently, pushing sales ahead of testing by offering X to a higher-level design client, but then after three weeks of myopic Wixian delays decided to pivot back to Wix Classic when X began negatively weighing down the production timeline. Lesson learned. Don't try to breakdance in glass slippers.
We're hoping X can someday leave Beta with at minimum all the functionality the Classic editor has with the additional improvements X provides. Until then, we're offering a very limited range of capabilities which might sound like a critique but for the right client, it's actually quite a lovely fit.