{"id":988625,"date":"2026-10-05T14:00:00","date_gmt":"2026-10-05T14:00:00","guid":{"rendered":"https:\/\/croncodestudio.com\/en\/?post_type=croncode_post&p=988625"},"modified":"2026-09-08T22:58:43","modified_gmt":"2026-09-08T22:58:43","slug":"fixed-price-vs-retainer-for-app-work","status":"publish","type":"croncode_post","link":"https:\/\/croncodestudio.com\/en\/journal\/fixed-price-vs-retainer-for-app-work\/","title":{"rendered":"Fixed Price vs Retainer for App Work"},"content":{"rendered":"
\n

Fixed price buys a written increment. A retainer buys a week of a named team. They are commercial shapes, not moral values. The process essay about store gates is separate: fixed scope vs agile<\/a>. This page is how money and change orders meet. Croncode LLC can invoice from a US entity. Work is done in Istanbul. We will not quote a fantasy Friday.<\/p>\n

\n

Use fixed price when the first store increment is written. Use a retainer when you are buying weekly capacity after that increment. Mixing them without a rule is how disputes start.<\/p>\n<\/blockquote>\n

What must be true for a fixed price to be honest?<\/h2>\n

A first job, a not-now list, platforms, languages, and who owns Apple. The packet: what to send<\/a>. If those are missing, a number is a guess you will both regret. Thin MVPs still need those items: MVP too thin<\/a>. AI extras need a fail-safe or they are not in the number: fail-safe AI<\/a>.<\/p>\n

Choose the vendor model first: studio vs freelancer vs agency<\/a>. iOS diligence: choose an iOS studio<\/a>.<\/p>\n

When is a retainer the cleaner paper?<\/h2>\n
    \n
  1. Version one is live and you need crash and review response. Crashes<\/a>, reviews<\/a>.<\/li>\n
  2. You have two tracks, store and client tool, and hours must be explicit. Lean hours<\/a>.<\/li>\n
  3. Seasonal content will change copy without changing the object. Seasonal content<\/a>.<\/li>\n
  4. You want founder-led support covered in the same week. Founder support<\/a>.<\/li>\n<\/ol>\n

    Retainers fail when they hide an infinite backlog. Write the weekly demo: sprint demo<\/a>.<\/p>\n

    How do you mix them without lying?<\/h2>\n\n\n\n\n\n\n\n\n
    Layer<\/th>\nFixed<\/th>\nRetainer<\/th>\n<\/tr>\n<\/thead>\n
    First store job<\/td>\nUsual<\/td>\nOnly if discovery is the product<\/td>\n<\/tr>\n
    Store promise<\/td>\nYes<\/td>\nChange via a version<\/td>\n<\/tr>\n
    Week-two experiments<\/td>\nPoor fit<\/td>\nGood fit. Week two<\/a><\/td>\n<\/tr>\n
    Android later<\/td>\nNew fixed or new retainer<\/td>\nDo not sneak it in. Android<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

    Paywalls and privacy labels are store events even on a retainer: honest paywalls<\/a>, account ownership<\/a>.<\/p>\n

    What should the invoice describe?<\/h2>\n

    The increment name or the week dates, the people, and what was not done. People you may see: Goktug Unver<\/a>, Yusufhan Sokur<\/a>, Ozgur Ismet Ozkan<\/a>. Shipping: Istanbul shipping<\/a>. References: check references<\/a>.<\/p>\n

    What mistakes create a fight?<\/h2>\n