Skip to content
N
NOME DIGITAL

Service Agreement

What Nome Digital will build for you, what you owe us in return, who owns the code and the design, and what happens if either side needs to stop.

Document reference
ND-LGL-001
Last reviewed

1. Who this agreement is between

This agreement is between the client named on the quotation ("you") and Nome Digital ("we", "the studio"). It applies to the project described in the quotation and to the package you have selected. If the quotation and this document say different things about scope or price, the quotation wins, because it is the document you have actually agreed to.

Read together, these four documents are the whole contract: this Service Agreement, the Delivery Policy, the Payment Policy and the Refund Policy. Nothing is added to them by a side conversation, so anything we have agreed with you that is not written down should be put in writing before work continues.

We may update these policies from time to time. The version published when your quotation was issued is the version that applies to your project, unless we agree an amendment with you in writing.

2. Scope of the work

The scope is the package you selected plus everything listed on your quotation. Every package runs through the same six stages: discovery, strategy, design, development, testing and launch. The /process page describes each stage in full.

  • The design and build of the pages listed in your quotation, including responsive layouts and the components needed to make them work.
  • The design system behind those pages: type scale, spacing, colour, and the reusable components.
  • Motion and interaction direction, implemented where it is specified in the approved design.
  • Front-end development, the content or admin system your package includes, and the integrations listed in the quotation.
  • Technical setup: metadata, structured data, analytics where included, form handling, and a launch-ready build.
  • Testing across the browsers and devices we agree with you, and the fixes that come out of it.
  • Deployment, handover, documentation and the training session included at launch.

The following are not part of the fee unless they are quoted separately. If you want one of them, we will price it before we start rather than after.

  • Domain registration, hosting and paid licences, which are third-party costs and are billed separately from the development fee.
  • Copywriting, translation, photography, video and product imagery. We can source and direct all of these, but they are quoted work.
  • Marketing, advertising, paid campaigns and search-engine ranking. We set up the technical basics; we do not buy rankings.
  • Native mobile applications, and any software or service the project does not need.
  • Ongoing updates, backups and security patching after the support window, which are available as a maintenance plan but never required.

A few accounts have to belong to you rather than to us: your domain registrar, hosting, analytics, payment gateway merchant account, social accounts and any content system. We are happy to set these up on your behalf, but they must be registered in your name and you must be the account holder.

Where a request falls outside the agreed scope, we say so before we start it. If you want it anyway, we price it and add it to the schedule in writing. We will not quietly absorb it and then send you an invoice you did not expect.

3. What we need from you

A project moves at the speed of its inputs. We will always tell you clearly what we need and when we need it by, and we will never use a missing asset as a reason to hand over something incomplete without saying so.

  • Content and material: copy, images, logos, product data, prices, brand guidelines, and any existing site you want us to work from.
  • Access: accounts and permissions for your registrar, hosting, content system, analytics and payment gateway, plus the credentials to publish.
  • A named decision-maker who can approve design, scope and content. If more than one person has to agree to everything, the schedule has to allow for that.
  • Feedback that is consolidated: one message per round, covering the whole deliverable, rather than a trickle of separate comments.
  • Timely approval, in writing, of each deliverable when we ask for it. Approval is what unlocks the next milestone.
  • A check that anything you send us is yours to use, and that using it does not infringe anybody else's rights.

If an input is late, the delivery window moves with it. The Delivery Policy sets out exactly how that works, and it is not a penalty: it is just arithmetic.

4. Revisions and change requests

Each package includes a fixed number of revision rounds, and the number is stated on your quotation: two rounds for the Landing Page package, three for the Starter Website, four for the Business Website and four for the E-commerce Website. A Premium Custom build carries an agreed number of rounds fixed during discovery.

A revision round is one consolidated set of changes submitted together against an agreed deliverable. Once we present a deliverable, the round is open until you send your feedback; we then work through that feedback in one pass and present the revision.

  • Send every change for that round in one message, ideally in one place. Feedback that arrives piecemeal across a week does not give you more rounds than the one you have.
  • We confirm in writing what we are changing and what we are not, so that nothing is silently dropped and nothing is silently ignored.
  • New work is not a revision. A new page, a new feature, a different visual direction after sign-off, or a change to the agreed scope is a change request: we price it, and it adds to the timeline.
  • Fixing a defect against the approved design is not a revision, and it is not limited by the revision count. Defects get fixed.
  • Third-party costs for anything new, such as a paid plugin or a licence, are quoted at cost and billed separately.

If a design direction changes after you have approved it, that is a new direction rather than a refinement. We will price it and tell you the schedule effect before we start, so the decision stays yours and stays informed.

5. Intellectual property and handover

The work is yours. From the moment the final payment has cleared, we assign to you all rights in the custom design, the source code, the content we produced for you and the project-specific documentation. That includes the repository history and the design files, not just a screenshot of them.

Handover happens at launch and includes: access to the source repository, admin access to the content system, the domain and hosting accounts in your name, the documentation, and the training session. You are not left holding a website you cannot maintain.

  • We may show the finished project in our portfolio after launch, unless you ask us in writing not to. If you would rather we did not, say so before handover and we will remove it.
  • Your materials, content and brand assets remain yours at all times, before and after handover.
  • We keep ownership of our own internal tooling, general-purpose libraries and techniques, such as build pipelines, animation helpers and starter kits, and we license those to you for use inside your project. That licence is non-exclusive and royalty-free for that project.
  • Third-party components keep their own licences. See the next section.

6. Third-party components and services

Most professional websites sit on top of other people's work: open-source libraries, fonts, a content system, a hosting provider, a payment gateway. We use them because reinventing them would cost you money without making the site better.

  • Open-source components are used under their published licences. Where a licence requires attribution, or restricts a use, we tell you before launch.
  • Paid licences, such as premium plugins, fonts or themes, are billed to you at cost and stay yours, subject to the provider's own terms. We do not lock you into a subscription to keep a site running.
  • Where a third party changes or withdraws a service the project depends on, we will work around it where that is commercially reasonable, and we will tell you if it changes the cost or the timeline.
  • Your hosting, domain and gateway accounts are yours from the start. We work inside your accounts rather than holding them for you.

7. Confidentiality

We treat your business information, unreleased designs, product data and commercial terms as confidential, and we use them only to deliver your project and to support it afterwards.

We may describe the project anonymously in our portfolio, for example as a twelve-page business website for a services company, unless you ask us not to. We will not publish your name, your figures or your screens without your written permission.

The confidentiality obligations do not apply to information that is already public, that you ask us to publish, or that we are required to disclose by law. Where the law allows it, we will tell you before we disclose anything.

8. Fees and payment obligations

Fees are quoted in Pakistani Rupees and the price for an agreed scope is fixed. We do not bill by the hour, and we do not issue invoices you have not already seen as part of a quotation.

Payment follows the milestone split set out in the Payment Policy: a deposit before work begins, a payment when the design is approved, and a final payment before launch and handover. Work on a stage starts when the payment that unlocks it has cleared.

Domain, hosting, licences and payment gateway fees are not part of the development fee and are billed separately. The Payment Policy lists them.

9. Liability

We take reasonable care in what we do, we are liable for breaching this agreement, and we will put right a defect in the delivered work. We are not liable for indirect or consequential loss, such as lost profit, lost revenue, lost data or lost goodwill, except to the extent that such loss results from our breach of our confidentiality or intellectual property obligations.

  • We are not liable for the acts, omissions or outages of third-party providers such as hosting, registrars, gateways, email or messaging services.
  • We are not liable for events outside our reasonable control, including natural disasters, civil unrest, and failures of power or internet connectivity.
  • Our total aggregate liability for any claim is limited to the fees you paid us for the project that gave rise to it.
  • Nothing in this agreement limits liability that cannot lawfully be limited.

10. Termination

Either of us may terminate this agreement for material breach that is not remedied within ten working days of written notice describing the breach. If we terminate for your breach of the payment obligations, we hand over the work completed to that point, for which payment has cleared, and we invoice you for it.

You may cancel the project at any time. On cancellation we do three things: we deliver and hand over the work completed and paid for, we refund amounts you have paid for work that has not started, and we keep the work already produced. The Refund Policy explains how that is calculated.

  • We may pause work if an invoice is overdue. We will warn you and give you a chance to settle it first.
  • A pause we have to make on the project side also pauses the delivery window, in the same way a pause on your side does.
  • On termination we provide the repository, the documentation and the credentials for whatever has been paid for, so that you can hand the project to someone else.

11. Status, governing law and your rights as a client

Nothing in this agreement creates a partnership, employment relationship or agency between us. We are an independent contractor, and you are a client, not an employee, partner or agent of the studio.

This agreement is governed by the laws of Pakistan, and the courts of Karachi have jurisdiction over it. The Terms and Conditions set out the dispute resolution steps we agree to follow before any proceedings.

If you are a consumer, nothing in this agreement removes any right you have under Pakistani consumer law that cannot lawfully be removed.

12. Changes to this agreement

We can update this agreement when our commercial terms change. A material change applies to projects that start after it is published. If a change affects a project already running, we will tell you before it takes effect and agree how it applies.

Questions about anything in this agreement are welcome before you sign, not after. Send them to us and we will answer in writing so the answer becomes part of the record.