A CLEAR WORKING PROCESS

Let us make the working terms clear before we start your project.

Scope, pricing, deliverables and communication are documented before work begins. Both sides know what will happen, when it is expected and under which conditions; new requests are not quietly added to the original job.

1 Written scope
2 Milestone delivery
3 Documented payment
handshake

How do we reach an agreement?

  1. We discuss the project goal, users, required pages or features and any existing system in writing.
  2. The written proposal defines scope, deliverables, estimated schedule, price, payment milestones and revision limits.
  3. Work starts after both sides approve the proposal and the first milestone is funded on the selected platform.
  4. I share deliverables by milestone. Requests outside the approved scope receive a separate time and cost estimate.
rule

Basic working terms

  • Work does not begin until the written scope is approved and the first milestone is funded.
  • Unless the proposal says otherwise, domain, hosting, paid plugins, licences, APIs, advertising and other third-party costs belong to the client.
  • Delays in client-provided copy, images, access or approvals may move the delivery schedule.
  • The client confirms that they have the right to use the copy, images, brand assets and data they provide.
  • A revision corrects approved work. A new page, feature or change of direction is additional scope.
  • Maintenance, support, backups and later development are not automatically included after delivery unless the proposal lists them.
shield_person

How are the client and developer protected?

  • We keep scope, deliverables, decisions and files on the selected platform or another written channel whenever possible.
  • The client funds the relevant milestone, tests each delivery and reports issues in writing before accepting it.
  • I work only on funded, clearly defined scope, document changes and retain delivery records.
  • I do not request passwords in public messages. Access is limited to what the work needs; temporary permissions can be removed and credentials rotated after handover.
  • Platform payment and dispute tools create a record, but they do not guarantee a particular outcome for either side. The current platform rules and written project terms apply.

WORK PLATFORM

Where are the contract, payment and delivery records kept?

Initially, I plan to manage proposals, payment milestones and delivery records through Contra. The client can see the job and its milestones on the platform and pay through the methods it supports.

Contra is a payment and record-keeping intermediary; using it alone does not guarantee a flawless project or a particular dispute outcome. Fees, payment availability, refunds and dispute handling depend on the platform’s current terms. Review the scope and milestones in the proposal before work begins.

If I move to another platform later, I can update the platform name, link and explanation from the admin panel. The platform for an active project changes only with written approval from both sides.

Initial platform

Contra

View the platformopen_in_new
translate

A clear note about communication

I can communicate in Turkish in writing or by video call. For projects handled in English, I communicate in writing only; I do not currently hold voice or video calls in English.

NEXT STEP

Choose the contact option that suits you.

chat

Start with a written conversation

Send the project type, goal, any existing website and an approximate schedule. The prepared message helps you include the useful details; this first conversation is not a binding price or delivery commitment.

Write your project details on WhatsApparrow_outward
video_call

Request a video call in Turkish

Video calls are available in Turkish. Send suitable dates and times for a short introductory call; the appointment is confirmed only after we agree on the time in WhatsApp.

Request a Turkish video callcalendar_month