> ## Documentation Index
> Fetch the complete documentation index at: https://docs.oneperfectslice.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Example: Renewal Call Summary

> A real example of the structured summary OnePerfectSlice generates for a renewal call — showing renewal signals, renewal risks, decision dynamics, and deal-level slices.

This is an example summary generated from a renewal call between an account manager at **Vetro** (a B2B data integration platform) and the data team at **Clarion Logistics**, an existing customer approaching their annual renewal.

<Info>All names, companies, and details are fictional. The structure and depth of the output reflect what OnePerfectSlice actually produces.</Info>

***

## BLUF (Bottom Line Up Front)

Clarion Logistics intends to renew but is leveraging three quarters of Salesforce connector issues to negotiate a pricing restructure — strong platform dependency and organic adoption growth from 3 to 7 pipelines signal retention, while the CTO's request to "bring back options" is a soft competitive signal that adds urgency to closing the restructured deal before the 45-day expiration window.

***

## Renewal Signals

* **Deep platform adoption**: Expanded from 3 to 7 active pipelines organically — no sales push required. Operations team built daily warehouse replenishment reporting on top of Vetro that is now business-critical.
* **Team dependency**: Marcus said "our ops team would revolt if we pulled Vetro out at this point" — the platform is embedded in their daily workflows with no viable alternative in place.
* **Unprompted expansion interest**: Marcus asked about the real-time streaming tier without prompting — they want to track inventory movement across 12 distribution centers, currently running batch jobs every 4 hours.

***

## Renewal Risks

* **Salesforce connector frustration**: Three support tickets in the past quarter related to sync failures and field mapping issues on custom objects — Marcus described this as "the one thing that keeps coming up" in their internal platform reviews.
* **CTO pressure to evaluate options**: Marcus mentioned the CTO asked him to "bring back options" — no formal evaluation underway, but the door is open if Vetro doesn't address their concerns during the renewal window.
* **Pricing sensitivity**: Marcus framed the renewal as an opportunity to "reset the economics" — they feel per-pipeline pricing doesn't reflect the volume they're running through the platform.

***

## Decision Dynamics

* **Decision authority**: Marcus has authority to approve the renewal but indicated the CTO is watching the outcome, particularly on pricing and the Salesforce connector resolution.
* **Pricing structure preference**: Marcus wants to move from per-pipeline to volume-based pricing — needs a restructured proposal he can present to the CTO as a win within one week.
* **Timeline constraint**: Contract expires in 45 days. Marcus wants the restructured proposal within one week, CTO conversation likely within two weeks after that.

***

## Additional Context

| Element                    | Value                                                                                                                                                                                                                           |
| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Proposal Pricing**       | Current per-pipeline model is the main negotiation point. Marcus wants volume-based pricing that accounts for their growth from 3 to 7 pipelines. Streaming tier would be incremental budget.                                   |
| **Budget**                 | No specific dollar amount discussed. Budget exists for renewal — the negotiation is about structure (per-pipeline vs. volume) rather than total spend. Streaming tier expansion would require separate approval.                |
| **Alternatives Discussed** | No specific competitors named. CTO's "bring back options" is the only competitive signal — more of a negotiation lever than an active evaluation.                                                                               |
| **Decision Process**       | Marcus approves renewal, CTO has oversight. Two-step process: (1) agree on restructured pricing, (2) CTO sign-off on the package including connector resolution commitment.                                                     |
| **Deal Risks**             | If Salesforce connector issues recur during the renewal window, it undermines the reliability narrative. Pricing negotiation could stall if the restructured proposal doesn't land within the one-week window Marcus requested. |
| **Timeline Urgency**       | Contract expires in 45 days. Marcus wants restructured proposal within one week. CTO conversation expected within two weeks. Need verbal commitment before the 30-day expiration threshold.                                     |

***

<Card title="How summaries work" icon="arrow-right" href="/product/summaries">
  Learn how OnePerfectSlice generates structured summaries automatically for every call, tailored by call type.
</Card>