Limited-time dealSupermicro HGX B200, 8 GPUs8-GPU NVIDIA HGX B200 server in stock
View the specification Call +91 92058 93902innovations@udhyamlabs.tech
How an engagement is structured, and what you hold at each stage.
This is how we work, written down so that you can check it before the first technical call. The contract and the statement of work for an engagement set the terms, with the dates and the figures filled in.
A fixed-fee assessment that you can stop after
Every engagement starts with an assessment of fixed scope and fixed length. It ends with written findings and a short paper for your management: what we found, what we recommend, an estimate of what it would cost, and what could go wrong.
What we examineThe billing export, network flow logs, load balancer logs, DNS query logs, the provider's API audit log and traces for a named slice of the estate.
What you receiveA dependency map, a classification of each workload, a wave plan for the slice examined, an estimate for the rest of the estate, and a model of what running two estates in parallel will cost.
What we examineThe code, the data model and production telemetry.
What you receiveWhat is sound and what has to change, the order of extraction, and the cost of the period in which both systems run.
What we examineThe pipeline, the differences between environments, and recent releases and incidents.
What you receiveThe points where a faulty release can pass unseen, a target rollback time, and an ordered plan of changes.
What we examineThe pilot, a sample of real requests, and your definition of a correct answer.
What you receiveAccuracy, response time and cost for each request, measured where there is a pilot to run, the evaluation cases, and a statement of whether the use case can reach its targets and what that would take.
What we examineThe quotation, if there is one, and a representative workload.
What you receiveA written recommendation to buy as quoted, buy less or more, buy a different part or rent first, with the arithmetic shown in your currency.
Fixed fee and fixed length
The fee and the dates are quoted before the assessment starts.
Under an NDA
An NDA, yours or ours, is signed before you share any detail of your systems.
Read access only
The assessment has read access to the sources you choose and cannot change them. Any test runs in a separate account that you control, where we are given permission to create the capacity it needs.
The findings are yours
The findings belong to you and can be taken to any other firm.
Milestones, each with acceptance tests agreed before work on it starts
The build is proposed only after the assessment, when the scope is known. The proposal sets out the milestones, the engineers, the planned dates and the price. Where a milestone can advance only when a measurement passes, the proposal says so, and it states what happens to the date and the price if the measurement does not pass.
Tests you can witness
Each milestone has acceptance tests agreed in writing before work on it starts. A milestone is complete when those tests pass in front of you.
Consistent stopping points
Milestones are drawn so that each boundary leaves the system in a consistent state. The proposal says what you would be running, and at what cost, if the work ended there.
Irreversible steps run only with your sign-off
Where a step cannot be reversed, we tell you before it runs, and it runs only when you have signed it off.
The work is done in your accounts, and the code is yours
The work is done inside your environment, and everything produced belongs to you. The sections below set out what that means for access, for ownership, and for continuity if we are no longer there.
Access that you control
We work under named identities that you issue and can revoke, with the permissions the task needs. Your change approval applies to our changes.
Data stays where it is
We do not copy production data out of your environment. Where the system itself has to send data to an outside service, such as a model reached through an API, you choose and approve that service before anything is sent to it. The same rule applies to your code and to AI coding assistants.
Everything produced is yours
From the first day of the build, code, configuration, tooling, evaluation cases and documents are committed to your repositories, and they belong to you.
If we were no longer there
Because the work lives in your accounts and every decision is recorded in your repository as it is made, another team could continue from where we stopped.
Who does the work, and who takes over if the lead is unavailable
The firm is new and small, so these are the questions a careful buyer asks first.
A new firm
Udhyam AI Labs Private Limited is newly incorporated, and the experience behind it is its engineers' own, gained in earlier roles. The Company page says what that means for a buyer.
Profiles before the first technical call
The names and working histories of the engineers who would do your work are sent to you before the first technical call. Each profile states the country that engineer works from, and you are welcome to interview them before anything is signed.
Two engineers on every engagement
The engineer who scopes the work leads it. A second engineer follows the engagement from the first day and can take it over. If the lead has to change, you are told first.
Nothing is subcontracted
All engineering is done by engineers engaged directly by Udhyam and named in the statement of work. None of it is passed to another company.
Our advice is paid for only by our clients.
We take no commission, referral fee or rebate from any hardware, cloud or colocation supplier, and no supplier pays us for a recommendation, whichever answer we give. From time to time we list equipment for sale under Hardware available. Those listings are kept apart from our advisory work. The findings of an assessment are yours, and you are free to take the build to another firm.
What we do not do
- Recommend equipment that we have listed for saleAn assessment names what fits your workload, and the recommendation is a document that you can take to any supplier.
- Take commission, referral fees or rebates from suppliersThis holds whether the answer is to buy more, to buy less or to rent.
- Supply engineers for a client to direct by the monthWe are accountable for the result in an agreed scope. Staff augmentation is a different service.
Handover is complete when your engineers have run the system themselves
Receiving the code is the easy part of a handover. What matters is that your own engineers have operated the system before we step back.
Handover tests
Your engineers run the system, a release and a rollback themselves while ours observe. The runbooks handed over are the ones used in those runs.
A support period
A support period follows handover, and its length is set in the statement of work. During it we correct defects in what we built.
A retainer if you want one
Continued engineering after the support period is available on a retainer. It covers engineering work that we scope with you, it is optional, and nothing in the handover depends on it.
Answered here, before the first technical call
If yours is not here, ask it on the contact page and an engineer will reply.
You are a new firm. Why would we give you access to production?
You would not need to give us write access at the start. The assessment needs read access to sources that you choose, which can include production telemetry, and no ability to change anything. The analysis runs in a workspace that you create inside your own account, and where a source holds personal or cardholder data you can place a masked or aggregated export in that workspace. The assessment runs under an NDA and is carried out by engineers whose profiles you have seen. If you stop when it ends, you have spent the fixed fee and the cost of any capacity rented for the tests, and you hold findings that any other firm can act on.
What happens if your lead engineer leaves, or the firm stops trading?
A second engineer follows every engagement from the first day and can take it over. Everything we produce is committed to your repositories and runs in your accounts, and every decision is recorded there when it is made. You would hold the code, the configuration, the measurements and the decision record, which is what another team needs to continue.
We have several hundred services. Can a small firm move them?
We do not try to staff every wave ourselves. The Services page sets out how the work divides between our engineers and yours. The assessment gives a wave plan for the slice it examined and an estimate, stated as an estimate, for the rest of the estate. We tell you if the estate is more than we can take on at the time.
Do we have to engage all five practices?
No, you can start with one. Whichever practice it is, we examine the layer above it and the layer below it, because a fault can show itself in a different layer from the one that causes it, and we report what we find. You decide whether to act on it.
Nothing is running yet. What do you measure?
For an AI use case we run the pilot with a sample of your real requests, on capacity rented in an account you control. Where there is no pilot yet, we work from stated inputs and say so. For a hardware purchase we run a representative workload, built from the model, the context lengths and the number of users you expect, on capacity rented in the same way. In both cases we state how uncertain the result is and what would reduce the uncertainty.
How do you work inside a regulated estate from another country?
We work inside your tenant under named identities that you issue and can revoke, through your own workstations or virtual desktops if you require it. We do not copy production data out of your environment, and your change approval applies to our changes. Remote access from another country can still count as a transfer under your rules, so tell us what your privacy team and your regulator require, and we will answer it in writing.
How is the work priced?
The assessment has a fixed fee and a fixed length, and both are quoted before it starts. The price of the build is set out in the proposal that follows the assessment. We do not publish rates, because the fee follows the scope.
Who chooses the AI model, and where does our data go?
You choose. We recommend a model and show the measurements behind the recommendation, and you approve it. Your data and the evaluation cases built from it stay in an account you control. Nothing is sent to a model provider or to any other service unless you have approved it.
Can you check a GPU quotation before it expires?
Tell us the validity date and what you intend to run. An engineer replies within one working day and tells you whether the check can be completed in the time you have. The quotation itself can follow once the NDA is signed.
Who runs the system after handover?
Your team does, from the day the handover tests pass.
Describe the problem, and an engineer will reply within one working day
Tell us in general terms what you are trying to do and what has stopped it. If it is not ours to take on, we will say so.