Question 1

How much does a project cost?

Accepted Answer

Cost depends on scope, complexity and integrations, so we do not publish fixed prices. After an initial conversation we prepare a written proposal with the scope and fee. For larger or less certain projects we may suggest a short discovery phase first, so the estimate is based on detail rather than guesses.

Question 2

How long will my project take?

Accepted Answer

We only commit to a timeline once the scope is defined. Your proposal sets out the phases or milestones. Delays in receiving access, data, decisions or approvals can affect the schedule, and we will tell you early if anything threatens it.

Question 3

How are payments structured?

Accepted Answer

Proposals quote a fee for the agreed scope, paid in milestones — for example on confirmation, on design approval, during development, at user acceptance testing and at go-live. The exact milestones and percentages are set out in each proposal. Applicable GST is added to invoices.

Question 4

Are third-party costs included?

Accepted Answer

Usually not, unless the proposal says so. Software licences, cloud hosting, domain registration, SMS or payment-gateway charges and external API subscriptions (including AI services) are typically paid separately, often directly by you to the provider.

Question 5

What happens if our requirements change during the project?

Accepted Answer

Changes are normal. Significant changes beyond the approved scope are estimated separately and agreed with you before the work is done, so you always know the effect on cost and schedule.

Question 6

What do you need from us to start?

Accepted Answer

A clear description of the problem, the people who will use the software, any existing systems or data involved, and a decision-maker who can answer questions and approve work. Rough documents, spreadsheets and screenshots of current tools are all useful.

Question 7

Will we be able to review the work before launch?

Accepted Answer

Yes. Work is reviewed with you at agreed milestones, including user acceptance testing before go-live, so issues are found and fixed before your team relies on the system.

Question 8

Who owns the source code?

Accepted Answer

What is delivered — including whether source code is handed over — and the ownership and licensing terms are set out in your proposal or agreement before work starts. Third-party libraries and services remain under their own licences.

Question 9

How do you handle our data?

Accepted Answer

We ask only for the data a project needs and use it only for that project. Where third-party services such as hosting or AI providers would process your data, we tell you which ones before connecting them.

Question 10

What support do you provide after launch?

Accepted Answer

Proposals include a complimentary bug-fix support period after go-live; its length is stated in each proposal. After that, ongoing maintenance — such as bug fixes, security updates and technical support — is available under an optional annual maintenance contract (AMC) agreed separately.

Question 11

Can you integrate with the software we already use?

Accepted Answer

If your existing tool offers an API, webhook or reliable export, integration is usually possible. We confirm feasibility by reviewing the tool’s documentation before committing to it in the scope. Any fees charged by that tool’s provider are separate.

Frequently
asked questions.

Cost & timelines

Scope & changes

Ownership, data & support

Service-specific questions

Still have
a question?

Frequentlyasked questions.