Frequently asked questions

It starts with a free 30-minute consultation — a genuine conversation about the problem, not a sales script. If it looks like a fit, we propose a paid discovery phase of one to three weeks that produces an architecture, a delivery plan and a costed estimate. That output belongs to you whether or not you continue with us, which keeps the incentive on getting the analysis right rather than on winning the build.

Our smallest engagements are typically a two-to-three week discovery or a focused technical assessment such as an architecture review or a security posture assessment. For build work, the smallest sensible unit is a dedicated squad for one quarter, because anything shorter tends to end before the system reaches the state where it can be handed over safely.

Yes — a significant share of our work is embedded alongside client engineering teams. We adopt your process, your tooling and your standards, and we build knowledge transfer into the engagement deliberately rather than leaving it to osmosis. Staff augmentation is a formal engagement model for exactly this, and many clients start there before moving to a dedicated squad.

Fixed scope suits bounded, well-understood deliverables where budget certainty matters more than flexibility. A dedicated team suits multi-quarter product work where scope will legitimately evolve. Time and material suits genuine R&D. Managed delivery suits organisations without in-house delivery management. We will recommend the model that fits the work, including when that means a smaller commitment than you asked about.

Discovery runs one to three weeks. Design adds two to four. A first production release typically lands four to six weeks after build starts, with full delivery ranging from three months for a focused system to twelve or more for a platform programme. We deliver in thin, reversible slices specifically so you see production value early rather than waiting for a single large release.

On dedicated-team and time-and-material engagements, changing priorities is the normal operating mode — you reprioritise the backlog at each sprint boundary. On fixed-scope engagements, changes go through a written variation with a cost and schedule impact stated before anyone starts. We do not charge a change fee for clarifying something we should have asked during discovery; that was our omission, not your change.

A shared board and repository you have access to at all times, a sprint demo every two weeks that stakeholders attend, a written weekly status, and monthly steering with the delivery lead. DORA metrics and burn-up charts are on a dashboard rather than in a summary. If a date is at risk you hear it in the week we identify it, not in the week it slips.

Every engagement includes 30 days of hypercare with the delivery team on standby and heightened monitoring. After that you can take the system in-house — we hand over source, infrastructure code, runbooks and documentation, and run structured handover sessions — or move onto a managed support tier from Essential through to 24/7 Enterprise cover.

You do, completely and on every engagement. Source code, infrastructure definitions, designs, documentation and any models we train for you transfer to you. We do not license our work back to clients and we do not retain rights in what you paid us to build. Our retention comes from results; building in dependency would be a worse business for both of us.

Against your constraints, not our preferences: the skills your team already has or can hire for locally, your existing platform commitments, the regulatory environment, and the operational maturity required to run it. We document the trade-offs in an architecture decision record so the reasoning survives after the people who made it move on. If your team is strongest in .NET, we will not propose Go because it is fashionable.

Usually, and it is often the better answer. The strangler-fig pattern lets you build new capability around an existing system and migrate domain by domain, so value arrives continuously and there is never a single high-risk cutover. We have put API and event layers over systems more than twenty years old that let the digital roadmap move at a completely different speed from the core.

Yes — retrieval-grounded assistants, copilots, document processing, forecasting and agentic automation. Every AI system ships with four documented answers: what data it can access, who sees its output, what happens when it is confidently wrong, and how a human overrides it. We also build a ground-truth evaluation set before we build the system, because without one you cannot distinguish improvement from change.

Security is a workstream from day one: threat modelling in design, secrets management and dependency scanning as blocking pipeline gates, penetration testing before launch, and encryption in transit and at rest as a baseline. We hold ISO 27001 alignment across our own delivery and prepare client systems for SOC 2, HIPAA, PCI-DSS, GDPR and India's DPDP Act with control-mapped evidence packs.

Wherever your regulatory and commercial requirements dictate — we architect for data residency explicitly. For Indian entities that usually means an India region on your chosen cloud; for EU data it means EU regions with transfer safeguards documented. On AI engagements we deploy models on private endpoints inside your own cloud tenancy where residency requires it, so content never crosses the boundary.

The minimum required, granted just in time and expiring by default. We work through your identity provider wherever possible so access is visible in your own logs and revocable by you at any moment. Every Mits engineer works under a signed NDA, on managed and encrypted devices, and access is recertified at each engagement phase boundary.

It depends on scope, integration surface, assurance depth and timeline pressure, which is why we do not publish a price list — a number produced before discovery is either padded or optimistic. What we commit to is a costed proposal after discovery with a range per phase, the assumptions each range depends on, and what would move it. Rate cards are published by seniority rather than blended.

Yes, following a paid discovery phase. We will not fix a price before discovery, because doing so honestly requires padding for unknowns and doing it dishonestly leads to a difficult conversation in month three. Once scope is genuinely understood, a fixed price with milestone invoicing and formal change control is often the right instrument, particularly for procurement.

Discovery is typically invoiced on completion. Build engagements invoice monthly in arrears against delivered effort, or on milestone acceptance for fixed scope. Dedicated teams carry a three-month minimum with 30 days' notice; staff augmentation is one month with 30 days' notice. Standard terms are 30 days net, and we are comfortable working through enterprise procurement and vendor onboarding processes.

We are headquartered in Bengaluru at IndiQube Alpha, Outer Ring Road, Bellandur, and we work with clients across India, the Middle East, Europe, the UK and North America. Delivery is remote-first with overlap hours agreed per engagement, and Enterprise support tier clients get follow-the-sun on-call cover 24/7/365.

Banking and financial services, healthcare, insurance, retail and e-commerce, manufacturing, logistics and supply chain, real estate, education, hospitality, and family office and wealth management. Depth matters more than breadth here, so we will tell you plainly when a sector is one where we would be learning on your project — and we would rather lose that engagement than discover it together in month two.