Engagement terms

A price is agreed against a written scope before work begins, and the studio carries the risk of that estimate being wrong. If a build takes longer than expected for reasons inside the agreed scope, the overrun is absorbed rather than invoiced. That is what fixed means, and it is the substance of the offer rather than a framing of it.

What moves the price is a change to the scope itself: a new integration, a flow that was not described, a regulatory requirement discovered after signing. Those are quoted separately at the time and accepted or declined before the work happens. They are never absorbed silently and presented at the end, which is the practice these terms exist to rule out.

The delivery window runs from kickoff, not from first contact, and kickoff requires whatever the build actually depends on — API credentials, a merchant account, access to the system being written to. Where those are outstanding the window pauses rather than quietly consuming itself, and the pause is stated at the time rather than raised as an excuse afterwards.

The client owns the delivered source outright on final payment. At handover that means the repository, the deployment configuration, the database and the bot token, transferred into accounts the client controls. There is no arrangement under which the studio retains the running system while the client holds a licence to use it.

Third-party components keep their own licences — open-source libraries remain under theirs, and platform accounts such as a payment provider or a CRM are the client's own commercial relationships throughout. The studio does not resell those, and does not sit between the client and a provider on billing.

Anything pre-existing that the studio brings — internal tooling, templates, boilerplate written before the engagement — is licensed to the client perpetually for use in the delivered system rather than assigned. That distinction matters only if the client later wants to sell the codebase as a product, and it is flagged here rather than buried.

Defects against the agreed scope are fixed free of charge for thirty days after handover. A defect is behaviour that does not match what was specified; it is not a change of mind about what the specification should have said, and the two are distinguished by reading the scope rather than by negotiation.

Outside that window, and for anything that is not a defect, support runs on a monthly retainer with a stated response time. Telegram changes its Bot API on a schedule nobody controls, third-party providers deprecate endpoints, and a bot with nobody watching it degrades quietly — so the retainer is offered as the default rather than as an upsell, and declining it is a legitimate choice with a stated consequence.

The studio does not guarantee uptime for infrastructure it does not control. Telegram outages, payment provider incidents and chain congestion are outside any commitment that could honestly be made, and a vendor promising otherwise is promising something it cannot deliver.

Invoicing is split across kickoff and handover, in the currency stated in the agreement. A working demo precedes the handover payment, so the client sees the delivered system before the balance is due rather than after.

Confidentiality runs both ways and survives the engagement. The studio will not name a client, describe their system, or publish any figure about their business without written consent — a commitment the evidence policy on this site already makes structurally, since nothing is published unless a reader can verify it independently.

Either side may end an engagement in writing. Work completed to that point is invoiced and handed over in the same condition as a completed handover: source, credentials, deployment. A partially built system the client has paid for is the client's, and withholding it as leverage is not a mechanism available under these terms.

The contracting entity and the governing jurisdiction are named in the signed agreement for each engagement rather than asserted on this page. That is deliberate: this site publishes no legal entity, no registered address and no incorporation claim, because none of those is currently verifiable by a reader and an unverifiable claim about who you are contracting with is worse than an explicit deferral.

A prospective client is entitled to that information before signing anything, and it is provided on request at the point it becomes relevant — which is before money moves, not after.