Reduce migration risk before writing production code.

Engineering

Hassan Jamal

Co-founder and Lead Engineer

Architecture

Imran Raza Ladhani

Co-founder and Lead Architect

Migration continuity

The scope identifies current URLs, content, integrations, redirects, analytics, cutover responsibilities, and rollback conditions.

Written acceptance

Deliverables, exclusions, test pages, browser support, performance methodology, ownership, warranty, and remedies belong in the accepted written project terms.

Documented access and handover

Repository, hosting, domains, accounts, licenses, and handover timing are documented so control is not implied or left until launch.

You own everything

Source code, design files, CMS models, documentation and production accounts are transferred to, or created under, your control. There is no proprietary layer you have to keep paying us for, and no scenario where leaving means starting over.

A measured speed target

A 90+ Lighthouse target on mobile and desktop, for representative pages named in your scope, verified across three recorded runs before handover. It is a lab acceptance test with stated conditions, not a promise about rankings, traffic or revenue, which nobody controls.

No platform rent

We do not charge a monthly licence to keep your own site running. You will still pay third parties for hosting, a CMS or email if your build uses them, and we document those costs and who owns each account before you approve anything.

Your exposure is capped at the deposit

Payment is normally 30% at onboarding and 70% at the delivery milestone, after you have reviewed the work. So you never pay the balance for something you have not accepted. Where scope protection is included in your accepted terms, we refund the fees paid under that scope if we fail to deliver what was promised, which at that point is the deposit. The terms define the trigger, verification and cure process. It is not a change-of-mind refund, and we would rather say that plainly than bury it.

Fixed price, no hourly billing

You approve a number before work starts, and that number holds for the agreed scope. Anything outside it is quoted and approved separately before it is built. A common structure is 30% at onboarding and 70% at the delivery milestone.

Support after launch

Discussions typically start at 15 business days for Starter and 30 for Growth and Scale. What it covers, when it starts, and what counts as a defect versus a new request are written down, so nobody argues about it later.

A launch you can reverse

Your current site stays live until you approve the new one. Redirects, analytics, forms, DNS, monitoring and a documented rollback path are agreed before cutover, so going live is a decision rather than a leap.

You talk to the engineers

Two co-founders scope your project and two co-founders build it. There is no account manager relaying messages, and no junior team you were not told about. If we think repairing your current site beats rebuilding it, you will hear that from the person who would have done the rebuild.