CASE STUDY 4 //
NDIS support coordination and coaching, Melbourne - Full rebrand + WordPress + Elementor + compliance integration
Scope: Full rebrand, social assets, business cards, web, compliance integration // Platform: WordPress + Elementor // industry: NDIS / Disability Support
The Brief //
Majakka is a Melbourne-based NDIS support coordination and coaching organisation.
Their Majakka Coaches guide individuals through the NDIS system, advocate for families navigating education, and help businesses become NDIS-ready.
It's important, nuanced work, the kind where first impressions on a website can either build trust immediately or quietly undermine everything that follows.
This was the second time I'd worked on the Majakka brand.
The first version, done when the organisation was newer and finding its feet, had leaned into neon colours and illustration-forward design.
It was right for where they were at the time: energetic, approachable, getting noticed.
But Majakka had grown.
They were working with more complex clients, building more institutional relationships, and operating at a level where the original visual identity no longer reflected who they actually were.
They needed a brand that had matured with them.
The Problem //
Rebranding an organisation with an existing client base is different to building from scratch.
There are people who already know the name, already associate it with certain visual cues. The question isn't just "what should this look like", it's "how far do we move, and what do we keep?"
The audience complexity added another layer. Majakka serves NDIS participants and their families, professionals and organisations seeking specialist partners, and self-funded clients navigating the system independently.
Warmth and professionalism aren't opposites here, they both have to be present, simultaneously, for the site to work.
There was also a specific compliance challenge: as an NDIS-registered provider, Majakka needed a way for employees to submit incident reports digitally, but the handling of that data had to meet strict compliance requirements around security, storage, and data erasure.
The Solution //
Brand identity // Logo // Social media assets // Business cards // WordPress + Elementor // Compliance integration
The new direction moved toward warm, upscale, and grounded.
The neon palette was replaced with a charcoal-anchored system, `#40403F` as the base, with warm supporting tones that feel considered rather than corporate.
The illustration style gave way to clean, confident typography: Ink& Quill for headings, Advent Pro for body & for pull-quote moments.
The distinctive layered mountain SVG shape dividers that appear throughout the site became a visual signature. structural, calm, and quietly distinctive.
The full brand rollout covered everything Majakka puts in front of people: logo, business cards, social media templates and campaign assets, and a complete brand system that could be applied consistently across every channel.
Service architecture was structured around how a visitor actually arrives:
Am I an individual with NDIS funding? Am I self-funding? Am I a parent or carer? Am I a business?
Each pathway leads to the right program tier without forcing someone to read everything. The site also needed to earn trust quickly for visitors who arrive already exhausted from navigating a complex system, that's a specific design constraint, and it shaped every layout decision.
Performance was a problem that needed diagnosing before any of the design work could land properly.
The site was slow, pulling images through Jetpack's WordPress.com CDN, creating an external dependency that PageSpeed penalised hard.
The root cause turned out to be a conflict between Jetpack's own caching modules and Bluehost's built-in Jetpack Boost cache manager: two overlapping systems fighting over the same resources, with neither working properly as a result.
With Jetpack's performance modules disabled and Bluehost's cache manager running as the sole authority, the site jumped from 57 to 92 on Google PageSpeed.
NDIS providers operate under strict requirements around how incident reports are created, stored, and handled.
The solution built for Majakka used a Microsoft Azure function triggered by an HTTP call from the website, employees could submit incident reports via a non-navigable page on the site, the data was posted securely to the Azure function, a temporary WordPress JSON was created and then immediately erased after the function processed it, and the final record landed in a SharePoint-connected Excel sheet that accumulated reports in a secure, compliant environment.
The result was a digital incident reporting pathway that met NDIS compliance demands without requiring staff to use a separate system or handle sensitive data through standard web infrastructure.
Website form (non-nav) // HTTP call to Azure function // Temporary WP JSON — created and erased // SharePoint Excel sheet — secure accumulated record
The Results //
-Full rebrand. from neon/illustration to warm and upscale
-PageSpeed soared after diagnosing Jetpack conflict
-Incident reporting system built to NDIS requirements.
A brand that finally matches the organisation Majakka has become.
Warm enough for a family in crisis. Credible enough for an institutional partner. And built with the technical rigour their compliance obligations actually require.
Contact //
No cookie-cutters. No templates. Just your problem, solved properly.