Azari Holdings
Product Engineering, Platform Foundations & Technical Leadership
Engagement arc and ownership
The Azari relationship began with hands-on independent product delivery and grew into primary engineering ownership and technical leadership across an expanding group of production systems. The work moved well beyond websites: hospitality operations, property platforms, member products, partner workflows, financial and lifestyle experiences, administrative control planes, public developer surfaces and group-wide digital properties all became part of the engineering responsibility.
I remained hands-on as the scope expanded: translating business requirements into system behaviour, defining product and application boundaries, implementing core workflows, building authorization and audit controls, hardening failure paths, qualifying releases and maintaining continuity between products that served very different users.
End-to-end ownership of early systems, from requirements and workflow design through production readiness and stakeholder handoff.
Responsibility expanded across more applications, user groups and business units, including architecture decisions, quality control and release hardening.
Hands-on leadership across cross-product dependencies, implementation direction, engineering standards and delivery priorities.
Azari Residences — hospitality and property operations
One of the earliest major systems was the Azari Residences hospitality platform. It was designed around the full guest and property lifecycle rather than a booking form: property discovery, live availability, reservations, payments, identity and guest information, check-in, stay services, support, checkout and post-stay engagement.
Discovery, availability, booking, payment state, documents, guest information, check-in, service requests, support and post-stay activity were connected as one governed customer journey.
Owner onboarding, agreement acceptance, listing drafts and submissions, administrative review, revision and publication states, owner-specific bookings, performance views, earnings, balances and withdrawal lifecycle controls.
Role-appropriate operational access for staff and administrators, with assignment, internal notes, guest-visible updates, status histories, reporting and audited state transitions.
The approved mobile programme carried applicable website capability into phone-first guest, owner, staff and administrator experiences, including deep links, notifications, uploads, offline/network interruption handling and release qualification.
Testing covered role and permission boundaries, booking and payment edge cases, duplicate or interrupted callbacks, session expiry, uploads, service requests, support, listing approval, owner balances, withdrawals, responsive behaviour and regression protection.
Azari Luxury Properties — property platform and publishing operations
Azari Luxury Properties grew into a substantial property-development and corporate platform rather than a brochure site. The work covered public company and founder narratives, development and portfolio records, property categories, design and development material, locations, insights and news, enquiry flows, publishing controls, legal and governance surfaces, search visibility and administrative operations.
- A large public information architecture with dedicated company, development, design, partnership, sustainability, location, insight, news and programme surfaces.
- Managed publishing workflows for developments, locations, insights and changing operational content while keeping permanent corporate material controlled.
- Administrative permissions, staff access, auditability, maintenance controls and production-safe editing boundaries.
- ARPIP-related product communication around property discovery, capital planning, mortgage support, ownership coordination, managed-rental pathways and long-term portfolio thinking.
- Release QA across routing, metadata, structured data, sitemaps, legal links, accessibility, mobile behaviour, error handling, production debugging and content integrity.
Azari Select — financial-lifestyle and membership product
Azari Select became one of the broadest engineering surfaces in the engagement: a premium member product combining financial access, account activity, transfers, cards and bills with membership, privileges, concierge, bookings, travel, events, rewards, networking, marketplace activity and support. The challenge was keeping those domains coherent without weakening security or turning a complex product into disconnected dashboards.
Account and balance views, account details, internal and external transfer journeys, transaction activity, statements, foreign-exchange flows, bill payment, cards, verification states and business-account experiences with explicit loading, failure and recovery behaviour.
Digital membership identity, QR verification, benefits, offers, rewards, travel and booking experiences, events, concierge requests, saved items, personalized discovery and member activity summaries.
Reviews arise from verified completed activity, remain versioned and auditable, support moderation and appeals, and include fraud signals rather than treating star ratings as unauthenticated vanity data.
Durable tickets, conversation timelines, assignment, escalation, service recovery, notification preferences, security alerts, device/session controls, privacy, consent and account-support workflows.
Authorization, risk and operational correctness
The Azari Select work was designed around permission-first and fail-closed behaviour. User type alone does not grant unrestricted access: ownership, organisation, assignment, record state and approval boundaries are evaluated alongside granular capabilities. Sensitive administrative actions use reason capture, audit records and maker-checker controls where appropriate.
- Member, partner, support, concierge, moderation, finance, administration and audit responsibilities are separated rather than collapsed into one generic admin role.
- High-impact refunds, corrections, settlement actions and privilege changes are structured as explicit operations with approval and audit context.
- Identity, verification, device and session state are part of authorization decisions, not simply profile metadata.
- Unavailable or incomplete dependencies fail closed rather than assuming financial, identity or permission success.
- Interface visibility never substitutes for server-side enforcement.
Azari Private Network Partners
APNP was engineered as a first-class partner programme with its own public acquisition flow, dedicated authenticated partner workspace and staff-side administration. It is not merely a referral form attached to the member product.
Structured application and invitation journeys with draft, review, information-request, compliance, interview, approval, decline, withdrawal and expiry states.
Overview, referrals, new submissions, referral status, rewards, performance, events, training, resources, compliance, support and profile management inside a separate authorization boundary.
Consent-aware referral intake, attribution, progression, status communication and auditable reward/performance records without exposing unrelated member data.
Administrative review, compliance actions, agreements, training and event management, reporting, support and audit across the programme.
ARRK — internal operations and control plane
ARRK was developed as a dedicated staff operations product rather than hiding every operational task inside the member application. The product model spans work queues, approvals, alerts and exceptions across the domains that operational teams actually need to run.
Member and business records, security/session state, verification queues, evidence, reviews, restrictions, beneficial-owner information, documents and risk actions.
Accounts, balances, holds and restrictions, transfers, reconciliation and exceptions, refunds, reversals, corrections, statements and maker-checker work queues.
Card and lending workflows, investment and insurance operations, vendors, marketplace disputes, concierge, bookings, travel, events and APNP administration.
Support queues, incidents, service health, notification failures, developer access, request and webhook incidents, abuse controls, roles, permissions, audit logs and security events.
The objective was a readable control plane for authorized operations teams: enough depth to investigate and act, but with capability boundaries so operational convenience does not become unrestricted access.
Developer platform, API and documentation
The wider Select product also required real developer-facing surfaces rather than a marketing page labelled “developers.” Engineering responsibility covered application registration and access workflows, credential lifecycle metadata, request logs, webhooks, usage and rate-limit visibility, API contracts and testable documentation.
- Developer accounts and applications with controlled testing and live-access workflows.
- Request logs, webhook configuration and incident visibility suitable for integration debugging.
- API surfaces across identity, profiles, businesses, accounts, activity, transfers, cards, foreign exchange, bills, documents, notifications, support, marketplace and partner operations.
- Documentation search, API reference, machine-readable specifications, examples and interactive testing flows designed to remain aligned with the actual platform behaviour.
Public status and incident management
I also worked on turning status into an operational product rather than a page of permanently green indicators. The status model covers the main member product, developer platform, documentation, API and partner application with meaningful subcomponents and real checking or derived health state.
Operational, degraded, partial outage, major outage, maintenance and checking states are represented through component health, incident timelines, affected services, scheduled maintenance and historical availability. Public status information is sanitized so it can be useful without leaking internal hosts, credentials or operational identifiers.
Seven Azari corporate brands
Alongside the application work, I engineered the coordinated corporate estate for Azari Holdings, Azari Capital, Azari Concierge, Azari Aviation, Azari Yachts, Azari Foundation and Azari Energy. This was a substantial delivery in its own right, but only one part of the larger Azari engagement.
Each business received its own information architecture, visual rhythm and sector-specific personality while preserving a recognizable Azari family standard.
Corporate, legal, governance, responsibility, sustainability and contact material was structured around evidence, editorial quality and long-term maintainability rather than generic filler.
Canonical routing, route-aware metadata, structured data, sitemaps, accessible interaction patterns, responsive navigation and mobile/tablet qualification were treated as release requirements.
Broken routes, image failures, placeholder content, console errors, legal links, cookie behaviour, keyboard focus, contrast, social previews, 404 handling and deployment correctness were checked estate-wide.
The completed estate reached 164 principal pages with a large locally managed image library and zero dependence on runtime stock-image hotlinks.
Cross-product engineering discipline
The value of the engagement is not just the number of screens or brands. It is the repeated application of the same production discipline across very different products: explicit state machines, authorization boundaries, auditability, safe error recovery, responsive behaviour, durable support and notification records, reconciliation, testing, release qualification and operational handoff.
Client recommendation
Williams is a highly skilled software engineer who consistently delivers quality work. He quickly understood our requirements, communicated clearly throughout the project, and built a solution that exceeded our expectations. His professionalism, attention to detail, and problem-solving ability made him a pleasure to work with. Based on the success of our engagement, we were confident in entrusting him with additional software projects. I would gladly recommend him to any organization looking for a dependable and talented engineer.
Engineering outcome
The Azari engagement progressed from successful solo delivery into broad production engineering ownership. Hospitality, property, financial-lifestyle, partner, operational and corporate products each required different domain thinking, but the responsibility remained consistent: turn business intent into software that is secure, maintainable, auditable, usable and ready for real operations.
Discuss comparable work
Open to backend, platform, API, infrastructure-minded application engineering, enterprise software and technical delivery conversations.
Work emailwilliams@zivoralabs.xyz
link Book 30min call