Questions we get asked most
Straight answers about how we work, what we cost, and what happens when things don't go to plan.
A 30-minute strategy call where you describe the problem. We ask questions, not to qualify you, but to understand what the software needs to do. Within 48 hours we send a brief with our recommended approach and a high-level scope.
Yes, before any technical discussion. We use a standard mutual NDA and can work with your company's NDA template if required.
Yes. We're based in Lahore, Pakistan. International clients typically work with us remotely, but we're happy to host in-person workshops for scoping and design phases.
PKT (UTC+5). We have 3–4 hours of overlap with UK business hours and are fully async-capable for US clients. We schedule standups, demos, and review calls within available overlap windows.
Milestone-based fixed pricing. You approve a scope, we produce a timeline with defined milestones, and each milestone has a fixed price. Payment is due when you sign off the milestone. No hourly tracking, no surprise invoices.
Changes go through a formal change request: we document what's changing, estimate the impact on timeline and cost, and you approve before we build. Scope creep by definition cannot happen without your signature.
Yes, for post-launch support and ongoing enhancement work. Retainer plans start at $800/month (10 hours) and are capped — you always know the maximum you're committing to.
MVP and focused internal tools: $8,000–$20,000. Mid-complexity platforms with multiple integrations: $25,000–$60,000. Full ERP or enterprise systems: $60,000–$150,000+. We scope every project independently.
You do. Entirely. We sign an IP assignment on day one. We retain nothing — not even the right to show the code in our portfolio without your explicit permission.
Open-source components are used under their respective licences (typically MIT, Apache 2.0). We document all dependencies and their licences in the project handoff package.
Yes. We code for readability and include documentation specifically so this transition is smooth. We can hand off at any milestone boundary.
For most web and backend projects: Node.js or Python backend, React or Vue/Nuxt frontend, PostgreSQL, Redis, deployed on AWS/Azure/Cloudflare. For mobile: React Native (primary), native Swift/Kotlin for performance-critical requirements. For AI: Python, PyTorch/scikit-learn, FastAPI for serving.
Yes. Unit tests for business logic, integration tests for API endpoints, and E2E tests for critical user flows. Test coverage targets are defined per project and CI gates prevent merging code that drops below them.
Secure-by-default practices: parameterised queries, OWASP Top 10 review, dependency scanning in CI, secrets management (never in code), HTTPS everywhere, and a penetration test before production launch for sensitive applications.