The GarunaCDX Blog
Engineering notes, AI automation playbooks and industry breakdowns from the systems we build for clients in healthcare, marketplaces, B2B SaaS and industrial businesses.
Server-rendered pages and AI search: what crawlers see
If your content only appears after JavaScript runs, some crawlers never see it. How to check what a crawler receives, and the machine-readable files that help.
What a maintenance retainer should and should not cover
A retainer without limits becomes unlimited development, and a retainer that ignores a bad audit becomes a surprise invoice. What to put in, what to keep out, and what to price after the audit.
What a CMS needs so editors can publish without breaking SEO
Roles, a review step, scheduled publishing, an audit log and generated sitemap and structured data. What we built into a publication's CMS, and what we still lack.
How to take over software another vendor built: the first two weeks
Inventory before audit, audit before changes, and a written scope before a contract. A two-week sequence for inheriting a live system, from our own handover of a marketplace.
Moving a React single-page app to Next.js without losing search traffic
A checklist for migrating a client-side React app to a server-rendered framework: inventory the URLs, keep or redirect them, render content on the server, and record a baseline first.
32 articles
Building a blog engine in MDX that marketing can run
MDX lets a post carry real components, but a marketer needs an editor, guardrails and previews. The trade-offs of MDX against a database CMS, from a rebuild we did.
Moving a React single-page app to Next.js without losing search traffic
A checklist for migrating a client-side React app to a server-rendered framework: inventory the URLs, keep or redirect them, render content on the server, and record a baseline first.
What a CMS needs so editors can publish without breaking SEO
Roles, a review step, scheduled publishing, an audit log and generated sitemap and structured data. What we built into a publication's CMS, and what we still lack.
How to take over software another vendor built: the first two weeks
Inventory before audit, audit before changes, and a written scope before a contract. A two-week sequence for inheriting a live system, from our own handover of a marketplace.
What a maintenance retainer should and should not cover
A retainer without limits becomes unlimited development, and a retainer that ignores a bad audit becomes a surprise invoice. What to put in, what to keep out, and what to price after the audit.
Server-rendered pages and AI search: what crawlers see
If your content only appears after JavaScript runs, some crawlers never see it. How to check what a crawler receives, and the machine-readable files that help.
Where should our app's data live, and what does DPDP mean for us?
Choosing where data is hosted, what you collect, how people consent and delete are design decisions you make before launch. What India's DPDP rules reportedly require and when, what the App Store already requires, and what we built in. Not legal advice.
What should a tech handover and a maintenance agreement cover?
A handover leaves you holding every account, repository, secret and renewal date. A maintenance agreement says what it covers, what it doesn't, and how it ends. Two checklists you can hold any vendor to.
What should go in version 1 of a custom platform?
Put in the one workflow that proves the idea, and write down what's out as carefully as what's in. A scoping method from a 30-day clinic-platform build.
India solar market, October 2026: what the numbers mean for EPC operations
Capacity is booming, but three states carry most of it, rooftop growth dipped month on month, and the real bottleneck is grid connection, not installation. What that means for how an EPC should run its operations.
One backend for the app and the web: the right call?
For a first release where several roles share data in real time, one backend usually beats one per app. The trade-offs, the lock-in question, and how we built five surfaces on one backend.
Why solar EPC projects overrun cost and time, and where to catch it
Rooftop and C&I solar projects rarely fail on panels. They drift: a survey gap, a BOM change, a late delivery, an approval that sits. Five places the drift starts and the one comparison that catches it.
How do I vet a software vendor, especially a new one?
Ask for evidence of habits, not years in business. Eight checks you can run on any agency, including us, and what a good answer and a warning sign look like.
Will the new site get found? A technical SEO and AI-search checklist
A rebuild can quietly delete the search visibility you already have. Ten technical checks to run before a relaunch, what helps AI assistants quote a page, and what nobody can honestly promise.
Solar EPC receivables and working capital: why profitable projects still run out of cash
An EPC pays suppliers up front and gets paid in stages. The gap is your working capital, and a stalled approval can stretch it by months. A worked cash curve and the three numbers to watch.
How do you test a system before real users arrive?
A demo that works proves little. Test the things real days do to a system: concurrent use, retries, abuse, and a release that goes out half-finished. Three problems we found in our own build, and what we still haven't fixed.
How to evaluate a solar ERP vendor: a demo script, a scorecard and red flags
Make every vendor run your scenarios on your data, score them on weights you set in advance, and ask the questions that expose a team that has never done solar.
Will my team actually use the new system?
Adoption fails when the new system is one more screen on top of the old habits. How to design for the five tasks each role does daily, and how to roll out so the old sheet actually retires.
What a solar ERP must do: a requirements checklist for Indian EPCs
A requirements checklist built from the lifecycle, grouped into must-have, should-have and later. Use it to write your own spec before you talk to any vendor.
Solar procurement delays and BOM control: stop idle crews and surprise purchases
Late material idles crews and extra purchases erase margin. How to make the quote BOM the spine of procurement, add a material-ready gate, and see variance before the invoice arrives.
Solar ERP vs CRM plus Tally: which setup fits a solar company?
Sheets, a stitched stack of CRM, project tool and accounts software, a configured ERP, or a custom build. Four setups, when each breaks, and a rule for the order to try them in.
Serial-number and warranty tracking for solar panels, inverters and batteries
Warranty claims fail when nobody can prove which unit went where, and when it started. A simple chain from supplier invoice to customer roof, and the minimum fields to capture.
PM Surya Ghar for EPCs: tracking subsidy claims, equipment rules and paperwork
The scheme pays the customer, but rejected paperwork lands on the EPC. What the subsidy covers, what a vendor must record, and a tracker that stops claims bouncing.
Milestone billing, retention and bank guarantees in solar EPC contracts
Staged payments, retention held for a defect period and bank guarantees that expire quietly. How to track each as a dated obligation so nothing is billed late, released late or lapses.
Project-wise costing and margin for solar EPC: estimated, committed and actual
Company-level profit hides project-level losses. Three costs per project, three margins, and the weekly view that turns margin from an after-the-fact number into a steering wheel.
How do you stop double bookings when a request is retried?
Retried taps, flaky networks and two people clicking at once are normal. Idempotency keys, version-guarded writes and transactions are how a booking system survives them. With what we found in our own queue.
How to track DISCOM approvals and net metering across projects
Installation takes days. Feasibility, inspection and the net meter take weeks, and each DISCOM behaves differently. A tracker design that shows which project is waiting on whom, for how long.
Getting solar site teams to use the system: surveyors, installers and store staff
Most solar ERPs fail on the roof, not in the demo. Six field roles, the few tasks each does daily, and the design rules that stop the WhatsApp group from becoming your real system.
Should one vendor build the product and run the go-to-market?
One team for tech and go-to-market removes hand-offs, and creates a conflict of interest. When to combine, when to split, and what we do: we sell both, so read this with that in mind.
Solar O&M and AMC: turning monitoring alerts into tickets, visits and renewals
Installed systems become a recurring-revenue book only if alerts become tickets, tickets become visits and contracts renew on time. A workflow from inverter alert to AMC renewal.
Should we build custom software or buy SaaS?
A three-question test for owners deciding between buying a tool, configuring one they already pay for, and building something custom. With two of our own builds, one that stayed a spreadsheet and one that couldn't.
Can our marketing team publish without waiting on a developer?
If every blog post or page change needs a developer, content slows to the speed of the engineering queue. What a publishing setup should let marketers do alone, what should stay with developers, and the CMS we built and now run our own hub on.
Industry insights, once a month
New case studies, healthcare, marketplace, B2B SaaS and industrial breakdowns, and the engineering notes behind what we ship. One short email a month, no fluff.
We never share your data — see our Privacy Policy for details.