Builder.ai

We started revamping the platform from its core, the features page.
We streamlined the interface with patterns built around best practice, testing and iteration.
Builder Studio users relied on product experts to help them with feature selection and every subsequent step, so we introduced a virtual assistant to facilitate the process and offload resources.

Next we worked on the landing page, where users start by selecting templates.
We wanted the AI to assist the user at every step so we made it the primary journey on this page, also considering that brand-wise Natasha had become the face of the product.
The goal was for the assistant to eventually replace user template selection: users would just have to input their idea and the assistant would compile a set of features to be refined in the next step.
However, as a first step we remained closer to the original experience: for now Natasha would just act as a template filter.

It was now time to work on delivery and payment, which in the flow come after feature selection.
Friction was reduced by streamlining navigation, consolidating steps and adopting a tried and tested ecommerce page layout.

Before I left I also put down the IA for the home hub, which when ready would substitute the templates page as the start of the app-building process.
This page would also act as a management centre to track project progress and stay in touch with the team.

It took a while to get there since we had to establish proper design methodologies first, but eventually we managed to redesign the whole primary journey.
At the time of writing this, the new Builder Studio is being tested as a beta.

During this long contract I contributed to many other products within the Builder family, such as the cloud, the rapid prototyping and the backend platforms as well as the overarching design system.