<?xml version="1.0" encoding="UTF-8"?><oembed><type>video</type><version>1.0</version><html>&lt;iframe src=&quot;https://www.loom.com/embed/b9342ee62b5e404cb60b1c9b99d5c82c&quot; frameborder=&quot;0&quot; width=&quot;1920&quot; height=&quot;1440&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1440</height><width>1920</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1440</thumbnail_height><thumbnail_width>1920</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/b9342ee62b5e404cb60b1c9b99d5c82c-35e5feaeb742dcf3.jpg</thumbnail_url><duration>83.467</duration><title>Why we built Wagepoint 2.0</title><description>This Loom explains the rationale and benefits of moving from version 1.0 to 2.0. The speaker says 1.0 is built on an archaic, not future-proof co-refusion code architecture, which drove the shift to a clean, modern, scalable code base that enables more automation and ongoing innovation. They emphasize that 2.0 gives customers more control, making tasks like adding custom code or a special bonus for an employee much easier without needing to reach out to the team first. The Loom also highlights a goal of a single integrated platform for HR, payroll, time, and mobile functions rather than disjointed apps.</description></oembed>