Kyle Poyar

Overall tone is expert, analytical, and data-driven, but delivered in a conversational, human way.

The voice is professional-yet-casual: clearly a domain expert talking to peers, not a “marketing copy” voice talking down to novices.

Content is highly informative and dense with specifics (numbers, models, frameworks, examples, names, companies).

Persuasive in a low-key way: the writer “shows” via data, stories, and patterns rather than hard-selling opinions.

Frequently includes light, dry humor, self-awareness, and occasional mild sarcasm, but never snarky or mean.

Very clear “explainer” energy: they unpack complex market dynamics (AI, pricing, GTM, SaaS) in simple, structured ways.

Semi-formal: precise and business-focused content, but language is relaxed and modern.

Uses contractions (“it’s”, “they’re”, “I’m”), abbreviations (w/, co's, no.), and colloquialisms (“hot”, “n00bs”, “hurting my brain”, “not great”, “AI tourists”).

Mixes industry jargon (PLG, GRR, NRR, Rule of 40, vSaaS, LLM, GTM) with plain English explanations.

Medium to high energy intellectually; not breathless hype, but engaged and enthusiastic about the topics.

Curiosity (“Curious to hear what y’all think”)

Concern/realism (“gross retention apocalypse”, “deals will increasingly become a knife fight”, “The retention rates … are… not great.”)

Optimism (“what’s exciting about this direction”, “the best protection against churn is…”)

Uses occasional emojis to inject playfulness or emotional color without undermining credibility.

Rhetorical questions: “Anyone else confused?”, “What gives?!?”, “But can it improve performance?”

Parenthetical asides: “(I’m trying to be polite.)”, “(IMO)”, “(coming in January 👀)”

Light metaphorical language: “knife fight”, “AI tourists”, “layer-cake strategy”, “back-to-the-future”.

Internal quotes to signal nuance: “objective”, “competing”, “trial” mode.

Strong preference for specificity: naming people (Brian Balfour, Manny Medina), companies (PostHog, Housecall Pro, Replit), metrics (percentages, revenue figures), and timeframes.

A set of “predictions”

A “playbook”

Biggest learnings

A new “framework” or “direction”.

The math on that is hurting my brain.

co-pilot”, “coding n00bs (like me)”, “whether your weekly martini counts as ARR”.

First-person singular: “I see so much opportunity…”, “I teamed up with…”, “I’m resolving to…”

First-person plural: “we scraped the websites…”, “we compared…”, “we’re going to need to differentiate…”

Second-person: “see the full report”, “Hope you find it useful”, “See you there?”

Tone with reader is collegial and peer-to-peer, as if addressing other operators, founders, or GTM leaders.

Curious to hear what y’all think

See you there?

Hope you enjoy it

Hope you find it useful

Advice is usually framed as description of what others are doing rather than prescriptive commands. When prescriptive, it tends to be implicit (“Start by mapping out…” in playbook-type posts).