What we agree,
written down.

A contract is a small shared memory. You write down what both parties already believe, so that later, when the memory falters or the weather changes, the paper can speak.

By engaging Bit Studio. Through a written brief, a scope document, a WhatsApp message that ends with 'let's do it', or a transferred deposit. You accept the terms below. They apply to every piece of work we make together until we agree otherwise, in writing, also together.

You own the work. When the final invoice clears, the code, the design files, the copy, the brand assets, the deployment keys. They are yours. Unambiguously. We do not believe in surprise-you-later licensing.

We retain the right to name you as a client, to show the work in our portfolio, and to speak about the work in public talks, case studies and social posts. If a project is under embargo or genuinely confidential, tell us before we start and we will honour it.

We keep the right to reuse internal patterns. Hooks, utilities, component primitives we built before and during your project. You do not license our library to us; we simply do not re-license ours to you.

We quote fixed fees for shaped work, and time-and-materials for open-ended work. Both are legitimate. You will always know which you are paying for before you pay for it.

Typical cadence: 50% to begin, 50% on delivery. Longer engagements stage into phases. Invoices are due within 14 days. Late payments accrue a 1.5% monthly charge. Not as punishment, but as a signal that the project's context has shifted and we should talk.

We accept ZWL, USD, EUR, GBP, ZAR, and crypto where it makes sense. We do not chase. We ask once, clearly, then we pause work until the pause is resolved.

What you share with us. Internal documents, roadmaps, customer data, half-formed ambitions, post-funding-round anxieties. Stays with us.

Our team is small. Access to your material is need-to-know within that team. We sign NDAs when you want one, even though our instinct is already to behave like we've signed one.

We use AI tools in our daily work. To write boilerplate, to surface references, to draft copy, to test edge cases. We do so transparently. No tool replaces judgment; no output ships without a human having read, understood and edited it.

We never feed your proprietary material into a consumer-grade model without asking first. Where models are used in production. Agents, assistants, pipelines. We specify which, why, at what volume, and what happens if they fail.

We warrant that the work will do what we said it would do, on the platforms we said it would run on, for thirty days after delivery. Bugs found inside that window are ours to fix. After that window, continued work is billable, and generally small.

We are not responsible for third-party service outages, for changes to APIs we don't maintain, for acts of regulation or nature, or for business outcomes we cannot control. We are responsible for our own craft and for speaking up the moment something looks wrong.

Our total liability, in the rare case something goes catastrophically sideways, is capped at the fees paid for the specific engagement. This is how studios stay solvent enough to keep making things.

Either party may terminate an engagement with fourteen days' written notice. On termination we stop work, invoice for everything delivered up to that point, and transfer all finished assets.

We will not hold your deliverables hostage. If we have been paid for them, they are already yours. Notice or no notice.

If the ending is sudden because something broke between us. A missed deadline, a miscommunication, a disagreement. We would prefer a fifteen-minute phone call before a lawyer. That is not always possible. We reserve the right to try anyway.

These terms are governed by the laws of Zimbabwe, where Bit Studio is registered. Any dispute that cannot be resolved by conversation will be settled in the High Court of Zimbabwe, Harare Division.

If one clause of these terms turns out to be unenforceable, the rest still hold. If the whole thing turns out to be unenforceable, we will sit down and write a better version together.

Last edited: 24 April 2026. If this page ever changes materially, we will tell our active clients before the change lands.