Hiring A Custom Software Agency in India: A Founder's Checklist (2026)

If you are a founder evaluating custom software agencies in India, you are being lied to more than you realise. Not maliciously — most agencies have just learned that saying yes to everything wins the contract, and figuring out the gaps is the next team's problem.

This is the checklist we would hand a founder friend who asked us, over coffee, how to not get burned. It is written from the other side of the table — we are an agency, and we will point at ourselves as one example, not the only one. If another team is the better fit, hire them.

Red flags to walk away from

These are not "be careful" signals. These are "end the call" signals.

• A quote before the brief. Any agency that gives you a number before they have read a written brief or done a working session is selling you a rate card, not a product. The number will move once they understand the work, or the scope will shrink to fit it.
• No named engineers on your project. "We have a pool of 40 developers" means your project will be staffed by whoever is free that week. Ask who, specifically, will write the code. Get names.
• "We have done projects like this before" without showing you one. Every agency has a similar-sounding case. Ask for a live URL. If the links are all "under NDA," pattern-match: either they have shipped nothing public, or they have shipped things they are not proud of.
• A fixed quote with no fixed scope. Fixed-price contracts are fine. Fixed-price contracts on a vague two-paragraph brief will end in a fight. Either get the scope written out in detail or pay hourly with a cap.
• Payment fully upfront. Standard in India is roughly 30-40% upfront, milestones after. Anyone asking for 100% before week one is either desperate or planning to leave.
• Communication only on WhatsApp. Fine for quick check-ins. Not fine as the only channel. You want decisions written down in a tool that will still exist in six months.

Green flags worth paying a premium for

• They push back on your idea in the first call. An agency that says "that feature is going to cost you three weeks — is it worth it?" is thinking about your business, not their invoice.
• They offer a small paid discovery before the full project. A one to two-week paid discovery phase that produces a real scope document is the single best risk-reducer in software buying. Budget for it.
• A working portfolio you can click through. For example, our IJRN academic journal platform and Julex 24 jewelry store are both live and you can see the work yourself. That is the bar.
• They show you the code handover process. You should own the repo, the domain, the database, and the deployment account. If they cannot describe how that transfer works, you are renting your own product.
• Founder or senior engineer on every call. Not an account manager, not a junior PM. The person who will make architectural decisions should be in the room from day one.

Questions to ask on the first call

Copy-paste these. Ask them exactly as written. Good agencies will answer without flinching.

1. Who specifically will be writing the code, and what else are they working on during our build? You are trying to find out if your project has dedicated attention or is filler work.
2. Show me a project you shipped that failed or slipped. What happened? Nobody has a clean record. If they say they do, they are lying or they have not shipped enough to have lost.
3. What is your stack and why? You want specifics. A team that answers "whatever fits the project — we have shipped in TypeScript, Python, Node.js, React Native" is more honest than one that chants a single framework at you.
4. What happens if we find a bug three months after launch? You want a real support answer, not "we will take a look." Ours, for example, is 90 days of free bug fixes and an optional retainer after.
5. How do you handle scope changes? "Change request, re-estimated, signed off, then built" is the correct answer. "We will figure it out" is not.
6. Can I talk to two past clients directly? Not testimonials on a page — actual founders on a phone. If the agency hesitates, there is a reason.

If the agency cannot answer any of these cleanly, that is your answer. If you want to run these questions past our team to see how we respond, that is a free call — we would rather you hire us after a hard interview than regret it after a soft one.

Real price ranges by scope (India, 2026)

These are ranges we see across the Indian agency market, not our rate card. Budget against these, and adjust for your specific needs.

• Marketing site with CMS: 1.5 - 4 lakh INR, 3-5 weeks
• Ecommerce store with custom logic (beyond Shopify): 4 - 12 lakh INR, 8-12 weeks
• SaaS MVP with auth, billing, dashboard: 6 - 18 lakh INR, 8-14 weeks. Our breakdown of SaaS MVP timelines explains why the range is that wide.
• LMS or academic platform with role workflows: 8 - 20 lakh INR, 10-14 weeks
• Marketplace with payouts, multiple user types: 12 - 30 lakh INR, 14-20 weeks
• Mobile app (React Native or native) paired with a backend: 8 - 25 lakh INR, 10-16 weeks

If someone quotes you half the low end of those ranges, they are skipping something — usually design, QA, or the handover. If someone quotes you double the high end, they are either a big firm with enterprise overhead you do not need, or they are betting you do not know the market.

What the first month should look like

Regardless of who you hire, a healthy first month looks like this:

• Week 1: Working session to map the business model into a data model. Written scope document out by end of week. Design direction agreed.
• Week 2: Core data model and auth working. First UI screens in review. You should see a deployed preview URL, even if it is ugly.
• Week 3: Main happy-path flows working end-to-end. Weekly demo call happens on a fixed day.
• Week 4: First feature round is done. Scope check — anything that is going to slip should be flagged now, not in week 10.

If the first month does not look roughly like this, you are not in a build — you are in a negotiation. Fix it or leave.

How we do it, as one example

We take the approach above because we have been burned on the other side of it as clients ourselves. Our own projects — IJRN, Julex 24, and others on the projects page — were all scoped in a one-week working session, quoted fixed-price, and shipped against a visible weekly demo. That is not unique to us, and it is not the only way to run a build. It is the only way we know how to run one without lying to the founder.

If you want a second opinion on a quote you have received from another agency, send us the scope and we will tell you honestly what we think. No pitch, no follow-up spam — we would rather save a founder from a bad build than win one ourselves.