Lila Ozturk

Founder, CEO · Pivot CRM

Lila runs Pivot, a CRM for small B2B sales teams. $400K ARR across about 80 customers, mostly 5-to-15-person sales teams at startups.

The setup

Pivot is a CRM for small B2B sales teams. Lila bootstrapped it three years ago, hit $400K ARR last fall, and has been running it lean ever since, two engineers, one sales lead, and her.

Pivot is not a thin-margin business. Its customers are startups paying $39 per seat per month for a tool that sits next to Slack in their daily workflow. Retention has been good. Until last quarter.

Last quarter Pivot lost three customers to silent churn. None filed a support ticket. None replied to renewal outreach. They just stopped logging in. Two weeks before the renewal date, Lila pulled the usage report and realized she’d been blindsided. By the time she made the calls, two of them had already signed with a competitor.

Three customers at her ACV is $14K of recurring revenue gone in a quarter. Annualized, that’s nearly 15% of the business, and the rate was accelerating. She came to Zynkex with a single sentence: “I need to catch the signal before it becomes a cancellation.” She thought she was going to walk out with a dashboard.

The session

The session opened with Lila’s framing: dashboard. Within the first six rounds, Zynkex pushed back. Dashboards die because nobody acts on them. The numbers sit there, everyone stares at them on Monday, nobody changes what they do on Tuesday. The pattern that works isn’t a dashboard, it’s a signal landing in front of the person who can act, at the moment they’re already thinking about the week ahead.

That reframe opened the central question of the session: what is the moment of decision Lila, and Lila’s customers, are already making? She didn’t have to think about it for long.

“Monday morning. I look at last week’s numbers, I think about what to focus on. That’s when this would matter.”

From there, the architecture fell into place quickly. The product is not a dashboard inside Pivot. The product is the Monday-morning view a founder reaches for when she opens the laptop on the first day of the week. A short list of customer names. One sentence about each. One action per row. Calm voice, no anxiety amplification, this is the founder’s COO speaking, not a smoke alarm.

The strategic moment was identifying the founder, not the CS rep, as the actual audience. Pivot’s existing surface serves the sales lead, daily user, in the pipeline view every morning. The founder logs in once a week. Building for the daily user means building another dashboard the founder ignores; building for the founder means building a new front door, a new ritual, and a new pricing tier that follows from the new positioning.

By the end of the session, Pivot’s product narrative had shifted. Not "Pivot is a CRM." Not even "Pivot is a CRM with a churn prediction feature." Pivot is the founder’s Monday-morning operating system. The churn surface is the first surface; more founder-facing rituals follow.

The Build Brief

For Lila’s two engineers. Directive throughout. Names the surface, the signal pipeline, the email digest, the voice rules, the operational handoffs. The .docx the engineering team works from.

Build Brief for the Pivot CRM Monday-morning churn-prevention surface. Paste into your AI coding tool; the tool will determine the file structure for the build environment. The implementation extends the existing Pivot CRM web app with a new /monday surface, a signal-ingestion job, a churn-scoring module, and a configurable email digest. Read end-to-end before generating code, the founder-as-audience frame in Section 1 governs every CTA, copy, and surface decision downstream.

Pivot CRM, Monday-morning churn surface

What this is. A new surface inside the existing Pivot web app, plus the signal pipeline that powers it, that catches silent-churn before it becomes a cancellation. It is built for the founder's Monday-morning planning ritual, not for the customer-success team's daily workflow.

The founder-as-audience constraint. Every decision in this brief is gated on the fact that the primary user is the founder of Pivot's customer companies, not their CS rep, not their sales engineer. Founders open the tool once a week, on Monday morning, to plan the week. They will not log in daily. They will not configure dashboards. The surface is designed for that single ritual.

Pivot is not adding a churn dashboard. Pivot is adding the Monday-morning view a founder reaches for to plan the week.

When uncertain whether to ship a feature, ask: does this serve a founder who opens the tool weekly? If yes, ship it. If it requires daily check-ins or configuration to be useful, reject it.

Section 1. Users and jobs-to-be-done

Primary user: the founder. They run a 5-to-15-person sales team. They have a sales lead but no dedicated customer-success function. They open Pivot weekly, Monday morning, between 7am and 9am their local time, to plan the week.

Job to be done: "Tell me which customers are at risk so I know who to call, who to ping the AE about, and who to take off my mind this week."

Secondary user: the sales lead. They open Pivot daily. They use the existing pipeline and contact views; they do not own churn-prevention. Founders may ping them with names surfaced from the Monday-morning view.

Job to be done: "Stay out of my pipeline workflow. Surface insights to me only when the founder asks."

Section 2. The Monday-morning surface

A new top-level route: /monday. Default landing surface for any user whose role is founder and who logs in between Sunday 6pm and Tuesday 9am local time. Other users continue to land on the existing pipeline view.

Above the fold: the at-risk-account list.

Section title (H2): Customers to think about this week.

Purpose: primes the founder's attention without alarmism. "To think about" is softer than "at risk" or "in danger"; it respects that the founder may already know the context.

Cumulative contribution: this single section carries the entire weekly conversion job. If a founder doesn't open /monday on Monday morning and immediately know which three names to act on, the product has failed for the week.

Each row in the list shows:

Customer name (large, no logo, typography only).
A single-sentence "what changed" note in the AI's voice. Example: "Login depth dropped 60% the last two weeks; the champion (Sara) has not logged in at all."
A confidence chip: high signal / worth a check / quiet for now.
A primary CTA: Ping the AE (opens prefilled Slack DM via the existing Slack integration). Purpose: the founder's next action is almost always to delegate the call to the AE, not to call the customer directly. Make that one click.
A tertiary text link: Mark as handled (snoozes the row for 7 days).

Resist the urge to add a "Risk score" number column. Founders respond to language ("Sara hasn't logged in") not to numbers (78%). Numbers ask the founder to interpret; sentences tell them what to do.

Below the fold: the quiet-good list.

Section title (H2): Customers to leave alone.

Purpose: the explicit absence-of-attention list. Founders worry that quiet customers are silently churning; this section names the customers whose signal is healthy so the founder can release them from working memory.

Each row: customer name, one sentence about why they are healthy ("Steady weekly logins from three users; expansion event last Thursday").

No CTA on these rows. The action is "leave alone."

Section 3. Signal architecture

The score that drives the list is computed nightly. Inputs:

login_depth_14d: the number of distinct users who logged in from the customer org in the trailing 14 days, normalized to that org's 90-day baseline.
champion_silence_days: days since the named champion (set during sales hand-off) last logged in.
feature_engagement_decay: trailing 14-day vs trailing 60-day usage of the top three features for that customer's segment.
expansion_or_contraction_events: any seat-count changes, plan changes, or invoice anomalies in the trailing 30 days.

The scoring rule: any one of these in the red zone surfaces the customer on the Monday view. Two or more compounds the confidence chip from worth a check to high signal.

The scoring is intentionally interpretable. A founder reading the "what changed" sentence should be able to map it back to one of the four inputs in their head.

Section 4. The Monday-morning email digest

The same content as the /monday surface, sent as an email at 6:30am local time on Monday. Default-on for any user with role founder. Toggleable in account settings.

Subject line: "3 customers to think about this week." The number is dynamic. Purpose: the integer is the load-bearing trust signal. A founder who sees the same generic "Weekly digest" subject line every Monday stops opening. A specific number is read as "this email did some work."

The email body mirrors the surface: at-risk list at the top, quiet-good list at the bottom. Each row links into the in-app view; the in-app surface remains the canonical action layer.

Resist the urge to send a daily digest. The whole product is positioned around the once-a-week ritual; a daily email betrays that frame and trains the founder to ignore the surface entirely.

Section 5. Voice and copy

The surface speaks founder-to-founder. Plain, calm, never alarmist.

Phrases to use. Worth a check. The champion has not logged in. Steady weekly logins. Expansion event last Thursday.

Phrases to avoid. At risk! Critical! Action required. Customer in danger. Don't ignore this.

The voice is what differentiates the Monday-morning view from every churn-prediction tool the founder has ignored before. Anxiety-amplification copy makes the surface feel like a smoke alarm; calm-attention copy makes it feel like a trusted COO.

Section 6. Operational details to provide

The Slack integration's bot token (existing, confirm scope includes DM sending).
The list of customer orgs whose champion contact is set; any without need a UI flow to set it (out of scope for this surface; surface them in a "needs champion" widget).
The email delivery service Pivot currently uses (Postmark, per recent context, confirm).

The Strategy Plan

For Lila to take into the next investor conversation. Names the repositioning, the pricing tier, the moat. The .docx the board reads before the Series A pitch.

Pivot CRM, Strategy Plan

Pivot's $400K ARR business is leaking three customers a quarter to silent churn, and the upside is bigger than churn recovery. Repositioning Pivot from "sales pipeline tool" to "the founder's Monday-morning operating system" is the strategic upgrade that opens the next funding round, the higher pricing tier, and the founder-attention moat competitors can't copy quickly.

Opportunity

$400K ARR across 80 paying customers. Three silent churns last quarter, none filed a ticket, none replied to renewal outreach, all just stopped logging in.

The recovery: 12 customers a year, ~$48K ARR retained. The hidden upside: a founder-segment product position that justifies a higher price tier and opens a Series A narrative.

The actual audience is the founder of a 5-to-15-person sales-team company. They use Pivot indirectly through their sales lead today. The sales lead is the daily user, but the founder is the buyer and the renewer, and the founder is the audience whose attention Pivot has been failing to capture.

Founders do not want a dashboard. Founders do not want a daily digest. Founders want one weekly view that tells them what changed and who to think about. That is the product Pivot has been adjacent to building without naming.

Our Position

Pivot is not adding churn prediction. Pivot is becoming the founder's Monday-morning operating system.

The CRM-as-pipeline category is crowded and undifferentiated. The CRM-as-founder-tool category is empty. Salesforce serves the sales lead; HubSpot serves the marketer; Pipedrive serves the AE. Nobody builds for the founder of a 12-person company who opens the tool once a week to plan.

If Pivot ships the Monday-morning surface and the founder logs in every Monday for a year, Pivot becomes the founder's ritual. That ritual is the moat. Competitors can copy the churn score in a quarter; competitors cannot copy the Monday-morning habit Pivot has trained.

Every product decision downstream is gated on this position. Daily-digest emails break it. Configuration UIs break it. Dashboards with sixteen metrics break it. The Monday-morning surface is the only surface that protects the position.

The Strategy

Founder-as-audience. The Monday-morning surface is built and copy-edited for the founder, not the CS rep. Plain language, three-to-five names per Monday, one action per name. The sales lead's existing workflow is untouched.

The signal architecture earns the founder's trust through interpretability. The score is built from four inputs (login depth, champion silence, feature decay, expansion/contraction). The "what changed" sentence on each row maps back to one of the four. Founders never see a percentage they don't understand.

Voice as differentiator. The surface speaks calmly. No urgency markers, no red badges, no "action required." The voice carries the position: this is a trusted COO, not a smoke alarm.

Pricing implications. The Monday-morning surface lives on a new Pivot for Founders tier at $79/seat/month (vs $39 for the existing per-seat plan). Existing customers grandfather; new founder-tier seats are sold separately. Target outcome: 20% of customers add at least one founder seat within 90 days.

The decisions we made.

Weekly cadence, not daily. The whole product is the founder's once-a-week ritual.
Names, not numbers. The surface speaks in sentences.
One action per row. Ping the AE. Mark as handled. Nothing else.
No new dashboards. The Monday-morning surface is the only new view.
Email digest is default-on for founders. The trust signal is the dynamic subject line.

Risks

The single largest risk is mistaking the Monday-morning surface for "an additional view inside Pivot" instead of "the new front door for founders." If the surface ships as a tab next to Pipeline and Contacts, founders never find it, never open it, never integrate it into their week. Mitigation: route founders to /monday as their default landing surface on Sunday-evening-through-Tuesday-morning login windows.

Second risk: alert fatigue. If the surface shows the same names every week, founders stop trusting it. Mitigation: the surface only shows a customer when the score crosses a threshold change week-over-week. Steady-state at-risk customers without new signal change roll off the visible list after two weeks; they re-surface only on new movement.

Open, whether to expose the Pivot for Founders tier publicly on the pricing page from day one, or land it as a quiet expansion offer to existing customers first. Deferred until the first thirty days of founder-tier signups tell us whether the public messaging needs the social proof of customer logos first.

What’s your Monday-morning question?

Already have an account? Sign in