ProDevs looks at one AI workflow or one business automation, 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 developers, small teams, and operators who already have a workflow, or a concrete build they can describe. It is not a course, a workshop, or a retainer to make everything AI.
Three problems this path is built to look at
Not customer results. This page has no testimonials.
A support draft sends a date nobody approved. The published sample has no client behind it. The automation classifies support mail, writes a draft, and files a CRM note. On busy days the draft adds a refund or feature date the team did not approve, and the note drops the original message. Send and draft share one run, so a prompt line does not hold the mail. The paid look needs the export and redacted drafts. The sample stores the message id, checks a written list of allowed promises, and holds the send for a person.
A payment workflow loses events when a later step times out. This illustrative case is not a real enquiry, and its sample counts are not a customer measurement. Self-hosted n8n takes a payment webhook, appends a Sheet row, then sends a WhatsApp alert, in one execution. Spikes drop events. The free note cannot name the active cause without the export, a redacted execution list, and disk numbers. A payment id stored only at the last step can duplicate a row on retry.
Uncapped Docker logs fill the host that runs the workflow. Measured on a disposable test VM on 5 October 2026, not a client server. The default json-file driver does not rotate logs. One container at about 89 short lines a second wrote 90,642,495 bytes in one hour with no limit. A neighbour with max-size 10m and max-file 3 peaked at 29,854,913 bytes. Restarting after a daemon.json change left the old container unlimited until it was re-created. Image prunes do not delete those logs. A full disk stalls the workflow host.
How the path works
- Describe one problem on the contact form, or email contact@prodevs.in. Name one AI workflow (n8n, Make, or Zapier), one business automation, one AI application, or one Docker, Postgres, VPS, or CI issue that blocks that work. 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. Usual access is a workflow export plus redacted logs or metrics. 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 problem you named, you keep a document with measured causes. Each cause has a count, a timestamp, an error string, or a disk figure. The document also lists what we could not see, findings you can use without us, what not to build, a prioritized roadmap, and a go or no-go. Go includes the fixed 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 fenced product packages or from-price retainers.
FAQ
How much does an AI workflow 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 a document with measured causes, gaps, 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 take on this page?
Workshops, unlimited Slack coaching, a multi-cloud move sold as a small fix, and open-ended retainers. Vendor fees stay at cost. A published guide gets a free note, not an audit.