The terms, written to be read.

Last updated 19 October 2026 · Yume Systems, Islamabad, Pakistan

1. Who these apply to

These terms cover use of this website and any work we do for you, unless we have signed a separate written agreement with you — in which case that agreement wins wherever the two differ.

“We” and “us” mean Yume Systems, Islamabad, Pakistan. “You” means the business engaging us.

2. How an engagement starts

Nothing is binding until there is a written scope and you have accepted it. A conversation, a quote in an email thread or an estimate given on a call is not a contract, and we will not treat it as one.

Most engagements begin with Discovery: a paid piece of work that produces your process mapped properly, a written scope with the screens listed, and a fixed price. The Discovery document is yours to keep whatever you decide afterwards, and its fee is credited in full against the build if you proceed with us.

3. Scope and changes

The written scope defines what is included. Anything outside it is a change, and changes are quoted separately before being done — so a new requirement in week four is a decision you make with a price in front of you, not a surprise on the final invoice.

We will not do extra work silently and bill for it afterwards, and we will not let a scope quietly expand without saying so.

4. Fees and payment

• Standard terms: 40% to begin, 60% before go-live.
• Larger projects: 40% / 30% at the midpoint / 30% on delivery, against milestones rather than dates.
• Monthly plans: billed in the first week of the month, in advance, cancellable any month with no notice period.
• Methods: bank transfer, JazzCash, Easypaisa, or Wise for international clients.
• Taxes and transfer fees are yours unless we have agreed otherwise in writing.

Published prices are indicative ranges, not an offer. Your price is the one in your written scope.

If an invoice is significantly overdue we may pause work, and we will tell you before we do rather than simply going quiet.

5. What we need from you

Projects slip for one reason more than any other: waiting on the client. To hold a timeline we need:

• A decision-maker who can approve things without a committee
• Content, data and access when we ask, not at the end
• Feedback within a reasonable period at each milestone
• Accurate information — we build against what you tell us

Where a delay is on your side, timelines move accordingly. We will say so at the time rather than raise it later as an excuse.

6. Ownership

• Your code is yours on final payment, in writing. The repository, accounts, credentials and documentation transfer to you.
• Your domain is yours and is registered in your name from the start, never ours.
• Your data is yours. We hold it to do the work and return or delete it on request.
• Before final payment the work remains ours, which is simply how staged payment works.
• General knowledge — techniques, patterns and our own pre-existing tools and libraries — stays ours and may be reused. Nothing specific to your business is ever reused for anybody else.
• We will not name you as a client, publish a case study or screenshot your system without asking you first in writing.

7. Third-party services

Projects usually rely on services we do not control: hosting, payment gateways, SMS providers, mapping, email delivery, app stores. We will integrate them properly and tell you which ones a project depends on.

We are not responsible for their outages, their pricing changes, their policy changes, or an app store's review decision. Where one of them breaks something, we will help you fix it — under support if you have it, or quoted if you do not.

8. Confidentiality

We keep what you tell us confidential, and we will sign your NDA or provide ours before you send anything sensitive. That obligation does not end when the project does.

It runs both ways: our written scopes, estimates and documentation are provided for your use and not for passing to another supplier as a specification to quote against.

9. Support and warranty

Three months of support is included after go-live. Within that period we fix defects — that is, the system not doing what the written scope said it would — at no charge.

What is not a defect: a change of mind, a new requirement, something outside the agreed scope, or a problem caused by someone else modifying the system. Those are quoted as changes.

After three months, a monthly agreement is available and is never compulsory.

10. Liability

We will do the work carefully and fix what we get wrong. What we cannot do is accept unlimited exposure for consequences we have no control over, so:

• Our total liability for any engagement is limited to the fees you have paid us for it.
• We are not liable for lost profits, lost business, lost data where backups were available, or indirect losses.
• Nothing here limits liability where the law does not permit it to be limited.

We would rather state that plainly than bury it. If your organisation needs different terms, tell us before we start and we will discuss them.

11. Ending an engagement

Either of us may end a project in writing. If you do, you pay for work completed to that point and we hand over everything completed, including the documentation. We will not hold finished work hostage over a dispute about the rest.

Monthly plans can be cancelled any month, with no notice period and no exit fee.

12. Using this website

The content here — text, design, illustrations and screenshots of our own work — is ours. You are welcome to read it, quote it with attribution and send it to a colleague. Do not republish it as your own.

The demonstration sites we link to are fictional businesses with made-up data, and each says so on the page. They exist to show how we build, not to represent a real company.

The site is provided as it is. We keep it accurate and we correct errors when we find them, but we do not warrant that it is free of them.

13. Law and disputes

These terms are governed by the laws of Pakistan, and the courts of Islamabad have jurisdiction, unless a signed agreement with you says otherwise.

Before anything formal, talk to us. Most disputes in this industry come from an expectation that was never written down, and the written scope usually settles it in one conversation.