ProDevs looks at one custom web app, one internal tool, or one AI-powered application, then writes the price. You describe the problem. We reply in writing. If that look shows a fit, you can pay for a written audit. Nothing on your systems changes until you accept a quote in writing.
This page is for founders and small teams who can name the one application they need. It is not a course, a workshop, or a retainer to make everything AI.
Who this path is for
You can describe one application in a few sentences. A web app your customers would log into. An internal tool your team would use every day. An AI-powered application that reads your data and writes a draft a person still approves.
This path is the wrong one if you want a workshop, a standing chat channel, a rewrite of several products sold as a small fix, or a package with no look.
One worked example, from a published guide
Not a client result. Nobody hired ProDevs for the run below. The numbers are from the public guide “Idle Postgres in Docker: read the stats line, not shared_buffers”, measured on 29 September 2026: https://prodevs.in/tools/postgres-docker-idle-ram/. It is not your server, and it is not a quote.
The guide started two idle postgres:16-alpine containers. Each was capped at 512MiB, with memory and swap set to the same ceiling. Docker inspect printed Memory=536870912 and MemorySwap=536870912 on both. That is 512 times 1024 times 1024. There was no query load. Both logs said the database system was ready to accept connections, at 2026-09-29 16:16:26.879 UTC and 2026-09-29 16:16:53.569 UTC.
The defaults container showed shared_buffers of 128MB. docker stats printed 17.34MiB / 512MiB, 3.39% of the cap, and 6 processes. A second container was started with shared_buffers=32MB, max_connections=20, and work_mem=2MB. Its shared_buffers line was 32MB. Stats printed 21.73MiB / 512MiB, 4.24% of the cap, and 6 processes. The smaller buffer setting did not shrink the idle line.
The server was Docker Engine 29.4.0 on linux/arm64. The client was Docker Engine 29.2.1 on darwin/arm64. The image line was docker.io/library/postgres:16-alpine. Both runs were idle.
The guide is written to stop one mistake: treating 128MB as the RAM the application uses. The setting and the 17.34MiB stats line are different numbers, in the units each tool printed. A paid audit measures your application on the access you agree. It does not paste this idle lab in as your result.
How the path works
- Describe one application on the contact form, or email contact@prodevs.in. Say whether it is a custom web app, an internal tool, or an AI-powered application. Include what you see, when it started, and what you already tried. Do not send passwords or API keys.
- We reply in writing, usually within one business day, with a short go or no-go. Nothing is billed. The free look is capacity-capped. If we are full, we say so.
- If a paid audit fits, the standard fee is ₹20,000, inside ₹15,000–₹25,000. The payment link is on the services page. Use it only after that note. Any other fee in the band is a Razorpay invoice after we confirm.
- After payment clears, access is agreed in writing. We look at the setup with the access you choose. Production stays unchanged during the audit unless you ask in writing.
- You then get the written findings and, when a build is a good idea, a fixed quote. You decide. A bad idea means you keep the audit and there is no build invoice.
- One scoped build is ₹45,000–₹1,00,000. The exact price is written after the audit. You pay half the net to start and half at go-live. The audit fee credits in full if you start within 30 days of delivery (IST). The credit reduces that invoice. It is not cash. If you do not start, the credit ends. A quote below ₹45,000 is not used to absorb the credit.
What the written audit contains
For the one application you named, you keep written findings you can share. The audit cites counts and error strings from the access you agreed. It also has a prioritized roadmap and a fixed quote when a build is a good idea. Go includes that quote. No-go has no quote.
Five working days
Day 1 is the business day when cleared payment and agreed access are both in hand before 18:00 IST. Otherwise day 1 is the next business day. Findings are due by the end of day 5, IST. A day waiting on access you still owe us does not count. Both in hand on a Monday before 18:00 IST means delivery by the end of that Friday. If the findings are not delivered, the audit fee is refunded.
Out of scope
Out unless a separate agreement names them: live teaching, workshops, unlimited Slack coaching, a multi-cloud migration or a full re-architecture sold as a small fix, third-party API, model, or hosting fees, an open-ended retainer, and work already declined. This page does not sell a blind buy-now package or a from-price retainer.
FAQ
How much does a custom application build from ProDevs cost?
The diagnostic is free. The audit is ₹15,000–₹25,000 (standard ₹20,000) and credits in full into a ₹45,000–₹1,00,000 build if you start within 30 days. The build price is written after the audit.
What do I get in the written audit?
You keep written findings you can share, with counts and error strings from the access you agreed, a roadmap, and a go or no-go. Go includes the quote. No-go has no build invoice.
How long does the paid audit take?
Five working days after payment and access are both in hand. Day 1 is that business day before 18:00 IST, otherwise the next business day. Days you still owe access do not count. Undelivered findings are refunded.
What if ProDevs says the build is a bad idea?
You keep the written findings and there is no build invoice. The audit fee pays for the audit itself, so it is not refunded unless the findings are not delivered.
What will ProDevs not build on this page?
A workshop, unlimited Slack coaching, a multi-cloud move sold as a small fix, and an open-ended retainer. Vendor fees stay at cost. The job is the one application you named.