Websites
A site a first-time visitor can finish. Writing, structure, and the front end, checked on a phone.
farahkhanworld.com
Website designEntiko designs websites and builds the software that runs the business behind them.
You need a site that can take an enquiry, a store that can take an order, or a tool the team will actually open on Tuesday. We take that brief — however messy — to a live URL: writing, design, engineering, then the week after launch.
Entiko builds custom operations software for Indian businesses. We build custom software for any workflow.
From a messy brief to a live URL — and the week after.
- 01
Brief
Messy is fine. Who you sell to, and what has to exist.
- 02
Written
Sitemap, flows, and the list of what we will not build.
- 03
Live URL
You review the thing itself, in short passes.
- 04
Week after
The first awkward case is still the job.
Transport & Fleet Operations ERP
One loading-dock entry. The bilty, the GST invoice, diesel, driver bhatta, the market challan, and a balanced TallyPrime voucher.
One trip · bilty to Tally. Live book. Own trailer, LR-4601 · Indira Dock → Mangaon. Own container, LR-4608 · JNPT → Chakan. Market truck, LR-4614 · Mumbai → Wakad. Trip revenue ₹1,76,500. Diesel + bhatta ₹9,866. Net on trip ₹1,66,634.
Stores
Catalogue, checkout, and the screen the warehouse actually uses on a Tuesday.
thebijoubox.in
E-commerceOps software
A tool your team will actually open on Tuesday. Bilty, diesel, bhatta, and the GST invoice from one entry — this crop is the sample book, not a customer account.
Transport ERPSoftware we build
Entiko builds custom operations software for Indian businesses. We build custom software for any workflow.
01
Bilty, diesel, driver bhatta, GST freight, and a Tally export for one fleet.
02
Demo · Malwa Traders
Kirana & distributor billingMalwa Traders, Indore, still writes the beat in a notebook and types the GST bill again at night.
03
Demo · Asha Diagnostics
Clinic & lab deskAsha Diagnostics, Kothrud, takes bookings on WhatsApp and then cannot say which report is ready.
04
Demo · Vedanta Classes
Coaching fees & attendanceVedanta Classes, C-Scheme, marks the roll on paper and chases fees in a parents’ WhatsApp group.
05
Demo · Kulkarni Furniture Works
Workshop job cardsKulkarni Furniture Works, Nagpur, writes the job on a slip, so dispatch day and the balance never match.
06
Demo · Mehta Rentals · Shanti Society
Rental & maintenance collectionsShanti Society and Mehta Rentals, Ahmedabad, share one book: who paid, and who only promised on WhatsApp.
07
Demo · Ruchi Textiles
Accounting & GST filingRuchi Textiles, Surat, pays about ₹2,500 a month for someone to type the same invoices into Tally and file the return.
The trip sheet, in the sample book.
Open the Transport ERPTaxable freight, kilometres, and driver bhatta from the three trips on the product page. ₹/km is taxable divided by km. Nothing here is a client result.
| LR | Kind | Route | km | Taxable ₹ | ₹/km | Bhatta ₹ |
|---|---|---|---|---|---|---|
| LR-4601 | Own trailer | Indira Dock → Mangaon | 174 | ₹1,72,000 | ₹989 | ₹3,400 |
| LR-4608 | Own container | JNPT → Chakan | 138 | ₹1,48,000 | ₹1,072 | ₹2,500 |
| LR-4614 | Market truck | Mumbai → Wakad | 620 | ₹2,10,000 | ₹339 | ₹0 |
What this studio is for
One company for the public face and the operating system. You review a URL. You own the code when we are done.
The public face
Information architecture, writing, design, and front-end build. Marketing sites, brand sites, and stores — structured so a first-time visitor knows who you are and what to do next. SEO, sitemap, and analytics ship with launch.
- Multi-page sites, not a single scroll pretending to be a company
- Copy and layout that match how you actually sell
- Checked on real phones, not only a designer’s laptop
The operating system
Custom tools for stock, jobs, bookings, catalogues, and the unglamorous middle. We map how the week already runs, then encode it — portals, dashboards, WhatsApp-aware flows, and care after go-live.
- Internal tools the staff will actually open
- Payments, chat, maps, and the systems you already pay for
- You own the repositories and the credentials
Who we work with
Not a jewellery-only studio. Consumer brands, manufacturers, schools, hospitals, operators, media houses — anyone who needs a serious website or a system that has to survive a real week.
01
Retail & D2C
Brands that sell on a phone: catalogues, stories, checkout, and the ops behind the order.
02
Industry & manufacturing
Job tickets, inventory, vendor portals, and the shop-floor truth that ERP never quite captured.
03
Education & institutions
Admissions, programmes, content, and the internal tools staff use between terms.
04
Operations & logistics
Bookings, dispatch, status, and the customer-facing page that must not lie about it.
05
Professional & healthcare services
Clinics, consultants, practices — enquiry, scheduling, records with the care they require.
06
Media, events & hospitality
Calendars, listings, ticketing-adjacent flows, and sites that have to look expensive at 11pm.
The hard parts are the point.
A world-class studio is not a list of buzzwords. It is whether we can hold checkout, inventory, auth, integrations, and a public site in the same head.
Stores that survive an Indian checkout
Not a theme with a logo swapped in. Catalogues that hold thousands of SKUs, collection logic a merchandiser can run, UPI and cards, COD with the fraud rules you actually use, GST-ready invoices, WhatsApp order updates, and a warehouse view that does not require a second spreadsheet.
- Configurable catalogues, variants, lookbooks, and editorial merchandising
- Checkout, refunds, partial fulfilments, and pincode-aware shipping
- Staff tools for stock, returns, and the 6pm rush
The unglamorous systems that make the week work
If the business still lives in WhatsApp groups and three Excel files that disagree, we map the week as it really happens, then encode it. Job cards, bookings, inventory, approvals, client portals — with roles, audit trails, and a first slice that is usable instead of a two-year wait.
- Role-based access, activity logs, and credentials you own
- Workflows with statuses, SLAs, and the exceptions the floor already knows
- Phased delivery: one working loop, then the next
Payments, chat, maps, sheets, and the tools you already pay for
Most “custom software” fails at the seams. We wire Razorpay or the gateway you already have, WhatsApp Business flows, Google Maps, email, and the sheets or ERPs the accounts team will not give up — so the new product does not become another island.
- Payment webhooks that reconcile instead of hoping
- WhatsApp and SMS as first-class channels, not a widget
- APIs, webhooks, and exports your next vendor can read
Marketing sites built like products
Information architecture, writing, design, and engineering as one pass. Multi-page structures search engines can crawl, motion that does not tank a mid-range Android, CMS your team can edit, analytics from day one, and a live URL you review — not a deck that still needs a developer.
- Next.js-class front ends: fast, structured, deployable
- SEO foundations, sitemaps, redirects, and metadata that are not an afterthought
- Design systems so page 24 still looks like page 1
Dashboards and catalogues people will actually open
Filters that remember, tables that do not die at 50,000 rows, search that understands the way your staff name SKUs, maps of jobs in the city, calendars that conflict-check. The hard part is not drawing a chart. It is making the person on the floor faster than they were in Excel.
- Search, bulk actions, saved views, and keyboard-speed admin
- Realtime or near-realtime where the floor needs it
- Mobile-first ops screens, not a desktop tool squeezed onto a phone
Automation where it earns its keep
Drafts, classification, routing, and summaries on top of a real database — not a chatbot taped to a brochure. We use models where they cut a human loop (intake, tagging, first-pass copy, exception flags) and keep a person in charge of the decision that can cost money.
- Structured intake instead of a free-text black hole
- Assistive generation with review, not unsupervised publish
- The same auth, logs, and ownership as the rest of the product
01
Website design
Multi-page sites with a clear story, a usable structure, and a path to enquiry or purchase.
02
Software development
Custom web software and APIs — the systems spreadsheets and WhatsApp groups cannot hold anymore.
03
Mobile apps
Android and iOS products that live in the pocket — native or one codebase, in the stores, with a release train.
04
E-commerce
Stores that sell the way your customer actually buys — catalogues, UPI, COD, WhatsApp, and the ops behind the order.
05
Brand & UX
The system behind the screens: how it looks, how it reads, and how a first visit feels competent.
Problems we like walking into
If one of these is the week you are having, we are the right call. If you need a logo animation and nothing else, we are not.
01
The brand is sharp. The website is not.
Visitors cannot tell what you sell, who it is for, or what to do next. We rebuild structure, writing, and the interface until the first screen does the job.
02
WhatsApp is still the operating system.
Orders, jobs, and approvals live in chats that vanish. We move the loop into software the team will open — and keep WhatsApp as a channel, not the database.
03
Two vendors, two versions of the company.
A site from one team and a tool from another. We hold both: the public face and the system behind it, in the same language.
04
The catalogue outgrew the theme.
Filters break, stock lies, checkout fails on COD. We treat commerce as software — not as a template with apps piled on.
How you work with us
You do not get a 40-page process diagram. You get a written brief, a named owner, and a URL that updates in short passes. Discovery is conversation. Build is the product. After launch we stay for the awkward cases — that is the job, not a surprise invoice. The longer version lives on Approach.
From brief to the week after.
Four steps. The week counts are the ones we already publish — a two-week map, six to ten weeks for a site, eight to twelve for a store, and the week after launch.
01
Discovery
2 weeks
Who the customer is, what must happen this week, and what “done” means. We write that down before we design. If the brief is still a feeling, we will not pretend it is a specification. The map, before anyone decorates a page.
- A conversation with the people who sell, pack, or support — not only the founder
- A written brief you can correct, including what we will not do
- How the week already works: chats, sheets, the person who knows the exception
02
Structure
Before build
Sitemap, flows, and copy. You see the skeleton while it is still cheap to change. Decoration waits. Named pages and flows, while a change is still cheap.
- Pages and screens named, in order, with a job for each
- Headlines in your language, not lorem
- A choice of stack written down — Next.js, Shopify, native, RN — with reasons
03
Build
6–10 weeks for a site. 8–12 for a store.
You review a live URL (or a TestFlight / internal build) in short passes. Feedback lands on the product, not in a forgotten thread. Software is phased after the two-week map. A first slice the floor can open, then the next loop.
- Staging you can share with legal, merchandising, or the floor
- Decisions recorded so the next week does not re-litigate the last
- A named owner on our side who actually answers
04
Aftercare
The week after launch
Launch is a beginning. We tighten copy, fix the awkward cases, and stay reachable. The first broken form and the first “can we add a page” are part of the job. The first broken form is in the brief, not a surprise invoice.
- Credentials, CMS guide, and repositories in accounts you own
- The first production nits included — not a surprise invoice
- A care arrangement if you want one; handover if you do not
Live sites.
The roster is the URL. We do not print a result we cannot show you.
Questions teams actually ask
Do you only design websites, or do you also build software?+
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.
What languages and stacks do you actually ship in?+
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.
Can you build Android and iOS apps, not only a website?+
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.
We already have a WordPress / Shopify / custom site. Do you take that over, or start again?+
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 the working week does not break. We do not pretend a rebuild is cheaper when a repair will do.
What about payments, UPI, COD, and GST?+
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.
Will the website be fast on a mid-range Android, and will Google find it?+
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.
Who hosts it, and can our team edit pages without calling you?+
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.
How do logins, roles, and data work in the software?+
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.
Can you connect WhatsApp, maps, sheets, and the tools we already pay for?+
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.
How long does a website take versus a piece of software?+
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 the work already runs, 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.
Who owns the website or software after launch?+
You do. Repositories, domains, and credentials sit with the client. We are not a hostage vendor.
What happens after go-live — bugs, new pages, a festival rush?+
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.
How do you make sure our requirement does not get lost?+
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.
Can you work from our existing brand, or do we start from zero?+
Either. We inherit a strong brand with respect. Where there is none, we establish a tight visual and verbal system before we scale pages.
Where are you based?+
Entiko is a Mumbai studio. We work with clients across India.
How do we start?+
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.
Tell us what has to exist. We will tell you if we are the studio for it.
hello@entiko.co.in · +91 99879 11330 · Mumbai
Who you sell to, what must ship, and any hard date. A yes, a no, or a tighter question — not a pitch deck.