Post-call CRM entry is a good problem to pick because the output is structured and checkable - name, intent, follow-up date are fields you can validate, not a summary someone has to judge. That also makes the failure mode manageable: a wrong date is visible to the rep, unlike a subtly wrong paragraph. Two minutes to three seconds is a big enough jump that the interesting detail is where the time was going. In pipelines like this it is usually not the model but the serial arrangement around it - waiting for a full transcript before extraction starts, one request per field, or a synchronous write at the end. Curious which of those dominated for you, since that is the transferable part of the result.
Post-call CRM entry is a good problem to pick because the output is structured and checkable - name, intent, follow-up date are fields you can validate, not a summary someone has to judge. That also makes the failure mode manageable: a wrong date is visible to the rep, unlike a subtly wrong paragraph. Two minutes to three seconds is a big enough jump that the interesting detail is where the time was going. In pipelines like this it is usually not the model but the serial arrangement around it - waiting for a full transcript before extraction starts, one request per field, or a synchronous write at the end. Curious which of those dominated for you, since that is the transferable part of the result.