# Services > I'm Deependra Vishwakarma, a senior software engineer based in Mumbai. I design, build, scale and secure web platforms and AI features for teams in the United States, the United Kingdom, the European Union, the UAE, Saudi Arabia, Japan and South Korea, and I plan my working day around theirs. - Page: https://deependra.in/services - Type: Services hub, 22 services in 5 lines - Last updated: 2026-11-02 - Author: [Deependra Vishwakarma](https://deependra.in/about), senior software engineer in Mumbai ## Start from a problem - I need a first version of my product. Start with [MVP Sprint](https://deependra.in/services/build/mvp-sprint) (Build line). First step: Week 1: scope. - My pages are slow and I don't know why. Start with [Performance and Core Web Vitals audit](https://deependra.in/services/scale/performance-audit) (Scale line). First step: Day 1: access and baselines. - I want an AI feature that holds up on real data. Start with [AI features in your product](https://deependra.in/services/ai/ai-features) (AI line). First step: Scoping sprint (one week). - A security questionnaire or audit is coming. Start with [Security audit and penetration test](https://deependra.in/services/secure/security-audit) (Secure line). First step: Scope. - Google and AI assistants don't find or cite our site. Start with [SEO, AIO and GEO: AI search visibility](https://deependra.in/services/scale/technical-seo-ai-visibility) (Scale line). First step: Crawl and measure. - I need an independent view before we invest, acquire or rebuild. Start with [Architecture review and due diligence](https://deependra.in/services/lead/architecture-review) (Lead line). First step: Agree the questions. ## Every service, by line 22 services in 5 lines. Each name opens its page. ### [Build: Product engineering](https://deependra.in/services/build) Web platforms and SaaS, designed and built end to end. Who it is for: Funded founders and product teams who need a first version, a new platform, or a legacy system moved to a modern stack - [MVP Sprint](https://deependra.in/services/build/mvp-sprint) (the line's usual first step): A production-grade first version of your product, at a fixed price and on dates fixed after the scoping week. - [SaaS development and web platforms](https://deependra.in/services/build/web-platforms): Custom web applications, APIs and integrations, built to be inherited. - [Legacy modernization](https://deependra.in/services/build/legacy-modernization): Move an aging system to a modern stack without stopping the business. - [Website redesign and project refactor](https://deependra.in/services/build/website-redesign-refactor): An old website or project rebuilt into a better version: a new design that works on phones, cleaner and faster code, and every old URL kept or redirected, so search visibility isn't lost. - [Laravel development and upgrades](https://deependra.in/services/build/laravel-development): Laravel applications and APIs built, upgraded and kept current by an engineer whose main stack is Laravel. - [Next.js development and migration](https://deependra.in/services/build/nextjs-development): Fast, indexable front ends: new Next.js builds, and migrations from single-page React or PHP templates without losing search traffic. - [API development and integrations](https://deependra.in/services/build/api-integrations): APIs other teams can build on, and integrations with payments, CRMs and SaaS tools that never lose data quietly. - [Custom CMS and headless content platforms](https://deependra.in/services/build/headless-cms): Editorial platforms that fit how your team actually publishes, with the old content migrated and every URL kept. - [Maintenance and support retainer](https://deependra.in/services/build/maintenance-support): Your application kept patched, current and watched, by a named engineer who knows the code. ### [Scale: Performance and reliability](https://deependra.in/services/scale) Fast under load, calm on launch day, cheaper to run. Who it is for: Teams whose pages or APIs are slow, whose launch is coming, or whose cloud bill keeps rising - [Performance and Core Web Vitals audit](https://deependra.in/services/scale/performance-audit) (the line's usual first step): Find out in five working days exactly why your application is slow, and what to fix first. - [Launch-day readiness](https://deependra.in/services/scale/launch-readiness): Your biggest day shouldn't be your first real load test. - [Cloud, DevOps and cost](https://deependra.in/services/scale/cloud-devops): Deployments you don't dread, backups you've actually tested, and a cloud bill that makes sense. - [Database design and query optimization](https://deependra.in/services/scale/database-optimization): Slow queries found and fixed, schemas that hold at the next stage of growth, and backups that have actually been restored. - [SEO, AIO and GEO: AI search visibility](https://deependra.in/services/scale/technical-seo-ai-visibility): SEO, AIO and GEO for websites and projects: pages that search engines and AI assistants can crawl, understand and cite, with the checks built into every deploy. ### [AI: Applied AI engineering](https://deependra.in/services/ai) AI features that are useful, safe and affordable in production. Who it is for: Product teams that want an AI feature that holds up on real data, or agents that act safely inside their tools - [AI features in your product](https://deependra.in/services/ai/ai-features) (the line's usual first step): LLM features that work on your real data, measured before they ship. - [AI agents and MCP servers](https://deependra.in/services/ai/agents-mcp): Agents that act in your tools with permissions, audit logs and a person in the loop. - [LLM evals, guardrails and cost control](https://deependra.in/services/ai/llm-evals): Know whether your AI feature is getting better or worse, and what it costs. - [Workflow automation and internal tools](https://deependra.in/services/ai/workflow-automation): The repetitive work between your tools, automated with code you own: CRMs, email, spreadsheets, WhatsApp and AI steps, with logs and retries. - [AI coding agents for engineering teams](https://deependra.in/services/ai/ai-coding-enablement): Claude Code and similar agents set up to ship real work in your codebase, with guardrails, tests and review rather than unreviewed pull requests. ### [Secure: Security and compliance engineering](https://deependra.in/services/secure) Find the holes before someone else does, and make the code do what the policy promises. Who it is for: SaaS, fintech and health teams facing a security questionnaire, a launch or a privacy review - [Security audit and penetration test](https://deependra.in/services/secure/security-audit) (the line's usual first step): An attacker's view of your application and infrastructure, and a fix list you can act on. - [Accessibility audit and remediation](https://deependra.in/services/secure/accessibility-remediation): WCAG 2.2 AA audits and the fixes in your code, for teams under the European Accessibility Act or asked for a conformance report. ### [Lead: Technical review](https://deependra.in/services/lead) Senior technical judgment, in writing, before you commit. Who it is for: Non-technical founders, and investors or acquirers who need an independent technical view - [Architecture review and due diligence](https://deependra.in/services/lead/architecture-review) (the line's usual first step): An independent, written view of a system: what's solid, what's risky, and what it will cost to fix. The work falls into five lines. Each one is a different kind of problem, but they share a way of working: one senior engineer who owns the result, a small fixed-price first step with a written outcome, code in your repository from the first day, and a written update every week. I've been building for clients since 2018, most recently as the senior engineer behind a media group's products, where I ran 15+ production servers across Google Cloud and AWS. If you're not sure which line fits, the first step of any of them will tell you. ## Proof, in case studies - [InfluencerX voting platform](https://deependra.in/work/influencerx-voting-platform) (Real-time voting platform): 1.6M+ users over a campaign of 22 days, with 99.99% availability. Scale and Build. - [TopGear India CMS migration](https://deependra.in/work/topgear-india-cms) (CMS migration and modernization): CodeIgniter on shared hosting to Laravel on Google Cloud; page loads went from 1–3 min → 3 s. Build and Scale. - [Zyrobe AI pipeline](https://deependra.in/work/zyrobe-ai-wardrobe) (AI wardrobe app): A phone photo to a product image in 3–8 s on average. AI. ## Further reading - [How a voting platform held up through a 22-day campaign](https://deependra.in/writing/voting-platform-22-day-campaign-architecture) (2 November 2026): The architecture behind the InfluencerX case. - [What a penetration test report contains](https://deependra.in/writing/what-a-penetration-test-report-contains) (2 November 2026): The anatomy of the report a security audit ends with, with a fictional sample finding. ## Where I work The [markets page](https://deependra.in/markets) shows our shared hours, contract terms and the data-protection rules I design for in each market. ## How engagements work Start small, then grow the engagement only if it's working. - **A fixed-price first step.** A small, bounded piece of work with a written outcome: an audit, an assessment or a scoping sprint. You see how I work before committing to more. - **A fixed-scope project.** Scope, timeline and price agreed in writing, with working software to review every week. - **A monthly retainer.** A set number of days each month for ongoing development, maintenance or performance work. Always: - Intellectual property is assigned to you on payment. - An NDA before we discuss details, if you'd like one. - A written update every week, and a demo whenever there's something to see. - Working hours that overlap yours. ## From first message to handover 1. **A conversation.** A short call or a written brief: what you need, by when, and what success looks like. 2. **A small first step.** A fixed-price audit, assessment or scoping sprint with a written outcome. It's useful on its own, whatever you decide next. 3. **Scope in writing.** Deliverables, timeline, price and what's out of scope, agreed before the build starts. 4. **Build in the open.** Working software on a staging URL, weekly updates and demos, and priorities you can change as we learn. 5. **Handover or keep going.** Documentation, a runbook and a handover session, then a retainer if you want ongoing help. --- Cite as: Deependra Vishwakarma, "Services", https://deependra.in/services (last updated 2026-11-02). This is the Markdown version of https://deependra.in/services; the page is the canonical source. Start a project: https://deependra.in/contact