Terms of Service
A Warm Welcome
We are genuinely glad you are here. At ORbix Studio, every project we take on is a collaboration we care deeply about — and these Terms exist not to create distance, but to give our work together the clearest, most respectful foundation possible.
These Terms of Service ('Terms') form a binding agreement between ORbix Studio ('we', 'us', 'our') and you, the Client. By proceeding with a project — whether through signing a proposal, making a payment, or giving us a go-ahead — you are confirming that you have read and agreed to these Terms.
Think of these Terms as our shared rulebook — designed so that both of us know exactly what to expect, and neither of us is ever left guessing.
1. The Services We Provide
ORbix Studio offers UI/UX design services alongside low-code, no-code, and custom code development. Every engagement is unique, which is why all services are defined specifically in your signed Project Proposal and Scope of Work ('SOW').
The SOW is the single source of truth for your project. If something is not listed there, it is not included — and that is intentional, so you always know exactly what you are getting and exactly what you are paying for.
2. Scope of Work — What's Included and What Isn't
2.1 The Includes / Excludes Clause
The SOW is the single source of truth for your project. If something is not listed there, it is not included — and that is intentional, so you always know exactly what you are getting and exactly what you are paying for.
The SOW is the single source of truth for your project. If something is not listed there, it is not included — and that is intentional, so you always know exactly what you are getting and exactly what you are paying for.
Think of these Terms as our shared rulebook — designed so that both of us know exactly what to expect, and neither of us is ever left guessing.
2.2 How We Handle Out-of-Scope Requests — The Change Request Process
When new ideas come up during a project — and they often do — we welcome them. Here is the process we follow so that additions are handled fairly and transparently:
A quick note on informal channels: messages sent via WhatsApp, Telegram, or personal DMs are wonderful for staying in touch, but they do not constitute formal scope approvals. All changes require a signed Change Request.
2.3 Technical Handoff Documentation
Detailed handoff documentation — covering custom code, plugin configurations, and system architecture — is not a standard deliverable unless explicitly listed in your SOW. If you would like this, please let us know before the project begins. Every project includes a concise project summary as standard.
3. Revisions — How They Work
3.1 What a Revision Round Means
Revisions mean changes to existing work within the approved scope. Anything new — additional features, new pages, new functionality, or a fundamentally different creative direction — is a Change Request and will be handled accordingly.
Please gather all feedback for a round before submitting. Drip-fed feedback over days counts as a new round — this protects the flow and quality of the work for both of us.
3.2 What Counts as a Revision vs. a Change Reques
3.3 Contradictory Feedback
If feedback in one round contradicts feedback from a previous round — for example, 'make it bolder' followed by 'actually, make it more subtle' — the second direction counts as a new revision round, not a correction. We say this gently but clearly: changing direction uses a revision round.
3.4 Additional Revision Rounds
Additional revision rounds beyond your included allowance are always available. They are billed at a pre- agreed rate and must be paid before the additional work begins. Your project proposal will state the rate clearly.
3.5 Silent Approval — Keeping Things Moving
When we share a deliverable with you, we ask for your response within 5 business days. If we do not hear back within that window, the deliverable will be considered approved and the project will move to the next phase.
Once a deliverable is approved — either explicitly in writing, or via the 5-day silent approval window — it is locked. Returning to revise an approved deliverable requires a new Change Request.
4. Your Project Brief & AI-Generated Requirements
4.1 The Brief Verification Step
A clear, accurate brief is the foundation of great work. Before we begin, we will review your requirements together to make sure everything is aligned, feasible, and agreed upon. You will be asked to formally sign off on the brief before work commences.
4.2 A Note on AI-Generated Briefs
We understand that many clients today use AI tools like ChatGPT to help articulate ideas. We welcome this
— but ask that you personally review any AI-generated content before sharing it with us. AI documents can
sometimes contain directions that are technically unworkable, contradictory, or broader than the project
budget allows.
• All AI-generated briefs must be reviewed and endorsed by you as accurate and achievable before
submission.
• We will flag content that is unclear or technically unworkable, and work through it with you before
commencing.
ORbix Studio is not liable for delays, rework, or additional costs resulting from inaccurate or unverified requirements submitted by the Client — including those generated by AI tools.
5. Intellectual Property & File Access
5.1 Ownership During the Project
A clear, accurate brief is the foundation of great work. Before we begin, we will review your requirements together to make sure everything is aligned, feasible, and agreed upon. You will be asked to formally sign off on the brief before work commences.
5.2 Figma Access
We will share view-only Figma access throughout the project for review and feedback. Edit access to Figma files is not available at any stage. Final assets will be delivered in agreed formats upon full payment.
5.3 GitHub & Code Repositories
Development happens within ORbix Studio's own repositories unless Client GitHub access is explicitly agreed in the SOW. Any mid-project request to move to a Client repository is a scope change.
5.4 Hosting Environment
Unless your SOW specifies otherwise, we develop and stage projects in our own environments. Requests to switch to Client hosting mid-project will be treated as a scope change.
5.5 Staging Approval Before Production
No project will be deployed to a live production environment without: (a) your approval of the staging version in writing, and (b) authorisation from ORbix Studio's Project Manager. Staging approval is a required step — not optional.
5.6 Transfer of Ownership
Upon receipt of full payment, ownership of agreed deliverables transfers to you. Partial payments do not grant partial ownership. Staging previews and Figma view access are shared in good faith and do not reduce or alter outstanding payment obligations.
6. Client Responsiveness
6.1 Response Time Commitment
We ask that you respond to all feedback requests, approval requests, and project communications within 5 business days. We understand that life gets busy — if you know you will be unavailable, simply let your Project Manager know in advance and we will plan around it.
6.2 Project Hold Protocol
If we do not receive a response within 5 business days of a communication requiring your input, we will issue a formal Project Hold notice. Work will pause and the timeline will shift by the number of days the project remains on hold.
6.3 Project Abandonment Clause
If we do not receive a response within 15 business days of a Project Hold notice being issued, the project will
be considered abandoned. Upon abandonment:
• All payments made to date are non-refundable.
• Orbix Studio retains ownership of all work product not yet delivered.
• The contract is terminated.
• If you wish to resume the project after abandonment, a new engagement and new deposit will be
required.
We include this clause not as a threat, but as a fair protection for both sides. It ensures that our team's time and your investment are both treated with respect.
7. Communication Protocol
All project communication must flow through the designated project channel agreed at kickoff. Direct contact with individual designers or developers via personal social media, personal phone, or personal email is not permitted and will not be actioned as a formal instruction.
The Project Manager is the single point of contact for all feedback, approvals, and change requests. This keeps your project moving efficiently and ensures nothing falls through the cracks.
Orbix Studio aims to respond to all official communications within 1–2 business days.
8. Payment
8.1 Milestone-Based Payment Structure
We structure all projects on a milestone-based payment model. This means payment unlocks each phase of work, so that neither party ever has more at stake than the other.
Work on the next milestone will not begin until the current milestone payment is received and the previous deliverable has been formally approved in writing.
8.2 Late Payment Protoco
We understand that timing can sometimes be tricky. Here is how we handle late payments, fairly and
transparently:
• Grace period: 3 business days after the invoice due date before any action is taken.
• Day 4: A friendly reminder email referencing the invoice.
• Day 8: All work pauses until payment is received. The timeline shifts by the number of days delayed. A
late fee of 1.5% per week (compounding) begins on the outstanding balance.
• Day 30+: ORbix Studio reserves the right to terminate the contract, retain all payments received, and retain ownership of all undelivered work.
Staging previews and Figma view-only links are shared in good faith. They do not constitute delivery and may
not be used as a basis for payment renegotiation or discount requests
9. Our Commitment to You
Orbix Studio commits to performing all work with skill, care, and professionalism. We do not make guarantees about specific business outcomes, but we do promise to give your project our genuine best. Our total liability in any circumstance will not exceed the total fees paid for the specific project in question. We are not liable for indirect, third-party, or consequential losses.
10. Force Majeure
Neither party shall be held liable for delays or failure to perform caused by circumstances beyond their reasonable control — including but not limited to natural disasters, platform outages, government actions, civil unrest, or other unforeseeable events. In such cases, both parties will communicate promptly and work in good faith to resume the project as soon as possible.
11. Dispute Resolution
We sincerely hope we never need this section — but it is here just in case. In the event of a dispute, the following process applies:
Our goal is never to be adversarial. These steps exist so that, if something does go wrong, we have a clear and civilised path to resolution.
12. Ending a Project Early
Either party may end the engagement with 14 days written notice. If that occurs:
• The Client is responsible for payment of all work completed to date, calculated at the project rate.
• Deposits are non-refundable once work has commenced.
• Completed and paid phases will be delivered. Work in progress will not be released.
13. Governing Law
These Terms are governed by the laws of the jurisdiction in which ORbix Studio is registered. We commit to approaching any legal matter in good faith and with professionalism.
.svg)
.svg)
