Our physical office is in Kepez, Antalya. The provinces listed here do not imply that we have branches or clients in those locations. We can discuss website requirements remotely with businesses across Turkey. Your sector, visitors’ needs and readiness of content matter just as much as your city when planning a project.
Plan the working process, not the distance
In a remote project, decisions need a clear written record. The summary of your requirements, design notes and content files should be easy to follow. Appointing one person to consolidate feedback helps avoid conflicting requests. We hold calls in Turkish and English. File sharing and screen reviews can take place online; we agree the practical arrangements at the start.
How to use the province directory
Choose a province from the alphabetical list to open its web design page. A city page is neither a service contract nor an office you can visit. For regional navigation, use our service regions directory (in Turkish). Before deciding which service you need, note the condition of your existing website and the functions you want it to provide.
Preparing for online collaboration
It helps to know who manages access to your domain, hosting and website administration panel. You do not need to share confidential credentials before the initial call. Instead, list the system you use, the content already prepared and any pages that need migrating. For a redesign, a record of old URLs helps us review existing links. For a new website, start by explaining your services and the action you want visitors to take.
Your business review before launch
An authorised person from your business should confirm the contact address, opening hours and services shown on the site. If you genuinely operate in several cities, describe that presence using information you can substantiate. Do not imply that you have an office somewhere you do not operate. Agree who will receive form submissions and who will respond to enquiries: this is as important as the content itself.
Remote handover covers responsibility for using the website as well as its appearance. Identify who will update the content and record any admin-panel guidance they need. Treating post-launch maintenance, hosting and changes separately from the initial project makes the scope easier to understand.