Frequently Asked Questions

Because the handover between the two is where projects lose the most value. The engineering team says "marketing asked for it", marketing says "engineering can't build it". In one team that handover disappears: the person who sees the landing page underperform is the person who can change the code.

Two founders. That is deliberate: on every project you work directly with the founders and the brief never gets lost in a middle layer. When we are at capacity we give you a date instead of taking the project — we would rather not grow by getting crowded.

Yes, we work remotely and serve clients in Türkiye and internationally. Weekly reviews happen over video; for critical meetings within İstanbul we also meet in person.

Turkish and English. Documentation, code and technical correspondence default to English; meetings and reports follow your preference.

For project work we do fixed scope, fixed price: at the end of discovery you get the scope document and the price in writing. Ongoing services (SEO, marketing, maintenance) run on a monthly retainer. We use hourly rates only for consulting and technical reviews.

The first 30-minute call is free. A full discovery (architecture decisions, scope document, estimate) is paid and is credited against the first invoice if you go ahead. The output is yours either way, including if you do not continue with us.

Every out-of-scope request gets its own estimate and approval step. Work does not start before approval and unapproved work is never invoiced. That step is what removes the surprises.

Yes. The repository lives in your GitHub organisation from day one, and the domain and cloud accounts are opened in your name. You can revoke our access any day; nothing is held in our accounts.

A 30-day bug-fix warranty after launch is standard. After that there is an optional maintenance package: security updates, monitoring, backup verification and a monthly budget for small improvements.

Because we build static. Pages are rendered to HTML at build time and served from Cloudflare's global network — there is no server running at request time. JavaScript loads only where interaction genuinely needs it, and only when that section reaches the screen. That is a measurable difference for both users and Googlebot.

No, but if you sell internationally the upside is real. A correctly built multilingual setup — hreflang, x-default, language-specific URLs — expands search visibility rather than splitting it. A badly built one genuinely hurts, which is why we get the foundation right from day one.