{"id":2770,"date":"2026-06-01T10:41:03","date_gmt":"2026-06-01T10:41:03","guid":{"rendered":"https:\/\/sawaryn.com\/uslugi\/implementing-incentive-programs-for-game-developers\/"},"modified":"2026-07-14T17:08:03","modified_gmt":"2026-07-14T17:08:03","slug":"implementing-incentive-programs-for-game-developers","status":"publish","type":"service","link":"https:\/\/sawaryn.com\/en\/uslugi\/implementing-incentive-programs-for-game-developers\/","title":{"rendered":"Implementing Incentive Programs for Game Developers"},"excerpt":{"rendered":"

We help game development studios create a transparent, secure, and implementable incentive system: from sharing in the game\u2019s success, through bonuses and vesting, to rules tied to milestones, roles, and actual contributions to the project.<\/p>\n","protected":false},"featured_media":0,"template":"","meta":{"_acf_changed":false},"specialization":[1209],"practice_area":[],"class_list":["post-2770","service","type-service","status-publish","hentry","specialization-gaming-game-development"],"acf":{"short_description":"We help gamedev studios create a transparent, safe and implementable incentive system: from sharing in the game\u2019s success, through bonuses and vesting, to rules tied to milestones, roles and contribution to the project.","full_description":"Design an incentive programme that retains key people and organises promises to the team<\/strong>\n\nWe help gamedev studios create a transparent, safe and implementable incentive system: from sharing in the game's success, through bonuses and vesting, to rules tied to milestones, roles and real contribution to the project.\n\nA view of an organised incentive programme model for a studio: team roles, project milestones, bonus mechanisms, entitlement rules and implementation documents joined into one clear framework.\n

CLIENT PROBLEM<\/h2>\nIn gamedev many incentive arrangements start innocently: \u201cwe will share the success\u201d, \u201cyou will get a bonus after launch\u201d, \u201cwe will think about equity\u201d. The problem appears when the project grows, the team waits for specifics and the management board must answer: who, when, for what and on what terms should receive additional compensation.\n\n\u201cAn incentive programme should not be a collection of promises. It should be a management tool: for retention, engagement, risk and team expectations.\u201d\n\nWithout a clear model, tension builds quickly. Different people have different expectations, founders act under pressure and every further ad hoc decision raises the risk of conflict. A well-designed programme organises the rules, protects the company and gives the team a clear answer: what is possible, for what, when and under what conditions.\n

MOST COMMON PROBLEMS \/ CHALLENGES<\/h2>\nPromises without clear rules<\/strong>\n\nThe team has heard about equity, a bonus or a success fee, but does not know exactly what that means. The management board also does not yet have a model that can be implemented safely.\n\nWe design the programme rules: beneficiaries, conditions, entitlement moments, forfeiture criteria and the settlement method.\n\nBusiness benefit:<\/strong> fewer ambiguities and greater control over the team's expectations.\n\nRisk of inaction:<\/strong> growing conflicts, pressure for quick decisions and difficulty withdrawing from imprecise declarations.\n\nTurnover of key people before an important milestone<\/strong>\n\nA senior developer, lead or producer leaves at the moment the project most needs stability.\n\nWe build a retention mechanism tied to project stages, role and real contribution. It may include vesting, a project bonus, a share in success or a hybrid model.\n\nBusiness benefit:<\/strong> a better chance of retaining key people through an important stage.\n\nRisk of inaction:<\/strong> loss of know-how, delays, lower quality and costly replacement hiring.\n\nDifferent rules for different people<\/strong>\n\nPart of the team has email arrangements, part verbal ones, part individual deals. Nobody sees the full picture, and every compensation conversation starts with negotiations from scratch.\n\nWe organise the programme structure for different groups: founders, leads, developers, producers, contractors and collaborators.\n\nBusiness benefit:<\/strong> consistent rules and easier management of conversations with the team.\n\nRisk of inaction:<\/strong> a sense of unequal treatment, internal disputes and loss of trust in the management board.\n\nPressure for equity without certainty it is the right model<\/strong>\n\nThe team expects a \u201cshare in success\u201d, but founders do not want to complicate the cap table, governance or a future funding round by accident.\n\nWe compare possible models: equity, options, bonuses, success fees, phantom shares or hybrids. We match the mechanism to the studio's stage of development and ownership plans.\n\nBusiness benefit:<\/strong> an attractive programme without unnecessary risk to the company structure.\n\nRisk of inaction:<\/strong> giving away equity too quickly, an unclear ownership structure or a programme that cannot be sustained financially.\n\nNo link between motivation and milestones<\/strong>\n\nThe programme is meant to motivate, but it does not support delivering the project. The bonus is not tied to responsibility, the production stage or measurable contribution.\n\nWe connect incentive mechanisms with the project lifecycle: pre-production, production, soft launch, release, commercial results or subsequent milestones.\n\nBusiness benefit:<\/strong> motivation supports concrete goals, not only a general sense of \u201csharing in success\u201d.\n\nRisk of inaction:<\/strong> the programme costs money but does not reinforce behaviours that matter for the project.\n\nThe investor expects order<\/strong>\n\nBefore a round, due diligence or a larger transaction, informal promises to the team come to light.\n\nWe formalise the programme and tie it to the cap table, corporate documentation and ownership governance rules.\n\nBusiness benefit:<\/strong> greater predictability for the management board, the investor and the team.\n\nRisk of inaction:<\/strong> questions in due diligence, claim risk and reduced confidence in how prepared the organisation is.\n

HOW OUR SOLUTION WORKS<\/h2>\nFrom informal promises to a programme that can be implemented and run<\/strong>\n\nWe do not start with documents. First we define the business outcome the programme should achieve: retention, greater engagement, organising the rules, preparing for a round, securing a milestone or stabilising a key team. Only then do we design the mechanism and formalise it in documents.\n\nDiagnosis of studio structure and programme goals<\/strong>\n
    \n \t
  • analysis of the studio's stage of development,<\/li>\n \t
  • identification of key roles and participant groups,<\/li>\n \t
  • review of current arrangements, promises and risks,<\/li>\n \t
  • defining the programme goal: retention, motivation, project bonus, share in success, order before a round.<\/li>\n<\/ul>\nA map of the situation, risks and decisions needed to design the programme.\n\nChoice of incentive model<\/strong>\n
      \n \t
    • comparison of possible mechanisms: bonus, success fee, options, equity, phantom shares, vesting, hybrid model,<\/li>\n \t
    • assessment of impact on finances, the cap table and governance,<\/li>\n \t
    • matching the model to studio scale and project type,<\/li>\n \t
    • indication of the recommended variant.<\/li>\n<\/ul>\nAn incentive model recommendation with business and legal rationale.\n\nDesign of programme rules<\/strong>\n
        \n \t
      • defining who may participate in the programme,<\/li>\n \t
      • setting what entitlements are granted for,<\/li>\n \t
      • designing rules for earning, exercising and forfeiting entitlements,<\/li>\n \t
      • linking the programme to milestones, role and contribution,<\/li>\n \t
      • exceptions and edge cases.<\/li>\n<\/ul>\nA complete rules model: who, when, for what, how much and under what conditions.\n\nProgramme documentation<\/strong>\n
          \n \t
        • preparing the programme regulations,<\/li>\n \t
        • preparing agreements or addenda for participants,<\/li>\n \t
        • developing settlement mechanisms,<\/li>\n \t
        • consistency with company documentation,<\/li>\n \t
        • protecting the interests of the management board and the studio.<\/li>\n<\/ul>\nA document pack ready for the studio to implement.\n\nIntegration with the cap table and corporate governance<\/strong>\n
            \n \t
          • assessment of the programme's impact on ownership structure,<\/li>\n \t
          • link to investment plans,<\/li>\n \t
          • protecting founder control,<\/li>\n \t
          • organising the relationship between the programme and governance.<\/li>\n<\/ul>\nA programme that does not break the company structure and is clear for investors.\n\nSupport for communication to the team<\/strong>\n
              \n \t
            • organising the programme logic in plain language,<\/li>\n \t
            • guidance on how to communicate rules and limits,<\/li>\n \t
            • preparing key messages for participants,<\/li>\n \t
            • minimising the risk of wrong expectations.<\/li>\n<\/ul>\nA coherent implementation narrative: clear for the team and safe for the management board.\n

              WHO THIS SERVICE IS FOR<\/h2>\nFor studios that want to motivate the team without chaos and imprecise promises<\/strong>\n\nThe service is for organisations that already feel real tension around retention, sharing in project success or the rules for rewarding key people.\n\nHead of Operations \/ Studio Operations Manager - when the incentive programme topic blocks operational decisions and needs the rules organised quickly.\n\nGeneral Counsel \/ Head of Legal \/ CFO - when you need to assess risks, compare models and prepare a recommendation for the management board or an investor.\n\nFounder \/ CEO \/ Studio management board - when the programme should support retention, scaling and the long-term structure of the organisation.\n

              STAGES OF WORK<\/h2>\nA simple process: diagnosis, model, documents, implementation<\/strong>\n\nWe run the project so the management board quickly sees possible decisions, risks and consequences. The outcome is not documentation alone, but a programme that can be used in day-to-day studio management.\n\nStage 1. Diagnosis and business context<\/strong>\n\nWe talk about studio structure, projects, the team, earlier arrangements and programme goals. We identify tensions, risks and decisions that must be made before implementation.\n\nWhat the client gains:<\/strong> A clear picture of the situation and a list of topics to organise before documents are created.\n\nStage 2. Model design<\/strong>\n\nWe match the incentive mechanism to studio realities: share in success, options, bonus, vesting, success fee or a hybrid model. We show the legal, financial and organisational consequences.\n\nWhat the client gains:<\/strong> A recommended programme variant that can be defended before the management board, the team and an investor.\n\nStage 3. Formalisation and implementation<\/strong>\n\nWe prepare documents, regulations, agreements, addenda and settlement mechanisms. We tie the programme to company structure, the cap table and governance rules.\n\nWhat the client gains:<\/strong> Safe documentation and a coherent system that does not stay at the level of a general concept.\n\nStage 4. Launch and operational organisation<\/strong>\n\nWe help translate the programme into practice: communication to the team, application rules, answers to hard questions and how to manage the programme over time.\n\nWhat the client gains:<\/strong> Less tension at launch and greater confidence that the programme will be understandable for participants.","icon":"","order_within_specialization":0,"flexible_content":[{"acf_fc_layout":"hero","section_header":{"section_header":{"eyebrow":"","heading":"Zaprojektuj program motywacyjny, kt\u00f3ry zatrzyma kluczowych ludzi i uporz\u0105dkuje obietnice wobec zespo\u0142u","heading_highlight_mode":"split","heading_split":{"small_part_text":"incentive programme for a gamedev studio","strong_part_text":"a good game is made by people","":null,"small_part_size":"step-2","strong_part_size":"step-5","tag":"h1","style":"inherit","alignment":"inherit"},"description":"Do you want to reward the people working on the game, or encourage them to stay at the studio longer? We will help you define how the compensation programme should work, write the rules down and explain them to the team.","":null,"heading_tag":"h1","heading_style":"hero","alignment":"left"}},"actions":{"button_cluster":{"intro":"","buttons":[{"button":{"link":{"title":"Find the right operating model for your studio","url":"#contact","target":""},"variant":"primary","icon":"arrow","icon_size":"inherit","size":"default","aria_label":""}}],"alignment":"left"}},"media":{"media":{"image":2771,"mobile_image":"","object_position":"center","object_position_custom":""}},"section_meta":{"anchor_id":"","is_enabled":true},"variant":"split","mobile_body_card":false},{"acf_fc_layout":"person_cta","person":2710,"section_header":{"section_header":{"eyebrow":"","heading":"in a game every reward has rules; in a studio it should too","heading_highlight_mode":"split","heading_split":{"small_part_text":"in games a reward has its rules","strong_part_text":"in a studio it should too","":null,"small_part_size":"step-4","strong_part_size":"step-2","tag":"h2","style":"inherit","alignment":"inherit"},"description":"With incentive programmes it often feels clear at the start. You agree that there will be a bonus after launch. While the game is still in production, that seems fine. You may not even remember what you promised to whom.\n\nAfter launch, the team buries you in questions. An incentive programme helps you avoid that. Once everyone already has their own version of the promise in mind, it is much harder to sit down and set shared rules.","":null,"heading_tag":"h2","heading_style":"h2","alignment":"left"}},"carousel_settings":{"carousel_settings":{"autoplay_mode":"default","autoplay_delay":6.5}},"actions":{"button_cluster":{"intro":"Want to work with me?","buttons":[{"button":{"link":{"title":"Contact","url":"https:\/\/sawaryn.com\/en\/contact\/","target":""},"variant":"primary","icon":"none","icon_size":"inherit","size":"default","aria_label":""}}],"alignment":"center"}}},{"acf_fc_layout":"expandable_box","section_header":{"section_header":{"eyebrow":"most common problems and our solutions","heading":"the team will ask for specifics","heading_highlight_mode":"none","heading_split":{"small_part_text":"In games a reward has its rules. ","strong_part_text":"In a studio it should too.","":null,"small_part_size":"h4","strong_part_size":"h2","tag":"h2","style":"inherit","alignment":"inherit"},"description":"The team rarely asks which legal model you chose. It focuses on what, how, when and how much. Fortunately you do not have to foresee every variant and possibility. That part is our job.","":null,"heading_tag":"h2","heading_style":"section","alignment":"center"}},"items":[{"problem_title":"\u201cWhat is my bonus actually calculated from?\u201d","teaser_description":"In conversation someone says \u201ca percentage of the game\u2019s result\u201d. But sales, profit after production costs and the amount after settlement with the publisher produce three different figures. Until the studio chooses one base, everyone can mean a different amount.","solution_title":"We set one base","solution_description":"We look at the project finances and the settlement rules with the publisher. Together we decide which revenues and costs to include and at which point the reward can be calculated. Then we write that rule so the team and the person responsible for payment arrive at the same result.\nWe define which revenues and costs count, where the calculation data comes from and who performs the calculation. We test the finished rule on examples before it goes into the documents.","icon":"","accent":"blue","open":false},{"problem_title":"\u201cWhen do I actually get the bonus?\u201d","teaser_description":"The team delivered the milestone, but the publisher has not accepted the build yet. Acceptance arrived, but launch was postponed. If the programme does not separate those moments, each side may expect payment on a different date.","solution_title":"We define the \"what\" and \"when\"","solution_description":"Delivering a milestone, publisher acceptance, launch and the payment itself can happen at different times. We separate them and decide which one triggers the bonus. We also check whether extra conditions are needed - for example continued work with the studio or an individual goal. We describe who confirms they have been met and when the team learns the outcome.","icon":"","accent":"violet","open":false},{"problem_title":"\u201cWhat happens if the game launch slips?\u201d","teaser_description":"During production the launch date, project scope or role split may change. A programme written only for the first schedule quickly stops matching what is happening in the studio.","solution_title":"We prepare rules for a change of plan","solution_description":"We check what happens to goals, deadlines and the reward in several likely scenarios. We also decide who can change the programme assumptions and how to inform the team. That way every project change does not mean rewriting the rules from scratch.","icon":"","accent":"violet","open":false},{"problem_title":"\u201cWhat about my reward if I leave the team?\u201d","teaser_description":"One person may leave after two years on the game, another a few months after joining. The same answer will not always fit both situations. If the programme does not provide one, exit terms have to be set only when someone is already leaving.","solution_title":"We describe what happens after someone leaves","solution_description":"Together we decide what happens to the reward depending on when someone leaves and which conditions were met. We write the possible variants into the programme and explain them to the team before launch. Later the studio follows the adopted rules instead of negotiating them again.","icon":"","accent":"pink","open":false}],"section_meta":{"anchor_id":"","is_enabled":true}},{"acf_fc_layout":"box_variants","variant":"process-detail","section_header":{"section_header":{"eyebrow":"SCOPE OF COOPERATION","heading":"let's agree what you can promise the team","heading_highlight_mode":"none","heading_split":{"small_part_text":"","strong_part_text":"","":null,"small_part_size":"","strong_part_size":"","tag":"h2","style":"inherit","alignment":"inherit"},"description":"Behind a bonus, equity or a percentage of results there must be organisational decisions about who you reward, for what and how much the studio can allocate. We will help you make them, then prepare the documents and explain the rules to the team.","":null,"heading_tag":"h2","heading_style":"section","alignment":"center"}},"items":[{"title":"We will start with what matters to you","description":"","body":"

              Do you want the people working on the game to stay until launch? Share in sales results? Or are you talking about equity with someone who has been co-building the studio for years?<\/p>\nWe will establish:\n

                \n \t
              • who the programme should cover<\/li>\n \t
              • and what you want to reward.<\/li>\n<\/ul>\nWe will also return to earlier conversations with the team. We will check;\n
                  \n \t
                • what you have already promised,<\/li>\n \t
                • what you have written down,<\/li>\n \t
                • and what you were still considering.<\/li>\n<\/ul>\n ","tags":"Programme assumptions","count":"","accent":"pink","icon":""},{"title":"We will help you choose how to reward","description":"","body":"

                  A milestone bonus answers a different need than company equity. We will compare solutions that fit your plans: a bonus, profit share, equity, phantom shares or a combination of several forms.<\/p>\n

                  We will show you:<\/p>\n\n

                    \n \t
                  • what a programme participant will receive,<\/li>\n \t
                  • how the reward will be calculated,<\/li>\n \t
                  • when the studio will need to settle it,<\/li>\n \t
                  • what that choice means for the company and the founders.<\/li>\n<\/ul>\nWe will point to the model we recommend and explain why.\n\n ","tags":"Model comparison and recommendation","count":"","accent":"violet","icon":""},{"title":"We will account for changes that may appear along the way","description":"","body":"

                    The programme is meant to apply for months, sometimes years. In that time someone may leave, take another role or move to a second project. The launch date may also change.<\/p>\nWe will define how such situations affect the reward. We will separate the moment a participant earns the right to it from the payment date. We will also set what they keep after the cooperation ends.","tags":"Rules for when things change","count":"","accent":"blue","icon":""},{"title":"We will put the arrangements into documents","description":"","body":"

                    We will prepare the regulations, agreements, addenda or other documents needed for the chosen model. In them we will record participation terms, how the reward is calculated and settlement rules.<\/p>\nIt will be possible to check what a given person is entitled to, on what basis and what happens in the situations we discussed earlier together.","tags":"Documents to implement the programme","count":"","accent":"orange","icon":""},{"title":"We will check what the programme means for the company","description":"","body":"

                    Before you present the proposal to the team, we will check the obligations the studio takes on. For an equity model we will also look at how founders' shares and rights will change.<\/p>\n

                    We will factor in your plans for an investor or a studio sale. We will flag which clauses may complicate talks and what we propose to change before the programme is adopted.<\/p>","tags":"Impact map for the company and founders","count":"","accent":"pink","icon":""},{"title":"We will prepare you for the conversation with the team","description":"","body":"

                    \u201cDoes this cover me?\u201d will be one of the first questions. Right after it come the next ones:<\/p>\n\n

                      \n \t
                    • how much,<\/li>\n \t
                    • when<\/li>\n \t
                    • and under what conditions.<\/li>\n<\/ul>\nWe will help explain the programme so the team knows what you are offering. We will prepare a description of the rules and answers to questions about participation, rewards and programme limits. We will make sure the communication matches what we wrote in the documents.","tags":"Programme description and answers for the team","count":"","accent":"violet","icon":""}],"footer_heading":"","footer_tags":"","actions":{"button_cluster":{"intro":"","buttons":null,"alignment":"left"}},"section_meta":{"anchor_id":"","is_enabled":true}},{"acf_fc_layout":"box_variants","variant":"box-point","section_header":{"section_header":{"eyebrow":"WHO WE HELP","heading":"for studios that want to motivate the team","heading_highlight_mode":"none","heading_split":{"small_part_text":"","strong_part_text":"","":null,"small_part_size":"","strong_part_size":"","tag":"h2","style":"inherit","alignment":"inherit"},"description":"You may only be planning a programme, or you may already have had conversations where amounts and promises were made. We will help you decide what to do next - including when the current rules no longer fit the studio.","":null,"heading_tag":"h2","heading_style":"section","alignment":"center"}},"items":[{"title":"Founder | CEO | Studio management board","description":"The team is waiting for a proposal, and you want to know what the studio can afford. How much to allocate to rewards? Whether to give equity? How to tie a bonus to the game\u2019s result? We will help you make those decisions before announcing the programme.","body":"","tags":"reward budget \nparticipation terms \nfounders' decisions","count":"","accent":"orange","icon":""},{"title":" Head of Operations","description":"Someone remembers a conversation about a bonus; someone else got a promise when joining the project. The question lands with you: what to do about it. We will help gather the arrangements and describe rules you can point to every time someone asks \"what about me?\"","body":"","tags":"team arrangements \nsettlement dates \nrules on leaving\n\n","count":"","accent":"orange","icon":""},{"title":"General Counsel | Head of Legal | CFO","description":"You need to check what obligations toward the team the company takes on and whether the documents describe them without gaps. Perhaps the management board is waiting for your assessment of the programme, or due diligence is approaching. We will indicate what needs fixing and which decisions still need to be aligned with the founders.","body":"","tags":"company obligations \nclauses to fix \npreparation for due diligence","count":"","accent":"orange","icon":""}],"footer_heading":"","footer_tags":"","actions":{"button_cluster":{"intro":"","buttons":null,"alignment":"left"}},"section_meta":{"anchor_id":"","is_enabled":true}},{"acf_fc_layout":"cooperation_process","section_header":{"section_header":{"eyebrow":"STAGES OF COOPERATION","heading":"you do not need to arrive with a ready programme idea","heading_highlight_mode":"none","heading_split":{"small_part_text":"","strong_part_text":"","":null,"small_part_size":"","strong_part_size":"","tag":"h2","style":"inherit","alignment":"inherit"},"description":"","":null,"heading_tag":"h2","heading_style":"section","alignment":"center"}},"steps":[{"title":"Audyt","description":"We learn about your plans and the arrangements already made with the team. We identify what we need to propose a programme model.","accent":"pink"},{"title":"Model","description":"We discuss possible options and our recommendation. You choose a model knowing its implications for the studio and participants.","accent":"blue"},{"title":"Dokumenty","description":"We send drafts for your comments, explain the clauses and agree the details before preparing a version for adoption and signing.","accent":"violet"},{"title":"Implementation","description":"We help implement the programme and explain it clearly to the team.","accent":"orange"}],"cta_text":"Do you like the way we work?","actions":{"button_cluster":{"intro":"","buttons":[{"button":{"link":{"title":"Contact","url":"https:\/\/sawaryn.com\/en\/contact\/","target":""},"variant":"primary","icon":"none","icon_size":"inherit","size":"default","aria_label":""}}],"alignment":"left"}},"section_meta":{"anchor_id":"","is_enabled":true}},{"acf_fc_layout":"contact","section_header":{"section_header":{"eyebrow":"Write to us","heading":"turn informal promises into a programme that strengthens the studio","heading_highlight_mode":"none","heading_split":{"small_part_text":"","strong_part_text":"","":null,"small_part_size":"","strong_part_size":"","tag":"h2","style":"inherit","alignment":"inherit"},"description":"Tell us who you want to cover with the programme and what has already been said in conversations with the team. If you have a set date for announcing the rules, include that too. We will come back with questions or a proposed next step.","":null,"heading_tag":"h2","heading_style":"section","alignment":"center"}},"person":2654,"person_eyebrow":"Twoj\u0105 wiadomo\u015b\u0107 czyta","person_body":"They will get back to you with follow-up questions or a proposed next step.","response_title":"Quick response","response_body":"We usually respond within two hours on business days.","form":{"cf7_form":"","name_label":"Imi\u0119 lub nazwa podmiotu","name_placeholder":"Wpisz swoje dane","phone_label":"Telefon","phone_placeholder":"+48 000 000 000","email_label":"E-mail","email_placeholder":"twoj@email.pl","message_label":"Napisz, czego potrzebujesz","message_placeholder":"Opisz kr\u00f3tko sytuacj\u0119, etap rozm\u00f3w i termin decyzji.","privacy_text":"O\u015bwiadczam, \u017ce podane dane kontaktowe mog\u0105 zosta\u0107 wykorzystane do odpowiedzi na moje zg\u0142oszenie.","newsletter_text":"","button_label":"Sprawd\u017a model dla swojego studia"},"background":"","section_meta":{"anchor_id":"","is_enabled":true}}]},"_links":{"self":[{"href":"https:\/\/sawaryn.com\/en\/wp-json\/wp\/v2\/service\/2770","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/sawaryn.com\/en\/wp-json\/wp\/v2\/service"}],"about":[{"href":"https:\/\/sawaryn.com\/en\/wp-json\/wp\/v2\/types\/service"}],"version-history":[{"count":0,"href":"https:\/\/sawaryn.com\/en\/wp-json\/wp\/v2\/service\/2770\/revisions"}],"wp:attachment":[{"href":"https:\/\/sawaryn.com\/en\/wp-json\/wp\/v2\/media?parent=2770"}],"wp:term":[{"taxonomy":"specialization","embeddable":true,"href":"https:\/\/sawaryn.com\/en\/wp-json\/wp\/v2\/specialization?post=2770"},{"taxonomy":"practice_area","embeddable":true,"href":"https:\/\/sawaryn.com\/en\/wp-json\/wp\/v2\/practice_area?post=2770"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}