Entiko designs websites and builds the software that runs the business behind them.

Both, as one practice. Many clients need a public site and an internal tool. We keep the language, data, and design system aligned so the company does not feel like two vendors met in the parking lot.

Websites and web software: TypeScript, JavaScript, React, Next.js, Node. Backends and services also in Python, Java, Go, PHP, and SQL where that is what the system needs. Mobile: native Android (Kotlin/Java) and iOS (Swift), plus React Native or Flutter when one codebase is the right call — not as a default slogan.

Yes. Native when the product needs the platform (camera, payments, offline, performance). React Native or Flutter when the same product has to ship on both phones without two full teams. We will say which, and why, before you pay for the wrong one.

Either. If the bones are sound we extend them — CMS, checkout, speed, SEO, a new front end on the same catalogue. If the theme is the constraint, we migrate: content, redirects, payments, and the staff login, so Tuesday does not break. We do not pretend a rebuild is cheaper when a repair will do.

Indian checkout is part of the product, not a plugin afterthought. Razorpay or the gateway you already have, UPI, cards, COD with the fraud rules you actually use, refunds, partial fulfilments, and invoices that accounts can live with. Webhooks that reconcile — not a spreadsheet hoping they match.

That is the job. Structured pages, sitemaps, redirects, metadata, Core Web Vitals that hold up on Indian networks — not a designer’s laptop on office wifi. Analytics ship at launch. We do not leave SEO as a phase-two slide.

Hosting sits in accounts you own — typically Vercel, AWS, or the stack your IT already runs. The CMS is for your team: pages, products, jobs, posts. We train the people who will actually type into it. We are on the hook for the awkward cases after launch, not for changing a comma.

Named users, roles, and an activity log. Staff see what their job needs; they do not all get the production database. Credentials and repositories sit with you. If you already have Google Workspace, WhatsApp Business, or an ERP, we integrate — we do not invent a second identity system for sport.

Yes. That is usually where custom software dies. WhatsApp as a channel (not the database), Google Maps, email, Razorpay, and the sheets or ERPs accounts will not give up. APIs and exports your next vendor can read.

A serious multi-page site is weeks, not a weekend, once the sitemap and copy are honest. Software is phased: a two-week map of how Tuesday already works, then a first slice the floor can open, then the next loop. We will not quote a single date for “an app” until the first loop is named.

You do. Repositories, domains, and credentials sit with the client. We are not a hostage vendor.

Launch is not the end of the brief. We stay for the cases that only appear in production: a payment that fails on one bank, a SKU the merchandiser added wrong, a page that must exist by Friday. Care is scoped, not a surprise invoice. If you need a 24/7 NOC, we will say so — that is a different product.

Every engagement has a written brief, a named owner on our side, and reviewable builds. Decisions are recorded. If something is unclear, we stop and ask — we do not invent a requirement to keep the timeline pretty.

Either. We inherit a strong brand with respect. Where there is none, we establish a tight visual and verbal system before we scale pages.

Entiko is a Mumbai studio. We work with clients across India.

A short written brief — who you sell to, what must exist, and any hard dates. We reply with whether we are the right studio and what the first two weeks would look like.