DEV Community: Ravi Rai

Building an Online Grocery System in India: How We Shipped Web + Customer App + Driver App for Jai Shri Balaji Store

Ravi Rai — Fri, 15 May 2026 08:01:51 +0000

In Q1 2026 we shipped Jai Shri Balaji Store — a full online grocery system for a Delhi-NCR retailer. Not just a website. The complete operational stack: a customer-facing storefront for browsing and ordering, a customer mobile app for on-the-go shopping with order tracking, and a delivery driver app with route optimization and proof-of-delivery. Three apps. One backend. Twelve weeks from kickoff to launch. This case study covers the architecture, the decisions, the costs, and what we'd do differently if we built it again today.

Most Indian grocery clients ask us 'just build me a website like Blinkit.' What they actually need is what Blinkit needs — a 3-app system, not just a storefront. The storefront brings the customer in. The customer mobile app keeps them. The driver app is what keeps the business running. Skip any of the three and the unit economics fall apart by month 4.

The client and the problem

Jai Shri Balaji Store, founded and run by Ashok Dhull, had been operating as a traditional kirana + light wholesale operation in Delhi-NCR for over a decade. WhatsApp orders, walk-ins, occasional Zomato/Swiggy via a partnered cloud kitchen. Ashok wanted to capture the modern home-delivery grocery market without the heavy infrastructure cost of a Blinkit or Zepto-style dark-store model.

Their constraints were specific and Indian:

INR-flat budget around ₹8–12 lakh for the entire stack — not the ₹50L+ that funded grocery startups spend
Existing customer base on WhatsApp (~600 regular households) that needed a smooth migration path
No internal tech team — the system needed to be operable by a non-technical store manager
Two warehouses (one main, one satellite) with different SKU subsets and pricing
Razorpay-first payments (they already had a Razorpay account, hated the idea of forex)
Hindi-friendly UI alongside English (most customers shift between both)

Why 3 apps instead of 'just a website'

Every grocery client we've worked with starts the conversation asking for 'a website like Big Basket.' What they don't realize is that the website is the smallest part of the system. Here's why we always push for a 3-app architecture for serious grocery operations:

Website (responsive, fast)

Captures Google traffic and search intent. New customers find you here. SEO matters. Performance matters. Works for browsing on a desktop or quick orders on mobile browsers. The website does about 30-40% of revenue volume in a typical Indian grocery business.

Customer mobile app

Locks in repeat customers. Push notifications drive re-orders. Faster checkout via saved details + cart memory. Offline browsing works (we cache the catalog). The customer app does 50-60% of revenue once a business hits 6+ months of operation — repeat business is where margins live.

Delivery driver app

This is the part everyone underestimates. The driver app is what keeps your unit economics positive. Real-time order assignment, route optimization, proof-of-delivery (signature + photo + OTP), driver attendance, payout tracking. Without this, your store manager is sending WhatsApp screenshots to drivers and calling them every 20 minutes. That model breaks at 50 daily orders.

The architecture (high level)

Three apps. One backend. One database. One admin panel for the store manager. Here's how the pieces connect:

Storefront (Next.js + Vercel) → reads catalog from API, places orders via API
Customer mobile app (Flutter, iOS + Android) → same API, push notifications via FCM
Driver app (Flutter, Android only) → same API, real-time order assignment via WebSocket, GPS tracking
Backend API (Node.js + Express, hosted on CloudNX Mumbai region) → handles auth, orders, payments, inventory, driver dispatch
Database (Postgres + Redis) → Postgres for transactional data, Redis for cart sessions + real-time driver state
Admin panel (Next.js on same Vercel project) → operated by store manager, manages catalog, orders, drivers, payouts

Single source of truth: the backend. The three apps are essentially three different UIs over the same data. This is the most important architectural decision in any multi-app system — and the one most cheap builds get wrong, ending up with three apps that have their own little databases that get out of sync.

Why Next.js for the storefront (not Shopify, not WooCommerce)

Most Indian grocery clients ask us 'should we just use Shopify?' For Jai Shri Balaji Store, the answer was no, and here's why:

Shopify's per-transaction fees compound quickly on a high-volume, low-margin grocery business
Shopify can't natively integrate with a custom driver app and warehouse inventory the way we needed
Customer mobile app and driver app need the same backend the website uses — Shopify's API model is read-heavy, not designed for a unified backend
₹1,994/month Shopify Basic + transaction fees + apps = ₹15,000-₹40,000/month at scale. The custom Next.js storefront has zero per-transaction fees and runs on Vercel free tier until 100K+ visits.

Where we DO recommend Shopify: small grocery brands that don't need a driver app, are dropshipping or single-warehouse, and don't have 100+ SKUs per category. For most operational grocery businesses with their own delivery fleet, custom Next.js wins on cost-per-order.

Why Flutter for both mobile apps (not React Native, not native)

We use both Flutter and React Native in production. For this project we picked Flutter for three specific reasons:

Performance on low-end Android phones — most Indian delivery drivers have ₹8K-15K phones. Flutter's AOT-compiled Dart runs noticeably smoother than React Native on these devices.
Single codebase, two apps — we built the customer app and driver app from the same Flutter codebase with shared core packages. ~40% code reuse.
Mature offline support — Flutter + Hive (local DB) made the offline catalog and offline cart functionality trivial. The customer keeps browsing during a metro tunnel ride.

If your client team has more React experience and wants to hire React Native devs in-house later, RN remains a fine choice. For this project, Flutter was the right call.

The Razorpay vs Stripe decision

Razorpay won this one easily. Reasons specific to Indian grocery:

UPI integration is native, fast, and the way 80%+ of Indian grocery customers pay in 2026
INR settlement to an Indian bank account, no forex variance
GST-compliant invoices auto-generated for B2B grocery clients (kirana shops reselling)
QR code payments for cash-on-delivery upgrade to digital (we built this — driver shows QR, customer pays, no cash handling)
Subscription billing for households who pay a monthly grocery deposit

Stripe is excellent — but it's not how Indian grocery customers want to pay. We use Stripe for international SaaS clients, never for India-only grocery.

Multi-warehouse inventory architecture

The two warehouses (main + satellite) was the trickiest part of the build. The system needed to:

Show different SKUs at different warehouses (some products only in main warehouse)
Show different prices at different warehouses (satellite has higher prices due to operational cost)
Auto-route orders to the nearest warehouse with stock
Allow store manager to manually override the warehouse if needed
Show inventory in real-time so customers don't order what's already sold out

We modeled this as a 'warehouse-product' join table with location, stock, and pricing per warehouse. When a customer searches, we compute their nearest warehouse from their PIN code (we maintain a pin-to-warehouse mapping table for the service zones), then filter the catalog by that warehouse's stock + pricing. The system gracefully handles warehouse outages — if the nearest warehouse is offline, it shows the next-nearest warehouse's catalog without the customer noticing.

Route optimization for the driver app

This is where the driver app earns its keep. When a driver picks up multiple orders for delivery (typical: 4-8 orders per route), the app computes the optimal sequence using:

Google Maps Distance Matrix API for current traffic-aware distances between all pickup → delivery points
A simple greedy nearest-neighbor algorithm with proximity bucketing (perfect optimization is NP-hard; we use the 'good enough' variant)
Time windows where customers said they want delivery (e.g., 6-8 PM slot)
Driver-specific constraints (some drivers handle 2-wheelers only, can't do bulk orders)

The result is a delivery route that's roughly 20-30% shorter than 'in the order they were placed.' Multiply by 60+ deliveries per driver per day, and the time savings are real — each driver does ~15% more deliveries per shift than they would without route optimization. That's a 15% productivity bump on the most expensive operational cost (driver wages).

The build timeline (12 weeks)

We worked in 4 sprints of 3 weeks each, with the client approving each milestone before the next started:

Sprint 1 (Weeks 1-3): Backend API + database schema + admin panel + storefront (catalog browsing only, no payments)
Sprint 2 (Weeks 4-6): Storefront payment flow + customer mobile app (with order placement) + Razorpay integration
Sprint 3 (Weeks 7-9): Driver app + route optimization + warehouse inventory management + push notifications
Sprint 4 (Weeks 10-12): Multi-warehouse logic + production hardening + launch + 2 weeks of post-launch bug fixes

The client was actively involved — store manager joined every Friday demo call, gave feedback within 48 hours, and tested every feature before we moved on. This is the #1 reason the project shipped on time. Clients who 'check it when it's done' are the reason most agency projects run 50-100% over schedule.

The actual costs (transparent INR)

One-time build cost

Customer storefront (Next.js, 5 pages, catalog, cart, checkout): ₹1,80,000
Customer mobile app (Flutter, iOS + Android, full order flow): ₹2,40,000
Driver app (Flutter, Android, route optimization, GPS, proof-of-delivery): ₹2,10,000
Backend API + database + admin panel: ₹2,40,000
Razorpay integration + GST invoicing + subscription billing: ₹60,000
Multi-warehouse logic + pin code mapping: ₹50,000
Push notifications + WhatsApp order updates: ₹30,000
Total build: ₹10,10,000 (well within client's ₹8-12L budget)

Ongoing monthly costs (the client's actual budget)

Vercel Pro (storefront + admin) — ₹1,500/month
CloudNX Mumbai region (backend + database) — ₹3,500/month
Google Maps API (route optimization) — ₹2,000-₹6,000/month depending on volume
FCM push notifications — free up to high volume
Razorpay transaction fees — 1.9% per transaction (~₹15-30/order at average ticket size)
Apple Developer Program — ₹8,000/year
Google Play Console — ₹2,000/year one-time
Total monthly running cost: ₹7,000-₹12,000/month + Razorpay transaction fees

What we would do differently if we built it again today

1. Skip the customer iOS app at launch

About 92% of the client's customer base is on Android. We built iOS anyway because 'launch parity feels right.' In hindsight, we should have shipped Android-only for the customer app in v1 and added iOS in month 4 once revenue justified it. Would have saved ~₹50,000 in build cost and 2 weeks of iOS-specific App Store review delays.

2. Use Supabase for auth + realtime instead of custom Node.js

We built custom JWT auth + WebSocket dispatch in Node.js. Worked great. But Supabase's combination of Postgres + auth + realtime subscriptions would have saved us about 3 weeks of work for the same outcome. Their pricing fits this scale (~₹2,000/month) and offloads the auth/realtime maintenance.

3. Cache the catalog more aggressively in the customer app

The customer app fetches the catalog fresh on every cold start. We later added 5-minute caching. We should have done 24-hour caching with a background refresh from launch. Customers don't need real-time catalog updates — they need fast app open times.

If you're building something similar — costs to expect

For an Indian grocery business building a 3-app system in 2026, realistic budget ranges (full custom, no SaaS lock-in):

Solo storefront only (Shopify or simple Next.js, no driver app): ₹85K-₹2.4L
Storefront + customer mobile app (no driver app — you use WhatsApp/manual dispatch): ₹3.5L-₹6L
Full 3-app system (web + customer app + driver app) like Jai Shri Balaji: ₹8L-₹15L depending on complexity
Blinkit/Zepto-scale dark-store stack (50+ warehouses, real-time inventory, marketplace dispatch, complex pricing): ₹40L-₹1.5cr

If a 'grocery app developer' is quoting you ₹3 lakh for a 'complete Blinkit clone with all features' — they're either using a white-label SaaS template (you'll outgrow it in 6 months) or they're going to disappear before completion. Real builds in this category cost what they cost.

The operational outcome (3 months in)

Three months after launch, here's where Ashok's team at Jai Shri Balaji Store is:

120-180 daily orders, up from ~30 on WhatsApp pre-launch
60% of new orders coming through the customer mobile app
Average ticket size ₹420, average margin per order ~28% (typical Indian grocery)
4 delivery drivers active, doing 30-40 deliveries each per shift
Customer retention at week 4: 64% (industry average is around 50%)
Store manager spends ~2 hours/day on admin panel, vs 6+ hours of WhatsApp chaos pre-launch

The unit economics are positive. The system pays for itself (build cost amortized over 18 months) by month 14 at current growth rate.

buildbyRaviRai built our entire system in 3 months — website, customer app, and driver app — all working together. Before this, we were managing 30 daily WhatsApp orders chaotically. Today we do 150+ a day with less stress than we had at 30. The driver app alone changed how our team operates. Ravi and the team understood our business, not just our tech requirements.

— Ashok Dhull, Founder — Jai Shri Balaji Store

Want to talk to us about something similar?

If you're scoping a grocery business, dark-store, marketplace, or any operational e-commerce business with delivery — we'd genuinely like to talk. We've built 4 different operational e-commerce systems in 18 months (grocery, pharmacy, restaurant chain, B2B wholesale). The architecture decisions are similar; the business models and unit economics are very different.

First conversation: 20-min call, free, project fit only — not a sales pitch. We'll ask about your existing operations, your delivery model, your warehouse setup, and your real budget. By the end of the call we'll tell you honestly whether we're the right partner or whether you should look elsewhere.

Building a grocery, pharmacy, or delivery-driven business in India? Let's talk. 20-min call, free, no sales template. We'll send you a 1-page written proposal within 48 hours if it's a fit. → Talk to us about your project

Click through the live system

If you want to see the storefront live: https://jaishribalajistore.com — it's a working production grocery store, not a demo. Place a small order, see the flow, watch the order status update in real-time. The customer mobile app is on Play Store and the driver app is internal-only (Play Store private channel) but we can demo it on a screen-share if you want to see the route optimization.

₹4,200 Crore: What Indian Small Businesses Quietly Lost to Bad Websites in 2025

Ravi Rai — Fri, 15 May 2026 07:49:20 +0000

In 2025, Indian small businesses collectively lost an estimated ₹4,200 crore in revenue to a single, fixable problem: a customer searched for them on Google, didn't find them (or found a broken/slow version of them), and went to a competitor instead. Most of those businesses don't know it happened. The customer didn't WhatsApp them, didn't call, didn't walk in. Just searched, didn't find, gone. This post breaks down where that ₹4,200 crore came from, who lost it, and exactly how to avoid being in next year's number.

Every Indian small business owner I've spoken to who didn't have a website thought they were 'saving money' on it. None of them knew they were losing 3-5x the cost of the website every year in customers who searched, couldn't find them, and quietly went elsewhere. That's the invisible tax of not being online properly.

Where the ₹4,200 crore number comes from

There are roughly 6 crore registered small businesses in India in 2026. About a third of those (≈2 crore) operate in categories where customers actively search Google or Maps before buying — restaurants, clinics, salons, gyms, coaching, repair services, manufacturers, wholesalers, B2B suppliers, real estate, legal, accounting, retail. Inside that 2 crore:

About 50% (1 crore) have no website at all — only WhatsApp / Instagram / Facebook / no online presence
About 30% (60 lakh) have a website but it's broken, slow, outdated, or not indexed on Google
About 20% (40 lakh) have a working, indexed, modern website

Conservative estimate of customer loss per business in the first two buckets: ₹3,500 per month on average (some lose ₹500/month, some lose ₹40,000/month — average across categories lands at ~₹3,500). Multiply: 1.6 crore × ₹3,500/month × 12 months = approximately ₹6,720 crore in gross loss. After deducting customers who would have found the business anyway via Word of mouth / Instagram / walk-in, the net Google-search-driven loss is roughly ₹4,200 crore.

This isn't a marketing stat we made up. We arrived at it from auditing 200+ Indian small businesses' search visibility (using free Google tools) and extrapolating to the national base. Your exact number depends on your category, location, and competition — but if you're in the first two buckets, it's almost certainly between ₹40,000 and ₹3,00,000/year per business.

Breakdown by business category

Restaurants & cafes

Biggest single category of loss — roughly ₹800 crore in 2025. Why: 'best [cuisine] near me' is one of India's highest-volume search queries. A restaurant without a Google-indexed website with hours, menu, and reservation flow is invisible to ~40% of its potential customers. We've audited restaurants in Bangalore and Delhi losing ₹50,000-₹2,00,000/month in tables they could have filled.

Doctors, clinics, dentists, physiotherapists

Estimated ₹620 crore lost. Patients searching 'best dentist [neighborhood]' or 'dermatologist near me' go to whoever shows up first with reviews. A clinic with no website loses 30-50% of new patient enquiries to clinics that DO show up. Average loss: ₹40,000-₹1,50,000/month for established practices, scaling to ₹3 lakh+/month for specialists.

Coaching centers, tutors, music schools

Estimated ₹540 crore lost. Parents searching 'best maths tutor 8th class [city]' or 'IIT coaching [neighborhood]' rely heavily on Google. A coaching center with a poor website loses 50-70% of its inbound to better-positioned competitors. Many tutors don't realize this because they fill up via referrals — but referrals plateau, and Google traffic doesn't.

Lawyers, CAs, financial advisors

Estimated ₹480 crore lost. Particularly painful because per-client values are high (₹15,000-₹2,00,000 per matter). A boutique law firm losing 2-3 enquiries a month to a poor website is losing ₹30,000-₹6,00,000/month. The lost client doesn't tell them — they just hire the other lawyer.

Salons, spas, gyms, fitness studios

Estimated ₹390 crore lost. 'Best salon near me' and 'unisex gym [city]' are massive search categories. Indian customers in 2026 increasingly book trial sessions and consultations online. No website = no trial = no membership.

Real estate agents, brokers, property managers

Estimated ₹450 crore lost. Property buyers Google extensively before contacting agents. An agent without a website loses 60-80% of their potential digital inbound to MagicBricks-listed competitors with proper sites.

Retail & wholesale (small/medium)

Estimated ₹380 crore lost across jewelry, fashion, electronics, hardware, sweet shops, grocery, specialty foods. The Lajpat Nagar sweets shop scenario times 10,000.

Manufacturers, B2B suppliers, industrial services

Estimated ₹540 crore lost. B2B procurement professionals search Google before contacting suppliers, especially for industrial parts, machinery, services. A manufacturer without a website with clear product catalog loses 50-80% of digital B2B inbound.

The four ways small businesses lose customers online

1. They have no website at all

The biggest category. ~1 crore Indian small businesses. They rely entirely on WhatsApp, Instagram, walk-ins, and word of mouth. When a customer searches Google, they get zero results for the business. The customer assumes the business is too small, too informal, or doesn't exist. They go to the next result.

2. They have a broken or expired website

The Lajpat Nagar pattern. Site was built, ran for a year or two, then broke (domain expired, hosting suspended, contact form failed, freelancer disappeared). Site shows '404 not found' or 'this site can't be reached' to Google searchers. The customer assumes the business closed.

3. They have a website Google can't find

Site exists, loads, looks fine. But it's not in Google's index because the developer never submitted it to Search Console, didn't add a sitemap, used a template that blocks crawlers, or hosted it on a free platform that adds noindex tags. The customer searches Google → can't find it → goes to competitor.

4. They have a website that's slow or broken on phones

Site loads, but takes 8-12 seconds on mobile. Or buttons don't work on phones. Or the contact form is unreadable. 60% of Indian traffic is mobile. A site that's broken on mobile is broken for most of its audience. 50%+ of visitors leave within 4 seconds.

How to estimate YOUR business's loss in 30 minutes (free)

You can estimate your own number in half an hour using free Google tools:

Open Google Keyword Planner (free with any Google account)
Search for 5-10 terms your customers might use: 'best [business type] near me', 'best [business type] [your city]', '[service] [neighborhood]'
Note the monthly search volume for each. For most Indian small business categories in a tier-1 or tier-2 city, you'll see 500-50,000 monthly searches
Calculate: if your business currently captures 0% of those searches (no website / broken website), you're losing the proportion of those searchers who would have become customers. Industry conversion rate from search → customer is roughly 2-5% on average
Multiply: searches × 3% × your average customer value = monthly lost revenue

Worked example: a Pune dentist sees 4,000 monthly searches for 'best dentist near me Pune'. 3% conversion = 120 potential patient enquiries. Even if they'd only have captured 10% of those = 12 enquiries × ₹1,500 average first-visit value = ₹18,000/month, or ₹2.16 lakh/year in NEW patient revenue. Plus follow-up visits, dental work, family referrals. Real number: ₹5-10 lakh/year of compounding loss.

Why the loss is invisible to most owners

The cruelest part of this loss is that you can't see it. Customers who didn't find you don't message you to complain. They don't email. They don't WhatsApp. They went to your competitor and you have no way of knowing they tried to find you first. So Indian business owners feel 'business is okay, why spend on a website' — without realizing the business could have been 30-50% bigger.

This is the single biggest reason small business owners delay getting a website. The pain is invisible. The cost is invisible. The competitor capturing those customers is invisible. Only when someone explicitly walks them through the math do they realize what's happening.

What changed in 2024-2026 that made this worse

Three things accelerated this loss in the last 2 years:

Mobile internet penetration crossed 80% in Indian cities. Even tier-3 customers Google before buying.
Google increasingly favors Google Maps + verified business websites in local results. Businesses without verified profiles + websites drop off the first page.
AI-generated search results (Google AI Overview) increasingly summarize the top-ranked websites in your category. If you're not one of them, the AI answer literally doesn't mention you.

The 30-day plan to not be in 2026's number

Days 1-3: Diagnose where you are

Google your own business name + city. See what shows up. Note the position. Repeat for 3 main service searches ('best [service] [city]'). Note where you appear (or don't). This is your baseline.

Days 4-10: Decide what you need

Pick one path based on budget. Under ₹15K: set up a Wix/Squarespace site yourself in a weekend. Pay ₹1,500/month. Acceptable. ₹50K-1.5L: hire an agency for a proper site with SEO basics included. Avoid the ₹10-30K dead zone.

Days 11-25: Build and launch

If hiring an agency: 30-day build is realistic for Type 1 and Type 2 sites. Insist on Google Search Console setup, sitemap, Google My Business linking, mobile-fast loading. These are not optional.

Days 26-30: Verify it's actually showing up

Google your business name again. You should now show up first for your business name. Within 4-8 weeks, you should start showing up for some 'best [service] near me' searches. If you don't, your site isn't actually being indexed properly — and you should ask whoever built it.

What this means concretely for you

If you're in the 80% of Indian small businesses without a working website, the realistic cost of staying that way for 12 more months is ₹40,000-₹3,00,000 in lost revenue. The cost of fixing it is ₹50,000-₹1,50,000 once, plus ₹5,000/year hosting. The math is unambiguous. The friction is just the decision and the first message.

We've helped 80+ Indian small businesses make this transition in 5 years. Almost all of them say the same thing after 6 months: 'I should have done this years ago.' We've never had a client say the opposite.

Want us to estimate YOUR specific loss in 15 minutes? Send us your business name + city on WhatsApp. We'll run the Keyword Planner numbers and tell you what you're missing — free, no pitch. → Get a free loss estimate

Pass this on

Send this post to one Indian business owner who's been putting off getting a website. The conversation 'how much am I losing each month?' is the only conversation that moves them from 'I should get a website someday' to 'I'm doing this next week.' The ₹4,200 crore lost in 2025 wasn't a small businesses problem. It was 1.6 crore individual small business owners individually losing ₹3,500/month without realizing it. One conversation at a time, that number shrinks.

Don't Trust Your Nephew With Your Business Website — Read This First

Ravi Rai — Fri, 15 May 2026 07:42:55 +0000

Two months ago, a sweets shop owner from Lajpat Nagar messaged us at 11 PM on a Saturday. His website — built by his sister's son in B.Tech 2nd year, ₹9,000 fixed price, 'free hosting forever' — had gone offline three days before. The nephew had stopped replying. The site had ranked well on Google for 'best sweets Lajpat Nagar' for almost two years. Suddenly it was gone, customers were calling to ask if the shop had closed, and Diwali was 11 days away. This post is for any Indian business owner who's currently considering, or has already taken, the cheap-website route. It's not about mocking the choice. It's about what actually happens — because we've seen it about 30 times in 2 years.

The ₹8,000 website isn't expensive because of what you pay upfront. It's expensive because of what it costs you to fix it 12-18 months later — by which point your competitor's website has been ranking on Google for a year and the customers you needed have already gone to them.

Who actually builds those ₹8,000 websites

There are three categories of people offering ₹8,000-₹15,000 websites to Indian small businesses in 2026:

Engineering college students looking for portfolio practice. Genuinely well-meaning. Limited technical skill. Will move on to a full-time job in 6-12 months and stop responding to your WhatsApp.
Self-taught freelancers in tier-2/3 cities who use template-based site builders. They can produce a working site quickly. They cannot debug, optimize, or fix things when they break.
Resellers from 'website wholesale' marketplaces — they buy a generic template for ₹500, resell to you for ₹10,000, and pocket the difference. They do not write the code themselves. When something breaks, neither do they.

None of these are necessarily bad people. They're often offering exactly what they're capable of delivering at that price. The problem isn't dishonesty — it's that the result is not actually a sustainable business asset.

What actually goes wrong (in order of frequency)

1. The site disappears

Most common scenario. The freelancer registered the domain and hosting in their own account. After 12 months, the renewal email goes to them, not you. They either forget, ignore it, or genuinely move on. One day the site is just gone — replaced by a 'domain expired' page or a hosting suspension notice. You don't have the login. You don't even know which hosting provider it was on. To recover the domain you may have to wait 90 days for it to release back to the registrar pool, then bid against squatters.

2. The site doesn't show up on Google

Second most common. The site exists, looks fine, but cannot be found when someone searches your business name + city. Why? Because the freelancer didn't submit it to Google Search Console, didn't set up a sitemap, didn't add basic SEO meta tags, and used a template that wasn't mobile-friendly. You're paying for a website that exists in name but doesn't bring you customers. After 6 months you wonder why nothing's happening.

3. The contact form doesn't work

Customers fill it out. Nothing happens. You don't realize for 3-4 months because you assumed your phone would ring. We've audited sites where 60-80 customer enquiries were sitting in a database somewhere — never delivered to the business owner because the freelancer didn't set up email forwarding properly. Each of those was a potential customer who went to a competitor.

4. The site is slow on phones

60% of Indian web traffic in 2026 is mobile. If your site takes more than 4 seconds to load on a 4G phone, 50% of visitors leave before seeing your content. Most cheap websites use heavy templates with no image compression. We've seen ₹10,000 sites that took 9-12 seconds to load on a phone — essentially a 'no website' equivalent.

5. The site has security holes

Less common but more catastrophic. Cheap WordPress sites with outdated plugins get hacked. Visitors see spam links injected into your homepage. Google flags your site as 'unsafe.' Your phone number on the site gets harvested by spammers. Some sites have been used to redirect customers to gambling/adult sites without the owner knowing for months.

6. You can't update anything yourself

Your prices change. Your services list expands. Your address moves. Your festive offer needs to go up. But you don't have the login. The freelancer is unreachable. Your website now shows information from 14 months ago. New customers visiting your site get an outdated picture of your business and silently leave.

The 30 stories — common pattern

Across the 30+ rescue projects we've taken on in the last 2 years, the timeline is almost identical:

Month 0: Business owner hires nephew/cousin/cheap freelancer. Pays ₹8,000-₹15,000. Gets a website that 'looks fine.'
Month 1-3: Owner is happy. Site exists. They tell friends.
Month 4-9: Slow realization — phone isn't ringing more than before. Customer asks 'why didn't I see your business on Google?'
Month 10-15: Something breaks. Contact form stops working / domain expires / site gets hacked / freelancer stops replying.
Month 14-18: Business owner messages someone like us, embarrassed, ready to pay 5x what they originally spent.
Total cost over 18 months: ₹8,000 (original) + ₹60,000-₹1,20,000 (recovery + rebuild) + lost customers during the broken months. Realistically ₹1.5-3 lakh.

If they had paid ₹50,000-₹75,000 for a proper website in month 0, they would have spent ₹50,000-₹75,000 total over 18 months — and had a working asset the whole time.

When the cheap option IS actually fine

I don't want to pretend every cheap website fails. About 1 in 5 actually works fine for years. Here's when:

Your nephew is a senior software engineer (not a 2nd-year B.Tech student) who genuinely loves you and will support the site for years. Very rare. If it's true for you, take it.
You're using Wix / Squarespace / Shopify with a do-it-yourself template — these platforms handle hosting, security, updates automatically. ₹1,500-₹2,000/month total. Limited customization, but it works. Not 'cheap freelancer cheap' — this is platform-cheap, which is a different category.
Your business is genuinely brand new and you just need 'something on Google' for 6 months while you figure out the actual offer. Build a Wix site yourself in 2 hours. Plan to redo it properly in 6 months.

Note that in NONE of these scenarios are you hiring a random cheap freelancer to write custom code for ₹10,000. That specific path is the one that fails 80% of the time within 18 months.

Warning signs to watch for BEFORE you pay

If you're already in conversation with a cheap freelancer, here are the questions whose answers tell you whether to proceed:

'Whose name will the domain be registered in?' — Correct answer: YOUR name, with YOUR email as the contact. If they say 'I'll keep it in my account, easier to manage' — walk away.
'What hosting will you use? Can I have the login?' — Correct answer: a real hosting provider (Hostinger, GoDaddy, CloudNX) with the account in your name and credentials given to you. If they say 'free hosting forever, don't worry about logins' — walk away.
'How will you ensure the site shows up on Google?' — Correct answer: details about Google Search Console submission, sitemap, basic SEO. If they say 'Google will find it automatically' — that's not how Google works.
'Can I update content myself after launch?' — Correct answer: yes, with a 30-min training call. If they say 'WhatsApp me when you want changes, ₹500 per update' — you're locked in.
'What happens if I want to add a feature in 6 months?' — Correct answer: a clear quote per addition, normal hourly rate. If they say 'we'll figure it out then' — there will be friction.
'Do you have 3 live URLs of past work I can click on?' — Correct answer: yes, with URLs you can verify. If they only send screenshots — those screenshots may be from someone else's portfolio.

If you've already been burned

Don't be embarrassed. Don't feel stupid. About 30 Indian business owners have come to us in the last 2 years in exactly this situation. None of them deserved a lecture. All of them got their site back, properly, within 4-6 weeks.

What we'll do:

Free 15-min audit of your current site / situation (send us the URL or whatever access you have)
Tell you honestly whether to FIX what exists (₹15K-₹40K) or REBUILD properly (₹50K-₹1.2L)
Recover your domain if possible. Migrate hosting to your own account. Set up proper Google Search Console, analytics, contact form.
Build the new/fixed site in 2-4 weeks. You always own everything from day 1.

The math that decides it

For a small business doing ₹3-15 lakh per month in revenue, the math on website investment is:

Real website: ₹50K-₹75K upfront, ₹5K/year hosting, lasts 3-5 years before redesign. Total 3-year cost: ~₹95K.
Cheap website: ₹10K upfront, ₹8K rescue at month 14, ₹60K rebuild at month 18, plus ₹40K-₹2L lost in customers during the broken months. Total 3-year cost: ₹1.5L-₹3L.

The 'cheap' option is 1.5-3x more expensive over the life of the website. Every business owner I know who paid the cheap price first wishes someone had shown them this math upfront.

The actual question to ask yourself

It is not 'how much does a website cost?' It is 'how much does my business lose every month when a customer searches for me on Google and doesn't find me?' For most Indian small businesses, that number is between ₹4,000 and ₹20,000 per month. Multiply by 18 months of a broken cheap site, and you have your real answer.

What we recommend (simply)

If your budget for a website is under ₹15,000 total: don't hire a freelancer. Use Wix or Squarespace yourself. Spend 4-6 hours setting it up. Pay ₹1,500-₹2,000/month for the platform. Acceptable for 12-18 months while your business grows.

If your budget is ₹50,000-₹1,50,000: hire a real agency or senior freelancer. Get a written scope. Pay 50% upfront. Get all domain/hosting in your name. Get a 30-min handover. Get a working website that lasts 3-5 years.

Avoid the ₹10,000-₹30,000 range. It's the dead zone where everyone loses — you pay too much for a bad result, the freelancer makes too little to do good work, nobody is happy at month 14.

Got a website that's broken, slow, or you don't have access to? Send us the URL — we'll do a free 15-min audit and tell you honestly: fix it (₹15K-40K) or rebuild it (₹50K-1.2L). No sales pressure either way. → Get a free audit

If you read this in time

Forward this post to one business owner you know who's about to hire their nephew. The post might save them ₹1-3 lakh and 14 months of frustration. It cost them nothing to read. It costs you nothing to share. The 30 business owners we've rescued in the last 2 years would have given a lot for this post to land in their inbox at the right moment.

If You Run a Business in India and Don't Have a Real Website Yet — Read This

Ravi Rai — Fri, 15 May 2026 07:36:58 +0000

If you run a small business in India and you've been thinking 'I should really get a website' for the last 2-3 years and not actually done it — this post is for you. You're not lazy. You're not behind. You just got bad information from the people you asked, and the whole 'how do I get a website' process feels confusing and expensive. Let me un-confuse it. You'll know exactly what to do by the end.

70% of Indian small businesses still don't have a working website in 2026. Not because they don't want one. Because someone quoted them ₹2 lakh, or built them a template site that doesn't show up on Google, or told them 'WhatsApp Business is enough.' None of those are true. A real, working website costs less than you think and brings customers you're currently losing to the competitor down the street.

Why your WhatsApp / Facebook / Instagram alone isn't enough

Many Indian business owners say 'I have a WhatsApp Business number, why do I need a website?' Here's why those aren't a substitute, in plain language:

When someone searches 'best dentist in Noida' on Google, your WhatsApp doesn't appear. A website does.
Customers in 2026 trust businesses that exist on Google. No website = customer assumes you're small or temporary, even if you've been around 20 years.
Instagram and Facebook don't let people see your full price list, services menu, or contact details in 30 seconds. A website does.
You can't email a Facebook page to a corporate client when they ask for company details. You can email a website link.
Your competitor down the street has a website. When their site shows up on Google and yours doesn't, you lose the customer — even if your product is better.

What 'having a website' actually means in 2026

A 'real' website for a small Indian business in 2026 has these pieces:

A domain name (yourbusiness.com or .in) — the address people type
5-7 pages that explain who you are, what you sell/offer, prices (if relevant), contact details, and a few photos
A working contact form (or WhatsApp button) so customers can reach you in one click
A Google My Business profile linked to your website (free, takes 2 hours to set up properly)
Loads fast on phones (60% of your traffic will be mobile)
Shows up on Google when someone searches your business name + your city
Has decent photos — 8-15 photos of your product, shop, team, or work samples

Things you DON'T need on day one (despite what salespeople tell you): a custom-built CRM, an online booking system (use WhatsApp until volume justifies it), a chatbot, a mobile app, a custom backend system, an admin panel. Most websites get sold these things and never use them.

The 4 types of websites — pick the one that fits

Type 1: Service / Local Business Website (Most common)

For: doctors, lawyers, CAs, coaching centers, repair services, salons, gyms, real estate agents, consultants, manufacturers, B2B service providers. You want customers to find you, see your services, and contact you for an appointment or quote.

What it has: 5-7 pages (Home, About, Services, Pricing, Testimonials, Contact), photo gallery, WhatsApp + phone CTAs, Google Maps embed
What it costs (one-time build): ₹35,000 – ₹75,000
What hosting costs (yearly): ₹3,000 – ₹6,000
Build time: 2-3 weeks
What you can do yourself afterward: update photos, change prices, add new services (we'll show you how on a 30-min handover call)

Type 2: Restaurant / Cafe / Food Business Website

For: restaurants, cafes, cloud kitchens, food brands, bakeries, caterers. You want customers to see your menu, location, hours, and order via Zomato/Swiggy or directly.

What it has: Home, Menu (with photos and prices), About, Reservations (WhatsApp form), Reviews, Contact, Google Maps, links to Zomato/Swiggy
What it costs: ₹45,000 – ₹90,000
What hosting costs: ₹3,000 – ₹6,000/year
Build time: 2-4 weeks
Things you can do yourself: update menu, change hours, add specials

Type 3: E-commerce Website (For Selling Products Online)

For: anyone selling physical or digital products — fashion, jewelry, food brands, home goods, electronics, books, courses, services with online delivery.

What it has: Product catalog (10-200 products), shopping cart, online payment (Razorpay), order management, customer accounts, basic SEO, inventory tracking
What it costs: ₹85,000 – ₹2,40,000 (depends on product count and platform — Shopify recommended for most small businesses)
Monthly platform cost (Shopify Basic): ₹1,994/month
Hosting: included in Shopify or ₹3,000-6,000/year for WordPress
Build time: 4-6 weeks
Things to know: you need a GSTIN + current account to accept online payments in India

Type 4: Educational / Content Website (Schools, Coaching, Media)

For: schools, coaching centers, online educators, news/media businesses, blogs that earn ads/affiliate revenue.

What it has: Multi-page content management, blog/article publishing, student/teacher login (if needed), course listings, fee details, admission form, SEO
What it costs: ₹65,000 – ₹1,80,000
What hosting costs: ₹3,000 – ₹6,000/year
Build time: 3-5 weeks
What you can update yourself: blog posts, news, course listings, photos — we set this up so non-technical staff can manage it

The actual 30-day process (start to live website)

Week 1: Strategy + Content (Days 1-7)

We have a 30-minute call to understand your business, your customers, and what the website should achieve. We help you collect the 5-7 pieces of content we need: photos, list of services, pricing (if applicable), 2-3 testimonials, basic 'about us' text. Most clients have 60% of this material already — they just haven't organized it. We help you finish it.

Week 2: Design (Days 8-14)

We share a clickable design preview by end of week 2. You give feedback. We revise. This is where most agency projects get stuck — endless revisions. Our rule: 2 rounds of design changes are included; after that, additional changes are ₹2,000 each. This keeps the project on schedule without rushing you.

Week 3: Build (Days 15-21)

We build the actual website. You see daily progress on a staging URL. By end of week 3, you have a fully working website you can click around on, fill out the contact form, see how it looks on your phone.

Week 4: Launch + Training (Days 22-30)

We set up Google Analytics, Google My Business, the contact form delivery to your email, SSL certificate, search engine submission, and basic on-page SEO. We do a 30-minute handover call with you (or your staff) to show how to update content. Then we make the site live on your domain. You officially have a website.

What it costs over 3 years (vs your current setup)

Many small business owners think 'a website is too expensive.' Let's run the math. A Type 1 service website costs roughly:

Year 1: ₹50,000 build + ₹5,000 hosting = ₹55,000 total
Year 2: ₹0 build + ₹5,000 hosting + maybe ₹15,000 maintenance = ₹20,000
Year 3: ₹0 build + ₹5,000 hosting + ₹15,000 maintenance = ₹20,000
3-year total: ₹95,000 — or about ₹2,600/month averaged

Now compare that to: not having a website. Average small Indian business loses ₹40,000–₹2,00,000 PER YEAR in customers who searched for you on Google, didn't find you, and went to a competitor. That number scales with how many people in your city/area search for businesses like yours each month. We can estimate this for you on the first call using free Google tools.

A website typically pays for itself in 4-8 months for service businesses, 2-4 months for e-commerce, and 6-12 months for content/educational businesses. The 3-year ROI is almost always positive, often massively so.

What you'll NEED to provide us

We do 90% of the work. Here's what we need from you:

30 min for the strategy call (in English or Hindi, whichever you prefer)
8-15 photos of your shop, product, team, or work (phone photos are usually fine — we'll tell you which ones to retake)
A 1-paragraph description of what your business does (we'll help you refine it)
List of services or products with rough pricing if applicable
Your business phone number, address, and email
2-3 testimonials from happy customers (we can help draft these from voice memos if you don't have written ones)
Logo (if you have one — if not, we can create a simple text logo for free)
50% upfront payment to start (via UPI, NEFT, or any payment method that works for you)

That's it. We handle: domain registration, hosting setup, design, development, deployment, SSL, SEO basics, Google My Business setup, and the post-launch handover call. You handle: the business, the customers, the actual work that pays for the website.

What clients typically ask on the first call

I have a website but it's old / broken. Can you fix it instead?

Often yes, and it's usually cheaper than rebuilding. We do a free 15-min audit and tell you whether to redesign (₹30K-80K) or start over (₹50K-1L+). About 60% of audits result in 'fix the existing one' rather than 'rebuild from scratch.'

My nephew/cousin/neighbor can make me a website for ₹8,000. Why should I pay more?

He might be able to make you a website. He probably can't make you a website that loads fast on phones, shows up on Google, doesn't break in 6 months, has working contact forms, and is properly secured. We've migrated 30+ small businesses off cheap freelance builds in the last 2 years — usually because the original developer disappeared or the site stopped working. The ₹8,000 site costs more in the long run.

I don't know what content to put. Can you write it for me?

Yes. We have a content writer on the team who can write the basic pages from a 20-minute interview with you (in Hindi or English). Cost: ₹8,000-₹15,000 depending on length. About 40% of our clients add this to their project.

Can you also do my Google Ads / Instagram marketing?

Yes — we have a separate digital marketing team for this. Most clients launch the website first, then add marketing 2-3 months later once we see what's working organically. We can quote both together if you want.

What if I want changes after launch?

Small content updates (changing prices, adding services, updating photos) — we include 30 days free. After that, monthly maintenance starts at ₹4,000/month covering small updates. Bigger redesigns or new sections quoted separately. We've never had a client surprised by maintenance pricing because we put it in writing upfront.

How to start (3 ways)

📱 WhatsApp +91 74289 19927 — fastest. Send one paragraph about your business and what you need. We reply same day.
✉️ Email support@buildbyravirai.com — slightly more formal, slightly slower (within 24 hours).
🌐 Use the contact form on /contact — gives us your details in a structured way.

Whichever you pick, our first reply is always: a couple of clarifying questions and a 30-minute call invite on a day that works for you. No sales pitch. No auto-responder. Ravi or the team will reply personally.

If you've been putting this off for years

I get it. Every Indian small business owner I've spoken to who DIDN'T have a website had three reasons for putting it off: it sounded expensive, it sounded complicated, and they weren't sure they 'needed' one. The post above addresses all three. The fourth reason — the one nobody says out loud — is that you don't want to be sold to by an agency. That's the reason this post is the longest 'sales pitch' you'll find on our site. We'd rather you read this and decide for yourself, than book a call where someone tries to convince you.

If you've been putting this off, 30 days from today you could have a real, working website that brings you new customers from Google every month. The hardest part is sending the first message. Everything after that, we'll guide you through.

Ready to finally get a website built? Send us one paragraph about your business — we'll reply with a written 1-page proposal within 48 hours. No sales call required. → Get started

Why Founders Hire buildbyRaviRai (And Why Some Founders Shouldn't)

Ravi Rai — Thu, 14 May 2026 08:41:37 +0000

Most agency 'why us' pages are written by marketing people for SEO and end up sounding like every other agency page. This isn't that. If you're considering hiring us, read this first. It will tell you exactly what working with buildbyRaviRai looks like — the engagement process, real INR pricing for the projects we do most often, our tech stack, the AI tools every developer on our team uses, and the clients we politely say no to. If you finish this post and want to talk, the form at the bottom is the right next step. If you finish this post and decide we're not the right fit, that's also a win — you saved both of us a sales call.

The best clients we've ever had read our blog before booking the call. They came in already knowing how we work, what we charge, and what we won't do. The conversation went from sales pitch to project scoping in 5 minutes. This post is for that kind of founder.

Who we work with best

Five years and 80+ clients across India, Canada, UK, UAE, and US have given us a clear picture of who gets the most value from working with us. If you fit one of these profiles, we're almost certainly a strong match:

Indian founders building a SaaS, e-commerce store, or B2B web app and they want a serious technical partner — not a freelancer they'll have to babysit
Companies migrating from WordPress to Next.js, from raw cloud to managed cloud, from spreadsheets to a real internal tool — projects with clear before/after
EV charging, fintech, healthcare, edtech operators who need production-grade backend systems (OCPP, Razorpay/Stripe, multi-tenant Laravel) with real reliability requirements
International founders who want India-quality work at India-pricing but expect agency-grade communication, written scope, milestone delivery, and clean handover
Existing businesses with a broken or abandoned site (developer ghosted, freelancer disappeared, ex-team left without docs) — we have a specific rescue process for these
Solo founders or small teams who need a fractional dev team for 3-6 months to ship version 1 of a product without hiring full-time

Who we honestly say no to

Saying no is part of how we keep the team's quality high and our clients happy. We turn away roughly 30% of inbound inquiries. The most common reasons:

Projects with budgets under ₹50,000 — we can do the work but we won't do it well at that price, and a freelancer is the better fit for you. We'll send you to one we trust.
Founders who want to pay only on launch / pay only if the project succeeds — we don't take revenue-share gigs from people we don't know personally. Real businesses pay for work delivered.
Founders who say 'I'll send the scope after we start' — we need a written 1-page scope before any work begins. If you don't know what you want yet, we can do a paid 90-min scoping call (₹3,500) that produces the scope.
Brand-new clients who refuse to pay 50% upfront. Non-negotiable. This isn't about distrust — it's about how we run a sustainable team. The clients who push hardest on this turn out to be the slowest to pay at the end.
Anyone whose first message contains the phrase 'we're disrupting [industry] using blockchain.' Not always. But usually.

What working with us actually looks like

Step 1: First message → 20-min call (within 24 hours)

You send us a message via the contact form, WhatsApp (+91 74289 19927), or email (support@buildbyravirai.com). We reply within 24 hours, usually within 4. The first call is 20 minutes, free, on Google Meet or WhatsApp video. It's a project-fit conversation, not a sales pitch — we want to understand what you're trying to build, what you've tried already, what the deadline is, and roughly what budget you have. If we're not the right fit, we tell you on that call and recommend someone who is.

Step 2: Written 1-page proposal (within 48 hours of the call)

If both sides are interested after the call, we send a 1-page proposal. It has: the project goal in your words, the deliverables in our words, the timeline broken into milestones, the flat INR price, the payment schedule (always 50% upfront, then milestone-based), and what's explicitly NOT included. No legal jargon. No 'starting from' pricing. One page, one number, one timeline.

Step 3: Contract + 50% upfront → kickoff

We use a simple 2-page contract that protects both sides. You pay 50% upfront via UPI, NEFT, or international wire. We set up a Slack channel (or WhatsApp group for smaller projects) and a shared GitHub repo. Kickoff happens within 3 working days of payment confirmation.

Step 4: Weekly milestone delivery + Friday update

Every Friday you get a written update: what shipped this week, what's blocked, what's next week's milestone, links to staging deployments. Most clients say this Friday update is the single most valuable habit we maintain. If we miss a milestone, we tell you that day, not on Friday. If you miss a feedback deadline, we extend the timeline by that much, not by 2 weeks of buffer.

Step 5: Handover + 30-day bug fix window

On project completion we hand over: GitHub repo (yours), deployment access (yours), database backups, written documentation (every project gets a handover doc), and a 90-min walkthrough call with your team. We include 30 days of free bug fixes post-launch. After that, you can either continue with us on a retainer or take it in-house — both are fine with us.

Real pricing for projects we do most often

We publish pricing here so the sales call doesn't have to be a budget discovery exercise. Real numbers, real 2026 INR, real ranges for projects we've actually delivered.

Marketing site (Next.js, 5-10 pages, CMS, SEO setup, basic blog): ₹65,000 – ₹1,80,000 · 3-5 weeks
WordPress business site (custom theme, contact forms, basic e-commerce, SEO): ₹45,000 – ₹1,20,000 · 2-4 weeks
Shopify store (custom theme, 50-200 products, app stack, payments, basic SEO): ₹85,000 – ₹2,40,000 · 4-6 weeks
Headless Shopify on Next.js (storefront API, Vercel deployment): ₹2,40,000 – ₹6,00,000 · 6-10 weeks
Custom SaaS / B2B web app v1 (auth, billing, dashboard, multi-tenant): ₹3,50,000 – ₹12,00,000 · 8-16 weeks
Laravel admin dashboard / internal tool: ₹1,50,000 – ₹5,00,000 · 4-8 weeks
Mobile app v1 (Flutter or React Native, 8-12 screens, auth, payments): ₹3,50,000 – ₹9,00,000 · 8-14 weeks
EV charging CSMS (OCPP 1.6-J, operator admin, billing): ₹6,00,000 – ₹18,00,000 · 12-20 weeks
Rescue / takeover project (developer ghosted, partial codebase): ₹50,000 – ₹4,00,000 depending on completeness · 2-8 weeks
Monthly retainer (1 senior dev, 40-60 hours/month, async + 1 weekly call): ₹50,000 – ₹1,20,000/month
Paid 90-min scoping audit (hosting, codebase, performance, SEO): ₹3,500 — pays for itself in month 1 for ~90% of clients

Every quote we send is the price of the project — no hidden hosting, no surprise plugin licenses, no 'plus tax' (GST is included in the quote). You pay one number for the deliverable. Hosting is invoiced separately by the provider (you pay them directly, we don't mark up).

Our actual tech stack (and why)

We're stack-disciplined: we don't chase trends. The tools we use today are tools we've used for at least 12 months in production. If you ask why we're not using whatever new framework launched last month, this is why.

Frontend: Next.js 16 (App Router), React 19, Tailwind CSS, shadcn/ui
Mobile: Flutter (production-polish projects) or React Native (faster time-to-market)
Backend: Node.js (small services), Laravel 11 (admin-heavy projects), Go (high-throughput WebSocket like OCPP)
Databases: Postgres (default), MySQL (legacy WP/Shopify integrations), Redis (caching, sessions), pgvector (AI workloads)
Hosting: Vercel for Next.js, CloudNX / DigitalOcean Mumbai for Laravel/Node, AWS Mumbai for high-compliance clients
Payments: Razorpay (default India), Stripe (international), Cashfree / PayU (specific use cases)
Auth: Clerk (default), Supabase Auth, Firebase Auth, custom Laravel for B2B
AI tools (we pay for these every month, not just talk about them): Cursor Pro, Claude Code Max, GitHub Copilot Business, Anthropic + OpenAI API access for internal use

The AI fluency thing

If you've read industry reports about Indian developer AI adoption, you know the breakdown: most developers are still in 'I use ChatGPT sometimes' bucket. Our team is not. Every developer at buildbyRaviRai has paid Cursor Pro and Claude Code Max access. We ship 30-60% of our code with AI assistance. This is roughly a 1.5-2x productivity multiplier compared to non-AI-first teams — which means for the same project cost, we ship faster, or for the same timeline, we ship more.

We mention this here because it shows up directly in your project timeline, your cost, and the quality of what we deliver. If you're hiring an agency for development work in 2026, ask any contender 'what AI tools does every developer on your team personally pay for?' If the answer is vague, you're hiring slower delivery for the same money.

Live work you can click on

We never send portfolio screenshots. Every project we mention has a live URL you can open. Three recent ones:

PlugEV (https://plugev.in) — production EV charging CSMS, OCPP 1.6-J, 40+ chargers live across 2 cities, WebSocket gateway in Go, Laravel admin
CloudNX (https://cloudnx.in) — managed cloud hosting platform for Indian developers, Next.js + Node.js + managed Linux servers, fast onboarding flow
ToolKiya (https://toolkiya.com) — all-in-one toolkit SaaS, multi-tenant dashboard, Stripe billing, Next.js + Postgres + Supabase

We also have 50+ client projects we can show under NDA on the first call. If your industry is sensitive (fintech, healthcare, government-adjacent) we have specific case studies that don't get listed publicly.

What clients say (in their own words)

Two testimonials we're proudest of, from clients you can verify on LinkedIn:

buildbyRaviRai transformed our online presence completely. Their team delivered a world-class platform that increased our customer engagement dramatically.

— Rajesh Sharma, CEO

The team at buildbyRaviRai is exceptional. They built our customer portal from scratch — UI design to cloud infrastructure. Highly recommend their services.

— Haroon Siddique, Product Lead

Common questions we get on first calls

How big is your team?

Small. Intentionally small. We're a senior-heavy team of 4-8 depending on active projects, with a network of ~10 trusted specialists we bring in for specific work (mobile, design, devops). We don't have a sales team, an account manager layer, or junior rotations. The person you talk to on the first call is one of the people who'll write the code.

Will my project get assigned to a junior?

No. We have no juniors. Every developer at buildbyRaviRai has 4+ years of production experience. This is intentional — we'd rather charge slightly more and ship faster than charge less and ship 2x slower with juniors learning on your dime.

Can you sign an NDA?

Yes, before any project conversation. Send your standard NDA and we'll sign within 24 hours. We have signed 60+ client NDAs over 5 years and never had a breach.

What if I want to fire you mid-project?

We hand over everything we've built, you pay only for delivered milestones (not the remainder), and we wish each other well. We've parted ways with 3 clients mid-project in 5 years — twice their priorities changed, once we mutually realized we weren't a fit. All three left with working code, full documentation, and no acrimony.

Do you do ongoing maintenance after launch?

Yes, via monthly retainers (₹50,000 – ₹1,20,000/month depending on scope). Most clients sign a 3-month retainer after launch, then either renew or transition to in-house.

How to start a conversation

Three ways, in order of speed:

WhatsApp +91 74289 19927 with one paragraph about what you're trying to build. We reply same day.
Email support@buildbyravirai.com with the same — slightly more formal, slightly slower.
Use the contact form on /contact — gives us your details in a structured way, replies in <24 hours.

Whichever you pick, the first response will be the same: a couple of clarifying questions and a 20-minute call invite, on a day that works for you. There's no sales person. There's no auto-responder marketing sequence. Ravi or the team will respond personally.

If this resonated

Then we're probably a good fit and a 20-minute call is the right next step. If parts of this post made you nod ('finally, an agency that publishes pricing') the rest of working with us will probably feel similar. Most of the values you read here — transparency, anti-template, no juniors, written everything — are how we run the team on Tuesdays at 11am, not just how we write our blog.

Project in mind? Book a 20-minute call. We'll send you a written 1-page proposal within 48 hours of the call. No sales pressure, no template responses, real human conversations. → Start a conversation

75% of Developers Still Aren't Really Using AI. The Honest 2026 Adoption Numbers.

Ravi Rai — Wed, 13 May 2026 05:29:42 +0000

If you read LinkedIn, you'd think every developer in India has been replaced by AI. Every other post is a screenshot of someone building a SaaS in 6 hours with Claude Code. Every founder you meet asks you why you still need humans. Investors quote stats like '90% of code in 2026 is AI-written.' Then you walk into actual companies, watch actual developers work, and the picture is completely different. Here's the honest breakdown from what we've seen across 80+ Indian engineering teams in the last 12 months.

75% of developers still aren't really using AI. 15% use free tools casually. Only 10% are AI-first. The gap between the LinkedIn narrative and the office reality is the single biggest hiring/scoping mistake Indian founders are making in 2026.

The actual 75/15/10 breakdown

We've audited engineering teams at startups, agencies, in-house product groups, and freelance pools — about 1,200 individual developers we've worked with, interviewed, or hired across the last 12 months. Self-reported usage is one thing; we cross-checked against actual usage patterns (commit messages, browser history when shared during pair sessions, IDE plugins installed, billing on company AI accounts). The pattern is consistent enough to be a real trend.

Bucket 1 — 70-75%: 'I open ChatGPT sometimes'

Three-quarters of working Indian developers in 2026 fall into this bucket. They have a free ChatGPT account. They open it 2-5 times a week. They use it for: regex patterns, SQL syntax reminders, error message translation, occasional boilerplate, and sometimes to outline an email to a client. They have NOT integrated AI into their actual code flow. They write code the same way they wrote code in 2022 — VS Code, Stack Overflow tab in the browser, console.log debugging.

Tools used: free ChatGPT, occasionally free Claude.ai
Average AI interactions per workday: 2-4 prompts
Time saved daily: 5-15 minutes
Why they're stuck here: comfort with existing workflow, no company push, fear of dependency

Bucket 2 — 15%: 'I use Cursor / Copilot but the free version'

15% of developers have installed an AI-aware IDE or plugin. Cursor (free tier), GitHub Copilot (free or via student/edu programs), Codeium, Cline. They get tab-completions, occasional 'fix this' suggestions, sometimes ask Cursor to write a small function. They're more productive than Bucket 1 — maybe 15-25% faster on routine work. But they hit the free tier limits every couple of days and just wait for the reset. They have not paid for AI yet.

Tools used: Cursor free, Copilot free/student, Codeium, Cline, occasional Claude.ai free
Average AI interactions per workday: 20-50 completions + 5-10 prompts
Time saved daily: 1-2 hours
Why they're stuck here: company won't pay for paid plans, personal budget pressure, uncertain if paid is worth it

Bucket 3 — 10%: 'AI is my default; I think differently now'

Only 10% of developers are what I'd call AI-first in 2026. They pay for Cursor Pro or Claude Code Max or GitHub Copilot Business. They use AI as their main way of thinking through problems — not as a tool, but as a workflow. They write 30-60% of their code with AI assistance. They use Claude Code to refactor whole modules. They have working knowledge of prompt patterns. They've moved past 'will this work' into 'what's the most efficient way to use this.' These are the developers everyone on LinkedIn pretends is the average.

Tools used: Cursor Pro, Claude Code Max, Copilot Business, occasional Devin/Trae/Cline pro
Average AI interactions per workday: hundreds of completions + 30-60 prompts
Time saved daily: 3-5 hours (genuinely)
Why they're here: agency or startup pays for tools, they've personally invested in learning the new workflow, network effects in their team

Why the gap is bigger than people think

1. Most Indian companies don't pay for AI

$20/month for Cursor Pro or $20 for ChatGPT Plus is roughly ₹1,700. Multiply by a 20-developer team and you're at ₹34,000/month. For a startup with a 6-month runway anxiety, that's a hard no without proven ROI. Companies that DO pay are mostly funded startups, IT consulting firms billing US clients, and a small set of agencies who've decided AI is core infrastructure. Everyone else asks devs to use free tiers.

2. AI productivity gains compound only with discipline

Buckets 1 and 2 developers often tell me 'I tried Copilot, didn't see the magic.' Of course not. AI productivity is a 3-month learning curve. You have to break old habits (Stack Overflow tabs, copy-paste from old projects), learn prompt patterns, learn when to trust output, learn when NOT to use AI. Most developers quit at the 'meh, this autocompletes wrong half the time' stage and never get to the 'oh, I think differently now' stage.

3. Cultural pressure to 'know how to code'

In India specifically, the 'real developer' culture punishes AI dependence. Tech leads from the 2010s scoff at devs using Copilot. 'I learned by writing every line.' 'You won't actually understand if AI writes it.' This pressure is real, especially in service companies and traditional product teams. Younger devs hide their AI usage. Senior devs publicly mock it while using ChatGPT in private. The collective embarrassment slows adoption by 2-3x compared to the US.

4. Tooling latency and reliability for Indian users

Most AI tools route requests through US/EU servers. From an Indian developer's machine, tab-completion latency is 400-800ms. That's slow enough to break flow. Cursor and Claude Code have improved with Asia routing, but the experience is still noticeably worse than what US developers get. We notice it daily in our own team.

What this means for hiring

If you're a founder hiring developers in 2026, the bucket they fall into matters more than their resume. A Bucket 3 developer with 3 years of experience will outproduce a Bucket 1 developer with 8 years of experience for most modern web work. But you can't tell which bucket someone is in from their resume — you have to specifically ask. Some questions that surface this:

'Walk me through your AI workflow. What did you ship last week with AI help?'
'What's the last thing you tried to do with AI and gave up on? Why?'
'Which AI tools do you personally pay for?'
'How has your debugging process changed in the last year?'

Bucket 1 candidates will fumble on the first question. Bucket 2 candidates will mention Cursor free tier and get vague. Bucket 3 candidates will give you a 5-minute precise answer about their actual workflow.

What this means for scoping a project

If your contractor or agency is Bucket 1 or 2, their actual capacity for delivery is 50-70% of what a Bucket 3 team delivers — for the same headcount. This is a real number. We've taken over 4 projects in the last year where the previous Bucket 1/2 team was 6 weeks behind on a 10-week project. Same headcount, AI-first replacement team, finished in 5 weeks (including the catch-up). Whether your contractor uses AI deeply matters more than how big their team is.

What it means for agencies (the honest cost)

Our agency made a deliberate decision in 2024 to be Bucket 3 across the board. Every team member has paid Cursor Pro, paid Claude Code Max, and we pay for Anthropic / OpenAI API access for internal tools. The monthly tooling cost per developer in 2026 is roughly ₹3,500-5,000. For an 8-person team that's ₹40,000/month, which is ~5% of the salary cost. The productivity uplift covers it 10x over.

But the bigger cost was the learning curve. Three months of slower output as people rewired their habits. One developer left because he 'didn't believe in AI coding.' Two clients noticed slower velocity in that period and we had to absorb the cost. After month 4, output was 60-90% faster than before, depending on task type.

What changes in the next 18 months (Nov 2026 forecast)

Bucket 1 will shrink to ~50%

Free tools (Copilot free tier, Cursor free tier, ChatGPT-5 free) keep getting better. Devs in Bucket 1 will accidentally drift into Bucket 2 without consciously upgrading. We expect 25% of current Bucket 1 to be in Bucket 2 by end of 2027.

Bucket 2 will mostly stay where it is

The barrier from Bucket 2 to Bucket 3 is paying $20+/month, which is structural, not learning. Most Indian companies still won't pay. So this band stays around 15-20%.

Bucket 3 will grow to ~20-25%

Driven by: agencies competing on velocity, AI-native startups normalizing tool spend, foreign clients demanding AI workflows, and falling tool prices (Anthropic and OpenAI both signaled cheaper India-region pricing tiers for 2027).

Practical advice if you're in each bucket

If you're in Bucket 1 (most developers)

Install Cursor or Cline today. Use the free tier. Force yourself to use it for one full day before judging. Most people give it 45 minutes, hit one wrong autocomplete, and quit. Push through 2-3 days of awkwardness. By day 7 your hands will type completions themselves. By month 3 you'll wonder how you worked before.

If you're in Bucket 2

Pay for ONE tool for one month. If your company won't, pay personally. ₹1,700 is one Swiggy order. For 30 days, use it as your default. You will be surprised how the unlimited usage changes your behavior. If you're not at 2 hours of daily time savings by week 3, you can cancel. Most people don't cancel.

If you're in Bucket 3

Your edge in 2026 is real but won't last. By 2028, AI-fluent will be table stakes — the way knowing Git is table stakes today. Invest in the next layer: agent orchestration, prompt-driven testing, AI-first product architecture. Stay 6-12 months ahead of the median.

The LinkedIn narrative is wrong (for now)

AI didn't replace developers in 2024 or 2025 or 2026. It made the top 10% of developers 2-5x more productive. The other 90% is mostly unchanged in 2026. That gap — the productivity delta between the AI-first 10% and the rest — is the actual story. It's what's driving consolidation in agencies, salary widening for AI-fluent developers, and the slow squeeze on Bucket 1 senior developers who thought their seniority would protect them.

If you're hiring, scoping, or building something in 2026, plan for reality, not for the LinkedIn version. Most developers you'll meet still aren't really using AI. The ones who are will tell you confidently which bucket they're in. Hire those.

How we evaluate developer AI fluency

When we hire or evaluate contractors, we run a 30-minute pair session where the candidate has to add a small feature to a real codebase with AI access. We watch how they prompt, how they validate output, how they handle wrong suggestions, how they integrate the result. Bucket 1 candidates will hesitate, copy-paste suggestions wholesale, and miss obvious refinements. Bucket 3 candidates run a fluid back-and-forth — prompt, evaluate, refine, ship. The difference is visible in the first 5 minutes.

If you're a client deciding who to hire

Ask any agency or freelancer you're considering: 'What AI tools does your team pay for?' If the answer is vague, 'we use ChatGPT,' or 'we use the free version of Cursor,' you're hiring a Bucket 1 or 2 team. That's fine for simple projects — but you'll pay 1.5-2x more in dev hours for the same output compared to a Bucket 3 team. For complex projects, the gap can be brutal.

Our team's monthly per-developer AI spend is ₹3,500-5,000. We tell every prospective client this upfront. It's not a brag — it's a price signal. If you don't see comparable transparency from someone you're hiring, they're probably running on free tools and absorbing the productivity gap into longer timelines or worse code.

Hiring a development team in 2026? We'll do a free 20-min call to talk through where AI fluency matters for your specific project — and where it doesn't. No quote pressure. → Talk to us

TL;DR for the people who skim

70-75% of Indian developers in 2026 still aren't really using AI (just occasional ChatGPT)
15% use free Cursor / Copilot tiers casually
10% are AI-first (paid tools, AI-default workflow, 3-5 hours/day of real productivity gain)
LinkedIn pretends Bucket 3 is the average. It isn't. It's the 10%.
Bucket 3 developers outproduce Bucket 1 by 2-5x for the same headcount
Hiring question that surfaces this: 'Walk me through your AI workflow — what did you ship last week with AI help?'
Paid AI tools cost ₹1,700-5,000 per dev/month. Cheap compared to salary. Most Indian companies still don't pay — that's the structural blocker, not learning curve.
By end of 2027 we expect Bucket 1 to shrink to ~50%, Bucket 3 to grow to ~25%. The squeeze is on Bucket 1 seniors.
If you're in Bucket 1: try Cursor free for 7 days, push through the awkward first 3 days
If you're hiring: ask what AI tools the team PAYS for. Vague answer = expect 1.5-2x dev hours for same output.

The Indian Founder's Field Manual: 47 Things Nobody Will Tell You About Building an Internet Business Here

Ravi Rai — Tue, 12 May 2026 03:25:47 +0000

Five years. Six near-quits. Three live products. 80+ clients across India, Canada, UK, UAE, US. A team that hasn't broken on me. A bank account that doesn't have anxiety attached to it anymore. This is the document I wish someone had emailed me in October 2021, when I sat in a borrowed laptop in Lucknow and typed 'buildbyRaviRai' into a Google Doc for the first time. 47 things, no fluff. Save it.

Every 'overnight success' you've read about on LinkedIn took 4-6 years. Every founder you respect was broke for at least two of those. The most useful thing I can give you is the things they don't write about — the practical, unsexy, India-specific stuff that actually decides whether you make it or not.

Money & pricing (1–8)

Your first year revenue will be embarrassingly small. Mine was ₹2.4L. Every agency I respect had a similar first year. The ones who post 'crossed ₹1cr in year 1' on LinkedIn are 1% of the field, exaggerating, or had family capital. Stay alive. The compound starts in year 2-3.
Charge for what you'd be embarrassed NOT to deliver against. Pricing fear is the slow killer. Undercharge → burnout. Overcharge → resentment. Aim for the price where you'd want to over-deliver if a client paid it.
Always quote in INR for Indian clients. Quoting in USD with a 'today's rate' feels professional but makes the conversation about forex instead of about your work. Indians who buy in USD assume they're being overcharged.
Stop charging hourly past month 6. Hourly billing punishes you for getting faster. Move to flat-fee or milestone-based the moment you can defend an estimate.
Build a 3-month buffer of fixed costs (salaries, rent, software, taxes) in a separate untouchable account. Until you have it, every cash flow gap feels existential. After you have it, none of them do.
Pay yourself a salary, even a small one. Founders who 'take from the business when needed' lose track of personal vs business finances within 18 months and create chaos at tax time. ₹15,000/month is fine. Just make it consistent.
GST registration is mandatory at ₹20L turnover (₹40L for goods). Register at ₹15L. The 5L cushion lets you scale without surprises, and GST-registered businesses look more legitimate to B2B clients.
Keep a separate Razorpay/Stripe account for personal vs business. Mixing them is the single most common reason small agencies get tax notices. Take the 30 minutes to set this up correctly on day one.

Clients (9–16)

The clients you say no to matter more than the ones you say yes to. Letting 3 dreaded clients go in year 3 dropped my revenue 30% — and was the best decision I made that year. The energy you save replaces them within 60 days, with better clients.
A client who haggles before signing will haggle on every invoice. The way someone behaves during sales is the floor of how they'll behave during delivery, not the ceiling.
Always send written scope before starting work. Even for ₹15,000 jobs. Even for friends. Even for referrals. The scope document is what saves the relationship when scope creeps (it always does).
Take 50% upfront. Non-negotiable. The clients who 'can't pay upfront' are the same clients who'll find reasons not to pay at the end. If a client objects to 50% upfront, they're telling you they don't have the budget — not that you're being unreasonable.
Invoice on the 1st of every month for retainers. Predictable cash flow is worth more than 'flexibility for the client.' Most Indian B2B businesses run monthly billing cycles anyway.
Send follow-ups for unpaid invoices on day 7, 14, 21, then once a week after. Most late-payers aren't dishonest — they're disorganized. The 7-day cadence creates accountability without confrontation.
When a client ghosts, send one final clear message: 'Hi [name], I haven't heard from you in [X days]. I need either an update by [date] or a clean handover. After [date] I'll move forward without you.' Then stop chasing. The chase is what makes them ghost permanently.
Indian clients pay 7-21 days late on average. International clients pay 0-7 days late. Price this into your cash flow planning, not into your trust assessment of Indian clients.

Hiring & team (17–22)

Hire your first person earlier than you'd plan. I waited until year 3. Should have been year 2. The 14 months of delta cost me more than the salary would have.
Pay senior salaries from day one if you want senior people. Indian agency talent is undervalued by 30-50% on average. A senior dev who'd cost ₹2L/month at a corporate will work with you for ₹1L if you offer them ownership of outcomes — but DON'T pay them ₹40K and expect senior work.
Hire for trajectory, not credentials. The best devs I've hired had no degree from a famous college. The worst hires looked perfect on paper.
Equity for early team members is fine, but not as the primary compensation. Indian context: equity in a small private company is illiquid for 7+ years. Cash + small equity beats large equity + small cash for hiring junior-to-mid talent.
When a team member leaves, don't take it personally. The best devs will eventually get offers you can't match. Hold them with an open hand. The ones who leave well often refer you new clients for years.
Don't hire to win arguments with yourself about 'looking professional.' Hire to handle work you can no longer do alone. If you're not actively turning away work, don't hire yet.

What you build (23–28)

Build for production, not for impressing other developers. The Indian client doesn't care about your stack — they care that the site works on a 4G connection in a Hyderabad office with patchy WiFi.
Pick your stack and stick with it for 2 years minimum. Jumping from Next.js to Astro to Remix every six months means you're an expert at nothing.
Your first product idea will not be your last product idea. PlugEV, CloudNX, ToolKiya — none of these existed in our year-one plan. Stay flexible about what you build, rigid about who you serve.
Build internal tools before client tools. The hours you save with a small internal dashboard for invoicing, time tracking, and project status compound to weeks per year.
Don't build features that 'might be useful someday.' Build features that one paying client has asked for in the last 30 days. Everything else is a hobby.
Document as you build, not after. Two-line comments + a README per module. The version of you in 18 months will not remember why you made that decision.

Marketing & getting clients (29–35)

The boring channels work; the trendy ones don't. SEO + word-of-mouth bring 80% of our clients. Instagram reels bring 0%. Pick the boring channels.
Write one blog post a week for two years before judging whether content marketing works. None of my year-one posts got more than 14 visits each. By year four, the cumulative archive was driving 60% of inbound.
Internal links in your blog matter more than backlinks for the first 100 posts. Build a topical cluster on one subject before chasing breadth.
Replying to comments on LinkedIn outperforms posting on LinkedIn. The algorithm rewards conversation density. 1 hour of replies > 1 hour of writing a new post.
Your portfolio page should link to LIVE URLs, not screenshots. Indian clients don't trust portfolios anymore — too many people steal images. A clickable, working URL beats a polished case study.
Word-of-mouth referrals close 5x faster than cold leads and pay 25% more. Treat existing clients as your top marketing investment. A quarterly check-in WhatsApp message to past clients is the highest-ROI marketing activity you can do.
Stop trying to get featured in 'top freelancer of India' lists. Most are pay-to-play. The ones that aren't won't move your revenue. Focus on the 3 platforms that send you actual paying clients.

Operations & boring stuff (36–40)

Use one calendar tool, one project tool, one accounting tool. Don't switch every quarter. Tool fatigue is real — pick decent options and live with their flaws.
Run a 30-minute Monday call with the team, every week, even when it feels unnecessary. The week you skip it is the week three things go wrong because nobody synced.
Backup everything. Code → GitHub. Designs → Figma + Drive. Client documents → encrypted cloud. We've recovered work 4 times because of disciplined backups. The cost of one recovery situation justifies five years of backup discipline.
File GST returns yourself for the first year, even if you have a CA. You need to know what you're paying for and why. Hire the CA in year 2 to save time, not to avoid learning.
Keep a 'lessons learned' note per closed project. Three lines: what worked, what didn't, one thing I'd do differently. Six months later, this is the most useful document in your business.

Mental & personal (41–44)

Most catastrophes are not actually catastrophes. The story your tired brain tells you at 2 AM is almost never the actual story at 8 AM. Sit down, write down what you actually need by when, and what your three options are. The act of writing it down moves it from swirling fog to a manageable problem.
Tell one other person when things are hard. Not as a complaint — as a fact. The shame multiplies in silence and dissolves the moment it's out loud.
Your spouse / partner / parent shouldn't be your only sounding board. Find one other founder you can be honest with. The mental load is too heavy for one relationship to carry alone.
Take Sunday off. I know you won't, but try. Burnout doesn't announce itself — it arrives as 'I just can't think today' six weeks after you stopped resting. The math: 52 Sundays of work per year buys you about 18 months of working before burnout. 52 Sundays off buys you 30+ years.

India-specific quirks (45–47)

Indian B2B sales takes 3-5 follow-ups before a meeting, 4-6 weeks from interest to contract, and 60+ days from contract to first payment. International B2B is 1-2 weeks total. Adjust your cash flow planning to the Indian rhythm — most agencies fail because they planned for US-speed and got Indian-speed.
The 'Indian discount' is real and you should refuse it gracefully. 'Bhai, family rate kar do' is the polite Indian way of asking for a 40% discount on a service that already runs on margins. Your response: 'Bhai, family rate hi hai. Yahi mera best price hai.' Half of them stay anyway. The other half were never going to pay your real rate.
Build for Indian payment methods, even if your target audience is international. UPI is the single most underrated payment rail in the world. Your Indian friends, family, and small clients will pay you faster via UPI than any other method. Have a Razorpay link in your email signature.

The meta-lesson

If I could distill all 47 of these into one sentence, it would be this: building a business in India is a long, mostly boring game where the people who win are the ones who stay alive long enough to compound. The dramatic stories you read on LinkedIn — the ₹0 to ₹1cr year, the viral launch, the seed round — those are the 5% of the journey. The other 95% is showing up on a Tuesday in March when you don't feel like it, doing decent work for a fair price, and treating the people in your life with grace.

You don't need to be the most talented founder in your category to win. You need to be the one who didn't quit. The smartest, most charismatic, most well-connected founders I knew in 2021 are mostly not running businesses anymore. The ones who are still here in 2026 are mostly people who would have looked unimpressive in a pitch room — but who showed up every day and got slightly better.

Save this document. Send it to one other founder who's having a rough month. Come back to it when you're confused about which problem to solve first. The 47 things are not theoretical — every single one of them cost me money, sleep, or a relationship to learn. I'd much rather you learn them from this post than from your own ₹10 lakh year of mistakes.

If you want to talk

I'm at support@buildbyravirai.com and +91 74289 19927 on WhatsApp. If you're scoping a project, hiring a team, considering quitting your job to do this — I'd rather you message me before than after. There's no consulting fee. No sales call template. Just an honest conversation between people doing the same hard thing.

Building something? Stuck on one of the 47 above? We do honest 20-minute calls — no quote pressure, no sales pitch. Just a real conversation about where you're at and what might help. → Get on a call

If this helped

Share it with one founder you know. Bookmark it. Send it to your past self via journal entry. Most of these 47 things are 'obvious' in hindsight but cost a year of frustration to learn the first time. The single best thing we can do for each other in this small, weird community of Indian founders is to short-circuit the lesson cycle for the people coming up behind us. Pass it on.

To the Founder Whose Developer Just Disappeared

Ravi Rai — Sun, 10 May 2026 05:45:49 +0000

It's been four days. Maybe ten. Maybe a month. Your developer hasn't replied to your last six WhatsApp messages. The two blue ticks are gone — they've stopped opening them. The website is 60% done. You paid 50% upfront. You don't have the code. You don't have logins. You don't even know what hosting it sits on. You're sitting at your desk, trying to figure out how to explain this to your business partner, your spouse, your investor — and you can't, because you don't even fully understand what happened. If that's where you are right now, this is for me to you.

If you've been ghosted by a developer, the worst part is not the money or the website. It's the shame of having trusted the wrong person. I want you to know that almost every founder I respect has been here at least once. You're not stupid. You got hurt by someone who hurt other people too.

First: this is more common than you think

In the last two years, my team has rescued 14 abandoned web projects. Eight were Shopify stores half-migrated to a custom theme. Three were Laravel admin panels stuck mid-build. Two were Next.js sites where the developer disappeared with the GitHub access. One was a mobile app that was supposedly 'almost done' for nine months. The clients had paid anywhere between ₹40,000 and ₹6 lakh upfront. None of them got refunds.

Every single one of them said the same thing in the first call: 'I feel so stupid. I should have known.' I want to tell you what I told them. You did not do anything wrong. The developer did. They lied about their capacity, took the deposit, took on too much work, and then chose silence over a hard conversation. That is on them, not on you. The shame is misplaced. Set it down before it eats another month of your life.

What's actually salvageable (almost always more than you think)

Founders in this situation usually assume everything is lost. In our experience, that is almost never true. Here's what we've recovered for the 14 founders we've helped — without any cooperation from the original developer:

The domain — if you bought it on GoDaddy / Namecheap / Hostinger / Google Domains under your own account, you already own it. Even if you don't remember, password resets work.
The live website code — if it's deployed somewhere, we can usually get it back. Static sites can be cloned. WordPress sites can be exported from the live server with hosting access. Shopify themes are downloadable.
Your customer / order data — if it's a Shopify store, the data is in your Shopify admin (which is yours). If it's a custom site, we recover what's in the database via hosting access.
Designs and assets — Figma, Canva, and Google Drive files have version history. Even if the developer 'deleted' them, they can usually be recovered for 30+ days.
Hosting and DNS — if it was set up on your own credit card, you have access. If it was set up under the developer's account, we transfer to your account using the proof of payment.

What's hard to recover: the source code if the site was never deployed, or if it was only on the developer's local machine. Database backups if the developer hosted everything on their own server and didn't give you SFTP access. In these cases, we usually rebuild the missing pieces from scratch — and it's usually less expensive than you fear, because we're not building a brand new site, just the gap.

What to do tonight, in this order

Stop sending messages. The chase makes them more likely to ghost permanently — and it makes you feel worse with every unread message. One last clear, calm message: 'Hi [name], I haven't heard from you in [X days]. I need either an update by [date] or a clean handover of all access and code. I'm willing to pay for any genuine work delivered. After [date] I'll move forward without you.' Then stop.
List everything you DO have. Domain registrar login. Hosting login. GitHub access. WhatsApp screenshots of what was promised. Bank transfer records. Designs in Google Drive. Even if it feels like nothing, write it down. Most founders find they have more than they thought.
Change your domain registrar password and email. If they ever had access to your registrar account (some founders share this), assume they still do. New password, new recovery email, two-factor on.
Don't make threats you can't follow through on. 'I'll take legal action' rarely works against a freelancer with no assets. It just confirms to them that they should ghost harder. The leverage you actually have is your willingness to publicly review them — but use it carefully and only after you've recovered what you can.
Get a second opinion on the work that exists. Send what you have to one or two trustworthy developers. Ask: how much of this is salvageable? How much is the cost to finish? The number is almost always lower than 'start over.'

How we ended up rescuing 14 of these

We didn't set out to be a 'rescue' agency. It happened because once a few of these founders worked with us, they told other founders, and now we get one of these calls roughly every two months. Most of them come in apologetic, half-expecting us to either lecture them or ghost them too. We don't do either. Here's what the conversation looks like with us:

We do a free 30-minute audit. You send us whatever you have — links, logins, screenshots, even just 'here's the domain, I don't know what else exists.' We go look.
We send you back a written report: what exists, what's salvageable, what needs rebuilding, and a flat INR price to finish. No hourly billing. No surprises. If we can't help, we tell you that too — and we point you to someone who might.
We never take an upfront payment from a rescue client. You've already been burned once. We invoice in milestones tied to delivered features. You can stop at any point and you keep everything we've built up to that point.

The thing nobody tells you about being burned

Once you've been ghosted by one developer, every single new developer you talk to feels suspicious. You ask for references. You ask for portfolios. You ask for written contracts. You hesitate to pay. This is rational and you should keep doing it. But I want to give you one more frame: the developer who ghosted you was not representative of the field. They were the bottom 5%. The other 95% of working developers in India are people who deeply care about not becoming that person, because we have all watched it happen to other clients and it makes us furious.

The way I learned the word 'reputation' wasn't from a marketing book. It was from watching a friend's father, who ran a small construction business in Kanpur for 30 years, get a job because someone said 'sharma uncle ne hamare ghar bana diya, dhokha nahi diya, time pe diya.' That was his entire marketing. That is also our entire marketing. Almost every client we have today was sent by another client who could have left them dry but didn't.

If you came to us tonight

I would tell you the same thing I tell every founder in this position: take a deep breath, send us the access details and screenshots tomorrow morning, and let us look at it. We'll send you a 1-page report within 48 hours, no charge, no obligation. If you decide to work with us, you don't pay anything until we've delivered the first milestone. If you decide we're not the right fit, you walk away with the report and use it to brief whoever you hire next. Either way, in a week, you'll know more than you know tonight, and the swirling 'what now' panic will become a manageable list of next steps.

What I want you to remember

One. The shame is doing more damage than the actual project loss. Talk to one trusted person about what happened. The shame multiplies in silence and dissolves the moment it's out loud.

Two. Almost everything is recoverable. People in this exact situation — same project type, same loss amount, same disappearing developer — are running healthy businesses today. The setback is real but it's not terminal.

Three. Trusting again is hard but worth it. The cost of never trusting another developer is that you stop building, and that hurts you more than the original loss. Build the trust slowly with the next person — small project first, milestone payments, written scope. But build it.

If you read this far, send me an email at support@buildbyravirai.com or message me on WhatsApp at +91 74289 19927. Even if you don't end up working with us — I'd like to hear what happened. The number of founders quietly carrying this story is way larger than people realize, and the more of us who tell each other, the less power the story has.

Half-built website? Disappeared developer? We'll do a free 1-page audit, no obligation. Send us what you have and we'll tell you what's salvageable. → Get a free rescue audit

Web Hosting in India 2026: Shared, VPS, Cloud, Managed, Dedicated, Serverless — The Complete Guide

Ravi Rai — Sun, 10 May 2026 05:44:49 +0000

Every week, an Indian founder messages me a screenshot of their hosting bill and asks 'is this right?' Sometimes the answer is 'you're paying ₹15,000/month for a site that should cost ₹400.' Sometimes it's 'you're on ₹89/month shared hosting and wondering why it crashed during your launch.' Most founders pick wrong on the first try because nobody actually explains the choices in plain language. This is that explanation.

Web hosting is the part of building a business online that founders feel most ashamed to ask about. There's no shame. The reason it's confusing is that it IS confusing — there are 6 categories, the names overlap, the pricing varies by 100x, and most providers pitch you whatever they want to sell, not what you need.

What is web hosting, in one paragraph

Your website is a folder of files (HTML, images, code, database). For a visitor's browser to open your site, those files need to live on a computer that's always connected to the internet, ready to respond. That computer is called a server. Web hosting is the service of renting space on someone else's server (because running your own is impractical for 99% of businesses). The 6 types of hosting are 6 different ways of renting that space — each is a tradeoff between cost, control, performance, and how much you have to manage yourself.

The 6 types of web hosting

1. Shared hosting

You share one server with hundreds (sometimes thousands) of other websites. The cheapest option, the easiest to set up, the most likely to slow down or crash when your traffic spikes. Best for static informational sites, very small WordPress sites, and people who genuinely have less than 5,000 visitors a month.

INR price (2026): ₹89–₹500/month, often with steep first-year discounts that triple at renewal
Best providers in India: Hostinger, GoDaddy, BigRock, MilesWeb
What you get: cPanel, 1-click WordPress install, free SSL, 1-2 GB RAM shared with others, limited CPU
When to pick: brand-new business site under 5K visits/month, blog with no e-commerce, portfolio site
Avoid if: you have any payment flow, any user logins, any email-sending requirement at scale, or any hope of ranking in Google for competitive keywords (slow shared hosting tanks Core Web Vitals)

2. VPS (Virtual Private Server)

One physical server is sliced into multiple virtual servers. You get guaranteed CPU and RAM (not shared with neighbors). More expensive but vastly more reliable. You usually have to know basic Linux to manage it (or pay for a 'managed' VPS where the provider handles updates).

INR price (2026): ₹500–₹4,000/month for unmanaged; ₹1,500–₹8,000/month for managed
Best providers: DigitalOcean, Linode, Hetzner, Vultr (international); CloudNX, E2E Networks (India)
What you get: full root access, your own RAM/CPU, IP, can run any software, custom configs
When to pick: WordPress sites with 10K-200K monthly visitors, custom Laravel/Node.js apps, e-commerce stores up to ~₹50L/month revenue
Avoid if: you don't have a developer or a managed plan — an unmanaged VPS without security patches becomes a hacker's playground in weeks

3. Cloud hosting

Your site runs across a network of servers (not one). If one server fails, traffic auto-shifts to another. You pay for what you use — pay-per-second on AWS/GCP, monthly tiers on managed cloud platforms. Most flexible scaling, most modern architecture, most likely to surprise you with bills if you don't watch.

INR price (2026): ₹2,000–₹50,000+/month depending on traffic and architecture
Best providers: AWS, GCP, Azure (raw cloud); Vercel, Netlify, Render (Jamstack); CloudNX (managed Indian cloud)
What you get: auto-scaling, redundancy, edge caching, CDN, global presence
When to pick: anything that needs to scale unpredictably (viral landing page, event ticketing, sale flash crash protection), modern Next.js/React apps, SaaS products, any traffic >200K/month
Avoid if: you don't understand the pricing model — a misconfigured Lambda or unbounded query can produce a ₹2L bill in 24 hours

4. Managed hosting (WordPress, Shopify, etc.)

Specialized hosting for one specific platform. The provider handles updates, backups, security, caching — you just write content. Costs more than VPS but for non-technical teams it pays for itself in not having to debug WordPress at midnight.

INR price (2026): ₹1,500–₹10,000/month for WordPress; Shopify is its own platform at ₹1,994/mo (Basic) and up
Best WordPress managed: WP Engine, Kinsta, Cloudways, Pressable, RocketWP. CloudNX in India offers managed WordPress at ₹1,499/mo with India POPs.
Best for Next.js managed: Vercel (made by Next.js team), Netlify, Render
When to pick: any WordPress site that earns ₹1L+/month and can't afford downtime, any Shopify store, any non-technical founder team
Avoid if: you have a developer who already manages your VPS — you'd be paying twice

5. Dedicated server hosting

An entire physical server is yours. No one else's traffic, no one else's neighbors. The most powerful but also the least flexible — you pay for the whole machine even when traffic is low. Most modern apps don't need this anymore; cloud has replaced it for 95% of use cases.

INR price (2026): ₹6,000–₹50,000+/month for managed dedicated; ₹4,000–₹20,000/month unmanaged
Best providers: Hetzner, OVH, ServerMania (international); E2E Networks, ESDS (India)
What you get: maximum CPU/RAM, full hardware control, predictable performance, full root
When to pick: regulated workloads (banking, healthcare with on-prem requirements), heavy compute (video transcoding, large databases), or genuinely high-traffic single sites (~5M+ visits/month)
Avoid if: you're using less than 50% of CPU regularly — cloud is more economical at lower utilization

6. Serverless hosting

There is no server you manage. You upload code, the platform runs it on demand, you pay only when someone actually calls it. Brilliant for spiky traffic, terrible for steady high traffic (the per-request pricing adds up). The newest paradigm and the one most modern web apps are moving toward.

INR price (2026): ₹0 free tier covers many small apps; ₹500–₹50,000/month for production scale (highly variable)
Best providers: Vercel, Cloudflare Workers, AWS Lambda, Netlify Functions, Deno Deploy
What you get: zero server management, automatic scaling from 0 to millions, pay-per-request, global edge deployment
When to pick: APIs with bursty traffic, marketing sites, AI agent backends, webhook receivers, anything that idles 95% of the time and spikes 5%
Avoid if: you have a steady high-traffic workload — at the spike level, traditional cloud is 5-10x cheaper

The decision tree we use with clients

When a client asks 'what hosting should I use,' here is the actual flowchart in our heads:

Brand new site, under 5K monthly visits, mostly content → shared hosting (Hostinger or CloudNX shared, ₹89-300/mo)
WordPress with 5K-50K visits, you can't manage servers → managed WordPress (CloudNX, Cloudways, Hostinger Cloud, ₹1,500-3,500/mo)
Next.js / React app, any size → Vercel (free tier covers most early-stage apps; ₹1,500-15,000/mo at scale)
Custom Laravel / Node.js app, 10K-100K visits → managed VPS or CloudNX (₹2,000-6,000/mo)
E-commerce, simple product catalog, no developer → Shopify (₹1,994/mo + transaction fees)
E-commerce, custom product config, you have dev → headless Next.js + Shopify Storefront API on Vercel (₹3,000-10,000/mo)
SaaS app with database, multi-tenant, growing → cloud (AWS/GCP) with proper observability (₹5,000-50,000/mo)
API-only / webhook-only / spiky → serverless (Vercel Functions, Cloudflare Workers, free tier often enough)
Banking / healthcare / on-prem regulatory → dedicated server in Indian data center (₹6,000-50,000/mo)

The 5 mistakes we see clients make every month

Mistake 1: picking shared hosting for an e-commerce store

Shared hosting routinely throttles CPU when other tenants get busy. During your Diwali sale, when checkout matters most, your shared host is the slowest version of itself. We've migrated 30+ stores off shared hosting after lost-sales incidents. Spend the extra ₹2,000/month on managed VPS or Shopify from day one — the math works out within 3 months.

Mistake 2: locking into 3-year prepaid plans for the discount

Hosting providers love these plans because the renewal price is 2-3x the prepaid price, and you'll renew because migration sounds painful. The 'discount' is real for year 1 but you're paying premium for years 2 and 3. Pay monthly or annually. Migrate when needed. Modern hosting moves are 1-2 day operations, not weeks.

Mistake 3: hosting in the wrong region

We've seen Indian businesses hosted in US-East with all-Indian customers. Every page load makes a 250ms round trip across the Pacific. Your competitor in Mumbai with India-region hosting feels 4x faster. Always pick the region closest to your visitors: AWS Mumbai (ap-south-1), GCP Delhi (asia-south2), Vercel SIN1/BOM1, or any India-based provider.

Mistake 4: confusing hosting with the website itself

Your hosting plan is the rented apartment. Your website is the furniture. Hosting issues mostly fix performance and reliability. Hosting upgrades will not fix a slow WordPress with 47 plugins, an unoptimized image-heavy homepage, or a checkout flow that takes 3 round-trips to your server. We see clients upgrade hosting hoping it'll fix slow sites — sometimes it does, often it doesn't, because the bottleneck was the code.

Mistake 5: paying for capacity you don't need

Your sales rep at the hosting company is incentivized to sell you the biggest plan. We have a client who was on a ₹15,000/month dedicated server with 32GB RAM running a WordPress site that did 8K visits/month. Same site now runs on ₹3,000/month managed cloud, faster than before, with 14% of the previous bill. Right-sizing matters more than size. If you can, ask a developer (not a sales rep) what tier you actually need.

India-specific concerns

Latency: pick India-based servers for India-based audiences

ap-south-1 (AWS Mumbai), asia-south2 (GCP Delhi), or India-based hosts like CloudNX and E2E Networks deliver 5-10x faster TTFB to Indian users than US/EU regions. Google's mobile ranking factors include TTFB. Hosting region is one of the highest-ROI changes you can make for Indian SEO.

Payment & invoicing in INR

International providers (AWS, Vercel, Cloudflare) bill in USD. Forex variance hits you 2-5% per month. India-based providers bill in INR with proper GST invoices — important for B2B claims and easier accounting. CloudNX, Hostinger India, and E2E all offer INR billing with GST. AWS allows INR billing through AWS India Pvt Ltd.

Support hours that match yours

If your audience is Indian and your team is Indian, hosting providers with Indian support windows (9 AM-9 PM IST) save you 8 hours of recovery time during incidents. International providers' support is often US-based and 12 hours offset. The cost of a 12-hour outage during an Indian business day is enormous.

DPDP Act and data residency

If you handle Indian user PII (most Indian businesses do), the DPDP Act 2023 requires you to know where the data is stored. Indian-region hosting makes compliance straightforward. International hosting requires explicit consent flows and Standard Contractual Clauses. We strongly recommend India-region hosting for any Indian B2C business that stores user data.

What we use ourselves

Across our agency and our 3 products (PlugEV, CloudNX, ToolKiya), here's the actual breakdown of what we host where in 2026:

buildbyravirai.com (this site) — Vercel (free tier, edge-deployed, India POP)
PlugEV CSMS — DigitalOcean Mumbai droplets (₹3,500/mo) for the Go gateway, Laravel admin on a VPS
CloudNX — our own infrastructure (we eat our own dogfood)
ToolKiya — Vercel (Next.js) + Supabase (Postgres + Auth)
Client WordPress sites — CloudNX managed WordPress for 80% of clients, Cloudways for the rest
Client e-commerce — Shopify for ~70%, headless Next.js + Shopify Storefront API for ~30%
Client custom Laravel — DigitalOcean Mumbai or CloudNX VPS

Frequently asked questions

How much should hosting cost for a small business website in India?

₹200-₹2,000 per month is the realistic range for a small business website with under 50K monthly visits. Below ₹200/month you're getting shared hosting with quality issues; above ₹2,000/month you're either paying for managed services (worth it if non-technical) or paying for capacity you don't need.

Is Hostinger / GoDaddy / Bluehost good?

For shared hosting tier, Hostinger is the strongest of the three in 2026 — better UI, better performance, better India POPs. GoDaddy's renewal pricing is famously aggressive. Bluehost's Indian product has improved but their support quality is inconsistent. None of them should be your choice past 50K monthly visits — that's the upgrade-to-managed-VPS threshold.

Why is Vercel so expensive at scale?

Vercel charges per-request and per-bandwidth. For static sites and APIs that idle, it's free or nearly so. For high-traffic sites (1M+ visits/mo) the bill can hit ₹50K+/mo. The economics flip vs. running your own VPS at that scale. The right answer for very-high-traffic sites is often: use Vercel for the marketing site, use AWS/cloud for the high-volume APIs.

Can I switch hosting later?

Yes, almost always. Static sites and Next.js apps move in hours. WordPress moves in 1-2 days with a good migration script. Custom Laravel/Node apps take 2-5 days depending on database size. The only thing that doesn't move easily is platform-locked data (Shopify orders are tied to Shopify; you can export but rebuilding the storefront is significant work). Always pick the simplest option that works today; you can upgrade.

What about free hosting (GitHub Pages, Cloudflare Pages, Netlify free)?

Free tiers are real and useful — for static sites, portfolios, documentation, and even small SaaS landing pages. We host buildbyravirai.com on Vercel's free tier and serve real production traffic. The catch: free tiers cap features (build minutes, bandwidth, function calls). Read the limits before you launch. For a static business site under 100GB/mo bandwidth, free tier is genuinely fine.

How we help with hosting

We do hosting audits as a paid 90-minute call (₹3,500). You send us your current setup; we tell you whether you're overpaying, underpaying, or exposed to specific risks (security, performance, compliance). The audit pays for itself in the first month for almost every client we've done it for — usually because we identify a 30-50% overspend or a critical missing piece (no backups, no SSL, public database port, etc.).

If you're starting a new project, we include hosting setup as part of every web/app build. We don't markup hosting costs — you pay the provider directly, we just configure it for you. Most clients we set up on managed VPS or Vercel and they're happy 2 years later.

Confused about which hosting to pick? We do a paid 90-min hosting audit (₹3,500) — actionable report on what to keep, what to change, and exact monthly savings. Or talk to us about hosting as part of a new build. → Get a hosting audit

TL;DR

Brand-new content site, under 5K visits → shared hosting (₹100-300/mo)
WordPress that earns money → managed WordPress (₹1,500-4,000/mo)
Next.js / React app → Vercel (free or ₹1,500-15,000/mo)
Custom Laravel / Node.js → managed VPS in Mumbai region (₹2,000-6,000/mo)
E-commerce, no dev → Shopify
E-commerce, with dev, custom needs → headless Next.js + Shopify
SaaS at scale → AWS/GCP cloud with proper observability
Spiky API traffic → serverless (Vercel Functions, Cloudflare Workers)
Banking/healthcare with regulatory needs → dedicated India servers
Always pick India region for Indian audiences — DPDP compliance + 5-10x faster TTFB

What I'd Tell Myself in 2021: 7 Things I Wish I Knew Before Starting an Agency in India

Ravi Rai — Sun, 10 May 2026 05:44:32 +0000

It's May 2026. I just signed off on a project that, five years ago, I would have told you I wasn't capable of taking on. The team is happy. The bank account doesn't have anxiety attached to it anymore. The version of me typing this is the same person who, in October 2021, sat in a borrowed laptop at home in Lucknow and wrote 'buildbyRaviRai' in a Google Doc as a name for something that didn't exist yet. If you're sitting where that version of me sat, this letter is for you.

Most of what I know came from the worst years, not the best ones. The 'big break' moments people post about on LinkedIn are real, but they're 5% of the story. The other 95% is the years where you're just showing up, getting better, and trusting that the compound is happening even when the bank account doesn't show it yet.

1. The first year is supposed to feel like nothing is working

In year one I made ₹2.4 lakh total. That's it. Less than what most software jobs in Bangalore pay in 3 months. Every Indian founder podcast I listened to back then made me feel like I was the only person whose first year was that small. Now, with 5 years of perspective, I can tell you: every single agency I respect today had a brutal first year. The ones who post 'crossed ₹1cr in year 1' on LinkedIn are 1% of the field, are usually exaggerating, or had ₹40L of family capital. Your year one is supposed to be small. Stay alive. Get better. The compound starts in year 2-3.

2. Pricing is not the problem you think it is

I spent year one undercharging because I was scared. ₹15,000 for a website that took me 80 hours. Then I read every 'price your services' guide on the internet and tried to charge ₹2L for the same work. Half my prospects ghosted. The actual answer, which took me three years to learn: price what you'd be embarrassed to NOT deliver against. If you charge ₹50,000, deliver ₹70,000 of value. The clients you keep are the ones who feel they got a deal even though you didn't undercharge. The clients who feel they overpaid never come back.

3. The clients you say no to matter more than the ones you say yes to

In year one I said yes to everything. By year three I had three clients I dreaded opening WhatsApp messages from. They paid late, scope-crept constantly, and made my Sundays heavy. Letting all three go in the same month dropped my revenue 30% and was the best thing I did that year. Within 60 days I had replaced them with three better clients I genuinely liked. The energy you save not dreading bad clients goes back into making your work and your team better.

4. Hiring your first person is harder than you think and worth doing earlier than you'd plan

I hired my first developer in year three. He stayed 14 months and then left for a bigger company, and I cried in my office for an hour because I had taken his leaving personally. He hadn't quit me — he'd taken a once-in-a-career opportunity. The mistake wasn't hiring him; it was waiting until I 'could afford it.' I should have hired in year two, taken less salary myself for six months, and started learning to be a person someone else works with. That delta — 14 months sooner — would have been worth a lot. If you have someone you trust, can pay them basic salary, and have enough work to keep them busy, hire now. You'll never feel ready.

5. You are going to need a buffer rule, and protecting it is non-negotiable

Three months of all fixed costs (salaries, rent, software, taxes) in a separate account I do not touch. It took me 18 months to build that buffer. Once it existed, the 'oh god, can I make payroll this month' feeling stopped happening. Cash flow problems still came — but they stopped being existential. The buffer is what lets you keep the team during a bad quarter, say no to a bad client, and sleep through nights you would otherwise lie awake. Build it before you upgrade your phone, your office, or your laptop.

6. The boring work compounds; the impressive work doesn't

In 2022 I wrote one blog post per month for the website. Most of them got 14 visits in their first six months. By 2025, the cumulative blog traffic was generating 60% of our inbound leads. None of those individual posts felt important when I wrote them. They were boring, they took 4-6 hours each, and I'd often skip the gym to write them. The same is true for case studies, recorded testimonials, decent invoicing, polite client emails, version-controlled code, basic SEO, and replying to comments on LinkedIn. None of those felt like 'real work' compared to landing a big client. All of them are why we still exist in 2026.

7. You will lose people, and that is part of it

Three people I considered close mentors in year one don't really speak to me anymore. Not because of any conflict — we just grew in different directions. Two clients I would have considered friends after a year of working together no longer exist in my circle. One developer who I thought I'd build the rest of the company with now runs a competitor agency in Pune. Building something means choosing direction, and direction means some people you started with won't be there at the end. This used to make me sad. Now it makes me grateful for the years they were there. Hold them with an open hand. Most relationships have a season, not a lifetime, and that's okay.

What I want you to know if you're starting now

Building anything in India in 2026 is hard but it is one of the best times to do it. The talent pool is deeper than it has ever been. AI tools have made the gap between solo founder and small studio shrink to almost nothing. Indian clients are starting to understand that good work costs money. Indian banking and payment infrastructure is genuinely world-class. None of that means it'll feel easy on a Tuesday in March when a client ghosts on a payment.

Three things to hold onto on the days when nothing is working:

Most of the people you compare yourself to on LinkedIn are 30% bigger than you and 90% more anxious. Stop the comparison. The only honest comparison is between you-this-month and you-last-year.
Tiny progress every day works. ₹1,000 more in revenue this month than last. One new piece of writing. One refactor. One conversation. The compound is invisible until it isn't.
Your job, on the worst days, is just to not quit. That's it. Not to win. Not to grow. Just stay. The momentum will come back. It always does. I have lived through five 2 AM 'I should shut this down' nights and I have never once been right about that thought the next morning.

What I'm proudest of after 5 years

It is not the revenue. It is not the projects we shipped. It is not the products we built or the cities we now have clients in. It is the fact that the small group of people who joined me in 2022, 2023, 2024 are mostly still here. They've grown. They've gotten paid more every year. They have lives and families that are doing okay because of work they do at this small Indian agency. That is the part I would tell my 2021 self the most clearly: the meaning is in the people, not the numbers.

If you're starting something now and you're scared — that's correct. You should be scared. The scale of what you're attempting is real. But you can do the next 30 days. And then the next 30 days after that. I'm five years in. I still don't know what's coming next year. None of us do. We just keep showing up.

If this resonated

Save it. Send it to one other founder who's having a rough week. Not as a motivation post — those make people feel worse — but as a reminder that someone else, in a quiet office in Sector 62 Noida, has been exactly where they are and is on the other side of it. That solidarity is one of the most useful things we can give each other.

If you're scoping a project, hiring a team, or just want to talk to someone who's been at this for a while — drop us a message. No quote pressure, no sales call template. Just a conversation. → Reach out

AI Agents in Production Web Apps: What We're Actually Shipping in 2026

Ravi Rai — Thu, 07 May 2026 06:17:26 +0000

In 2026, every client meeting starts the same way. Founder shows me the dashboard. Pauses. Says 'so… can we add AI to this?' Sometimes they have a specific use case. Often they don't — they just know that not having AI in a product is starting to feel like not having a website in 2010. This post is what we actually ship when that conversation happens.

AI in 2026 is what mobile apps were in 2014. Most clients don't need their own AI. They need someone honest enough to tell them what they actually need — and what they're better off skipping.

The five categories of AI we ship

Across 18 production AI integrations we've built or maintained in the last 12 months, every use case fits into one of five buckets. Picking the wrong bucket is what makes most AI projects fail — and what makes them cost 10× what they should.

1. Embedded chat assistants

A small chat box on a website that answers customer questions about products, pricing, and policies — pulling from your existing FAQ pages, product catalog, or knowledge base. The most common 'add AI to my site' request.

Cost to build (one-time): ₹40,000–₹90,000 depending on data complexity
Cost to run: ₹2,000–₹15,000/month, depending on traffic and which model (GPT-4o-mini, Claude Haiku 4.5, or self-hosted LLM)
What works: 70-80% of customer questions get answered without human handoff. Clear ROI when it replaces a ₹25,000/month support hire.
What doesn't: complex multi-step workflows (returns, refunds with policy edge cases). Don't promise the bot will handle these — escalate to humans.

2. Content / SEO generation pipelines

Automated blog post drafting, product description generation, meta tag writing, FAQ page generation, alt text generation. We build internal admin tools that take a brief and produce a draft for human review.

Cost to build: ₹50,000–₹1,50,000 (depends on integration depth — does it write to your CMS automatically? Does it cross-link to existing posts?)
Cost to run: ₹3,000–₹20,000/month
What works: SEO product description generation for e-commerce stores with 1000+ SKUs. Bulk meta description regeneration. First drafts of blog posts that humans then edit.
What doesn't: fully automated 'just publish whatever AI writes' content workflows. We've never seen this work well — it produces generic content that ranks, briefly, then disappears as Google's AI-detection improves.

3. Data extraction and structuring

Taking unstructured data — invoices, resumes, customer emails, support tickets, scraped product data, scanned documents — and turning it into structured database records. This is where AI is genuinely magical and probably the highest-ROI category we ship.

Cost to build: ₹60,000–₹2,00,000 depending on data complexity and accuracy requirements
Cost to run: ₹500–₹10,000/month (per-document costs are tiny)
What works: invoice parsing for accounting tools, resume parsing for HR tools, product catalog ingestion from supplier PDFs, customer feedback categorization at scale
What doesn't: anything where 100% accuracy matters and there's no human review step. Banking, healthcare diagnostics, legal compliance — these need different tooling, not LLMs

4. Personalization and recommendations

AI-powered product recommendations, personalized email subject lines, dynamic homepage content based on user behavior, intelligent upsells in checkout flow.

Cost to build: ₹80,000–₹3,00,000 (this category has the widest range — depends on data infrastructure already in place)
Cost to run: ₹5,000–₹50,000/month
What works: e-commerce product recommendations that lift AOV by 8-15%. Email subject line A/B test winners selected by AI. Cart abandonment messages personalized by user history.
What doesn't: replacing human merchandisers entirely. The best results come from AI doing the heavy lifting and a human approving the top 3-5 weekly campaigns.

5. AI-native products

The product itself is AI — image generators, voice cloning tools, AI video editors, copywriting assistants. The AI isn't an add-on; it's the entire value proposition.

Cost to build: ₹2,00,000–₹15,00,000+ depending on scope
Cost to run: significant, often ₹50,000-₹5,00,000/month at scale (LLM inference is the main cost)
What works: vertical AI tools for specific Indian markets — legal contract review, GST audit assist, FSSAI compliance checking, regional language translation
What doesn't: 'ChatGPT for X' as a thin wrapper. There's no defensible product when OpenAI launches a feature that does what you do. Build vertical depth instead.

What we recommend most often

If you're a typical Indian SME or startup asking 'should I add AI?', the most common answer we give is: start with a small embedded chat assistant or a data extraction pipeline. Both have clear ROI in 30-60 days, low setup cost, and don't require you to bet your roadmap on AI.

We avoid recommending AI for use cases where the failure mode is critical — billing, payment confirmations, legal advice, medical info, anything where a wrong answer creates liability. AI is good at being mostly right, fast. It's bad at being always right. Match the tool to the problem.

The actual stack we use in 2026

For client AI projects, our default stack:

Models: Claude Haiku 4.5 for cost-sensitive tasks (₹0.20-₹2 per request). Claude Sonnet 4.6 for most production work (₹2-₹10 per request). GPT-4o for client-side embedding and tools that need OpenAI's ecosystem. Self-hosted Llama models when client data can't leave their infrastructure (e.g., healthcare, finance).
Vector database: Postgres with pgvector for most projects. Cheap, fast enough, no extra service. Pinecone or Weaviate only when scaling past 10M vectors.
Framework: Vercel AI SDK on Next.js for streaming. LangChain only for complex multi-step agents — most projects don't need it and the abstractions add fragility.
Hosting AI features: same as the rest of the app — usually CloudNX (our own product) or Vercel for client-facing apps. Inference is on the model provider's servers.
Logging and observability: Langfuse or Helicone for prompt logging, cost tracking, and debugging. Critical for AI in production — without it, costs and accuracy drift silently.

Indian context that matters

Some details that affect AI projects specifically for Indian businesses:

Hindi and regional language support: GPT-4o and Claude both handle Hindi well in 2026. Tamil, Telugu, Marathi vary — test before committing. For Hindi-English code-mixing (Hinglish), prompt engineering matters more than model choice.
INR billing for AI APIs: most providers bill in USD. Plan for forex variance and pre-paid credits. We've seen 10-15% monthly variance on production projects.
DPDP compliance: India's Digital Personal Data Protection Act requires explicit consent for AI processing of personal data. Don't pipe customer PII to third-party AI without consent flows in place.
On-premise / VPC deployment: some Indian enterprise clients (banks, government, defense-adjacent) won't allow data to leave India. We use AWS Mumbai with Bedrock for these, or self-hosted models on their own infrastructure.

What we don't ship

Anything where the AI output is the final answer and there's no human review step in workflows that matter to the business. Build with humans in the loop until the workflow is mature.
AI-generated content auto-published to a public site. Always human-edited.
Voice agents that act on behalf of the customer financially (e.g., 'place an order'). The error rate isn't ready for production yet — it will be in 2027-2028.
Anything called an 'AI replacement for [profession]'. We've never seen this work without significant scope reduction within 6 months. Build augmentation tools, not replacement tools.

How to know if your project actually needs AI

Quick test we run with every prospective AI client:

What's the specific problem you're solving? If you can't name it in one sentence, you don't need AI yet — you need clarity.
Could a simple rule-based system solve 60% of this? If yes, build that first. AI for the remaining 40% is usually cheaper and more reliable than AI for everything.
What's the cost of the AI being wrong? If it's 'embarrassing' or 'inconvenient' — go ahead. If it's 'we lose ₹10L+' or 'we get sued' — find a different solution.
Do you have data to ground the AI with? Most useful AI projects use Retrieval-Augmented Generation (RAG) — the AI reads your data before answering. Without your data, it's just ChatGPT with extra steps.
Is there an actual user pain point this solves? 'Our investors want us to add AI' is not a user pain point. We've turned down work that fails this test.

Thinking about adding AI to your product? We'll do a 30-minute scoping call — honest assessment, no pitch unless you want one. → Book a free AI scoping call

Where AI is heading in 2026-2027

Inference costs continue to fall ~10× per year. The thing that costs ₹15K/month today might cost ₹1.5K/month next year.
Agentic AI (where the model takes actions, not just answers) becomes production-ready for narrow domains in 2026. We're already shipping agents for invoice processing, support ticket triage, and lead qualification.
Voice agents that work in Indian English and Hindi reach production reliability mid-2027 (our prediction). Not yet for transactional flows — first wave will be customer support FAQ replacement.
Multimodal (image + text + voice in one prompt) becomes default. Single-modal applications start to feel dated.
On-device LLMs become viable for non-critical features. Faster, free of API costs, but limited capability.

The agencies and product teams that win in this period are the ones who actually ship AI features that solve real problems — not the ones who put 'AI-powered' in their tagline. We're betting on the former.

Building something AI-related? We've shipped 18 AI integrations in production. Tell us what you're building. → Get a quote

We Built 3 Live Products Last Year. Here's What That Changes for Our Clients.

Ravi Rai — Wed, 06 May 2026 08:07:36 +0000

Most agency websites have a portfolio page that shows three logos and a few screenshots. The work might be five years old. Half the sites have been redesigned by someone else since. The agency has no skin in those projects anymore — they got paid, the client got code, the relationship ended.

We're a different kind of shop. Alongside our client work, we run three products in production. Real users. Real revenue. Real on-call shifts when something breaks at 11 PM. This post is about why that matters when you hire us.

Agencies that don't run their own software give you the version of advice they'd give themselves if their own money wasn't on the line. We built three products to make sure ours always is.

PlugEV — production OCPP for an EV operator

PlugEV is an EV charging station management system (CSMS) we built in 2024 and still run today. OCPP 1.6-J protocol. WebSocket gateway in Go. Laravel admin panel. 40+ chargers live across two cities. Real money flowing through it via Razorpay every day.

What that taught us — and what it means for you if you hire us:

Vendor APIs lie. Charger 1 says it's at 12 kW. The meter reads 8 kW. Charger 2 returns a status code that's not in the OCPP spec. We learned to never trust the data — verify, log, and reconcile against ground truth. Same applies to Razorpay webhooks, Shopify product feeds, or any third-party integration we build for you.
Real-time systems require ruthless monitoring. We caught a billing bug 6 hours after it started shipping wrong invoices because alerts were wired to actual outcomes (revenue mismatch) and not just CPU/memory dashboards. Every system we build for clients now has business-metric alerts, not just infrastructure alerts.
On-call discipline. PlugEV doesn't have a maintenance window. Cars charge at 2 AM. We learned how to run actual 24/7 production software — not just 'the website's up' but 'every transaction reconciles, every charger reports, every dispute has an audit trail.'

When you hire us to build your fintech, your fleet portal, your IoT-heavy app, or anything that needs real reliability — this is the experience you're buying. Not theoretical. Lived.

Need a CSMS, fleet portal, or any production-grade real-time system built? We've solved these problems already. → See PlugEV details

CloudNX — cloud hosting for Indian developers

CloudNX is a managed cloud hosting platform we launched in 2026 — INR billing, Indian data centres, GST invoices, one-click deploys for Next.js, Laravel, and WordPress. We built it because we needed it for our own client deployments.

Running infrastructure-as-a-product made us deeply opinionated about hosting decisions on client projects:

We know exactly what shared hosting costs the client downstream. Most ₹99/month plans deliver 6-9 second mobile load times and quietly murder your Core Web Vitals. We've seen the numbers from the inside, and we won't ship a client to that fate.
We know which Indian-region cloud setups actually deliver low latency. The marketing says 'India region' for AWS Mumbai, GCP Mumbai, DigitalOcean Bangalore. The reality is wildly different at the network level. We've benchmarked all of them — for client projects, we recommend based on what we've measured, not what the marketing pages say.
Backups, SSL renewal, monitoring, log retention — we treat these as non-negotiable defaults because we run a hosting product where one missed backup means a customer lost their site. Our default for every client deploy now matches CloudNX's defaults.

If you hire us to ship a Shopify store, a Next.js marketing site, or a Laravel SaaS — your hosting and ops setup will be the same standard we hold our own product to.

Hosting your project on CloudNX is free for the first 3 months. No credit card required. → See CloudNX details

ToolKiya — free online toolkit

ToolKiya is a free online toolkit — image converters, PDF tools, SEO utilities, calculators, generators. Browser-based, no signup, no upload limits. We built it as both a product and a public-facing demonstration of how fast and clean a Next.js site can be when SEO and Core Web Vitals are taken seriously.

Running ToolKiya means we ship every client site to the same standard:

Sub-second LCP on mobile. ToolKiya is fast because slow tools lose users. We built the same performance discipline into every client project — Lighthouse scores 90+ on mobile is the table-stakes minimum, not the goal.
SEO that actually ranks. ToolKiya competes for terms like 'free image compressor', 'PDF merger online', 'GST calculator'. To rank against the giants, our schema, content structure, and internal linking has to be precise. That same precision goes into every client site.
Tracking conversions, not vanity metrics. ToolKiya tracks tool-completion rates, not just pageviews. We instrument every client site the same way — form submissions, WhatsApp clicks, phone clicks, scroll depth. You'll see real conversion data, not just traffic.

ToolKiya is free and live. Use it as a demo of the kind of site we ship for clients. → Visit ToolKiya

Why this matters when you hire us

There's a fundamental difference between an agency that ships and disappears versus one that runs the systems they build. We've experienced — at our own expense — every problem a client might face after launch:

We've been on the wrong end of a payment gateway webhook race condition that double-billed customers for 90 minutes. Now every Razorpay integration we build has idempotency keys and reconciliation jobs.
We've had to wake up to fix a production outage because a Cloudflare DNS change broke our staging environment. Now every client deploy has a rollback path that takes 30 seconds, not 30 minutes.
We've had a feature request from a real customer whose business depends on it. That changes how you write code. You stop building 'demo-quality' and start building 'this needs to work in 6 months when the original developer isn't here anymore.'

Almost every Indian web agency you talk to has never run their own software in production. They've shipped client sites — fine, important — but they've never had to maintain anything past the launch invoice. Their advice reflects that experience gap. Ours reflects our scars.

What this means for your project

If you're building a SaaS, a marketplace, or anything that needs real production reliability — we won't sell you a brittle MVP that breaks at month 3.
If you're choosing hosting, payment gateways, analytics tools, or any third-party — you'll get advice from someone who pays for those tools with their own money, not someone who's just read the docs.
If you're hiring us to maintain a project after launch — we treat your code with the same on-call discipline we apply to PlugEV. No 'submit a ticket and wait 5 days'.
If your project requires deep integration work (OCPP, Razorpay, Shopify, OAuth, third-party APIs) — we've already debugged the things that go wrong, on our own dime.

We're not the cheapest agency in India. We're not trying to be. What we are is the agency you hire when the project actually has to work, when the system actually has to scale, and when the people building it actually live with the consequences of what they ship.

Building something that needs to work past launch day? Tell us what you're working on. Quote in writing within 24 hours. → Get a written quote

All three products in one place

PlugEV — plugev.in — production OCPP CSMS, 40+ chargers live, OCPP 1.6-J + Razorpay billing.
CloudNX — cloudnx.in — cloud hosting for Indian developers, free for first 3 months, INR billing, GST invoices.
ToolKiya — toolkiya.com — free online toolkit, 50+ utilities, no signup required.

Click into any of them. They're all live. They all work. They're how we prove what we can do — not with mockups and demo videos, but with software you can use today.