Request a callbackBook a call
AI data analyst

AI Data Analyst in Mumbai

The best AI Data Analyst in Mumbai, at the best available price.

$0 upfrontPay per accepted checkpointSenior engineer, no agency markup

Your team asks in English. The service finds the tables, writes the SQL, runs it against a read-only replica inside your own cloud, and returns the number with the query attached. It cannot touch a table whose schema it has not just read, and that is enforced in code rather than requested in a prompt. Starts at $0: you pay at checkpoints you accept.

Mumbai is India's financial capital, home to the RBI, SEBI, the NSE and the BSE and to the head offices of many large banks, insurers, brokers and asset managers, with film, television and streaming as its other defining industry. Software sold here almost always passes through an information security review shaped by those regulators, and the person signing off is as likely to be a risk officer as a technologist.

Finance, operations and risk teams here run on daily reports pulled from core systems. A read-only analyst on a replica answers ad hoc questions in plain English with the SQL shown, which a compliance reviewer can check before anyone relies on the number.

What you get

  • Deployed in your own cloud account against a read-only replica you create, so we never hold a credential to your database
  • A signed schema check the model cannot skip: no SQL runs against a table it has not just inspected, and the tokens expire in fifteen minutes
  • A grant list your data owner approves, naming the exact tables and columns the analyst may read, with everything else refused at the database
  • Exposed inside Claude or ChatGPT in your organisation's workspace, behind your existing Google sign in, so nobody learns a new interface
  • Every question logged with the SQL it ran, the tables it touched and whether it errored, which is what an auditor actually asks for
  • Runs on a private LLM on your own hardware where data security demands it, up to fully air-gapped, so nothing at all crosses your perimeter
Builds from $6,000. Assessment fixed fee, credited in full.

No payment before a checkpoint is delivered and accepted. Most builds land between $6,000 and $18,000 depending on how many databases are in scope and how much of the schema the first domain covers. Optional upkeep from $1,200 a month, and only if you want it.

Invoiced in INR, with GST as applicable.

Request a callback

You speak to the engineer who does the work. No sales rep, no deck.

No spam and no sales team. You talk directly to Neeraj.

Mumbai, Maharashtra

Who builds here

Banking, insurance and capital markets around BKC and Nariman PointThe broking, wealth and asset management industryFilm, television and streaming productionIIT Bombay and the Powai startup cluster
Best fit in Mumbai

On-Premise LLM Deployment

Mumbai's banks, brokers, insurers and the vendors that sell to them are the buyers most likely to reject a product because prompts leave for a third-party model API. Running inference inside their own Indian cloud region or data centre removes the objection that most often stalls the deal.

Try a question
1Question

How many free signups from June converted to paid, by week?

2Schema read
customers

plan tier is a column here, not a separate status table

subscriptions

one row per plan change, so take the first paid one

Schema proof issued, expires in 15 min
AQIAaPr2xQAAAACqL3d1Zw
3Verified SQL
SELECT DATE_TRUNC('week', s."startedAt")
         AS "Week",
       COUNT(DISTINCT c.id) AS "Converted"
FROM   customers c
JOIN   subscriptions s
         ON s."customerId" = c.id
WHERE  c.plan = 'free'
  AND  s.plan = 'paid'
  AND  c."createdAt" >= DATE '2026-06-01'
  AND  c."createdAt" <  DATE '2026-07-01'
GROUP  BY 1 ORDER BY 1
WeekConverted
2026-06-01214
2026-06-08188
2026-06-15243
2026-06-22201

Stage three refuses to run unless it is handed a valid token from stage two for a table in the query. The model cannot skip the schema read, because the check is a signature in code rather than an instruction in a prompt.

Architecture diagram of an AI data analyst that can only read: a question asked in Claude or ChatGPT goes to an MCP server running in your cloud, through a semantic layer of your metrics and definitions, into generated SQL, then a validation step that enforces read-only access, row limits and cited numbers, before it reaches a read-only replica. The answer returns with the numbers cited, and a write is refused by the database itself.
Every answer comes from a read-only replica through a validated query, with the numbers cited.
How you pay

Get it built at $0.

That is not a discount. It is when you pay. The work is split into checkpoints with acceptance criteria written down before anything starts, and each checkpoint is invoiced only after you have seen it and accepted it. No deposit.

$0 to start
You hold every dollar until a checkpoint is delivered and you accept it. No approval, no invoice.
Fixed cost, unlimited features
Or hire the team outright: one fixed monthly cost, unlimited feature development, any stack.
The engineer takes your call
The person on your first call is the one who architects and writes it. No account managers, no bench time.

A US agency quotes $50,000 to $150,000 for the same build and asks for 40 to 50% of it before a line is written. Account managers, project managers, sales commission and bench time. None of it appears in your product.

How it works

Three stages, nothing hidden.

01

Fixed-fee assessment

Five business days from the day read-only access is in place. Schema inventoried, the questions your team actually asks classified as answerable or not, the grant list drafted with whoever owns data protection, and acceptance criteria written as testable statements.

02

Build in checkpoints

About three weeks. Deployed in your cloud account, connected to your replica and to your assistant workspace, with the semantic layer written for the first domain. Each checkpoint has criteria agreed before work starts and is invoiced only once you accept it.

03

Handover and closeout

A real question from your team, answered end to end, with the SQL shown and the numbers reconciled against the source rows. Runbook, recorded handoff, code and semantic layer in your repository, and all our access removed with written confirmation.

Working in Mumbai

What actually applies here.

Regulation and data

The DPDP Act 2023 sits on top of sector rules that matter more day to day here. RBI-regulated entities follow its 2023 Master Direction on outsourcing of IT services, which requires audit and inspection rights over vendors and incident reporting within hours, and its 2018 direction that payment system data be stored only in India. SEBI's Cybersecurity and Cyber Resilience Framework, issued in August 2024, applies to brokers, depositories, asset managers and other regulated entities, though its data localisation requirement was put in abeyance in December 2024. Insurers follow IRDAI's Information and Cyber Security Guidelines, 2023. Maharashtra's IT and ITeS Policy, 2023 gives data centres essential service status, and Navi Mumbai has become one of the country's main data centre locations.

Contracting and payment

Simple domestic contracting. Invoices in INR with GST as applicable, under a standard services agreement. No cross-border payment friction, no forex conversion cost, and no time spent on paperwork for an overseas supplier.

Working hours

Same time zone. I work from India on IST, so calls, reviews and replies all happen inside your normal working day.

Can you work within RBI or SEBI vendor requirements?

Yes. That means completing your vendor risk assessment, agreeing audit and inspection rights in the contract, working through named, limited-privilege access, and keeping data in Indian regions of your own accounts. Your compliance team decides how the engagement is classified under your outsourcing policy.

Does SEBI's framework require data to stay in India?

CSCRF originally included a localisation requirement, but SEBI put it in abeyance in December 2024 pending further consultation, so check the current position with your compliance team. We deploy into Indian regions by default, which keeps you covered if the requirement returns.

Do you work with media and production companies?

Yes. Typical projects are transcription and subtitles, search over footage and script archives, and internal tools for scheduling and rights tracking. Content stays in your own storage, and nothing is sent to a model provider you have not approved.

We already have a BI tool. Does this replace it?

No, and it should not. Your dashboards answer the questions somebody anticipated, and they will keep doing that. This answers the ones nobody built a chart for, which is where the waiting happens. Teams that keep both end up using the dashboards for the standing numbers and the analyst for everything else.

How long before somebody can ask a real question?

Usually inside the first week of the build, on a narrow slice of the schema. The first domain being useful early is the point of doing it in checkpoints: you see it working on your own data before most of the money is committed.

What if our schema is a mess?

Most are, and it changes the shape of the work rather than ruling it out. Undocumented columns, legacy tables nobody dares delete and two spellings of the same idea are normal. The assessment tells you plainly how much of that has to be untangled first, and if the answer is that you need a data cleanup before an analyst is worth building, you will be told that instead of sold this.