Questions buyers ask before they email us

NextGen Global IT Park, registered in Bangladesh. Contracts are governed by our terms unless we sign yours; we are happy to work under a client's master services agreement where it is reasonable.

You do, unless we agree otherwise in writing. Everything we produce under a paid engagement — code, infrastructure definitions, documentation, designs — is assigned to you on payment of the invoice that covers it. We keep no licence to your product. The only things we retain are generic tools and templates that predate your project and contain nothing of yours.

Yes. Send yours, or ask for ours. We sign NDAs before seeing a repository or a cloud account, and we do not publish a client's name, product or screenshots without written permission — which is why one of our case studies has no screenshots.

When we handle personal data on your behalf we sign a data processing agreement, work only under your instructions and keep access scoped to the engineers on your project. Our privacy policy covers data from this website; our security page covers how we handle access to yours.

Five services are fixed-price and listed on the site. Everything else is quoted as a fixed price against a written scope wherever the scope allows it, or from $40/hour, senior-led, where it genuinely does not — less than a US agency charges for the same offshore seniors, with no agency in between. Minimum project size is $5,000. Projects are split into milestones you can see and test; each is invoiced on acceptance, so you never pay for more than one step ahead. Anything outside the written scope is quoted before we start, never invoiced afterwards.

Audits are invoiced on delivery of the report, due in 7 days — nothing up front, and the fee is credited against a fix sprint started within 30 days. Fixed-price sprints and project milestones are 50% to start, 50% on acceptance against a written checklist. The retainer is invoiced on the 1st and due on the 15th of the same month; cancel with 30 days' notice. Invoices are in USD (EUR on request), payable by international bank transfer.

We publish three defined sizes so the word means something. Prototype (2–3 weeks, $6k–10k): a working app with real data for demos and pilots, not hardened. Production MVP (4–8 weeks, $20k–40k): accounts and roles, one core workflow, one payment or integration, admin view, database with migrations and a rehearsed restore, tests on the money paths, CI/CD, monitoring and a handover runbook — the thing you can charge for. Platform (8–16 weeks, from $40k): multi-tenant, several integrations, mobile apps, compliance. The full in/out lists are on the services page; anything outside the list is a quote, not a surprise.

Because writing code stopped being the slow part. We use AI tools for the first draft of everything and a senior engineer for every decision and every review. What still takes time is what the tools cannot do: agreeing scope, your feedback rounds, store review, payment-provider verification, and testing against real data. Our timelines are set by those, and we quote conservatively so we deliver early rather than late.

No. The 20-minute call is free and ends with a written summary of what we would do and what it costs — or an honest “we are not the right team for this”.

That is how most clients start: a fixed-price audit, a scoped migration, or a two-to-four-week pilot feature. Larger work follows once you have seen how we deliver.

We work from Bangladesh (UTC+6) and keep 3–4 hours of daily overlap with US Eastern and Central European time. Production incidents on systems we operate are handled outside those hours under the retainer.

Written English, in your Slack or ours, with a daily written update on anything in progress. Calls when a decision needs one. Every production change has a written plan, tests and a rollback step before anyone touches a console.

A senior engineer with 12+ years of production experience leads every engagement and owns the result. We share named team profiles with prospective clients on request, under NDA if you prefer; we do not publish them on the site.

Yes. We act as the backend, mobile or DevOps team behind US and European agencies, under their name. Ask about the partner arrangement on the call.

For an audit, read-only: a repository invite and a read-only cloud role. For build or operations work, write access to your repository and a scoped cloud role, granted to named individuals — never shared accounts — and revoked the day the engagement ends. Details on the security page.

Dates assume access, feedback and decisions arrive within the agreed windows; delays on your side move the date by the same amount. If the delay is ours: You hear about a slip before the date, not on it. More than 10 business days late for reasons that are ours earns you 5% off that invoice; more than 30 and you can walk away, pay only for accepted work, and keep everything delivered.

A written checklist agreed before we start is the only test of done. No written objection within 5 business days of delivery means accepted. If a checklist item fails, we fix it free within 5 business days. If it passes but you wanted something else, that is a change — quoted before it is worked. Nothing stops payment for work already accepted. If we still disagree, the two leads meet within 5 business days, then the principals talk, then mediation before anything legal. It rarely gets past the first step.

Yes. Projects are split into milestones, each accepted and invoiced on its own, so you can stop at any milestone having paid only for what you have received — and you keep everything delivered. The retainer cancels with 30 days' notice.

Nothing you depend on is in our hands. Code lives in your repository from day one unless you ask otherwise, infrastructure is in your cloud account, domains and credentials are yours, and every runbook, report and evidence pack is handed over in a format your team can use without us. You revoke our access and carry on.

Because everything is in your accounts, the answer is the same as above. There is no step where you have to ask us for something you cannot already reach.

Yes, and we plan for it. Documentation and runbooks are written for the next engineer, not for us, and a handover period with your new hires is part of the scope whenever you want it.