In a Git repository you own and control — typically GitHub, GitLab, or Bitbucket. I push branches and open pull requests; you approve and merge. At the end of the engagement, my access can be revoked without losing anything.

The 30-day post-handoff support window covers questions and small fixes on delivered scope. Beyond that, the two recurring vehicles described above (reserved capacity blocks and care plans) cover ongoing needs without the open-ended-retainer trap. For one-off remediation later on, a fixed-scope sprint is usually the right shape — for example, a quarterly review and remediation…

Yes, most often the United States, occasionally further. Engagements are remote unless on-site work is specifically scoped. Quotes for non-Canadian clients are typically issued in CAD or USD by request.

Scope changes are normal — the audit usually surfaces things the original scope did not anticipate. New work is added through a written change request with a fixed price and a revised completion date. You decide whether to approve it. The original scope keeps its original price.

Yes. Mutual NDAs and standard professional-services contracts are routine. For larger engagements I work from your paper or mine, whichever your procurement team prefers.

Often the best outcome. I work directly with in-house developers, designers, and content teams — code review, pair work, and structured handover all in scope when the engagement calls for it. The aim is to upskill the team, not replace it.