Who you are buying from
An engineering firm that publishes its scope and its price.
UniStack Tech has been building software out of Bengaluru since 2019. Around 40 engineers, nine practices, and one commercial rule we have never bent: if we cannot write the scope down beforehand, we do not sell it.
49
Engagements live
9
Practices
₹100
Advisory from
Bellandur, Bengaluru
One office, one payroll, no subcontracted delivery.
What we believe
Six positions we would rather be judged against.
None of these are aspirations. They are the constraints the business is built inside, and each one costs us something — which is roughly how you can tell we mean them.
A fee you can read without a meeting
Every sprint carries its number on the page. Procurement can approve it, a founder can compare it, and nobody has to sit through a call to find out what something costs.
Scope is a document, not a conversation
The deliverables are written down before money moves. That makes us slower to sell and considerably faster to build, because no one is arguing later about what "included" meant.
The people who quote are the people who build
You are told which engineers are on the sprint and what they have shipped before. They stay on it until handover. There is no bench, no swap-in, no account manager relaying questions.
Nothing is held hostage
Repositories, cloud accounts, registries, CI runners and licences are provisioned in your organisation from day one. If you never speak to us again, nothing has to be rebuilt.
Small commitments, repeated
One sprint at a time. No retainer, no minimum term, no notice period. We would rather earn the next engagement than lock in the current one.
Saying no is part of the job
If a sprint would not help, we say so before you pay and refund it if you already have. A returned order costs us less than a client explaining to their board why it was bought.
Why the company exists
The engineering was never the hard part.
Buying it was. Every founder we spoke to could describe the work they wanted in two sentences and still could not buy it in under six weeks.
Scoping happens before a sprint is listed.
Not after you have signed something.
2019 — the thing that kept happening
Our two founders had spent a decade between them inside product engineering teams and inside a large services firm. The same pattern turned up on both sides: a client wanted one bounded piece of work, and the only way to buy it was a discovery phase, a proposal, a rate card and a twelve-month statement of work.
The bet we made
Most engineering work that firms sell as bespoke is not bespoke at all. A landing zone in Terraform, a design system in Figma and code, a CI pipeline that actually gates releases — these repeat. If work repeats, it can be scoped in advance. If it can be scoped, it can be priced in public.
What we built instead
We wrote down the deliverables for each piece of work, timed it honestly against our own delivery history, put the number on the page and let people buy it the way they buy anything else. The first version of this catalogue had four engagements. It now has 49.
Where that leaves us
Around 40 engineers across 9 practices, all on our own payroll, all in India. We are not trying to become the biggest firm in Bengaluru. We are trying to be the one whose quote nobody has to interpret.
The delivery model
Five stages, and a defined end.
An engagement is a finite thing with a start date, a deliverable list and a last day. That last part is the bit most firms leave out.
You read the scope
Each engagement page lists the artefacts, the stack, the working days and the fee. What is excluded is written down as plainly as what is included.
You buy it outright
Checkout is UPI. The figure shown is the figure charged, GST already inside it. There is nothing to negotiate afterwards because nothing was left vague.
We take access, not control
A short technical brief opens in your dashboard. You grant repository and cloud access under your own organisation, and engineers are assigned within 3 working days.
We build in your workflow
Your branch protection, your review conventions, your release cadence. Named engineers, standing calls only if you want them, written updates either way.
You take handover
Code in your repositories, a written handover document, a recorded walkthrough and one revision round inside the stated window. Then the engagement ends.
Not sure which stage you are at?
Send us the problem in writing. If none of the engagements fit, we will say so rather than pick the nearest one.
Since 2019
The numbers we track internally, published as they stand.
- Sprints delivered
- 380+
- Median time to kickoff
- 72 hrs
- Post-handover rating
- 4.9/5
- Clients who book again
- 94%
Figures cover engagements closed between April 2019 and the current quarter, taken from our own delivery records. The rating comes from the post-handover form we send every client, not from a review platform.
Who runs it
Four people you can name before you buy.
Between them they sign off every scope that gets published, every date that gets promised and every refund that gets issued.
Aditi Raghunathan
Co-founder and Managing Director
Ran delivery for a payments platform before this. Owns pricing, which is why the numbers are public.
Vikram Sundaram
Co-founder and Head of Engineering
Fifteen years of platform and infrastructure work. Signs off every scope before it is published.
Nandita Bose
Practice Lead, Data and AI
Warehouses, dbt models and retrieval systems. Sceptical of any model nobody can evaluate.
Rohan Mehta
Head of Client Operations
Runs kickoff, handover and the grievance process. The person who tells you early when a date is going to move.
Names and roles are real. The portraits are stock photography standing in until our own are shot — they are illustrative and are not pictures of these individuals.
Ways of working
Commitments, not badges.
We publish the controls we actually operate. You will not find a certification logo on this site that we have not earned, and if a vendor review needs evidence, ask and we will send what we hold.
Signed NDAs and DPAs
A standard mutual NDA and a data processing agreement covering DPDP Act obligations, available before you buy or on your paper instead.
Least-privilege access
We ask for the narrowest scope that lets the work happen, time-boxed, and hand it back at handover. Credentials are never shared over chat.
Reviewed against OWASP ASVS
Anything customer-facing is checked against the ASVS level we agree upfront. Findings go in the handover document, including the ones we did not fix.
Trunk-based, gated releases
Small pull requests, required reviews, automated checks before merge. Your repository history should read the same after we leave as before we arrived.
Written handover, every time
Architecture notes, runbooks, decisions and known gaps. If your own team cannot pick the work up without calling us, the sprint is not finished.
Registered and GST compliant
A private limited company registered in Karnataka, GSTIN on every invoice, prices quoted inclusive so the invoice never surprises finance.
A closing note
We are a small firm with a narrow promise: the scope on the page is the work you get, for the fee on the page, by the date on the page.
Everything else about UniStack Tech is ordinary. We are a private limited company in Karnataka, we file our returns, we pay our engineers on the last working day of the month, and we lose work regularly to firms willing to promise more than we will. That trade is deliberate. If you would rather have a supplier who tells you when an engagement is the wrong one to buy, we are probably worth an email.
Registered office
No. 15/1 , 185/2/ 185/A, 18th Main Road, Block 9, Jayanagar, Bengaluru, Bengaluru Urban, Karnataka, 560041.
UNISTACK SOFTWARE PRIVATE LIMITED