Obvious questions, answered upfront.

You do. Day one. We transfer the GitHub repository to your org at the start of week one, before we've written meaningful code. No vendor lock-in, no "perpetual license" stunt. The source, the deploy keys, the database, yours.

On fixed-scope builds (Validation Sprint, MVP build), you pay milestones: 30% to start, 40% at the midpoint demo, 30% on production deploy. If we miss the contracted date for the Core MVP (Phase 1), you don't pay the final 30%. We absorb the risk of going fast.

Fixed-price builds get a single change-order checkpoint at the halfway demo. You can add, remove, or swap features once, no per-change negotiation. Beyond that, additional scope goes into a follow-on engagement. Sprint retainers re-plan each two-week sprint, so scope shifts are continuous.

Rarely. Only for projects we'd otherwise turn down, typically pre-seed founders whose idea we think is exceptional and whose cash runway is tight. The bar for an equity engagement is much higher than a cash one.

If we deliver milestone 1 and you decide the project isn't worth continuing, you owe us only the work delivered (typically 30%). If we deliver and the production system doesn't work as scoped, you don't pay the final milestone (the guarantee). If we go non-responsive for more than 5 business days without notice, the contract is void and the deposit refunded. All written into the standard SOW.

We're in Lahore, Pakistan (UTC+5). We overlap with US-East mornings (8 AM to 12 PM ET) and the full EU working day. Async-default: Loom updates every business day, one weekly live working session (around 60 min), Slack DM to the engineers for everything else. No standups, no account managers between you and the work.

Day 1: kickoff call, GitHub org access transferred, project Slack channel opened. Days 2 to 4: architecture spike, with the riskiest component built first, and a first working demo at the end of week 1. Week 2 starts with you having seen running code, not a Figma.

Often. We translate product thinking into engineering decisions. The Validation Sprint exists partly for this: five days of structured back-and-forth surfaces what you need before we quote a build.

Yes, with caveats. We do a free 2 to 3 hour code review first. If it's salvageable, we quote a retainer or staff-aug engagement. If it's buried in technical debt, brittle dependencies, or AI-generated spaghetti, we'll say so and recommend a different path.

Geographic arbitrage, not corner-cutting. US/EU pricing for an AI-native MVP of equivalent scope runs $60–120k. We charge from $6k because senior engineering talent in Pakistan is 4× more cost-efficient: same stack, same standards, different cost base. Margins on our side are healthy enough that we can afford to turn down half of inbound and still pay above-market locally.

For most B2B SaaS engagements, no. We invoice via standard freelance contractor agreements; payment lands in our local entity. For HIPAA / SOC2-relevant projects, we structure through a US LLC partner and the engagement looks like any other US-based contractor agreement. We've shipped for clients in 12 countries across healthcare, fintech, and B2B SaaS. Happy to walk through specifics on a call.

A senior team means no single point of failure. Your code is in your GitHub from week one, every deploy is documented, and the architecture diagram and handover SOP stay written and accessible to your team. Another senior engineer can pick up the work without a cold start, and for projects where bus-factor is a stated concern we name a second senior engineer who shadows the build.

30 days of post-launch support: bug fixes, minor adjustments, on-call for the first production weekend. We don't restart the clock for trivial issues; we just fix them. Beyond 30 days, the Care Plan ($2,500/mo) keeps us on standby with a 24-hour response SLA for fixes and small features.

Most clients move to a Sprint retainer ($8k/mo: two senior engineers, a QA engineer, and a delivery PM, two-week sprints, cancel anytime). The engineers who built it stay on for the follow-on work, no re-onboarding cost.

No. After the first 6 months on a retainer, we recommend you hire your own engineer (often someone we've worked with before), and we move from primary engineer to specialist-on-call. We'd rather you outgrow us than depend on us.