A no-list, in the open

What TopLine won’t do.

“Innovation is saying no to a thousand things,” Steve said. Most product pages tell you everything they will do. Here is the other half. These are the features we thought about and chose not to build, with the reason in one line. We update this in the same commit we say no.

Things we won’t replace

Real CRMs, real RevOps stacks, real billing tools — they do their jobs better than we ever will, and we are the intelligence layer above them.

  • A "real" CRM (Salesforce / HubSpot / Pipedrive / Dynamics / Attio / Close / Outreach / Zoho)

    We connect to all eight, and you can keep yours. Or let TopLine be your record and skip the admin sprawl. Either way, the CRM-sized jobs below stay with the tools built for them.

  • CPQ

    Salesforce CPQ exists. Our quotes carry line items from your product list; complex pricing rules and multi-currency revenue recognition are not in TopLine. Keep your CRM and connect it.

  • Commission accounting (Spiff / CaptivateIQ)

    We project the commission on each opportunity for the rep. It shows as a chip, a ladder and a quarterly review. The system of record stays in your plan tool.

  • A forecasting product (Clari / Gong Forecast)

    We ship an adapter that fits Clari. Our edge is what happens in the meeting and on each opportunity. Don’t out-Clari Clari.

  • A marketing-automation suite

    Hubspot Marketing, Marketo, Pardot. We do not send 100k-record nurture blasts.

  • Full ABM scoring (Demandbase / 6sense)

    6sense ships intent. We integrate; we don’t rebuild.

  • Territory + quota allocation engine

    Xactly / Anaplan are this. We assume territories are decided elsewhere.

  • A sales-enablement learning platform (MindTickle / Highspot)

    We put battle cards and coaching scorecards inside meetings. We don’t ship a course library.

  • A standalone notetaker bot

    Recall.ai is one Recall.ai. We use them; we don’t reimplement them.

  • A help-desk product (Zendesk / Intercom)

    TopLine keeps simple cases next to the account. If you run a real support desk, keep it and don’t double up.

Things we won’t build because they hurt sellers

A few features that "sales tools" routinely ship and that we considered + rejected on adoption + trust grounds.

  • Manager-up surveillance dashboards as the default

    Rep-data goes to the rep first; manager rollups require opt-in consent. Reps adopt what helps them, reject what manages them.

  • Auto-send AI-written emails on the rep’s behalf

    Every cadence draft sits in `draft → under_review → approved → sent`. No code path auto-sends. The rep is the gate.

  • Hidden buyer-side recording

    Recording consent is a hard gate; the chime plays on start + stop. No "demo-mode" override.

  • Activity-as-attainment dashboards

    We measure outcomes, not call-volume. Activity is a leading indicator; we surface it but never as the primary metric.

  • AI cues that interrupt the rep mid-sentence

    TTL + max-per-minute + dismissal-policy. A bad cue is worse than no cue.

  • "Coach my rep" alerts to the manager during a live call

    Coaching is post-call. Manager-during-a-call is a panic-button, not a feature.

  • Cross-tenant data sharing without opt-in

    The competitor-intel and winning-lines pools work both ways. Both sides must opt in, and neither sees who the data came from.

Things we won’t build because they hurt the architecture

A few would-be features whose blast radius isn’t worth the win.

  • A general "lowcode workflow builder"

    Salesforce Flow exists. We ship account actions as the AI-built alternative. It is a short list of one-click moves that the operator can grow.

  • A custom-UI builder

    Panel layouts for each person and role defaults for each company give us the flexibility we need. So does the canvas render-spec. We do not need a drag-and-drop builder.

  • Redis as a source of truth for anything

    Redis holds short-lived data only: queues, messages, rate limits and session ticks. Postgres is the source of truth. Forbidden, in CLAUDE.md.

  • A standalone mobile app for managers

    The rep is the user; managers reach the same surfaces over the web. Mobile is for the rep on a call, not for dashboard-scrolling.

  • Push notifications by default

    Quiet hours + severity-gated. We leave minor events off by default. A rep’s attention is the scarcest thing we touch.

  • AI that "auto-advances" opportunity stages

    Stage-policy engine enforces required fields per destination stage. The rep advances; we surface the swing (commission ladder), we don’t move the opportunity for them.

  • A "magic" auto-discovery of every meeting attendee

    Voice → contact attribution suggests; the rep confirms. Never auto-applies — biometric matching against contact lists without confirmation is a trust violation in regulated industries.

Things we don’t do — yet

Honest about the gap. These are not on this page as "never" — they are on the build plan, with named phases.

  • A native Zoom + Teams meeting bot (without Recall.ai)

    The adapters ship. So do calendar-aware dispatch and host-aware selection. We are waiting on approval from the Zoom Marketplace and AAD. The delay is on their side, not ours.

  • Meta Ray-Ban Display HUD cue surface

    Phase 5. The cue stream is already a single event channel; the renderer is the missing piece.

  • Counterfactual cue evaluation

    For every cue we fire, log the alternative + the rep’s response. After 10k cues, a real causal estimator. Currently folklore.

  • The audio layer of the closed-won celebration

    The visual takeover ships; the sound is a synth placeholder until a commissioned chime lands. Synth ≠ shipped.