{
  "schemaVersion": 1,
  "id": "winner",
  "language": "en",
  "canonical": "https://paynalton.tech/en/projects/winner/",
  "title": "Winner",
  "summary": "Winner emerged when the withdrawal of an external platform put a near-launch campaign at risk. I reused components, added a Laravel service and deployed the solution on AWS. The development allowed meeting the deadline and was later reused in other campaigns.",
  "role": "Component reuse, service integration and deployment.",
  "operationalStatus": "Historical case; current operational situation not confirmed.",
  "startLabel": "2022.",
  "technologies": [
    "Laminas API Tools",
    "Laravel",
    "AWS ECS"
  ],
  "body": "## Background: a platform with limitations\n\nIn 2020 we worked on a campaign whose journey included a game and an experience that had to be executed on an authorized platform. During the review, several functions were flagged as incompatible with its capabilities.\n\nThe platform allowed adding custom CSS and JavaScript. I created a tool to copy the generated HTML and use it as a local development template. The team built the application on that basis and I prepared the minified code to incorporate it through the available fields. This way we managed to integrate the planned journey using the platform's extension mechanisms.\n\nThe team, which was around four people at the time, carried out the deployment with my remote guidance. That delivery strengthened the relationship with the client and led to more projects.\n\n## The need for Winner\n\nThe client of these campaigns was Reckitt.\n\nIn 2022, just before the launch of another campaign, the client ended the contract with the platform and ordered to stop related projects. To preserve the campaign we built Winner in a week.\n\nI recycled part of a previous project developed with Laminas API Tools, added a Laravel service and hosted the solution on AWS. It was my first experience using ECS. I personally carried out the deployment of this new platform.\n\n## Scope and evolution\n\nThe first version covered the campaign's journey: form presentation and games, data collection and metrics. The campaign was able to launch on time.\n\nAs with other solutions born out of urgency, I prepared a base that could continue to be used. Winner was used in more campaigns and later incorporated a chatbot and integrations with external services, such as customer data platforms (CDP).\n\n## Results and learning\n\nThe reuse of components and integration of services allowed responding to the withdrawal of an external dependency without losing the launch date. Afterwards, the platform supported new campaigns until the client stopped investing in games and prizes.\n\nThe case includes two learnings: examining the real possibilities of a platform before discarding an experience and designing a viable exit when conditions change abruptly.\n",
  "relations": [
    {
      "kind": "during",
      "id": "sodigital",
      "title": "SoDigital",
      "url": "https://paynalton.tech/en/experience/#sodigital"
    },
    {
      "kind": "demonstrates",
      "id": "desarrollo-fullstack",
      "title": "Fullstack development and applications",
      "url": "https://paynalton.tech/en/topics/desarrollo-fullstack/"
    },
    {
      "kind": "demonstrates",
      "id": "tecnologia-aws-ecs",
      "title": "AWS ECS",
      "url": "https://paynalton.tech/en/topics/tecnologia-aws-ecs/"
    },
    {
      "kind": "demonstrates",
      "id": "tecnologia-laminas-api-tools",
      "title": "Laminas API Tools",
      "url": "https://paynalton.tech/en/topics/tecnologia-laminas-api-tools/"
    },
    {
      "kind": "demonstrates",
      "id": "tecnologia-laravel",
      "title": "Laravel",
      "url": "https://paynalton.tech/en/topics/tecnologia-laravel/"
    }
  ]
}