cpchander@dev:~/blog$ ls -lt
➜ ~ ls -lt *.mdx
# essays · technical writing · field notes
Blog
Field notes from building B2B systems — outbound infrastructure, autonomous agents, telecom architecture, SEO/GEO, founder lessons.
May 23, 2026→May 22, 2026→May 21, 2026→May 20, 2026→May 18, 2026→May 16, 2026→May 15, 2026→
Navision + Power BI: the analytics maturity journey from Excel exports to executive dashboards
How a 1,500-employee company graduated from ad-hoc Excel reports to a real BI layer — Microsoft Dynamics NAV (Navision) as the system of record, Power BI for executive dashboards across CRM, HRMS, ERP, and call-center CDR.
Email deliverability at scale: SPF, DKIM, DMARC, and 17 years of Exchange
A practitioner's guide to email infrastructure for B2B — SPF/DKIM/DMARC, Exchange to Microsoft 365 migration, anti-spam architecture, and the deliverability lessons that decide whether your sales emails land in inbox or spam.
Multi-cloud migration: 10 years moving workloads to AWS, Azure, and GCP
A practitioner's playbook for migrating on-premise workloads to the cloud — when to choose AWS vs Azure vs GCP, the migration sequence, hosting and CDN architecture, identity, security, and the cost lessons from a decade of moving 1,000+ workloads.
Scaling Virtual Employee from 60 to 1,500: 17 years of IT operations leadership
What it actually takes to build the IT systems, telecom platform, security program, and operational playbook behind a remote-staffing company that scales from 60 to 1,500 employees over 17 years.
From PAP2 to Twilio: 15 years of VoIP architecture for a remote workforce
How a remote-staffing company's telephony evolved across three generations — PAP2 ATAs, then Asterisk + OpenSIPS, then Twilio + SIP trunks — and what each transition actually taught us about scaling B2B voice.
1,200 employees, 5 days: the COVID remote-work transition playbook
In March 2020 we moved 1,200 employees from a Noida office to their homes in five days — VPN, internet, payroll, attendance, vendor payments, and every department running smoothly from day 6. Here's the operational playbook, day by day, system by system, department by department.
Three generations of HRMS: from OpenERP to a multi-tenant SaaS
What I learned across 20 years and three generations of HRMS — OpenERP (CRM + telephony + document library), a custom in-house HRMS at scale for 1,500 employees, and now a modern multi-tenant SaaS on NestJS + Prisma + Postgres with row-level security.