<?xml version="1.0" encoding="UTF-8"?>
<record
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://www.loc.gov/MARC21/slim http://www.loc.gov/standards/marcxml/schema/MARC21slim.xsd"
    xmlns="http://www.loc.gov/MARC21/slim">

  <leader>01769nam a2200217Ia 4500</leader>
  <controlfield tag="003">OSt</controlfield>
  <controlfield tag="005">20260718102836.0</controlfield>
  <controlfield tag="008">230508s2022    xx            000 0 und d</controlfield>
  <datafield tag="050" ind1=" " ind2=" ">
    <subfield code="a">Allied HD 9665.5</subfield>
    <subfield code="b">K48 2022</subfield>
  </datafield>
  <datafield tag="100" ind1="1" ind2=" ">
    <subfield code="a">Moorman, Mike</subfield>
  </datafield>
  <datafield tag="245" ind1="1" ind2="0">
    <subfield code="a">Key account management excellence in pharma &amp; medtech /</subfield>
    <subfield code="c">Mike Moorman.</subfield>
  </datafield>
  <datafield tag="264" ind1=" " ind2=" ">
    <subfield code="a">London : </subfield>
    <subfield code="b">Routledge, </subfield>
    <subfield code="c">2022.</subfield>
  </datafield>
  <datafield tag="300" ind1=" " ind2=" ">
    <subfield code="a">xxv, 216 pages ;</subfield>
    <subfield code="c">24 cm.</subfield>
  </datafield>
  <datafield tag="500" ind1=" " ind2=" ">
    <subfield code="a">Includes index</subfield>
  </datafield>
  <datafield tag="505" ind1="0" ind2=" ">
    <subfield code="a">ch. 1. Kam is a business strategy, not a role &#x2014; ch. 2. The rise of the organized customer and kam in healthcare &#x2014; ch. 3. Where to play: key account segmentation and selection &#x2014; ch. 4. Value strategy: evolving from basic offerings to advanced solutions &#x2014; ch. 5. Kam organization design: form follows function &#x2014; ch. 6. Executive alignment and engagement: its make or break for life sciences kam program &#x2014; ch. 7. Kam program office: marshalling the internal support required for results &#x2014; ch. 8. The long and short of kam matrics &#x2014; ch. 9. Customer engagement process: the secret to agile execution &#x2014; ch. 10. Bringing  value to account planning and management &#x2014; ch. 11. Context is king: laying the foundation for a comprehensive kam talent strategy &#x2014; ch. 12. The unique learning journey required for kam &#x2014; ch. 13. Key account manager incentive compensation: aligning to strategic objectives &#x2014; ch. 14. Why technology is critical for breathing life into kam &#x2014; ch. 15. Kam in the United States versus Europe: are we headed to the same place? &#x2014; ch. 16. The future of kam in life science. </subfield>
  </datafield>
  <datafield tag="650" ind1=" " ind2="0">
    <subfield code="a">Pharmaceutical industry</subfield>
    <subfield code="x">Management</subfield>
  </datafield>
  <datafield tag="650" ind1=" " ind2="0">
    <subfield code="a">Medical supplies industry</subfield>
  </datafield>
  <datafield tag="650" ind1=" " ind2="0">
    <subfield code="a">Marketing</subfield>
    <subfield code="x">Key accounts</subfield>
  </datafield>
  <datafield tag="650" ind1=" " ind2="0">
    <subfield code="a">Customer services</subfield>
  </datafield>
  <datafield tag="942" ind1=" " ind2=" ">
    <subfield code="2">lcc</subfield>
    <subfield code="c">BK</subfield>
    <subfield code="k">EAC Cavite-Allied</subfield>
  </datafield>
  <datafield tag="999" ind1=" " ind2=" ">
    <subfield code="c">33454</subfield>
    <subfield code="d">33454</subfield>
  </datafield>
  <datafield tag="952" ind1=" " ind2=" ">
    <subfield code="0">0</subfield>
    <subfield code="1">0</subfield>
    <subfield code="2">lcc</subfield>
    <subfield code="4">0</subfield>
    <subfield code="7">0</subfield>
    <subfield code="a">CAVITE</subfield>
    <subfield code="b">CAVITE</subfield>
    <subfield code="c">EAC Cavite-Allied</subfield>
    <subfield code="d">2023-05-16</subfield>
    <subfield code="g">4041.00</subfield>
    <subfield code="l">0</subfield>
    <subfield code="o">Allied HD 9665.5 K48 2022</subfield>
    <subfield code="p">ML16623</subfield>
    <subfield code="r">2026-05-29 00:00:00</subfield>
    <subfield code="w">2023-05-16</subfield>
    <subfield code="y">BK</subfield>
  </datafield>
</record>
