Questions about working with RedRock.

RedRock Systems designs and builds custom software for Australian businesses with complex operations. That can include internal tools, connected workflows, data systems and carefully scoped AI features. We start by understanding the work, the people involved and the decisions the system must support.

RedRock Systems is based in Perth, Western Australia, and works with Australian businesses. Project meetings and reviews can take place remotely.

No. We work with operationally complex businesses across industries. Regulated work is a strength: we investigate obligations, approvals and record keeping where they matter, and ask the right subject-matter experts to validate them.

Work that crosses teams, tools or approval steps; information entered more than once; decisions that need a clear owner; or records that must remain understandable later. We assess the actual workflow before proposing a build.

We will say so. A custom system is useful when the workflow, constraints or connections between systems make standard tools a poor fit. Discovery can establish whether adapting what you already use is the better path.

Use the contact form and tell us the problem, who it affects and what you are hoping to improve. We review enquiries personally. A first conversation establishes whether further work makes sense; it is not a commitment to start a project.

It depends on the project. A written proposal should identify the services that store or process your information and the countries involved, including any overseas processing. Our Data Residency page describes our own systems separately.

Security requirements are part of the design. We document what needs protection, who needs access, and which controls fit the project. The security and hosting choices for one system should not be assumed for a new custom build.

We do not sell client data. Our privacy policy explains what we collect through this website and how providers may process it. Data handling for a custom project is set out in its agreement.

Export, retention and deletion need to be defined in the agreement for the system concerned. Ask us to include a clear handover and exit plan in a custom project's scope.

We choose the technology to suit the workflow, existing systems, security needs and long-term maintenance. A proposal should explain the major choices in terms your team can review.

It depends on scope and complexity. A focused compliance module for a specific regulatory obligation is a smaller, faster build than a full platform with multi-module compliance, role-based access, and external integrations. Discovery is a separately agreed first step. Its findings set the scope, and the written proposal that follows sets out the price and timing of each stage before you commit.

Yes. Post-launch support is set out in the written proposal. Ongoing support, maintenance, and product evolution are available under a retainer arrangement.

Often, but the answer depends on the other system's APIs, permissions, commercial terms and data rules. We investigate the specific connection during discovery and state what is feasible before it becomes a project commitment.

Software can support a process by making responsibilities, evidence and review steps visible. Your organisation and its qualified advisers remain responsible for interpreting requirements and making compliance decisions. We establish the relevant rules and validation points during discovery.

We map the work and the obligations that may affect it, then test our understanding with the people accountable for those obligations. The design makes owners, approvals, evidence and exceptions explicit. Any integration or compliance claim is checked before it is included in scope.