Terms of Service

What we commit to, and what we need from you

Most terms of service documents only list one side. Here are both.

Who these terms are with

Codroon (Pvt) Ltd is a private limited company registered in Islamabad, Pakistan. In these terms, "we" and "Codroon" mean that company.

These terms apply to anyone using codroon.com and to anyone engaging us for work, unless a signed agreement says otherwise.

Using this website

You may read, share, and quote anything on this site with attribution. Our blog posts, cost breakdowns, and guides exist to be used.

What you may not do is scrape the site at a volume that degrades it for other people, republish our content as your own, or attempt to access parts of the site that are not public.

The Codroon name, logo, and brand assets are ours. Everything else on the site is offered as information rather than as advice, and we are not liable for decisions taken on the basis of it.

The cost estimators are estimates, not quotes

This one matters, so it is stated plainly.

Our estimators at /tools/ai-agent-cost-calculator and /tools/mvp-cost-calculator produce an indicative range based on six to nine answers. They are not an offer, not a quote, and not a contract. Nothing you see in an estimator binds either of us.

They are built from what we have actually charged for comparable work and tuned to come in conservatively, which means a real quote usually lands inside the range. But six answers cannot see how difficult your integrations are, how firm your requirements really are, or what the discovery call will surface.

A binding number comes after the discovery call, in writing, and only then.

The discovery call and the scope document

We offer a free discovery call, typically forty-five minutes. You leave with a written scope, an approach, and a price, and you keep all three whether you hire us or not. That is a genuine commitment and we honour it.

The scope document is yours. Take it to another developer, build it yourself, or put it in a drawer. We do not ask for anything in return and there is no obligation attached to receiving it.

Two things it is not. It is not a fixed quote until you accept it in writing, because scope can change between the call and a decision. And producing one does not create an engagement, a retainer, or any obligation on either side.

We reserve the right to decline a discovery call where we do not think we are the right fit, or where the request appears to be for a specification we have no prospect of being engaged to build.

What fixed price means

We quote a fixed price for a defined scope, rather than an hourly rate. This means we carry the risk of our own estimates, which is the correct place for that risk to sit.

The trade is that the scope has to be defined. A fixed price covers what is in the written scope. Work outside it is a change order, discussed and priced before it happens rather than appearing on an invoice afterwards.

We absorb ordinary iteration. Refining a screen, adjusting copy, changing how something behaves within an agreed feature. That is normal work and we do not raise a change order for it. What triggers one is new scope: a feature that was not in the document, an additional user type, an integration nobody mentioned.

If we underestimate, that is our problem and we deliver anyway. That is what fixed price means.

Change orders

When something falls outside the agreed scope, we tell you before doing it, with a price and a timeline impact. You approve it in writing or you do not, and if you do not, we build what was originally agreed.

We will not do additional work and invoice for it afterwards. If you find unapproved work on an invoice, tell us and we will remove it.

Payment

Payment terms are set out in your project agreement. Typically that means a deposit before work starts and the balance on delivery, or staged payments against milestones on longer engagements.

Invoices are due within the period stated on them. If an invoice is significantly overdue we may pause work, and we will tell you before we do rather than simply stopping.

Ownership of the work transfers on full payment. This is covered in the next section and it is the one commercial term worth reading carefully.

Who owns what

On full payment, everything we build for you is yours. The repository, the application code, the prompts, the evaluation suites, the infrastructure configuration, and the documentation. It transfers outright, with no licence back to us, no per-seat fee, and no ongoing dependency on us to run it.

Where practical we deploy to your own accounts under your own name from the start, so that in practice you hold it throughout rather than receiving it at the end.

Two exceptions, both narrow and both standard.

We retain ownership of general-purpose tooling, libraries, and internal components that existed before your project or that we develop independently of it. Where any of that is used in your build, you receive a perpetual, worldwide, royalty-free licence to use it as part of the delivered work. You will never need our permission to keep running what we built.

Open source components remain under their own licences, which we document at handover.

Until full payment is received, ownership stays with us. We say this plainly because the rest of this section is unusually generous and the condition is what makes it workable.

How we use AI in our work

We use AI tools throughout our development process, including Claude Code, and we say so publicly rather than quietly. It is a substantial part of why our timelines and prices are what they are.

What that means for you in practice. Every line we ship is reviewed by a person who decided it was correct, and the delivered work is ours to transfer to you on the terms above. We do not send your proprietary code, credentials, or business data to AI services on consumer tiers, and we use business tiers where inputs are not used for training.

If your organisation has a policy restricting AI-assisted development, tell us before we start. We will either work within it or tell you we are not the right fit, and we would rather have that conversation at the beginning.

What we need from you

Projects run late for one reason far more often than any other, and it is usually not engineering.

We need decisions when we are blocked, access to the systems the work requires, feedback on what we ship each week rather than only at the end, and one person who can make a call without going away to ask three other people.

Where we are blocked waiting on any of those, the timeline moves by at least the length of the delay. We will tell you when that happens rather than absorbing it silently and then explaining at the end.

You are also responsible for the accuracy of what you give us, and for having the right to give it to us. If you provide content, data, or credentials that belong to somebody else, that is your responsibility rather than ours.

Confidentiality

Both ways.

We keep your business information, code, data, and plans confidential, and we do not use them for anything other than your project. This continues after the engagement ends.

We may reference the fact that we worked with you, and describe the work in general terms, unless you ask us not to. We will not publish specifics, metrics, screenshots, or your name in a case study without asking you first.

If you need something stronger, we will sign your NDA.

Third-party services and their costs

Most builds depend on services we do not control. Hosting, databases, payment processing, model providers, email delivery, and similar.

Those accounts are yours and the costs are yours, both during the build and after it. We will tell you what a project needs and roughly what it costs to run before you commit, and our estimators give a monthly figure where relevant.

We are not responsible for those providers changing their pricing, their terms, their APIs, or their availability. Where a change breaks something we built, we will tell you what it takes to fix it. Where the fix falls outside your original scope, it is a change order.

What we promise and what we do not

We promise that the work will match the agreed scope, that it will be built competently, and that we have the right to transfer it to you.

For thirty days after handover we will fix defects in what we built, at no charge. A defect means it does not do what the scope said it would. It does not mean a change of mind about what it should do, which is a change order.

We do not promise that software will be free of all bugs, that it will handle any particular scale we have not been asked to design for, that a third-party service will keep working as it does today, or that a product will succeed commercially. Nobody can promise those and anybody who does is overselling.

Where a project uses AI models, we do not warrant model outputs. Models are non-deterministic. We build evaluation suites, guardrails, and human review steps to manage that, and we hand those over with the code.

Limitation of liability

Our total liability for anything arising out of an engagement is limited to the fees you have paid us for that engagement.

We are not liable for indirect or consequential losses, including lost profits, lost revenue, lost data, or business interruption.

Nothing here limits liability for fraud, for wilful misconduct, or for anything that cannot be limited under applicable law.

Ending an engagement

Either of us can end an engagement with written notice.

If you end it, you pay for work completed to that point and we hand over everything built so far on the same ownership terms, meaning on payment of what is outstanding.

If we end it, which is rare and usually means the working relationship is not functioning, we hand over what has been built and refund anything paid for work not yet done.

Either way you leave with the code, the documentation, and enough context for somebody else to continue. We will not hold work hostage over a disagreement.

Equity arrangements

On some projects we work as a technical co-founder, taking equity in the company in exchange for a reduced build fee. Two of our products started that way.

That arrangement is never covered by these terms. It requires a separate signed agreement covering the equity itself, vesting, governance, roles, and what happens if either side wants out. Nothing on our website, in a discovery call, or in these terms creates or implies such an arrangement.

We offer it selectively and we decline it more often than we accept it.

Changes to these terms

We may update these terms. The date at the top changes when we do, and material changes are noted at the top of this page for at least thirty days.

Changes do not apply retrospectively to a signed project agreement. Your agreement is governed by the terms in force when you signed it.

Contact

Questions about these terms: legal@codroon.com