Frequently Asked Questions

For custom software developed under a project delivery engagement, intellectual property is typically assigned to you upon final payment, unless otherwise agreed in writing. You receive source code, deployment documentation, and credentials needed to operate the system. We retain the right to use general techniques and non-client-specific components. Specific terms are stated in our project agreement.

Yes. We can deploy and manage hosting on cloud infrastructure as part of a project or ongoing support arrangement. Alternatively, we can deploy to infrastructure you control and provide documentation for your IT team to manage. Hosting approach, costs, and responsibilities are agreed during scoping. See our Cloud Deployment page for more detail.

We select technologies based on project requirements, maintainability, and your existing environment — not a fixed stack applied to every job. Common choices include modern web frameworks, relational databases, REST and webhook integrations, and cloud hosting platforms. We explain our recommendations during design and document the architecture so future developers can work with the system if needed.

Scope changes are a normal part of software projects, but they need to be managed explicitly. When you request something outside the agreed scope, we assess the impact on timeline and cost and provide a change quote before proceeding. Minor adjustments that do not materially affect deliverables may be absorbed within the project; substantial additions are documented and priced separately so there are no surprises at invoice time.

Yes. We treat client information as confidential by default and are willing to sign mutual non-disclosure agreements before detailed discussions. We do not use client-specific business logic or data in work for other clients. If your industry or procurement process requires specific contractual terms, raise them early so they can be addressed before work begins.

A brief description of the problem you want solved, who will use the software, and any systems it must connect to is a good start. Sample workflows, screenshots of current tools, or examples of reports you need are helpful but not required. If you have a budget range or deadline in mind, sharing that allows us to suggest a realistic approach. We can also help you shape requirements if they are not yet fully defined.

Project delivery engagements are typically invoiced at agreed milestones — for example, upon design approval, mid-build review, and final delivery. Support retainers are invoiced monthly in advance or arrears depending on the arrangement. Consulting is invoiced on agreed terms, either time-and-materials or fixed fee. All invoices are in Australian dollars with payment terms stated on each invoice. Quotes and payment schedules are provided before work commences.

Yes. Many clients have internal IT staff or an external managed services provider handling infrastructure, identity, or networking. We coordinate on access, deployment environments, firewall rules, and handover responsibilities. Clear division of labour is documented — for example, we build and deploy the application while your IT team manages domain DNS or corporate SSO configuration. Shared access to staging environments and agreed change windows help avoid deployment surprises.

Project delivery includes a warranty period — typically thirty days after go-live — covering defects in functionality delivered under the agreed scope. If behaviour does not match documented acceptance criteria, we correct it at no additional charge. Warranty does not cover new features, changes to business rules, issues caused by third-party system changes outside our control, or problems arising from unauthorised modifications. After warranty, ongoing support is available under a separate arrangement. See Maintenance & Support for detail.