Illustration of FSMIA specialists collaborating on a project
Roles

Who does what on a typical FSMIA build

Not every project uses every role. A ₹999 banner does not get a mobile architect. An app MVP does not skip design. The owner decides the mix after discovery.

Project owner

Single inbox for dates, invoices, Figma or staging URLs, and “is this in scope?”. They do not disappear after the advance is paid. Escalations (hosting down, payment gateway fail) go here first.

Web engineers

Laravel, PHP and WordPress. They implement pages, admin, APIs and Indian payment flows as scoped. They also apply on-page SEO basics so the site is not a blank theme at handover. More: website development.

Mobile engineers

Android, iOS or a cross-platform MVP: screens, APIs, admin, and store listing support when the plan includes it. They do not promise App Store approval dates — Apple and Google review queues are outside our calendar. More: app development.

Design

UI/UX for web and app, plus campaign graphics (banners, sliders, brochures). Design is approved before heavy engineering so we do not “code first, look later”. More: graphic design.

SEO / search

Technical checks, Google Business, on-page fixes, and monthly programmes when you buy a retainer. They will tell you if the current CMS cannot rank. More: SEO.

QA

Phone and desktop checks on forms, payments and broken links before go-live. QA is not a separate company; it is part of delivery. Critical bugs in the warranty window come back to the same owner.

Communication

How you will actually talk to us

Default channels: email, phone, and WhatsApp for short updates. Video calls for kick-off, design review and launch. We work IST. We do not staff a 24/7 live chat with senior engineers; we do accept tickets and calls for live incidents on sites we maintain.

If you require Slack-only, Jira-only, or US-hours overlap, say so in the brief — we will confirm whether we can meet it before you pay.

Hiring

Want to join, not buy?

When we hire, listings go on careers with a real inbox ([email protected]). We do not run a fake “we are always hiring 50 roles” banner.

Clients who need extra hands inside their company are looking for staff augmentation — that is not our default product. We will say so rather than pretend a website package is a dedicated squad.

Team FAQ

Questions about people and access

Company history and office: about FSMIA. Whether we are the right vendor size: why choose us.

You have a dedicated project owner — one person accountable for dates and scope. On small design jobs that person may also be the designer. On larger builds they coordinate engineers and SEO. You are not passed to a call centre.
Yes. Kick-off is a call (or an office visit in Sector 132) with the people who will touch the work. We will not invent a “pre-sales architect” who never appears again.
The previous template used dummy names. Publishing fake leadership is worse for SEO and for trust than publishing roles. Named introductions happen when you are a real buyer or a candidate.
Warranty and retainers stay with FSMIA. The same owner is the default. If someone leaves the company, you get a handover, not silence.
Not through a website package. Full-time hiring is a job offer via careers, or a separate commercial discussion we may decline.
Calls can be Hindi or English. Product UI language follows the copy you approve. Legal pages should be reviewed by your counsel if they are bilingual.

Meet the owner on a short call

Share the product and the first-release list. We will tell you which roles the job actually needs.

Tools and ad platforms we implement with (not a client-logo wall)