BUSINESS ARCHITECTURE

PERIOD OF APPLIED DISCIPLINE
August 2021 - July 2025
 

A business doesn't become operational because software is installed. It becomes operational when its logic is properly defined: how products are structured, how services are sold, how members are managed, how billing behaves, how records are maintained, how workflows move; and how every one of those parts connects in a way that staff can actually use.

That was the core of my work in Systems and Business Architecture.
 

Centred on the configuration and architectural development of the Nexudus CRM platform, but the real work began long before any software settings were touched. It required first establishing the financial, operational, hospitality, technology and service structures of the business itself; then translating that logic into a digital environment capable of supporting day-to-day operations, customer lifecycle management and scalable growth.
 

The platform had to become a working model of the business: not a generic coworking tool running on default settings, but a structured operational environment shaped precisely around the Eclat brand and model.
 

Membership structures, products, resources, booking logic, service rules, billing relationships, customer states, communication flows, access conditions, operational permissions, reporting structures and system dependencies all had to be thought through, documented and embedded.
 

 

SCOPE OF WORK
 

Initial Scoping, Workflow Design & Operational Modelling

Before the platform could be configured intelligently, the business itself had to be clearly defined. This meant designing the workflows, service relationships and operational structures that the CRM would eventually enforce and support.
 

• Mapping the end-to-end operational model from enquiry through billing, support and retention

• Designing workflows for bookings, onboarding, access, hospitality and account management

• Clarifying how products, resources, permissions and service rules should behave

• Establishing dependencies between departments, systems and operational actions

• Identifying friction points and edge cases before implementation
   

CRM Configuration — Plans, Products & Parameters

• Configuring platform parameters to reflect Eclat's specific business requirements

• Setting up products, plans, memberships, resources and service offerings

• Structuring booking types, entitlements, account rules and usage permissions

• Aligning CRM setup with the reality of the business model rather than generic defaults

• Maintaining order and consistency across setup to reduce future operational confusion

​

Database Development & Management

• Managing records across members, organisations, plans, products and resources

• Maintaining data quality, consistency and usability across the platform

• Reducing duplication, inconsistency and record fragmentation

• Preserving data integrity as products, users and workflows evolved over time
   

System Customisation & Interface Design

• Adapting the platform environment to reflect Eclat's operating model and brand

• Interface design to improve clarity, navigation and usability for staff and members

• Reducing the friction of working within an otherwise standardised software environment

• Bridging system administration with experience design where appropriate