Business analyst in Indian IT services vs product companies
In this article (10 sections)
- Two jobs sharing one title
- A services BA's week
- A product BA's week
- The artefact both kinds of BA write: a testable user story
- What each context measures
- Delivery managers, product owners and clients
- BA versus the titles it is confused with
- BRD, FRD and SQL: phrases that reveal the flavour
- A first quarter on a project versus in a squad
- Product owner, pre-sales or product analyst
Related programme: the Data Analytics with Generative AI course (3–4 months; ₹90,000 (inclusive of GST) · EMI from ₹4,000/month).
In an Indian IT services company, a business analyst mostly translates a client's needs into requirement documents, user stories and acceptance criteria, then manages sign-offs and changes. In a product company, the same title usually means someone who uses data and user research to decide what gets built next, and writes much more SQL. Read the posting to find out which one you are applying for.
Two jobs sharing one title
| Aspect | IT services / consulting | Product company |
|---|---|---|
| Your "customer" | An external client with a contract | Internal product team and end users |
| Main output | BRD, FRD, user stories, traceability matrix | Analyses, specs, prioritised backlog inputs |
| Change control | Formal change requests; scope affects billing | Informal; priorities shift by sprint |
| Data work | Validating migrations and reports | Funnels, cohorts, feature usage |
| Typical tools | Jira, Confluence, Visio, Excel, sometimes SQL | SQL, a product analytics tool, Jira, spreadsheets |
| Success means | Client signs off, UAT passes, few defects from unclear requirements | The right thing gets built and metrics move |
Neither is better. They reward different habits: precision and documentation on one side, quantitative judgement on the other.
A services BA's week
Imagine you are the BA on a hypothetical project to digitise a bank's branch account-opening form for an overseas client, with the delivery team in Bengaluru.
- Monday: requirement workshop with the client's operations team over a video call; capture the current process, including the paper steps nobody mentioned in the RFP.
- Tuesday: write six user stories and walk the developers through them.
- Wednesday: the client asks for a new field for nominee details. Log it as a change request, estimate impact with the tech lead, and route it to the project manager.
- Thursday: update the requirements traceability matrix so each story links to test cases.
- Friday: support UAT; triage three defects into "bug", "requirement gap" and "change".
A product BA's week
Now imagine a BA at a hypothetical Indian fintech app.
- Monday: pull last week's KYC completion by step with SQL; the selfie step's drop-off rose.
- Tuesday: read 40 support tickets tagged "KYC failed" to see what users actually experienced.
- Wednesday: write a short problem statement and two options for the product manager.
- Thursday: define how success will be measured if option A ships.
- Friday: sprint review; check the event tracking for the new flow before release.
The artefact both kinds of BA write: a testable user story
The story below is the format that earns trust in either setting, because a developer can build it and a tester can verify it without asking the BA again.
Story: Save a partly completed account-opening form
As a branch officer
I want to save an incomplete application and resume it later
So that a customer who lacks one document does not have to start again
Acceptance criteria
Given an application with mandatory personal details filled
When the officer selects "Save draft"
Then the draft is stored with status DRAFT and a reference number is shown
Given a saved draft older than 30 days
When any officer opens the drafts list
Then the draft is not shown and is marked EXPIRED
Given a draft created by officer A at branch 101
When officer B at branch 205 searches for it
Then the draft is not returned
Out of scope: customer self-service resume; document upload in draftsThe "out of scope" line is the one services BAs learn to write first, because every missing exclusion eventually becomes an argument about billing.
What each context measures
Services BAs are judged on requirement stability (how many change requests trace back to something that should have been captured), defects classed as requirement gaps, sign-off turnaround and client feedback. Product BAs are judged on whether their analysis changed a decision, the quality of success metrics defined before launch, and whether shipped features moved those metrics.
Delivery managers, product owners and clients
In services, you usually report to a project or delivery manager and work with the client's business users, the tech lead and QA. In a product company, you often report to a product lead or analytics manager and work with product managers, designers, engineers and support.
BA versus the titles it is confused with
In services, BA is confused with project manager: the PM owns timeline, budget and staffing; the BA owns what is being built. In product firms, BA is confused with product analyst and product manager. A product analyst is more purely quantitative; the PM owns the decision the BA informs.
BRD, FRD and SQL: phrases that reveal the flavour
- "Elicit requirements, prepare BRD/FRD, conduct UAT" — services BA.
- "Domain knowledge in BFSI/insurance/healthcare" — services BA on a domain account; the domain matters more than tools.
- "CBAP/ECBA preferred" — services environment where formal BA practice is valued.
- "Strong SQL, work with product and growth teams" — product BA, close to product analyst.
- "Define KPIs, analyse user behaviour" — product BA with analyst expectations.
A first quarter on a project versus in a squad
Services: learn the client's process better than the client's newest employee, then own one module's requirements end to end. Product: learn the event data and definitions, and deliver one analysis that the product manager acts on.
Product owner, pre-sales or product analyst
Services BAs move to senior BA, product owner, pre-sales consultant or project manager. Product BAs move to product analyst, product manager or data analyst roles. Adding SQL and a BI tool keeps both doors open; the Data Analyst programme teaches those alongside stakeholder communication, live online with optional Noida labs.
Frequently asked questions
Does a business analyst in an IT services company need SQL?
Often less than in a product company, but it helps. Services BAs mainly write requirement documents, user stories and test scenarios. SQL becomes useful when validating data migrations or checking that a delivered report matches the requirement.
Can a business analyst become a data analyst?
Yes, and it is a common move. The BA already understands processes and stakeholders; adding SQL, a BI tool and basic statistics turns that understanding into measurable analysis.
Pankit Kumar has 10 years in Data Science & AI, building and shipping production systems in regulated pharma and clinical environments. He is a freelance trainer at Boston Institute of Analytics, AnalytixLabs and Scaler, and has taught this material to thousands of working professionals.
This article is part of our Data Analytics with Generative AI programme — 3–4 months. The full analyst stack — Excel, SQL, Power BI and Python pipelines — then a generative-AI layer you can prove is right.
Explore Data Analytics with Generative AI