Talk to the Istanbul team

Within 24 hours, and usually the same working day. Form submissions land directly in our inbox; anything that arrives at the weekend is answered on Monday morning Istanbul time. The first reply is not an automated acknowledgement — it is written by someone who has read your brief, and it states how we understood the scope, what information is still missing, and an estimated budget range.

For anything urgent, WhatsApp is the quickest channel and is normally answered within minutes during working hours.

Six things. Send what you have — we will fill the gaps together — but if these are in the first message, the first reply contains a price rather than a questionnaire.

• What your business does. One sentence: what you sell and who buys it.
• Project type. Brochure site, e-commerce, or an application with user accounts. If you are unsure, the services page draws the line between them.
• Number of distinct page types. Not the total page count — the number of layouts that must be designed separately. This is the figure that moves the price.
• Integrations. Payment provider, shipping, accounting, CRM, or an existing ERP the site has to talk to, and which product each one is.
• Deadline and budget band. A launch date if one is fixed, and a range if you have one. The pricing page lists the three packages in US dollars if you want a reference point first.
• Your current site, if there is one. Send the address. On a migration the URL mapping is the highest-risk task, so we need to see the existing structure before quoting.

One note on the form above: the budget dropdown is denominated in Turkish lira because the form is shared with the Turkish site. The bands map to the same three packages priced in US dollars on the pricing page — pick the nearest one, or leave it blank and describe the budget in your message.

Yes. Remote and international projects are a normal part of the work, not an exception, and the process is built to run without anyone being in the same room.

• Written first, calls second. Every stage produces a written summary you can forward internally. Video calls are scheduled when a decision needs discussion, not as a weekly ritual.
• You see the design before the code. A clickable Figma prototype is approved before development starts, so the thing you sign off is the thing that gets built.
• A demo link throughout. Development runs against a staging URL you can open at any point; progress is checkable rather than reported.
• Acceptance, then handover. Delivery includes a Lighthouse report, the source repository and every admin credential. Full source-code ownership transfers to you at delivery — there is no lock-in and no retainer.
• Contracting in US dollars. 50% advance before project start, balance on delivery. Invoiced by Obelisx Digital in Istanbul and settled by international bank transfer; the figures are on the pricing page.

Working in English is part of delivery rather than an add-on: briefs, specifications, documentation, code comments and handover notes are all written in English for English-speaking clients.

• Services — what we build, and how a remote engagement runs from brief to handover.
• Pricing — the three packages in US dollars, what is excluded, and how payment works.
• Portfolio — published projects with the challenge, the solution and the result for each.
• About Obelisx — the studio, the location and the stack.
• Türkçe — İletişim — the Turkish version of this page.