Most software companies don’t start in Alice Springs. Most are built in capital cities, shaped by urban workflows, and designed for scale across “typical” organisations. Brad Bellette took a different path. From the centre of Australia, he’s built three businesses with a shared focus: creating systems, strategy, and communication that actually fit remote and regional organisations. That difference in starting point is shaping a different kind of conversation. A career built around solving practical problems Brad’s connection to remote Australia isn’t recent. His family moved to Alice Springs in 1974. Since then, his work has stayed closely tied to the realities of regional and remote communities. Over time, that has translated into a wide range of projects, including: Technology behind the Bush Support Line, a 24/7 crisis service for remote health workers A Royalties Distribution App supporting Indigenous communities in Western Cape Systems for organisations like Katherine Women’s Information and Legal Service Software supporting logistics, infrastructure, and specialised operations Different sectors. Different requirements. But a consistent pattern. Most organisations weren’t struggling because they lacked effort or capability. They were struggling because the systems they relied on didn’t match how they actually worked. From one company to an ecosystem Today, Brad leads three interconnected businesses: HutSix – purpose-built software and systems Block G – digital transformation audits and consultancy bellette – communication, design, and storytelling Each plays a different role. Together, they solve a broader problem. Instead of treating software, strategy, and communication as separate challenges, the model connects them. Understand what’s broken (Block G) Build something that fits (HutSix) Communicate the change effectively (Bellette) For organisations, that removes a common friction point: managing multiple providers who don’t share context. Rethinking software for remote councils Much of the software used in local government is built for broad applicability. That approach works in predictable environments. It becomes more difficult in remote and regional contexts. Brad’s work focuses on an alternative: purpose-built software for councils and organisations that operate outside those norms. That means designing systems that reflect: Real workflows rather than assumed ones The need for offline capability in some locations Smaller teams managing multiple responsibilities Specific reporting and compliance requirements The goal is not to add complexity, but to reduce it. When systems align with how people actually work, adoption improves and reliance on workarounds decreases. The role of AI in changing what’s possible One of the reasons this approach is becoming more viable is the shift in how software is built. Advances in AI are accelerating development, allowing teams to move from concept to delivery much faster than before. For organisations, that has practical implications. Custom-built systems are no longer automatically associated with long timelines and high costs. Instead, they are becoming a realistic option for organisations that need: Flexibility Ownership of their systems and data The ability to evolve over time For Brad, AI is not the focus. It’s an enabler. It allows the team to spend more time on design and fit, and less time on repetitive build processes. Staying close to the problem Operating from Alice Springs is a deliberate choice. It keeps the work grounded in the environments it’s designed for. Rather than designing for remote contexts from a distance, Brad and his team work within them, which influences: How systems are structured What constraints are considered early How solutions are tested and refined This proximity helps avoid a common issue in technology projects: solutions that work in theory but not in practice. Building for the environments that need it most Brad’s focus isn’t on building software for everyone. It’s on building the right systems for organisations that operate in complex, often overlooked environments. From Alice Springs, that work continues to evolve, shaped by real-world use, practical constraints, and a clear goal: Create systems that support people to do their jobs effectively, without unnecessary friction. Want to talk about what’s not working in your current setup? Get in touch today .

Remote councils are stretched thin. Roles sit vacant for months. Good people carry double the load. Inboxes blow out. Reports pile up. Everyone talks about recruitment, retention, and the challenge of distance. But here’s the uncomfortable truth. Your staff are not leaving because of the outback. They are leaving because of the systems. We keep blaming location for a systems problem Remote work is hard. Nobody’s pretending otherwise. But remote councils have always worked in tough conditions. They know how to solve practical problems. They know how to get things done with limited resources. What burns people out is not the reality of regional and remote Australia. It is being forced to wrestle with software, reporting processes, and admin systems that were never built for the way they actually work. Systems designed for metro offices get sold into remote Australia every day. On paper, they look polished. Scalable. Cost-effective. Proven. In practice, they create workarounds. More spreadsheets. More duplicate entry. More reporting after hours. More time fighting the system instead of serving the community. That is not digital transformation. That is digital drag. When systems don’t fit, good people carry the cost Every broken workflow lands somewhere. Usually, it lands on the person already doing too much. They stay back to finish reporting. They manually move data from one system to another. They chase information that should have been easy to find. They build their own workarounds just to keep things moving. Over time, that becomes the job. Not the meaningful work. Not the reason they took the role. Just endless admin friction. That is how councils lose good people. Not in one dramatic moment. In a slow grind of frustration, overtime, and systems that make competent people feel ineffective. This is where HutSix started HutSix did not start with a pitch deck or a trend. It started with a bloke named Bradley. Bradley runs a construction company maintaining town camps in Alice Springs. He was drowning in reporting. Weekends disappeared into paperwork. The work mattered, but the systems around it were making the job nearly impossible. He was close to walking away. Not because he could not do the work. Because the systems made the work harder than it needed to be. So we built something that fit. Something purpose-designed for the way his team actually worked. Something that reduced friction instead of adding to it. Something useful, practical, and built around real conditions. That is still the mission. Generic systems are not neutral A lot of software gets sold as if it is universal. It is not. Every system is built around assumptions. Assumptions about internet reliability. Assumptions about staffing levels. Assumptions about workflows, reporting, approvals, mobility, and capacity. Most off-the-shelf systems are built around city assumptions. Stable connectivity. Bigger teams. More internal support. Less operational complexity across distance. Remote councils are anything but average. So when a generic system fails in a remote context, that is not bad luck. It is a design failure. Purpose-designed means built for reality At HutSix, we build systems for how people actually work. That means asking practical questions. What happens when the internet drops out? Who actually uses this every day? What reporting is essential, and what is duplication? Where are people losing time? What does the workflow look like in the field, not just in the office? That is the difference between adapted software and purpose-designed systems. Purpose-designed systems are built to fit the job. Built to reduce admin load. Built to support staff instead of exhausting them. And importantly, built so councils own the result. No per-user fees. No being trapped on someone else’s roadmap. No paying more every time your team grows. The cost of bad systems is bigger than software This is not just a technology issue. It is a workforce issue. A service delivery issue. A community impact issue. When systems are clunky, slow, or disconnected, they do not just frustrate staff. They weaken the whole organisation. Decisions take longer. Reporting becomes reactive. Good workers burn out. Knowledge walks out the door. Councils end up spending more money and getting less value, all while wondering why it still feels so hard. The answer is often sitting in plain sight. The system does not fit. Built in Alice Springs, for remote Australia HutSix is based in Alice Springs because that matters. We are not flying in, making assumptions, and flying out again. We live where the problem lives . We understand the pressures of remote service delivery. We know that software only works if it works in the real world, with the people and conditions it was built for. That is why we believe remote Australia does not need more generic tools. It needs better-fit systems. The question councils should be asking Not: what software is everyone else using? Ask this instead: Does this system actually fit the way our people work? Because if it does not, your staff will keep paying the price. And eventually, some of them will decide it is not worth it. Let’s fix the right problem Remote councils do not need another polished platform with a slick sales pitch. They need systems that reduce friction, support staff, and work in the conditions they are actually operating in. That is the work. That is what we build. And that is why your staff are not leaving because of the outback. They are leaving because of the systems. Want to talk about what’s not working in your current setup? Get in touch today .

Remote council CEOs carry accountability across services, communities, and funding bodies most organisations couldn't imagine.