The questions we get asked before every project starts
Before a client signs anything with us, they usually want to know the same things:
We've answered these questions in proposals and scoping calls for 12 years. This post is our attempt to answer them properly in one place — so you know exactly what to expect before you decide to work with us.
Who works on your project
Senior people. That's not a marketing line — it's a structural decision we made when we started capsinfra.
We don't hire junior engineers and bill them at senior rates. We don't use your project to train recent graduates. Every engagement is staffed by engineers and specialists with a minimum of 5 years of production experience in that specific domain.
For technology projects: the engineer who reviews your scope is the engineer who builds it. You're not dealing with a salesperson who hands the work to a team you've never met.
For sports infrastructure projects: the civil engineer who visits your site is the same person who leads the construction. We don't use subcontractors for core work.
This limits how many projects we take on at any time — typically 4 to 6. We'd rather do fewer projects properly than more projects poorly.
How we scope a project
We don't start work until scope is agreed in writing.
For technology projects, this means:
For sports infrastructure projects:
We don't issue quotes without a site visit for sports projects. The sub-base approach depends on what we find on site — quoting without seeing it produces unreliable numbers.
How we handle scope changes
Every project has scope changes. The question is how they're managed.
Our approach:
1. Any change to agreed scope is documented in writing before we implement it
2. We estimate the cost and time impact of the change
3. The client approves the change order before work proceeds
4. The change is added to the contract
We don't absorb scope changes silently and then invoice at the end. We don't refuse all scope changes either. The documented change order process keeps both sides honest — you know what you're adding and what it costs, and we don't get to retroactively claim everything was out of scope.
How we communicate during a project
For technology projects: weekly demo calls showing working software, not status updates or PowerPoint slides. You see what was built that week, running in a staging environment. If there's a problem, you see it when it's still cheap to fix.
GitHub repository is open from day one. You can see every commit, every branch, and the full history of the codebase. We don't hide work in progress.
For sports projects: weekly site photographs and written progress notes. You know what was done, what's coming next, and whether the timeline is on track.
We flag problems before they become crises. If a supplier has delayed a material delivery and it will affect the timeline, you hear about it from us before it affects the handover date — not after.
What fixed-price actually means
Fixed-price means the number in the contract is the number you pay — for the scope agreed in the contract.
It doesn't mean we absorb unlimited scope changes. It doesn't mean we'll deliver something different from what was specified and call it equivalent.
What it does mean:
If we underprice a project because of our own estimation error, we absorb that cost. That's happened. It's the cost of offering fixed-price work.
What post-launch / post-handover looks like
Technology projects:
Every project includes a post-launch defect warranty — typically 30 to 90 days depending on project size. During this period, any bugs or issues with functionality that was in the agreed scope are fixed at no charge.
After the warranty period, clients can engage us on a retainer for ongoing support and development, or handle maintenance internally using the codebase we've handed over.
Sports infrastructure projects:
Every project includes a structural warranty on the surface and sub-base. If the surface delaminations, the sub-base settles, or any structural defect emerges within the warranty period, we repair it at our cost.
We've honoured three warranty claims in our history. All three were resolved at our cost, without dispute.
What we won't do
We'll tell you upfront if we're not the right fit for something.
We don't do:
If you come to us with a requirement that doesn't fit, we'll tell you honestly — and if we know someone better suited, we'll say so.
How to start
The first step is a conversation — not a proposal, not a contract, not a commitment.
For technology: a 30-minute call where we understand what you're building, what you've tried, and what you actually need. You'll know by the end of the call whether we're the right fit.
For sports infrastructure: a site visit. Free, no obligation. We assess the site and give you an honest feasibility assessment and indicative cost range within 5 working days.
If we're not the right fit — for any reason — we'll tell you that too.
capsinfra delivers technology and sports infrastructure projects across India.