Questions we get asked most.
Answered by the engineers, not by a sales page.
-
Written by
The engineers who do the work
-
Covering
Pricing, contracting, ownership, support
-
Still not sure
One call, thirty minutes
Twelve answers, in the order they usually come up.
01 How do engagements start?
With a conversation, then a paid Technical Assessment for anything carrying real technical risk: a fixed-fee, one-to-three-day review producing a written findings document and a scoped fixed price for the build. It means our quotes are based on your actual systems, not guesses.
02 How do you price work?
Fixed-price for defined scope, monthly retainers for ongoing operations, and time-and-materials only where scope genuinely cannot be fixed yet. Milestones and acceptance criteria are agreed before work begins.
03 Who would we be contracting with?
Expandware Private Limited, incorporated in Pakistan under SECP Corporate Unique Identification Number 0351555, which you can verify with the regulator before signing anything. Engagements run under our master services agreement with a statement of work, a data processing agreement, and a service level agreement where one applies. Governing law and dispute resolution are agreed in the contract rather than assumed.
04 Where is the work performed?
From our secured facilities in Pakistan, operating as a certified Special Technology Zone (STZA) Enterprise: zero-phone production floors, biometric access, 24/7 monitoring, and network-level data loss prevention.
05 Who actually does the work?
Senior engineers with a minimum of five years of production experience. The engineer who scopes your work delivers it, with a cross-trained backup and no relationship-manager layer in between.
06 What time zones do you cover?
We deliver for clients across North America, the UK, Europe, Australia, and the Gulf, and we schedule overlap windows around your business hours. Managed-services clients on Enterprise SLA have 24/7 coverage regardless of time zone.
07 How do you handle confidentiality and data protection?
Every engagement runs under our master services agreement with a data processing agreement, GDPR and CCPA provisions, and SOC 2-aligned technical and organisational measures. NDAs are standard before discovery when required.
08 Who owns the work product?
You do. Code, documentation, and deliverables transfer to the client on payment under the terms of the statement of work, with full documentation and a structured handover.
09 Do you take over existing systems, or only new builds?
Both. A large share of our work is inherited systems: audits, rescues, modernizations, and ongoing operations of platforms other teams built.
10 What does support look like after delivery?
Every project closes with documentation, knowledge transfer, and a 30-to-90-day warranty period. Many clients continue into a managed services retainer with defined response targets and quarterly reviews.
11 Can you work alongside our internal team?
Yes. We regularly deliver as an embedded senior capability next to internal engineers, with shared trackers, joint reviews, and honest handover at the end.
12 What happens on the first call?
Thirty minutes, an engineer on our side, and a direct answer: what we would do, roughly what it costs to find out precisely, and whether we are the right fit at all. We would rather tell you the truth in a discovery call than oversell a six-month engagement.
Still deciding whether to call?
If your question is not among the twelve, it is probably specific to what you run, which is the kind we would rather answer with your architecture in front of us than in a paragraph.