Redesigning a complex platform to make it understandable and scalable

Plan de Bodas already made it possible to manage most of a wedding: events, venues, spaces, services, tasks, attendees, or tables. The problem wasn’t a lack of features, but how they were organized.

Sections that belonged to different contexts sat side by side at the same level within the main navigation. When entering an event, modules, actions, and icons competed for attention and required already knowing the system’s internal logic to know where to act.

The complexity also repeated itself inside the forms. Creating or editing information meant facing dense screens, with little prioritization and many decisions visible at the same time.

With few clients using the platform, part of the operation also still depended on the previous owner, who manually loaded each venue’s services so they could later be used in their events.

The starting point was a functional document previously worked on by the partners and the technical team. It laid out the product’s main entities, data, relationships, and needs, but that logic still had to be turned into an experience that could be navigated and understood.

Translating those requirements into screens raised new questions: what should be global, what belonged to a Masía, what lived inside an Event, and what information each profile actually needed at each moment.

We also refined naming that was initially hard to understand, and reviewed references from the industry — especially Bodas.net — to understand known patterns, without replicating their structure. Wedify needed to solve for multi-venue management and a different user hierarchy.

The main change was separating global navigation from contextual navigation.

That way, the main menu could stay compact while specific functions appeared within the entity they actually belonged to.

Wedify had to work for profiles with very different responsibilities and different levels of digital experience as well.

A Super Admin might need to access several organizations, masías, and events. Other profiles only needed to work with the masías or events assigned to them. The couple, on the other hand, didn’t need to understand the business’s internal structure: they needed to organize their own event.

That’s why the solution wasn’t just about hiding buttons based on permissions. Access, navigation depth, and the entry information were all adapted to each person’s actual scope.

The interface also relied on clear hierarchies, recognizable iconography, visible states, and contextual help to reduce the need to learn the system before being able to use it.

Services were one of the most complex flows in the previous platform.

Setting up a venue’s offering could involve prices, costs, per-person values, VAT, categories, options, questions for the client, and relationships between different elements. The difficulty was enough that, in practice, the owner of Plan de Bodas ended up loading most of that information for their clients.

In the redesign, we didn’t try to eliminate that complexity. We organized it into a progressive, reusable structure.

Wedding invitations weren’t part of the old platform.

The owner of Plan de Bodas offered them as an additional service, and it was he who put them together for clients.

In Wedify, we integrated that process inside the event itself, so the couple could choose a base, customize it, and manage the result from the same product.

We designed three templates with different styles. From the event page, the couple could select one and fill in content like names, dates, locations, transportation, the celebration, attire, photos, and RSVP.

The final result also needed to be viewable from Mobile, something especially important for an invitation that guests would usually receive and open from their phone.

The redesign turned a hard-to-learn platform into a system organized around contexts, responsibilities, and reusable pieces.

The new architecture made it possible to separate global management from the operations of each Masía and each Event. Access and dashboards were adapted to different levels of responsibility, while complex flows like Services and Packs were structured progressively.

The work covered both Web and Mobile, and also included client-facing experiences, such as editing invitations within the event itself.