Studio · Est. 2012

A small studio building AI & software for teams that ship for a living.

We're 34 people who write code, run models in production, and pick up on-call rotations. If you're looking for an agency that will hand off to a project manager after signing, we probably aren't the right fit.

Two engineers, one rented desk, and a client who needed CRM by Monday.

Rack InfoTech started in a Row House in Baner, Pune in 2012. The first project was a custom CRM for a logistics company that had outgrown four different SaaS tools and couldn't find one that understood consignment freight. We shipped it in six weeks. They're still on it.

The pattern repeated. Businesses would call us not because they wanted custom software — they hate having custom software — but because the off-the-shelf stack had failed them in some specific, expensive way. By 2019 we were shipping AI-adjacent projects: OCR pipelines, chat routing, recommendation engines. In 2022 we bet the studio on agentic AI when most of the industry was still calling it "GPT wrapper."

Today the studio is 34 people across engineering, ML, design, and delivery. We turn down about two-thirds of the projects that come in. Not because we're precious about the work — because we've learned that engagements without a clear metric to move quietly turn into consulting retainers that don't produce anything worth shipping.

We're deliberately not a hundred-person shop. Bigger studios sell bigger contracts. That has never been our game.

Mission & vision

Why we bother.

Mission

Put AI and custom software within reach of teams that don't have a research lab — startups, SMEs, and unfashionable industries that quietly run the economy.

Vision

A world where the difference between an ambitious business idea and a shipped product is measured in weeks — and the engineering doesn't feel like a compromise.

Values

Six things we won't compromise on.

i.

Ship, then iterate

Working software beats a beautiful roadmap. We'd rather explain a rough v1 than defend a polished spec.

ii.

Own the outcome, not the ticket

Our engineers care whether the metric moved. If the story is closed and the revenue isn't up, it isn't done.

iii.

No mystery meat

You get the code, the keys, the model weights, the docs. Nothing about our work is a black box you can't inspect.

iv.

Small > scaled

We staff for depth, not headcount. The founding engineers still push code.

v.

Say the honest thing

If the project shouldn't exist, we'll say so — before the contract, not after. It's cost us revenue and earned us referrals.

vi.

Boring in the right places

PostgreSQL, TypeScript, well-tested APIs. We save the exotic choices for the moments they earn.

The approach

Product engineering,
not IT services.

We think about the software the way a product team at a great startup would — because most of us used to be one. Every engagement is scoped, staffed, and measured with that in mind.

  • Small, senior team on every project — no matter the size
  • Weekly demos, not monthly status updates
  • Metrics agreed up front and reported honestly
  • Handover documentation from day one, not day 90
  • SLAs that survive contact with production
Engagement · Playbook
01
Discovery sprint
Flat fee, 5 days, ends in a written technical brief.
02
Milestone-based SOW
You approve each milestone before we start the next.
03
Weekly demo Fridays
Never surprise you. Never let a sprint drift.
04
Handover, not lock-in
Your team could take over the project on any Friday.
The people

Senior on every project.
Small enough to argue over lunch.

Every engagement is fronted by a founding engineer or a principal. The person who scopes your project ships it.

HJ
Founder · Principal Engineer
Harshal Jadhav
SN
Head of AI
Sneha Nadkarni
RM
Principal — Systems
Rahul Mehta
PT
Design Lead
Priya Tandon
VJ
Head of Delivery
Vikram Joshi
NB
Mobile Lead
Neha Bhat
KS
DevOps & SRE
Karan Singh
MI
Data & ML
Meera Iyer
Say hi

Curious how we'd approach
your problem?

Book a 30-minute call with a founding engineer. No sales team, no gate.