How we work together.

You're welcome to browse, share links, and quote from this site with attribution. Don't scrape it for training data, reproduce it wholesale, or use it in a way that could mislead someone about who made it.

We make reasonable efforts to keep content accurate and the site functional, but we don't guarantee either. Links to external sites are provided for reference — we're not responsible for what's on them.

Every project starts with a Discovery session. Nothing is committed on either side until we've agreed on scope, deliverables, cost, and timeline in writing. Verbal agreements and email threads don't substitute for a signed scope document.

The scope document is the source of truth for the project. If something isn't in it, it isn't included. If you want it added, we'll scope and price it separately — no surprises in either direction.

We invoice at milestones defined in the scope document — typically on project start, at key delivery points, and on completion. Payment is due within 14 days of each invoice.

If an invoice is overdue by more than 14 days without agreed deferral, we reserve the right to pause work until it's resolved. We'd rather sort it with a conversation than let it sit — so if something comes up on your end, tell us early.

Once a project is paid in full, you own the deliverables — the code, designs, and assets produced specifically for you. We transfer all relevant intellectual property at that point.

Third-party tools and open-source libraries used in your project retain their own licences. We'll document what's in your stack and what licences apply as part of the handoff.

We retain the right to list finished projects in our portfolio and describe the work in general terms. If you'd prefer we didn't — for confidentiality reasons or otherwise — say so at project start and we'll agree on it in writing.

If you want something that wasn't in the scope document, we assess it and quote separately before doing it. That's not a barrier to changing your mind — it's what keeps the project from quietly growing into something neither of us planned for.

Small adjustments within the spirit of what was agreed are handled pragmatically. The scope document will define what counts as a minor change versus a new request for the specific project.

We'll deliver what's in the scope document, to the standard described, within the agreed timeline. If something on our end puts that at risk, we'll tell you immediately — not at the deadline.

We don't subcontract work to third parties without telling you. The people you meet in Discovery are the people who build the project.

Projects move at the speed of the slowest feedback loop. We need content, approvals, and decisions within the timeframes set in the scope document. If your side runs late, the timeline shifts accordingly — this isn't punitive, it's just how sequential work operates.

If you're supplying content or data for us to work with, you're responsible for having the rights to use it.

Our liability for anything arising from a project is capped at the total amount paid for that project. We're not liable for indirect or consequential losses — lost revenue, lost data, missed opportunities — even if we were aware they were possible.

We're also not liable for failures of third-party services (hosting, databases, APIs) that are outside our control. We choose dependable providers and document them clearly, but we can't guarantee uptime on their behalf.

Either party can end a project engagement with written notice. If you terminate, you pay for work completed to that point. If we terminate — which would require a serious reason — we'll refund any prepaid amount for work not yet started.

These terms are governed by the laws of New South Wales, Australia. Any dispute that can't be resolved between us directly goes to the courts of New South Wales.

Questions about these terms or a specific project: hello@tinkertogether.studio