DEV Community: aNquest Media

Why Your Client's "Finished" Website Might Be Invisible to Google (SSR vs CSR, Explained for Non-Devs)

aNquest Media — Wed, 05 Aug 2026 09:53:57 +0000

If you build websites for clients, you've probably seen this pattern: ship a slick React or Vue SPA, everyone's happy with the demo, and three months later the client is asking why the site isn't showing up in Google.

Nine times out of ten, the answer is rendering strategy, not content quality.

The core problem

A pure client-side rendered (CSR) app sends the browser a nearly empty index.html and lets JavaScript build the DOM after load. Modern Googlebot can execute JavaScript, but it does so in a second rendering wave, with a delay, a resource budget, and no guarantee of full execution — especially on sites with heavy hydration, client-side routing, or render-blocking scripts. In practice, that means:

Meta tags, canonical tags, and structured data can resolve to homepage defaults or nothing at all
view-source: shows an empty shell — no headings, no body copy
Sitemaps generated client-side can return as unparseable to crawlers instead of clean XML
Pages look finished to a human, but Search Console shows them as "Discovered — not indexed" or "Crawled — not indexed" indefinitely

This isn't a hypothetical. It's a documented, sitewide failure mode I've seen firsthand — agencies shipping otherwise well-designed sites that are functionally invisible to search because nobody checked the rendering strategy against SEO requirements before launch.

The fix isn't complicated

SSR (Next.js, Nuxt, SvelteKit, Astro's server mode) — render on request, crawler gets full HTML immediately
SSG/ISR — prerender at build time or on a cache interval, serve static HTML with JS hydration on top
Dynamic rendering as a stopgap — serve a prerendered snapshot to known crawler user-agents while keeping CSR for real users (not ideal long-term, but works as a bridge)

What doesn't work: telling the client "Google can render JS now" and shipping pure CSR anyway. It technically can. It doesn't reliably, at scale, on a timeline your client's business depends on.

Why this matters beyond the technical fix

I ended up going down this rabbit hole while helping evaluate web design vendors for a project — turns out this exact SSR/CSR distinction is one of the clearest signals for telling a technically competent agency from one that's just good at sales. If an agency can't answer "will this be SSR or CSR" in one sentence, that's informative on its own.

I wrote up a longer, less code-heavy version of this as part of a broader comparison of web design agencies — worth a look if you're on the business side of this decision rather than the dev side: the technical writeup

Curious how others handle this on client projects — do you default to SSR/SSG now, or is dynamic rendering still in your toolkit as a stopgap?

How to Get an Apples-to-Apples Mobile App Development Quote (Noida Cost Breakdown)

aNquest Media — Thu, 30 Jul 2026 10:17:51 +0000

If you've ever had to explain to a non-technical client why "the same app" got quoted at ₹90K by one shop and ₹4L by another, this is the framework I use to walk them through it — sharing it here since the underlying cost logic applies wherever you're building.

The screens are never the expensive part

Two quotes for "an app where customers book a service and pay" can differ by 5x, and it's almost never the UI driving that gap. It's the backend: real database, payment gateway, admin dashboard, push notifications. A quote covering only app-facing screens with no working server-side logic will always look cheaper — and will always need a second budget round once the client realizes the app doesn't function yet.

Platform choice: the other hidden variable

Native (separate Kotlin + Swift builds) → ~2x engineering time
Flutter / React Native (one codebase) → ~1.15–1.25x a single-platform build

If a client's brief doesn't specify platform approach, quotes will scatter widely for exactly this reason. Worth surfacing early in any scoping call.

Starting cost bands (Noida market, for context — adjust for your region)

Project type Starting cost
Simple single-platform app, no custom backend ₹80,000–₹1,50,000
Cross-platform (Flutter/RN) with real backend ₹2,50,000+
CRM/payment/API integrations ₹4,00,000+
Enterprise, custom infra Scope-dependent

Don't forget the recurring platform fees

Google Play: one-time $25 registration
Apple Developer Program: $99/year, not one-time — easy to leave out of a client's budget model
Backend hosting: ongoing, scales with usage
Maintenance/OS-update support: budget ~10–20% of build cost annually, or the app quietly breaks within a year or two

The one question that fixes bad quote comparisons

Ask every vendor to itemize design, frontend, backend, and integrations as separate line items instead of one bundled number. It's the fastest way to find out whether two "quotes for the same app" are actually pricing the same scope.

I wrote this up in more depth for aNquest Media, a Noida-based dev shop — full cost tables and the vendor-vetting angle: Mobile App Development Cost in Noida. Cross-posting the framework here since it's not Noida-specific in practice.

https://anquestmedia.substack.com/p/the-noida-app-quote-trap-same-brief

Web Design vs Web Development: A Practical Framework for Vetting Agencies in Noida

aNquest Media — Sat, 25 Jul 2026 09:59:00 +0000

If you're a dev or freelancer in Delhi NCR who's ever been brought in to "just build what the designer handed over," you already know how often that handoff breaks down. Here's the framework I use to explain the design/development split to non-technical clients before scope gets set — useful if you're ever the one having that conversation.

Two different jobs, one confusing label

Web design = layout, typography, color, UX flow. Output is usually static screens (Figma, XD). No working site.

Web development = the actual build — frontend code, backend, database, CMS, integrations (CRM, payments, booking systems). Output is a live, functioning site.

Most agencies in Noida market as "full-service web design and development," but their portfolio usually reveals they're strong in one and weak in the other. Clients rarely know to check.

The three questions that expose the gap

"Show me 3 sites you both designed AND built."
→ Not sites where they only did the visuals.
"Who owns the CMS admin after launch?"
→ Vague answer = you're probably only getting a design file.
"What's the process for adding a new page type in 8 months?"
→ A real dev team has this answer ready. A design shop doesn't.
Where CMS fits into this

This is the part non-technical clients miss most: CMS development is its own category, separate from both "design" and generic "development." If the client's team needs to publish content or update pricing without a dev in the loop, that's a CMS-first conversation.

Rough cost benchmarks for Noida-based builds, for anyone scoping client work:

Scope Typical starting cost
Design only ₹20,000–₹50,000
Standard CMS (WordPress/Webflow) ₹40,000–₹90,000
Custom CMS + integrations ₹1,50,000+
Full design + dev, one team Scope-dependent
Why one vendor beats two

Split design and dev across separate vendors and you inherit the integration risk yourself — the dev has to reverse-engineer intent from static screens, and every revision request bounces between two teams that don't talk to each other. If you're the freelancer stuck in the middle of that, you already know how much unpaid time that costs.

I originally wrote this up in more depth — full cost tables and vetting checklist — for aNquest Media, a Noida-based dev shop: Web Design vs Web Development in Noida. Cross-posting here since the framework applies anywhere, not just Noida.

Curious how other devs handle this conversation with non-technical clients — drop it in the comments.

Best CRM Software for Real Estate in India: A Practical Guide

aNquest Media — Wed, 22 Jul 2026 09:08:51 +0000

Real estate businesses generate leads from websites, Google Ads, Facebook, Instagram, WhatsApp, property portals, and referrals.

Managing all these inquiries manually becomes increasingly difficult as the business grows.

That's why CRM software has become an essential technology investment.

Key Features of a Real Estate CRM

A modern CRM should include:

Lead Management

Automatically capture and organize leads from multiple sources.

Sales Pipeline

Track customer progress from inquiry to booking.

Property Management

Manage projects, units, availability, and pricing.

WhatsApp & Email Automation

Send reminders and updates automatically.

Analytics Dashboard

Monitor team performance, lead conversion, and sales metrics.

Benefits of CRM Software

A dedicated CRM helps businesses:

Improve response times
Reduce missed follow-ups
Increase lead conversion
Automate repetitive tasks
Improve reporting
Enhance customer experience These advantages contribute to better operational efficiency and revenue growth.

Choosing the Right CRM

Before purchasing a CRM, evaluate:

Industry expertise
Feature set
Customization
Scalability
Support services
Security
Integration options

Selecting software that aligns with your business processes is often more valuable than choosing the lowest-cost option.

Conclusion

CRM software is no longer optional for growing real estate businesses.

The right solution can simplify operations, improve customer relationships, and increase sales productivity.

Read the complete guide here:

https://anquestmedia.com/blogs/best-crm-software-for-real-estate-in-india

https://anquestmedia.substack.com/p/why-real-estate-companies-in-india

https://differ.blog/p/best-crm-software-for-real-estate-in-india-2026-top-tools-to-boost-5336c2

What I Wish Non-Technical Founders Knew Before Hiring a Dev Shop

aNquest Media — Sat, 18 Jul 2026 09:28:46 +0000

If you've ever been the technical friend a founder brings along to "just sit in on the call," you've probably seen this play out: the agency's sales rep is sharp, the deck looks great, and the founder is ready to sign before anyone's asked a single question about architecture, testing, or who's actually going to write the code.

Here's what I tell friends in that position, condensed.

Validation comes before vendor selection

A surprising number of founders go straight to "which company" without answering the cheaper questions first: have they talked to real potential users, do they have a clickable prototype, can they state the core user/problem/action in one sentence? None of that requires a developer — and skipping it means the dev shop is pricing a moving target.

Agency vs. in-house isn't a values question, it's a stage question

Agency / contractor — fast for MVP validation, but quality varies wildly with how closely it's managed.
In-house team — better long-term code quality and maintainability, but slow to assemble and expensive (senior engineers routinely clear $150K+ in the U.S.).
Hybrid — agency builds, a technical advisor reviews architecture and code quality along the way. This is usually the right call for a non-technical founder with some budget.

The tell in the first call

Red flags I've seen repeatedly: a fixed quote before any real requirements discussion, no client references they'll actually let you contact, vagueness about who's assigned to the project versus who's on the sales call, and an inability to explain their QA process without buzzwords.

Pilot before contract

The single best filter is a small, paid, scoped pilot task — one feature, one sprint, one technical audit — before committing to the full build. It surfaces communication quality and how they handle a scope change, which matters more long-term than any portfolio piece.

I laid out the fuller framework — cost ranges by region, what to lock into the contract, the exact red-flag list — in more detail here: How to Vet an App Development Company. Useful to forward to a founder friend before their next round of agency calls.

Curious what other devs here have seen go wrong (or right) when a non-technical founder is picking a build partner — drop it in the comments.

The Question I Get Most: "Who Should I Hire to Build My App?"

Hey all —

anquestmedia.substack.com

A Developer's Checklist for Vetting Software Development Partners in Delhi NCR

aNquest Media — Tue, 14 Jul 2026 11:34:13 +0000

If you're a technical founder or engineering lead outsourcing part of your build to a Delhi NCR firm, most of the advice out there is written for procurement teams, not for the people who actually have to work with the code afterward. Here's a checklist from the engineering side of the table.

1. Ask who's actually writing the code

Large IT services firms often staff junior developers on the ground and route architecture decisions through senior leads who aren't in day-to-day contact with you. Ask directly: who will I be talking to during sprints, and what's their seniority level? Boutique firms tend to give you more direct access to the people actually shipping code — worth confirming either way.

### 2. Check their git hygiene, not just their portfolio

A polished case study page tells you nothing about code quality. Ask for a sample repo (sanitized, obviously) or at minimum ask about their branching strategy, PR review process, and test coverage expectations. A firm that can't answer this concretely probably doesn't have strong internal engineering practices.

3. Clarify the handoff, not just the build

Who owns the repo? What's the documentation standard? Is there a runbook for deployment and rollback? These questions matter more once the project ships than during the sales conversation, and they're the ones vendors most often gloss over.

4. Match engagement size to project size

This is the one most technical teams get wrong: hiring an enterprise-scale IT services firm (TCS, Infosys, Wipro-tier) for an MVP-stage build usually means slower iteration and higher overhead than the project needs. Boutique, project-based firms are generally better matched to smaller, faster-moving builds — CRM implementations, healthcare software, mid-size applications — where you want direct developer access instead of an account-management layer in between.

5. Pricing model should match your certainty about scope

Fixed-scope pricing works when requirements are locked. Time-and-materials makes more sense for evolving product work. Any firm that pushes one model regardless of your situation is optimizing for their revenue predictability, not your outcome.

I put together a broader comparison of how the major Delhi NCR development companies — from enterprise IT firms to boutique teams — actually differ on these exact points (delivery model, engagement size, pricing structure): full breakdown here. Top 10 Software Development Companies in Delhi (2026)

A Technical Lead's Checklist for Vetting Outsourced Dev Teams in Noida

aNquest Media — Sat, 11 Jul 2026 11:07:48 +0000

If you're a CTO or tech lead evaluating an outsourced team in Noida, the sales deck is not where you'll find the signal. The signal is in how they answer a handful of specific, slightly uncomfortable questions.

I've collected the ones that actually separate a team you can hand production work to from one that will quietly become a bottleneck.

"Walk me through your discovery process before you send a proposal."

If they can quote a fixed price off a single call, they haven't scoped anything — they've guessed. A team that's actually going to build something maintainable will want to map your data model, integration points, and technical constraints before committing to a number.

"How often will we see working software?"

Two-week sprints with a demo at the end of each is the baseline, not a nice-to-have. If the answer is vague ("we'll keep you updated"), that's a team optimized for looking busy, not shipping.

"Who owns the source code and IP after final delivery?"

This should be a one-sentence answer: you do, in writing, effective on final payment. If there's hedging — licensing clauses, retained ownership of "reusable components," anything like that — you're building on rented infrastructure.

"What's your QA process — dedicated QA, or do devs test their own code?"

Self-testing isn't inherently disqualifying for a small team, but it should be disclosed upfront, not discovered in production. A dedicated QA function (even a lightweight one) is a real signal of engineering maturity.

"What's your response time for a critical bug post-launch?"

Get an actual SLA, in writing, before the project starts. "We'll support you" is not a support commitment.

On cost: Noida rates typically run ₹800–₹3,500/hour depending on seniority (~$15–$30/hour for international clients) — a meaningful discount against US/UK rates for comparable experience, without the quality tradeoff people sometimes assume comes with it. Complexity, not location, is what actually drives the price spread — a CRM/ERP build (₹15–50L+, 6–18 months) is a different animal from an MVP (₹1.5–5L, 4–10 weeks), and pricing should reflect that distinction clearly, not get bundled into one flat day-rate.

Red flags that should end the conversation: no discovery phase, no NDA before project details are shared, pressure for a large upfront payment, and an inability to put you on a reference call with a team they've shipped for in the last year.

I laid out the full version of this — cost breakdowns by project type, the complete pre-signing checklist, and the specific red flags in more detail — here: Software Development in Noida: Cost, Quality & Red Flags.

Curious what other technical leads screen for when vetting outsourced teams — what's on your list that isn't on mine?

What Non-Technical Founders Get Wrong When Hiring a Dev Agency in Ghaziabad

aNquest Media — Wed, 01 Jul 2026 11:51:29 +0000

I've seen a lot of software projects in Delhi NCR go sideways — not because the developers were bad, but because the engagement was structured in a way that made a good outcome nearly impossible. A few patterns that show up consistently:

They evaluate on portfolio aesthetics, not technical decisions.

A nice-looking case study doesn't tell you whether the underlying architecture was sound, whether the database schema will scale, or whether the deployment process is documented well enough for anyone else to maintain. Before signing with any agency, run their client sites through Google PageSpeed Insights and check the network requests in browser DevTools. That tells you more than a portfolio PDF.

They don't ask about the testing process.

Unit tests, integration tests, UAT — what's actually in scope and what's assumed to not be needed? A ₹60,000 web app quote that doesn't include a testing phase is a build that ships with unknown bugs into production.

They skip the IP ownership clause.

Source code ownership should be explicit in the contract — that the client owns all code, schemas, and assets upon final payment. Without it, ownership defaults to whatever the contract says, which sometimes isn't the client.

They treat the handover as the end.

What does the agency deliver at project close? Full source code in a repository the client controls? Documentation? Deployment runbooks? Environment variables and credentials? "We'll send over the files" is not a handover process.

None of these are exotic asks. Any professional dev agency in Ghaziabad should be able to answer them clearly before you sign anything.

Put together a fuller checklist for evaluating software development firms in Ghaziabad — including stack questions, pricing context, and contract terms — https://anquestmedia.com/blogs/best-software-development-company-in-ghaziabad if useful for anyone advising a non-technical client.

What to Actually Check Before Hiring a Web Dev Agency (Beyond Their Portfolio)

aNquest Media — Tue, 30 Jun 2026 12:17:04 +0000

Most "best web development company" content is marketing copy dressed up as advice. As a dev, here's what I'd actually want a non-technical founder to check before they sign with an agency — things that are easy to verify and harder to fake than a polished portfolio.

Run their own client sites through PageSpeed Insights. An agency claiming "SEO-friendly, fast-loading websites" should have client sites that back that up. If their flagship case studies load slowly, that's the actual signal — not the case study copy.

Ask what stack they're proposing and why. "We use modern technology" is not an answer. React vs. a simpler server-rendered setup, Node vs. PHP, MySQL vs. Mongo — these are real tradeoffs tied to what you're building, and a competent team should be able to explain the choice in plain terms, not jargon.

Check whether SEO is architecture or an afterthought. Clean URLs, correct heading hierarchy, and schema markup need to exist from the first commit, not get bolted on post-launch. Retrofitting this is real rework — ask if it's scoped into the build or sold separately later.

Get post-launch terms in writing before the build starts, not after something breaks.

I wrote a longer version of this checklist with realistic Delhi NCR pricing context — https://anquestmedia.com/blogs/best-website-development-company-in-delhi, if useful for anyone evaluating agencies for a client or their own project.

What to Actually Look for in a Mobile App Development Company Noida

aNquest Media — Thu, 18 Jun 2026 12:22:35 +0000

If you're a developer who's ever been brought in to "fix" an app that an agency built badly, you already know how often this goes wrong. Bad architecture, no API documentation, hardcoded values everywhere — the symptoms are always the same.

So here's a framework for evaluating mobile app development agencies, from a technical angle rather than a sales one.

Questions that actually reveal competence

1. What's their default stack, and why?

React Native and Flutter both have legitimate use cases. An agency that pushes one stack regardless of project requirements is optimizing for their own comfort, not your product.

2. How do they handle backend architecture?

Ask about API design, database choices, and how they plan for scale. "We'll figure it out as we go" is not an acceptable answer for anything beyond a throwaway MVP.

3. Do they understand platform-specific constraints?

iOS App Store review guidelines and Android's Play Store policies are not the same. An agency should be able to speak fluently about both — push notification handling, background processes, permissions models, etc.

4. What does their CI/CD and testing process look like?

Manual QA before every release is a red flag at any kind of scale. Ask about automated testing and release pipelines.

5. Can they integrate with existing systems?

Most real-world apps need to talk to a CRM, payment gateway, or internal database. An agency with experience in business automation and backend integrations (not just frontend polish) will save you a lot of pain later.

A team worth knowing about

I came across aNquest Media, a Noida-based dev shop that works across web, mobile, and CRM software — which is a slightly unusual combination, but a useful one. It means their mobile builds are designed with backend/CRM integration in mind rather than as isolated frontend projects.

They've built apps and systems for clients in real estate and healthcare — both of which involve fairly intricate workflow and data requirements, which is a reasonable proxy for technical maturity beyond basic CRUD apps.

If you're a founder evaluating mobile app partners, or a dev looking to refer a client, they're worth a conversation.

→ Full breakdown of their mobile app development services

their mobile app development services

Curious what the community thinks: React Native vs. Flutter in 2026 — has either pulled ahead for production apps? Drop your take below.

Designing CRM Systems for Multi-Department Medical Centres: A Quick Architecture Note

aNquest Media — Sat, 13 Jun 2026 12:46:13 +0000

If you're building or customizing a CRM for a healthcare client in India, "medical centre" clients are a category that trips up a lot of generic implementations — and it's worth understanding why before you scope the project.

The Three Tiers of Healthcare Facilities (and their CRM needs)

TierStructureCRM complexitySingle clinic1-2 doctors, 1 calendarLow — basic scheduling + remindersMedical centreMultiple departments, outpatient only, no bedsMedium — multi-calendar, cross-department data modelHospitalInpatient, ER, wardsHigh — full HIS, bed/ward management

Most off-the-shelf CRM products are built for tier 1 or tier 3. Tier 2 — the medical centre — gets handled by either over-scaling a clinic tool (department silos, no cross-department data) or under-scaling a hospital system (paying for ward/bed modules that go unused).

The Core Data Model Problem

The thing that actually breaks in tier 1 tools when applied to tier 2 clients is the patient-to-department relationship. A single-clinic CRM typically models:

Patient -> Appointments -> Doctor

A medical centre needs:

Patient -> Appointments -> Department -> Doctor
|
-> Internal Referrals -> Other Department

Without that referral edge in the data model, internal referrals between departments (dermatology → dietitian, for example) are invisible to reporting — even if they're happening constantly in practice. This is usually the single biggest gap when a clinic-tier CRM gets stretched to cover a medical centre.

Communication Layer: Centralize, Don't Fragment

A related but separate issue: each department often ends up with its own outbound communication channel (separate WhatsApp Business numbers, for instance), because that's the path of least resistance when departments are onboarded one at a time.

If you're architecting this from scratch, route all patient-facing messaging (confirmations, reminders, follow-ups) through one WhatsApp Business API integration, with department as a field on the message/template — not a separate integration per department. This keeps the patient experience consistent and keeps your messaging costs/quotas manageable as departments scale.

Reporting: Two Levels, Not One

Build reporting views at both the department level (for department heads) and the centre level (for administrators/owners) from the start. Retrofitting a centre-wide rollup after department-level reporting has already been built independently per department is more painful than it sounds — mostly due to inconsistent status/taxonomy across departments that nobody standardized upfront.

Where This Matters for Scoping

If a client describes themselves as a "medical centre," "polyclinic," or "multi-specialty centre" — ask early whether they currently have separate systems/numbers per department. If yes, the migration/data-consolidation work is often a bigger chunk of the project than the CRM build itself.

I wrote a more business-oriented (less architecture-y) version of this with a vendor evaluation checklist here, if useful for client-facing conversations: CRM Systems for Medical Centres: Choosing the Right Fit

Curious if others building in this space have run into the same tier-2 gap — feel free to share war stories in the comments.

What Healthcare CRM Software Actually Does (For Non-Healthcare Devs)

aNquest Media — Fri, 12 Jun 2026 11:14:16 +0000

Healthtech is one of those domains where the software requirements look simple from the outside ("just send some reminders, right?") but get surprisingly nuanced once you look at how Indian hospitals and clinics actually operate. I've been digging into this space recently — specifically healthcare CRM software — and wanted to share a quick breakdown for anyone building or evaluating tools in this category.

It's Not a Sales CRM With a Healthcare Skin

The instinct is to think "CRM = Salesforce/HubSpot, just rebrand it for hospitals." But the data model is different in a few important ways:

The "contact" is a patient, with a longitudinal history (visits, prescriptions, follow-ups) that spans years, not a sales pipeline that closes and ends.

Referral sources matter a lot. A huge chunk of patient inflow for Indian hospitals comes from referring doctors and diagnostic labs — so the CRM needs to track who referred whom, and surface which relationships are active vs. cold.

Communication channel priority is inverted. In most SaaS CRMs, email is king. In an Indian healthcare CRM, WhatsApp (via the WhatsApp Business API) is the primary channel — open rates on WhatsApp reminders are dramatically higher than SMS or email for this user base.

CRM vs. HMS — A Genuinely Important Distinction

If you're new to this space, it's easy to conflate a healthcare CRM with a Hospital Management System (HMS). They're different systems solving different problems:

HMS: operational system of record — billing, bed management, lab orders, EHR/EMR.

CRM: relationship layer — appointment reminders, follow-up automation, referral tracking, patient retention.

In practice, the two need to talk to each other. A good integration means an appointment booked or rescheduled in the CRM reflects in the HMS scheduling system, and discharge events in the HMS can trigger follow-up sequences in the CRM.

Worth Reading If You're Building in This Space

I came across a fairly thorough breakdown of this category — covering feature checklists, hospital vs. clinic requirements, pricing bands in the Indian market, and a step-by-step evaluation framework — here:
🔗 Healthcare CRM Software for Hospitals & Clinics in India: The Complete Guide

If you're a developer or PM working on healthtech for the Indian market — or just curious how this corner of B2B SaaS works — it's a solid primer on the domain requirements before you start architecting anything.