1. How a project begins
An enquiry or intro call is exploratory and does not commit either of us. Once I understand the requirements, I will provide a written proposal, quote or statement of work describing the deliverables, fee, payment schedule, assumptions and expected timeline.
A project begins when the client accepts that document in writing and pays any deposit it requires. The accepted proposal, any statement of work and these terms form the agreement. If they conflict, the accepted project-specific document takes priority.
2. Scope and deliverables
The project includes only the work and deliverables described in the accepted proposal. Anything not listed—including extra pages, features, integrations, content entry, migration or ongoing support—is outside scope unless we agree otherwise in writing.
I may make reasonable technical and implementation decisions needed to deliver the agreed outcome, while keeping the client informed about decisions that materially affect cost, timing or functionality.
3. Client responsibilities
The client will provide accurate requirements, content, brand assets, approvals, access credentials and feedback when reasonably needed. The client should appoint one person who can consolidate feedback and approve decisions.
The client confirms that they have permission to use any text, images, fonts, trademarks, data or other materials they supply. Delays in supplying materials, access or decisions may move the delivery schedule.
4. Fees, invoices and expenses
The proposal states the project fee, applicable taxes, deposit and payment milestones. Invoices are due by the date shown on them. Approved third-party costs—such as hosting, domains, software, fonts or stock assets—are separate unless the proposal expressly includes them.
I may pause work while an invoice is overdue. Final files, production handover and any rights that depend on payment are released after the relevant invoices have been paid in full.
5. Changes and additional work
Either party can suggest a change. Before out-of-scope work begins, I will explain any material effect on the fee, timeline or deliverables and we will confirm the change in writing. I am not required to begin additional work until that change is accepted.
6. Timelines, feedback and acceptance
Delivery dates are good-faith estimates unless the proposal expressly makes a date binding. They depend on timely client input and on third-party services outside my control.
The client should review each milestone promptly and identify any material difference from the agreed scope. I will correct genuine defects against the agreed specification. New preferences, new requirements and changes to previously approved work are handled as changes to scope.
7. Third-party services
A project may rely on hosting providers, domain registrars, content systems, payment processors, analytics tools, libraries or other third-party services. Their own terms, availability and pricing apply. I am not responsible for an outage, policy change or failure caused by a third party, but I will make reasonable efforts to help diagnose and mitigate issues within the agreed scope.
8. Intellectual property and portfolio use
The client keeps ownership of materials they supply. Once the project has been paid in full, the client receives the ownership or usage rights for the custom final deliverables described in the proposal.
My pre-existing tools, reusable components, methods and general know-how remain mine; the client receives the licence needed to use them as part of the delivered project. Open-source and third-party materials remain subject to their own licences. Unless we agree confidentiality in writing, I may identify the client and show the completed public work in my portfolio after launch.
9. Confidentiality and information
Each party will take reasonable care of non-public business, technical and commercial information received for the project and will use it only as needed to carry out the work. The client should not send personal data or confidential credentials unless they are necessary and shared through an appropriate secure method.
10. Pausing or ending a project
Either party may ask to pause or end a project in writing. The client remains responsible for work completed up to that point and for approved costs that cannot reasonably be cancelled. Any deposit or refund treatment stated in the proposal also applies, subject to mandatory law.
After payment of the amount due, I will provide any usable completed work that the proposal requires me to hand over. Either party may end the agreement for a serious breach that the other party does not remedy within a reasonable period after written notice.
11. Quality, support and project outcomes
I will perform the services with reasonable professional care and test the work in the environments agreed in the proposal. Any warranty, defect-fixing period, maintenance or ongoing support is limited to what the proposal states.
Websites and digital products can support commercial goals, but results such as revenue, rankings, traffic, conversion rates or uninterrupted third-party availability cannot be guaranteed.
12. Consumer rights, project-specific terms and questions
Nothing in these terms removes rights or remedies that the law does not allow either party to exclude. If the client is acting as a consumer, mandatory consumer protections—including any applicable cancellation or withdrawal rights—continue to apply. If a consumer asks for services to begin during a statutory withdrawal period, any required express request and acknowledgement will be handled in the project agreement.
Any governing law, dispute process or additional project-specific conditions will be stated in the accepted proposal or contract.
Questions about these terms can be sent directly to contact@builtbytayyab.com.