Ordering an IT project or a website?
Learn best practices to avoid problems
and stay in full control of your brand.

This guide was created for people commissioning IT projects, websites, or apps — both individuals and companies. It's a living project that will be regularly updated and expanded based on real questions and experiences from our clients.

  • 1. What should a contract include?
  • 2. What access should you receive?
  • 3. What to do when the contractor stops responding?
  • 4. Who owns the rights to code, graphics, and content?
  • 5. How to secure the domain and hosting in your name?
  • 6. What to watch out for in the “subscription” model?
  • 7. Do you need technical documentation?
  • 8. How to verify quality (UX and code audit)?
  • 9. What data must the contractor provide after completion?
  • 10. How to ensure GDPR and cookie policy compliance?
  • 11. When is a data processing agreement needed?
  • 12. What's the difference between a website, an app, and an MVP?
  • 13. How to protect your know-how and business idea?
  • 14. How to define a timeline and handover stages?
  • 15. How to settle with a freelancer vs. an agency?
  • 16. How to check if someone stole your domain or brand?
  • 17. How to ensure security (SSL, backups, login protection)?
  • 18. Is it worth signing an NDA with the contractor?
  • 19. When are you entitled to warranty or guarantee?
  • 20. What does “vendor lock-in” mean and how to avoid it?
  • woman at laptop
    lightbulb
    We want this material to be as practical, clear, and helpful as possible — that's why we're open to your suggestions, ideas, and questions. If something is unclear, missing, or you have your own story worth sharing — write to us at support (at) qwertyjobs.com.
    folder_info
    Our goal is to create a complete guide to best practices for IT outsourcing — helping you avoid mistakes, misunderstandings, and unnecessary costs.

    mystery Follow this guide — we will continue to develop it over time. mystery

    1. What should a contract include?

    2. What access should you receive?

    3. What to do when the contractor stops responding?

    4. Who owns the rights to code, graphics, and content?

    5. How to secure the domain and hosting in your name?

    6. What to watch out for in the “subscription” model?

    7. Do you need technical documentation?

    8. How to verify quality (UX and code audit)?

    9. What data must the contractor provide after completion?

    10. How to ensure GDPR and cookie policy compliance?

    11. When is a data processing agreement needed?

    12. What's the difference between a website, an app, and an MVP?

    13. How to protect your know-how and business idea?

    14. How to define a timeline and handover stages?

    15. How to settle with a freelancer vs. an agency?

    16. How to check if someone stole your domain or brand?

    17. How to ensure security (SSL, backups, login protection)?

    18. Is it worth signing an NDA with the contractor?

    19. When are you entitled to warranty or guarantee?

    20. What does “vendor lock-in” mean and how to avoid it?