Saizen Partner Portal & Alliance Network

Overview

I built the partner-facing layer at Saizen to make a growing alliance network understandable and usable, not just impressive on a page. The system combined a premium visual network with partner workspaces for joint projects, documents, progress, communication, services, responsibilities, and the commercial work happening behind each relationship.

What It Delivers

• A centralized digital environment representing Saizen's technology, strategic, market, growth, and delivery partners.
• A visual alliance-network interface that places Saizen at the centre of the wider partner ecosystem.
• Immediate visibility of the complete partner network rather than hiding each relationship behind sequential scrolling.
• Partner categorization and filtering across different alliance types and commercial functions.
• Interactive partner previews containing company identity, capabilities, partnership relevance, and available services.
• Expandable partner profiles for deeper information without forcing users into disconnected pages.
• Featured-partner areas for strategically important relationships and current joint initiatives.
• A complete partner grid designed to scale as the network expands.
• Partner-specific workspaces containing joint projects, timelines, documents, progress, communication, and latest updates.
• Structured sections for legal and partnership material, technical delivery, commercial assets, marketing, operations, reporting, and shared responsibilities.
• A place for joint proposals, decks, onboarding information, implementation material, and go-to-market assets.
• Support for partner-specific delivery models rather than forcing every alliance into the same generic structure.
• A foundation for partner onboarding, opportunity sharing, co-selling, joint account development, referral tracking, and shared delivery governance.
• A unified relationship layer connecting Saizen's partner network with its customer-delivery and commercial systems.

What I Did

• Designed the information architecture and interaction model for Saizen's partner ecosystem.
• Recognized that the original fixed round-table concept would become difficult to use as the number of partners increased.
• Redesigned the experience around an immediately visible and scalable alliance network.
• Structured Saizen as the central ecosystem node with connected partner categories surrounding it.
• Defined partner filters covering strategic, technology, market, growth, and delivery relationships.
• Designed hover previews, expandable profile cards, featured-partner areas, and the complete partner grid.
• Structured partner-specific workspaces around projects, timelines, communication, files, updates, and joint responsibilities.
• Defined how complex partners such as Prestige Properties Cyprus could organize website delivery, CRM systems, hosting, DNS, property feeds, listings, marketing, operations, and reporting inside one portal.
• Connected the partner experience with Saizen's wider customer portal, CRM, delivery, and onboarding architecture.
• Designed the portal to support both relationship presentation and practical collaboration rather than operating only as a marketing page.
• Created a framework capable of expanding beyond the initial group of visible partners without requiring a complete redesign.

Outcomes

• Saizen's partnership ecosystem became visible as an interconnected strategic network rather than a collection of isolated logos.
• The experience could scale from the initial partner group to a larger alliance ecosystem without breaking its navigation model.
• Users could understand each partner's capabilities, category, relationship with Saizen, and role within wider delivery.
• Partner projects, documents, responsibilities, and communications could be organized within dedicated relationship workspaces.
• The portal created a reusable structure for technology partnerships, referral relationships, delivery alliances, and joint commercial programmes.
• Partner information could support sales conversations, client delivery, onboarding, co-selling, and internal coordination.
• The project created a bridge between Saizen's public partnership narrative and the operational work occurring behind each alliance.

Proven Impact

• Initial interface designed around five immediately visible partner relationships.
• Architecture redesigned to support nine or more partners without depending on one-by-one reveal interactions.
• Supported Saizen's broader ecosystem of seven or more technology and delivery partnerships.
• Created dedicated structures for partner projects, timelines, documents, communication, and delivery updates.
• Provided a scalable model for representing partners across multiple commercial and technical categories.
• Turned partner relationships into organized digital assets capable of supporting joint delivery and commercial activation.

Why It Matters

• Partnerships create limited value when their capabilities, responsibilities, assets, and active work remain scattered.
• A visible ecosystem helps clients understand the combined strength available through Saizen rather than evaluating each organization independently.
• Dedicated partner workspaces create accountability across joint projects and reduce dependency on disconnected email threads and shared folders.
• The project demonstrated the ability to translate a complex relationship network into a scalable interface and operating structure.
• It created infrastructure for Saizen to grow through alliances rather than relying exclusively on internal delivery capacity.