StacktribeLast updated 4 November 2026

How we work

This is a plain-English summary of the terms in every Stacktribe project agreement. Each project gets its own written agreement and scope document. If anything here differs from the agreement you sign, the signed agreement applies.

1. 01

   Scope comes first

   Every project starts from a written scope, usually a requirements document, agreed before any work begins. It lists what is included, what is explicitly out of scope, and anything we need from you, such as access, content, test devices or decisions.

   If part of the work depends on an open question, we flag it and build that part once the answer is in, so nothing is built on a guess.

2. 02

   Changes along the way

   Small clarifications are included: adjusting copy, tweaking an animation, refining a screen within the agreed design, or correcting a misunderstanding of an existing requirement.

   A change request is anything that adds a screen, a new integration or a new core flow, or takes more than about 4 hours. You raise it in writing (WhatsApp, email or the project tracker). Within 3 business days we send its impact on scope, timeline and cost, and nothing changes until you approve it in writing.

3. 03

   You see progress as it happens

   • A shared project tracker (Notion, Linear or similar) showing every feature, its status, planned dates and open bugs.
   • Each feature is delivered for your review as soon as it is finished: test builds for apps, preview links for websites.
   • You test and send feedback within 5 business days; a feature is done when you approve it.
   • Regular check-in calls, weekly or fortnightly, with written notes after each one.
4. 04

   Quality and documentation

   • Documentation is a deliverable, not an afterthought: setup instructions, architecture, every integration and every important decision.
   • Automated tests on the core flows, and code reviewed before it is merged.
   • Only open-source libraries with licences that allow commercial use (MIT, BSD, Apache 2.0), all listed at handover.
   • No third-party SDK that can see your users' data is added without your written approval.
5. 05

   Handover

   • The full source code in a Git repository that you own.
   • A handover document: how to run it, build it and release it, every dependency and why it is there, and any known limitations.
   • Access to every project service, such as app store accounts, hosting and databases, transferred to you.
6. 06

   Payments

   Projects are paid in milestones: an advance at kick-off, payments tied to agreed milestones, and the final payment before handover. The exact amounts and milestones are set out in your agreement.

   Invoices are due within 5 business days. Work on a milestone starts once the previous milestone has been paid, and approved change requests are invoiced separately.

7. 07

   You own what we build

   Once the final payment is received, all intellectual property we create for you, including source code, designs and documentation, transfers to you exclusively.

   We only show a project in our portfolio with the client's permission, and never anything confidential.

8. 08

   Confidentiality

   Everything non-public you share with us, from documents and architecture to data and business plans, stays confidential during the project and for 3 years after it ends. We use it only to deliver your project.

9. 09

   Security

   The security requirements agreed in your scope, such as secure storage of logins, HTTPS-only connections and keeping personal data out of logs, are obligations we deliver, not suggestions.

10. 10

    After launch: 60 days of bug fixes

    At handover the software matches the agreed scope, is free of critical defects and has been tested on the agreed devices.

    For 60 days after handover we fix, at no cost, any bug caused by our own work. Problems caused by later changes to your servers or third-party services, or by operating-system versions released after handover, are not covered. We are not responsible for the availability of third-party services. Ongoing maintenance after the 60 days can be agreed separately.

11. 11

    Ending a project early

    • Either side can end the agreement with 30 days' written notice.
    • You pay for the work completed and accepted up to that date.
    • We hand over all completed work, code and documentation.
    • Anything you prepaid for work that has not started is refunded within 15 business days.
12. 12

    If we disagree

    We first talk it through in writing, in good faith, for at least 15 days. If that does not resolve it, we go to mediation with a neutral third party, and then to arbitration under the Arbitration and Conciliation Act, 1996. Agreements are governed by the laws of India; the place of jurisdiction is set in each project agreement.

13. 13

    Your information

    When you use the contact form, your name, email, phone number and message are sent to us by email through FormSubmit, an email-forwarding service. We use them only to reply to you about your project. We never sell them or share them for marketing. To have your details deleted, write to info@stacktribe.dev.

Questions about any of this? Write to info@stacktribe.dev, or WhatsApp Nimesh on +91 63556 03994. Stacktribe, Jaipur, Rajasthan, India.