Working together

Clear expectations before the work starts.

This page is a practical overview, not a substitute for the written agreement that governs a specific engagement.

Engagement types

Work may begin as a technical audit, a new product or feature build, an existing-platform takeover, or an AI and integration project.

Estimates and billing

Estimates are based on the current understanding of the work and are refined as unknowns become clearer. Hourly work is billed at the agreed rate and scope changes are discussed before additional work proceeds.

Communication and availability

I prefer clear, asynchronous communication with focused meetings when they add value. Availability, response expectations, and any support window are agreed for each engagement rather than assumed.

Client responsibilities

Clients provide timely access, decisions, feedback, domain context, and approvals needed to keep delivery moving. Sensitive access should be shared through an agreed secure channel.

IP, confidentiality, and handover

Ownership, licence terms, confidentiality, and handover materials are agreed in writing for the engagement. Delivery includes practical notes where they are needed to operate or maintain the system.

Support after launch

Post-launch support can cover bug fixes, monitoring, release work, maintenance, or further development. The scope and response expectations are agreed separately from the initial build.

Questions about fit or engagement terms? Email regan@rbtrends.com.au or use the contact form.