A startup's suppliers are service vendors: a dev shop or freelancers, a cloud provider, a payment gateway, identity and KYC or SMS and WhatsApp providers, and professionals such as a CA, a company secretary and a lawyer. Choose by integration quality, settlement terms and support response, not by headline price, and keep an exit path for each one.
These vendors are hard to switch once your product depends on them, so the quality of the first choice matters. This page lists vendor types, where to find them, what to ask, terms to check and red flags. The overall guide covers the legal setup; the hiring page covers people on payroll.
The vendor map for a typical Indian product
| Need | Vendor type | What decides the choice |
|---|---|---|
| First build or extra capacity | Dev shop, freelancers, studio | Code ownership, fixed scope, demo cadence, who writes tests |
| Hosting | Cloud provider with an Indian region | Managed database, backups, support plan, cost visibility |
| Collecting money | Payment gateway or aggregator with UPI, cards, netbanking, wallets | Settlement time, fees, refunds and disputes, onboarding paperwork |
| Paying out to sellers or drivers | Payouts or marketplace-splitting product from a gateway | Compliance for splits, bank verification, reconciliation reports |
| Know-your-customer checks | Licensed identity verification providers | Consent flows, data storage, coverage of the documents you need |
| OTP and alerts by SMS | SMS aggregator with registered sender and templates | Delivery on all networks, DLT registration support, retry logic |
| WhatsApp messages | Business solution providers for the WhatsApp Business Platform | Template approvals, per-conversation or per-message charges, number setup |
| Email and push | Transactional email and push services | Deliverability, domain authentication, reporting |
| Accounts and compliance | CA, company secretary, startup lawyer | Experience with startups, response time, clear fixed fees |
Dev shops and freelancers: how to shortlist and test
Look for teams who have shipped something like your product, not the largest portfolio. Ask to speak to two past clients, ask who exactly will work on your project, and read the contract before the proposal. Our guides on choosing an app development company and fixed price versus hourly go through the trade-offs.
- Source code and IP: the contract should assign IP to your company on payment, with the repository in your account from the first commit.
- Scope, milestones and acceptance: each milestone tied to a demo and a short acceptance list, not to calendar dates alone.
- Environments and credentials: cloud accounts, app store accounts and domains registered in your company's name.
- Handover: documentation, a setup guide and a walk-through call for your engineer after the final milestone.
- Support after launch: a defined bug-fix window and a monthly rate for maintenance, so you know the running cost.
- Sub-contracting: require disclosure if work is passed to others, and a confidentiality clause that covers them.
Run a one-week paid discovery sprint with the shortlist before committing to a full build. You will see how they ask questions, whether they challenge your scope sensibly, and how they communicate when something slips.
Payments, payouts and KYC
India's payment stack is UPI-led, with cards, netbanking and wallets for some segments. Payment gateways and aggregators onboard businesses with documents such as company registration, PAN, bank details and a website or app with clear refund and contact pages. Plan two to four weeks for approval and possibly more, and do not wait until launch week to start. Our UPI payments guide explains what to build around it.
- Settlement: ask when funds reach your bank, what holds are possible and how refunds are netted.
- Fees: get a written schedule for each method and for failed or disputed payments; do not assume one headline rate applies to everything.
- Marketplaces and payouts: if you pay out to third parties, ask the provider how splits, tax collection and nodal or escrow arrangements work, and take advice on whether any licence or approval applies to your model. RBI rules for payment aggregators and for fintech models are specialised; confirm with a lawyer and with the provider.
- KYC: use only licensed or compliant providers, collect consent, and store as little identity data as possible. This ties to the DPDP Act checklist.
- Reconciliation: the provider's reports should match your orders and your books; ask for a sample report before you sign.
Payments, KYC and fintech activity are regulated. I have not verified the current RBI, UIDAI or other rules; confirm with the provider's compliance team and a qualified lawyer. This is not legal advice.
SMS, WhatsApp and other messaging APIs
Many Indian apps use SMS and WhatsApp for sign-in OTPs, order updates and reminders. Commercial SMS in India generally needs your business entity, sender ID and message templates registered on telecom operators' DLT platforms under TRAI rules; your SMS provider can usually guide this. I have not verified the current process, so confirm with the provider and plan time for approvals.
- WhatsApp templates: business-initiated messages usually need pre-approved templates through a business solution provider; the platform's pricing and categories change, so read the current price list before building flows around it.
- Fallbacks: if an OTP does not arrive by SMS, offer a voice call, email, or WhatsApp option, and rate-limit retries.
- Opt-in: collect clear consent before sending marketing messages and honour opt-outs.
- Cost model: estimate monthly messages per active user, then multiply; a chatty notification design can cost more than your cloud bill.
- Two providers: keep a second SMS provider configured so a delivery failure on one route does not block sign-ins.
See also the WhatsApp for business apps guide.
CA, company secretary and lawyer: the people who keep you compliant
| Professional | Early jobs | Estimate |
|---|---|---|
| Chartered accountant | Books, GST returns, TDS, advance tax, annual accounts and audit | ₹3,000–15,000 a month for a small startup, depending on volume |
| Company secretary | Board meetings, annual filings with the Registrar of Companies, share allotments, ESOP paperwork | ₹15,000–60,000 a year for routine filings |
| Startup lawyer | Founder agreement, customer contracts, terms and privacy policy, employment letters | Often a fixed fee per document, ₹15,000–1 lakh each |
| Trademark attorney | Search and filing for your name and logo | Professional fee plus government fee, ₹8,000–25,000 for one class |
Look for people who handle other startups, can explain issues in plain words and respond within a day. Confirm DPIIT recognition, filing deadlines and any benefit claim on the official Startup India and MCA sites with them, since rules change.
Terms, backups and red flags
- Lock-in: avoid vendors who hold your data, code or customer list hostage. Ask how you export everything.
- Single points of failure: one payment gateway, one SMS route and one cloud region can each take you down; add a backup for the first two once volume justifies it.
- Credit and payment terms: pay agencies against milestones, not in full upfront; prefer monthly billing for infrastructure and review the invoices for surprises.
- Vague promises: red flags include no named team, refusal to share the repository, guaranteed install or revenue numbers, and pressure to sign today.
- No written support terms: if nobody commits to response times, expect delays when something breaks at night.
- Reviews and references: speak to at least two real customers, and treat unverifiable testimonials with caution.
Keep a one-page vendor register: what each vendor does, the contract end date, who owns the account, the monthly cost and the fallback. It takes an hour to make and saves a crisis. For fintech products, read the fintech app guide and the fintech solution before you pick providers.
More on starting a tech startup
- Start hereThe full playbook →Models, licences, startup costs and the steps to your first customer.
- Go deeperWhat to buy →Laptops, test phones, cloud and tool seats for a software startup, and what to leave for later.
- Go deeperWho to hire →First engineers, designer and product roles, India pay by city, ESOP basics and freelancer versus hire.
- Go deeperGetting customers →B2B and consumer routes to first users, launch channels, pilots, pricing and retention.
Questions people ask
How do I choose a payment gateway for my startup in India?
Compare settlement time, fee schedules for UPI, cards and disputes, refund handling, onboarding documents, and whether it supports your model, such as payouts or subscriptions. Ask for a sample reconciliation report and a named support contact. Apply early because approval can take weeks, and confirm any regulatory requirements for your model with the provider and a lawyer.
What should be in a contract with a development agency?
Include scope and milestones with acceptance criteria, payment tied to working releases, assignment of IP and source code to your company, repository and cloud accounts in your name, confidentiality, a defined bug-fix period, and a handover with documentation. Ask a lawyer to review it. Never accept a contract where the agency keeps ownership until final payment with no access in between.
Do I need DLT registration to send SMS in India?
Commercial SMS in India generally requires registering your entity, sender IDs and message templates on telecom operators' DLT platforms, under TRAI rules. Your SMS provider normally guides the process. I have not verified the current steps, so confirm with the provider and allow time for template approvals before launch.
Should I hire a CA from the start?
Yes. A company has monthly or quarterly GST and TDS tasks, annual accounts, an audit and filings with the Registrar of Companies, and mistakes cost penalties. A CA experienced with startups can also advise on DPIIT, input credit and ESOP tax questions. Start with a fixed monthly scope and review it each year.
How do I avoid vendor lock-in?
Keep code, domains and cloud accounts in your company's name, use standard databases and open formats, and ask each vendor how to export data on exit. Wrap third-party APIs behind a small internal layer so you can swap SMS or payment providers later. Keep a vendor register with contract dates and fallbacks, and review it every quarter.
