How do you price, and when do we pay?

Fixed price against a written scope, split across milestones — typically 40% on confirmation, 40% on build complete and 20% on go-live. Rates for individual capabilities are published on the home page; packaged engagements carry a starting price on the solutions page. Change requests are quoted and approved before they are started, never absorbed quietly and never billed as a surprise.

What do you need from us to hit the timeline?

A named decision-maker who can answer within a working day, feedback inside three working days of each review, content and credentials when the plan says, and access to one person who actually does the process we are automating. Timelines in our proposals assume these; where they slip, we say so in writing at the time rather than at the end.

Will you sign our NDA, MSA and security questionnaire?

Yes to the first two, routinely, and we will complete the third honestly. Where a clause does not fit a small firm — unlimited liability, for instance, or a certification we do not hold — we will say so and propose an alternative rather than sign and hope.

Who actually does the work?

A small team, named in the proposal, with the engineer who scoped it still on it. We do not resell the project to a subcontractor you have not met, and if a specialist is brought in for a specific piece — a regulatory consultant, an RF engineer — you are told who and why.

What happens if the project goes wrong?

You hear about it early. A milestone that will slip is reported when we know, not when it is due. If the work is not what was agreed we fix it at our cost; if the scope was wrong we re-scope it and say which of us got it wrong. Our liability is capped at the fees paid for the milestone in question, which is the normal arrangement at this size and is stated in the agreement rather than buried.

Can you work with our existing vendor or in-house team?

Frequently. We take the part nobody else wants to own — commonly the hardware, the cloud, or the admin surface — and agree the interface in writing on day one. Joint projects fail at boundaries, so we would rather spend a day over-specifying one than discover it in integration.

Where are you registered?

TheGradleW Technologies, KN135MINB, Neel Matha, Malak Road, Lucknow, Uttar Pradesh 226002, India. Udyam UDYAM-UP-50-0280551, GSTIN 09CPBPD9064H1ZS. Invoices are raised from India with GST as applicable; export invoices for overseas clients are raised without GST under the usual provisions.

How we work

The answers procurement asks for, before you have to ask.

How a project runs, what we need from you, how your data and credentials are handled, what happens after launch, and where the commercial terms sit. If you are comparing vendors, this is the page to send to the person who has to sign.

Udyam UDYAM-UP-50-0280551
GSTIN 09CPBPD9064H1ZS
Lucknow, Uttar Pradesh
Source code and IP yours
Reply in 1 working day

Delivery

Five stages, and what each one needs from you.

The right-hand column matters more than the left. Most delays we have seen were not engineering problems.

Discovery

3 days – 1 week

We look at the problem, the systems already in place and the constraints nobody mentions in a brief — the air-gapped network, the ERP that cannot change, the regulator. You leave with an architecture, a scope and a fixed price. This stage is paid and it is the one where we are most likely to tell you not to build the thing.

What we need

An hour with whoever owns the process, and access to one real example of the data.

Design and plan

1 – 3 weeks

Flows and screens for anything people touch; schema, API shape and infrastructure for everything behind them. The milestone schedule and payment plan are fixed here, and the scope document becomes the thing we both point at when something changes.

What we need

Feedback within three working days of each review. Timelines assume that and slip without it.

Build

4 – 12 weeks

Work lands on a staging environment you can open at any time — not a demo at the end. Source is in your repository from the first commit, infrastructure in your cloud account. You see the thing weekly, and we would rather hear a problem in week three than in week ten.

What we need

A named decision-maker who can answer a question in a day.

Hardening and launch

1 – 3 weeks

Access control, error handling, logging, backups, load behaviour and the unglamorous edge cases. Then deployment, a runbook, and training for the people who will use it. Hardware adds a pilot in the field here, because only the field finds some problems.

What we need

Whoever will operate it, for a training session that is genuinely attended.

Warranty and handover

30 days, then your choice

Thirty days of bug-fix warranty from delivery. Then either a maintenance retainer, or a clean handover with the architecture notes, runbook and an overlap period with the team you hire. Both are real options and we are not offended by the second.

What we need

A decision on which, before the warranty ends.

Security and data handling

What we do with your access, and what we will not claim.

Written plainly, including the certifications we do not hold — because the row you are really scanning for is the one a vendor left out.

Your accounts, not ours

Cloud infrastructure is created in your account and billed to you, and the repository is yours from the first commit. We work as collaborators with access that can be revoked the day a project ends.

Credentials

We ask for the least access that lets the work happen, through your own secret manager or a shared vault — never over email or chat. Keys live in environment configuration on the server, never in frontend code or a repository.

Your data during the project

Where we need real data to build against, we ask for a de-identified extract. Where that is impossible we agree in writing what may be copied, to which machines, and when it is deleted. Production data is not copied to a laptop as a convenience.

In the systems we build

Encryption in transit and at rest, least-privilege access, audit logging on reads of sensitive records, documented retention and deletion. For anything clinical, financial or personal these are specified in week one rather than retrofitted.

AI and your content

Where a project uses a model provider we use the enterprise or API tier under which the provider does not train on your inputs, and for sensitive work we run open-weight models on infrastructure you control. Which of the two applies is written down before the build starts.

What we will not claim

We are not SOC 2 or ISO 27001 certified, and we will not imply it. We build to the practices above and will complete your security questionnaire honestly, including the rows where the answer is no.

After launch

The part most proposals go quiet about.

A system nobody maintains is a liability with a login page. Here is what happens in month two and in year two.

See the maintenance retainer

Bug-fix warranty

30 days from delivery, included. A bug is behaviour that differs from the agreed scope; a new feature is a new feature, and we will say which one a request is.

Response times on a retainer

Production down: same working day. Something broken but working around: two working days. Everything else: the next change window.

Monthly change window

A published queue you prioritise, so small changes do not each become a negotiation.

Keeping it alive

Dependency upgrades, security patches, certificate renewals, cloud cost review. The work that is invisible until it is not done.

Leaving

Thirty days' notice, a handover document and an overlap call with whoever takes it on. No exit fee, and no hostage-taking of the deployment.

Procurement & commercial

The questions that decide a vendor.

Ownership, pricing, liability, who does the work and what happens when it goes wrong — answered here rather than in a call you have to book first.

You do, on final payment for each milestone — source, designs, schema and documentation. We keep the right to describe the work in general terms for our own portfolio, and even that stops if you ask. Anything we built before your project, or generic utilities, stays ours and comes to you under a perpetual licence so nothing in your system depends on our goodwill.

Tell us what the product has to do.
We'll tell you what it takes.

Startups, enterprises and product teams — from a napkin sketch to a fleet in the field. One team, concept to production.

Start a project Book a 30-min call Call +91 79859 20361

Udyam UDYAM-UP-50-0280551
GSTIN 09CPBPD9064H1ZS
Lucknow, Uttar Pradesh
Source code and IP yours
Reply in 1 working day

Start a project

Come with a problem. We'll scope it before we quote it.

Send us the constraint that worries you most. An engineer reads it — not a form queue — and replies within one working day.

Direct

Emailadmin@thegradlew.com
Phone+91 79859 20361 · Sourabh
Websitethegradlew.com
Book a callcalendly.com/abhishek-thegradlew
OfficeKN135MINB, Neel Matha, Malak Road, Lucknow, Uttar Pradesh 226002, India

Lucknow, Uttar Pradesh · India

Prefer a call? Book a 30-min callPick a slot that suits you — 30 minutes with an engineer, no forms in between.→

LinkedInGitHubXDribbble

The answers procurement asks for, before you have to ask.

Five stages, and what each one needs from you.

Discovery

Design and plan

Build

Hardening and launch

Warranty and handover

What we do with your access, and what we will not claim.

Your accounts, not ours

Credentials

Your data during the project

In the systems we build

AI and your content

What we will not claim

The part most proposals go quiet about.

Bug-fix warranty

Response times on a retainer

Monthly change window

Keeping it alive

Leaving

The questions that decide a vendor.

Tell us what the product has to do. We'll tell you what it takes.

Come with a problem. We'll scope it before we quote it.

Direct

Tell us what the product has to do.
We'll tell you what it takes.