Practical notes from the engineers who build agents, copilots and AI products.
Personalised messaging injects per-user picks and timing into your existing email and WhatsApp tools, tested against a control. Personalised marketing AI does not replace your campaign platform; it decides what each customer receives, when, and on which channel, and hands those decisions to the tools you already use.
Only a held-out control group proves lift; before-and-after comparisons are confounded by season, campaigns and traffic mix. Personalisation A/B testing randomises users into treatment and control, fixes the metric and sample size in advance, and reports lift with its uncertainty so finance believes it.
Personalisation sequences lessons or onboarding steps per user based on progress and behaviour, raising completion and activation. Personalised onboarding replaces one fixed path with a next-step model that reads what each user has done, chooses what to show next, and is measured against a control.
Permission-aware retrieval enforces document ACLs at query time so users only receive content they are allowed to see. The entitlement check runs in the retrieval layer before ranking, never in the prompt, and is proven with negative tests where a named user must not receive a named document.
Load-test to peak, cache aggressively, queue writes and rehearse the day; the sale is the design load. Peak-season readiness means treating the busiest hour of the year as the number your architecture is built for, proving it with a rehearsal weeks before, and having a runbook for the moment something still breaks.
Design and load-test for month-end and festival peaks, not average days; queues, caching and autoscaling are non-negotiable. Indian consumer apps spike on salary days, sale events and match nights, so the architecture must absorb bursts, shed load gracefully and be rehearsed under test before the real day.
Integrate UPI intent and collect flows, cards and wallets through a gateway, with webhooks and reconciliation on the backend. The app collects the payment attempt and shows status; the backend creates orders, verifies webhooks, decides success and handles refunds. Getting that split right is most of the work.
Patient data needs consent, retention rules, role-based access and audit logs, with models deployed inside the provider's environment. The DPDP Act sets consent and purpose rules, ABDM sets the consent architecture for sharing, and hospital governance sets retention and access; an AI system must satisfy all three.
India now offers senior AI engineering at fixed prices with global time-zone cover; evaluate on evals and ownership, not on rate cards. The old offshore model of billing hours for junior teams still exists, but the firms worth hiring sell outcomes, run evaluation suites and hand over everything they build.