Clear ownership.
Clear handover.

1. Parties and project document

Provider: Shi Lin, operating as Linshi Studio, an individual service provider based in China. Formal project correspondence: hello@linshistudio.com.

Client: the business named in the written project scope, acting through the contact and billing email recorded there.

The signed or expressly accepted written scope, this template and any stated project-specific schedule form the project agreement. If they conflict, the project-specific written scope takes priority only where it clearly says it changes this template.

2. Scope, acceptance and payment

The written scope identifies the agreed pages, features, exclusions, client materials, price, payment milestones, expected delivery route, revision allowance and handover items. Work outside that scope needs a separate written quotation or written variation before it begins.

For standard website builds, payment is normally 50% to book the project and 50% after final approval and before live-domain launch or transfer. Any alternative payment arrangement is written in the project scope. Payment is requested by PayPal in GBP after the scope is accepted.

Acceptance is recorded in writing. A client should report any agreed-scope delivery fault within seven calendar days of handover, with the affected page and enough detail to reproduce it.

3. Materials, source files and permissions

Client materials

Text, logos, photographs, videos, trademarks, account content and other materials supplied by the client remain the client's responsibility and property or licensed material. The client confirms it has the permission needed for Linshi Studio to use them for the agreed project.

Client-specific work

After final payment has cleared, the client receives the client-specific source code and editable design files that are expressly listed in the written scope and handover checklist. The client may use, change and appoint another provider to maintain those delivered project-specific materials.

Pre-existing and third-party material

Linshi Studio retains ownership of its pre-existing tools, reusable methods, generic components, internal templates and know-how. Where an included final deliverable contains one of those items, the client receives a perpetual, non-exclusive licence to use it as part of that delivered website. Fonts, stock images, icons, plugins, templates, hosted platforms, open-source libraries and other third-party items remain subject to their own licences and service terms. The written handover record lists the relevant item, supplier or licence route and any client action or renewal required.

No client is promised ownership of a third-party licence or platform account unless the provider's own terms permit its transfer and the written scope says that transfer is included.

4. Accounts, final backup and handover

Where the relevant service allows it, the client keeps control of the domain, hosting, billing and essential third-party accounts. New client-facing accounts should be created in the client's name where practical. Main passwords should not be sent by ordinary email; separate administrator access or an approved access method is used instead.

At final handover, the checklist identifies and, where included in scope, supplies: the live URL; final approved source code or exported website files; editable design files; client-provided materials held for the project; project-specific assets created for the project; the content or database export available from the relevant platform; account roles and access-removal steps; and the third-party licence or renewal list.

The final handover archive is placed in a client-controlled folder, repository or account agreed in the written scope. It includes a dated handover note that identifies the archive contents, file versions, live publishing route and the practical restoration route available for that platform. If a service does not provide export or restore functionality, the checklist says so rather than implying that a backup exists.

The restoration route explains the agreed platform steps, the account needed to perform them and any dependency that must be restored first. The client should download and retain its own copy at handover. Unless ongoing backup is separately agreed in writing, Linshi Studio is not the long-term custodian of the client's production backup or third-party account data.

For an agreed live change, a restorable pre-change backup is made only where the platform permits and the change is within written scope. This does not guarantee a third-party host's own backup service or recovery time.

5. Delivery fault, early end and refund

For seven calendar days from handover, a reported fault that prevents the agreed delivered scope working as specified is reviewed and, where confirmed, repaired without an additional fee. This period is not an automatic maintenance plan and does not cover new requests, client changes, third-party changes or hosting failures outside the agreed scope.

If an agreed part cannot be delivered and cannot be reasonably remedied, the client receives a proportionate refund of the payment allocated to that undelivered part in the written scope. If the project ends early, the parties record in writing the completed work, remaining work, available handover materials and any resulting refund position.

6. Notices and practical resolution

A formal project notice must be sent from the client's agreed contact email to hello@linshistudio.com with the subject line “Formal Project Notice — [client name] — [project]”. Linshi Studio sends a formal notice from hello@linshistudio.com to the client email recorded in the written scope. A notice is treated as received on the next business day if it is not returned as undeliverable.

Before court proceedings, either party should describe the issue, the remedy sought and supporting records in writing. The parties will first try in good faith to resolve the issue directly using the written scope, delivery checklist, handover record and payment record. This does not stop either party from taking urgent steps needed to protect its rights.

7. Governing law and disputes

This business-client project agreement, and any non-contractual dispute or claim arising from or connected with it, is governed by the law of England and Wales.

The courts of England and Wales have exclusive jurisdiction to settle any dispute or claim arising from or connected with this agreement. Nothing in this template excludes or limits a right that applicable law does not permit either party to exclude or limit.

This fixed clause is used for business clients. If a proposed project is for a consumer rather than a business, or requires a materially different jurisdiction arrangement, it must be reviewed and agreed in writing before payment rather than assumed from this public page.

8. No outcome promises

Linshi Studio does not promise search ranking, AI inclusion, citation, traffic, enquiries, revenue or any other commercial result. The agreement concerns the stated website work, agreed checks and documented handover only.