<?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/9e30a5c0675442f0b0b1f41e642682cf&quot; frameborder=&quot;0&quot; width=&quot;1280&quot; height=&quot;960&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>960</height><width>1280</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>960</thumbnail_height><thumbnail_width>1280</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/9e30a5c0675442f0b0b1f41e642682cf-75d1feacfa64e7cd.gif</thumbnail_url><duration>229.846</duration><title>Elevate Overview</title><description>This Loom explains the “Elevate” framework for getting engineering input into key business decisions before commitments are locked. It describes how companies often consult engineering after sales, product, or partnerships have already committed to features, roadmaps, or integrations, which causes engineering to be handed constraints without strategic influence. Elevate focuses on identifying decision types where engineering input materially changes outcomes, such as pricing with infrastructure implications, product commitments creating architectural debt, partnership integrations, and go-to-market timelines dependent on engineering capacity. It then positions the CTO to insert credibility into those conversations earlier by shifting from firefighting to strategic leadership and ensuring engineering has a voice before decisions are finalized.</description></oembed>