Knowledge Base
Guide11 posts

Building software for Indian SMBs

The posts in this guide are written from builds we have shipped: a gym-management platform with biometric attendance, a WhatsApp CRM, an offline-first inventory system. They cover the decisions that decide whether a custom build is worth it, how to structure it so a second branch or a mobile app does not mean a rewrite, and the mistakes that show up when apps are generated rather than engineered.

Start with the cost post if you are deciding between building and buying. Start with the architecture posts if you have already decided to build.

  1. 01How much does it cost to build a custom CRM in India?An honest breakdown of what drives custom CRM cost in India: scope, integrations and maintenance, plus when a bespoke build is worth it and when a product like Pariq is the smarter call.6 min
  2. 02Shopify vs a custom storefront for Indian D2C brandsA practical breakdown of when Shopify is the right call for an Indian D2C brand and when a custom or headless build pays off, covering payments, COD, scale, and total cost.5 min
  3. 03Multi-tenant SaaS architecture for Indian SMBs, explainedA practical breakdown of multi-tenant SaaS architecture (row-level, schema-per-tenant, and database-per-tenant models) and why RLS-based isolation matters most for Indian franchise and multi-branch businesses.6 min
  4. 04Why we build every app native-app-ready from day oneMost web apps assume the browser is the only client. We design every app so a mobile app can plug in later without a rewrite: token auth, API-first, no server-only shortcuts.7 min
  5. 05Single sign-on across a product suite, explainedWhy we built one login across our whole product suite (sign in once, move between products, sign out everywhere) and the principles that keep it secure without a heavyweight identity provider.4 min
  6. 06Bearer JWT vs cookie sessions: why we build token-onlyA practitioner's case for Bearer JWT over cookie sessions: token-only auth makes every app native-ready by default, but you have to get storage, expiry, and refresh right.6 min
  7. 07Metered billing vs per-seat pricing for SaaSPer-seat pricing charges by the number of users; metered billing charges by what you actually consume. For most Indian SMBs, a small base fee plus a usage wallet is the fairer model.6 min
  8. 08How biometric attendance works in modern gym softwareA practitioner's walkthrough of how fingerprint readers, a desktop bridge, and cloud software combine to track gym attendance across one branch or many, and where the real work hides.6 min
  9. 09How we QA a CRM before it touches a customer: a 254-point pre-launch sweepBefore any CRM we build reaches a customer, it goes through a 254-point pre-launch quality sweep. A look at what that covers, and how to get the same rigour on your product.2 min
  10. 10The most common security mistakes in AI-built appsAI coding tools ship working apps fast, but they also ship predictable security holes: secrets in the client bundle, open databases, missing auth, and exposed storage. Here's what to check and fix.6 min
  11. 11How to keep secrets out of your frontend bundleAnything shipped in your JavaScript bundle is public. Here is what is actually safe to expose, why API keys leak, and how to audit your own build before a key ends up on Pastebin.6 min
Building something in this space?Talk to BotBrained