Kathy Svetina
Professionalizing Finance Ops for Growing Companies | Fractional CFO | FP&A Infrastructure | Cash Flow Management | Forecasting | Board and Investor Ready Financials
Kathy Svetina teaches finance ops professionals how to build scalable financial infrastructure for growing companies, using problem-solution storytelling that converts 31.8% of engagement into comments. Her distinctive move is opening with a relatable business pain point (often quoted directly from a founder conversation) then systematically dismantling the myth that the problem is unsolvable.
0.8/wk
0 posts in 30d
24
avg per post
31.8%
comments / total
0.8%
reposts / total
problem-solution
Sun · 2 AM CET
Voice & tone
Conversational, slightly exasperated, and deeply empathetic to founder frustration. She writes like someone who has heard the same broken excuse 100 times and is tired of it. Phrases like 'It sucks, a lot' and 'That's essentially putting lipstick on a pig' show she refuses corporate sanitization. She's direct without being cold, and uses casual language ('the horse's mouth,' 'blowing my mind') to feel like a peer, not a consultant.
Signature phrases
- “It sucks, a lot.”
- “That's essentially putting lipstick on a pig.”
- “I hear this a lot, but no matter how many times I hear it”
- “The crazy part is that this is completely fixable.”
- “If it ain't clear to see, your numbers people will have to twist themselves into a pretzel”
- “flying that financially blind comes with a huge cost”
Top 3 posts, dissected
Their highest-engagement posts, broken down line by line. Steal the structure.
Are we really at a point of AI usage when a customer service directs you to use ChatGPT vs giving you an answer from their company's system? Called Lenovo today to figure out some specs for a laptop I'm trying to get. The person on the phone actually told me to use ChatGPT because it's friendlier than their own system. He then proceeded to read what it said. When I pushed back and said I'd prefer to get the information directly from the horse's mouth (you know, the actual company that makes the product), he doubled down. He tried to convince me that ChatGPT would actually give me MORE accurate information than Lenovo's own internal systems. I honestly don't know what to think of this... ps: if anyone has a ThinkPad P16s gen3 and can tell me where the vents are, I'd be very grateful because apparently the Lenovo reps have no idea. **UPDATE: The good people of Reddit have spoken - the vents are by the hinges, blowing in the back. My hands are going to be spared of all the hot air blowing on them!
The opening question 'Are we really at a point of AI usage when a customer service directs you to use ChatGPT...' works because it's absurd enough to feel universal (everyone has had bad customer service) but specific enough to feel real. It invites the reader to take a position immediately, creating mental friction that demands resolution.
Story structure with escalation: (1) Setup the absurd situation (2) Add the pushback moment where the rep doubles down (3) Introduce the personal stake (the laptop specs) (4) End with a relatable ask (the PS about vents) (5) Deliver the update that shows community solved it. The post moves from problem to resolution, mirroring how readers want their own problems solved.
- Conversational asides in parentheses ('you know, the actual company that makes the product') that feel like thinking out loud
- Escalation through repetition ('he doubled down') to show frustration building
- The PS and UPDATE structure that invites community participation and shows the post was listened to
The PS asking for help with the ThinkPad vents is not a traditional CTA but a vulnerability play. It invites comments because readers can be the hero. The UPDATE shows the post worked, validating engagement and encouraging more comments on future posts.
End with a genuine ask or vulnerability rather than a sales pitch, and if possible, show that community engagement solved the problem in an update.
Had a conversation with a business where the owner told me, "we're forced to make decisions based on gut. It takes months for us to see updated financial statements and we still don't have an overall company view." This wasn't a startup. This was a multi-million dollar company…
The founder quote hook works because it's specific enough to be credible ('it takes months for us to see updated financial statements') but universal enough that multiple founder archetypes recognize themselves. The contrast reveal ('This wasn't a startup') adds authority by showing this isn't a small-business problem, it's an enterprise-scale failure.
Problem-Solution architecture: (1) Open with the founder quote (2) Reveal the scale/surprise (3) List the emotional and business costs in bullet form (4) Acknowledge the pain ('It sucks, a lot') (5) Introduce the fix (6) Explain what the fix is NOT (the lipstick-on-a-pig line) (7) Hint at what it IS without fully revealing. The structure builds tension by validating pain, then releasing it with the promise of a solution, but withholds the full solution to keep readers engaged.
- Bullet-point cost enumeration ('You say no to opportunities you should take') that makes abstract pain concrete
- The 'lipstick on a pig' metaphor that dismisses a common wrong solution, positioning the creator as someone who knows what doesn't work
- Truncation at the end ('It means building a proper structure that gives you actual support and visibility into what the heck is happe...') that forces readers to click or scroll, extending engagement time
The post cuts off mid-sentence, which is a cliffhanger tactic that drives clicks and comments asking for the full answer. This is a soft CTA that doesn't feel salesy.
Use bullet points to itemize the cost of inaction, then introduce the solution without fully explaining it, creating curiosity that drives engagement.
In FP&A, one of the easiest ways to look like a hero is to stick your nose in the SaaS cost. That’s because up to 66% of SaaS licenses aren't being used. That means A LOT of money down the drain each year. There's still time to fix this before budget planning starts. If you wa…
The opening 'In FP&A, one of the easiest ways to look like a hero is to stick your nose in the SaaS cost' works because it flatters the reader (you can be a hero) while positioning the creator as someone who knows the insider moves. The stat (66% of licenses unused) immediately validates why this move matters, removing any doubt about whether it's worth the reader's time.
Statistic-to-Action structure: (1) Hook with the hero positioning (2) Deliver the shocking stat (3) Translate the stat to business impact ('A LOT of money down the drain') (4) Create urgency with a time window ('before budget planning starts') (5) Offer a specific next step (the webinar) with a named co-host and date. The structure moves from 'this matters' to 'here's proof' to 'here's what to do about it now.'
- The 'look like a hero' framing that appeals to career advancement, not just company benefit
- Urgency through scarcity ('There's still time to fix this before budget planning starts')
- Named co-host and specific date that makes the offer feel concrete and credible
Direct webinar link with a clear date and co-host name. This is the only post in the top 5 with an explicit promotional CTA, but it works because the value prop (learn how to save money and look good) is established before the ask.
When promoting an event or offer, lead with the benefit to the reader's career or status, then back it with data, then make the ask feel specific and time-bound.
What drives their engagement
Comments spike when Kathy opens with a relatable founder problem or asks a question that invites debate. The top post (54 engagement) is a question that challenges industry practice. The second (35 engagement) is a founder quote that readers validate. Comments are driven by recognition ('that's me') or disagreement ('actually, here's another angle'), both of which require the reader to take a position.
Repost rate is very low (0.8%), suggesting this creator optimizes for depth of conversation over breadth of reach. The two reposts in the dataset came from posts with specific, actionable advice (the SaaS cost post and the COA post), implying that tactical how-to content is more shareable than story-driven content.
High comment-to-like ratio (31.8% conversation index) suggests readers are saving these posts to reference later or to continue the conversation, not just scrolling past. The long-form posts (70% of content at 180-350 words) are designed to be bookmarked as mini-guides, particularly the COA breakdown and the EAD automation post.
Content pillars
Financial Structure & System Design
40%Teaching founders why their chart of accounts, reporting infrastructure, and financial workflows are broken and how to rebuild them for visibility and speed.
Decision-Making Under Uncertainty
25%Exposing the cost of gut-based decisions and showing how proper financial data eliminates anxiety and opens opportunity.
Cost Optimization & Efficiency Wins
20%Tactical moves like SaaS license audits and automation that make finance teams look like heroes while freeing capacity for strategy.
Founder Conversations & Case Studies
15%Real stories from business owners and finance leaders that validate the problem and prove the solution works at scale.
Hook patterns
Founder Quote Hook
Direct quote from a business owner expressing a specific pain point, framed as a conversation opener.
“Had a conversation with a business where the owner told me, 'we're forced to make decisions based on gut. It takes months for us to see updated financial statements and we still don't have an overall company view.'”
→ Readers immediately recognize themselves in the quote and feel seen, triggering comment engagement as they validate the problem.
Provocative Question
Open with a question that challenges current industry practice or exposes absurdity in how things are done.
“Are we really at a point of AI usage when a customer service directs you to use ChatGPT vs giving you an answer from their company's system?”
→ Questions demand mental engagement and invite debate, driving the highest engagement rate (54 likes + comments) in the dataset.
Statistic Shock
Lead with a surprising number that quantifies the problem, then immediately offer a solution window.
“In FP&A, one of the easiest ways to look like a hero is to stick your nose in the SaaS cost. That's because up to 66% of SaaS licenses aren't being used.”
→ The stat creates urgency and positions the reader as someone who can fix it, making them feel capable rather than blamed.
Problem Statement as Conditional
Start with 'If [broken situation], you got a problem' to make the reader self-diagnose.
“If your numbers people have to disappear for days to create some Frankenstein spreadsheet that barely answers your question, you got a problem.”
→ The conditional structure lets readers apply it to their own situation without feeling lectured, lowering defensive barriers.
Story Opening with Surprise
Begin with a personal anecdote or third-party story that sets up an unexpected insight.
“I've been into EAD (Eliminate-Automate-Delegate) concept for as long as I can remember, but every now and then I hear stories that just blow my mind. Nils Brauckmann's was one of them.”
→ The setup creates curiosity and the promise of a surprising outcome, pulling readers into the narrative.
Contrast Reveal
State a normal expectation, then reveal it's not what happened or not what should happen.
“This wasn't a startup. This was a multi-million dollar company making expansion decisions, hiring choices, and some complex investment stuff. All without current and useful financial information.”
→ The reversal of expectation creates cognitive dissonance that demands resolution, keeping readers engaged through the explanation.
Top-performing hooks
“Are we really at a point of AI usage when a customer service directs you to use ChatGPT vs giving you an answer from their company's system?”
→ The post highlights a relatable frustration with AI in customer service, sparking conversation and inviting community input. The personal anecdote and specific product question make it engaging and sh
“Had a conversation with a business where the owner told me, "we're forced to make decisions based on gut. It takes months for us to see updated financial statements and we still don't have an overall company view."”
→ The post effectively highlights a common pain point for SMB owners (lack of timely financial data) and offers a clear, actionable solution. By emphasizing the negative consequences of poor financial m
“In FP&A, one of the easiest ways to look like a hero is to stick your nose in the SaaS cost.”
→ The post uses a surprising statistic to grab attention and highlights a common pain point in SaaS finance. It offers a solution (webinar) with specific benefits, creating a compelling reason to regist
“If your numbers people have to disappear for days to create some Frankenstein spreadsheet that barely answers your question, you got a problem.”
→ The post identifies a common pain point for businesses and offers actionable advice, positioning the author as a knowledgeable expert. The numbered list format makes the advice easy to digest and impl
“I've been into EAD (Eliminate-Automate-Delegate) concept for as long as I can remember, but every now and then I hear stories that just blow my mind. Nils Brauckmann's was one of them.”
→ The post uses a compelling case study to highlight the benefits of procurement automation. It quantifies the impact with specific examples, making the value proposition clear and credible, and include
“The red flags to watch for when you're building your finance function:”
→ The post provides actionable advice in a clear, numbered list format, addressing common pain points in building a finance function. The use of relatable red flags makes the content easily digestible a
“There’s still time to register for tomorrow!”
→ The post uses a direct and concise approach, creating urgency by reminding the audience about an upcoming event and encouraging immediate registration. The simplicity and clear call to action make it
“If your eyes are glazing over when looking at financial statements, here's a useful tool to keep them focused: common sizing”
→ The post offers a practical solution to a common problem faced by small business owners, making financial statements more understandable. The numbered list format and clear benefits make the advice ea
“Smart advice that Isabella Moise, an IT procurement partner from Simplyhealth, gave me on vendor selection that every growing business should follow:”
→ The post offers a simple, relatable analogy (shopping list) to highlight a common mistake in vendor selection. It provides actionable advice, building credibility and resonating with businesses experi
“Building a procurement team? Technical expertise matters, but there is another thing that you should be looking for - thoughtfulness.”
→ The post challenges a common belief (technical skills are paramount) and offers a counterintuitive solution (prioritize thoughtfulness). This contrarian approach, combined with actionable advice, make
What works
- Founder quote hooks drive 35+ engagement. The second-highest post opens with a direct quote from a business owner, making the problem feel real and urgent. Readers comment to validate ('this is exactly us') or add their own version of the problem.
- Statistic shock followed by solution window. The SaaS post (31 engagement) leads with '66% of SaaS licenses aren't being used' then immediately offers a fix, creating urgency without despair. The stat makes the problem quantifiable, not just anecdotal.
- Problem-solution format dominates (60% of posts, 22 avg engagement). This creator rarely posts pure thought leadership or celebration posts. Every post is structured to expose a broken assumption and hint at the fix, which keeps readers mentally engaged.
- Bullet-point cost enumeration. In the second post, the lines 'You say no to opportunities you should take. You say yes to stuff that you shouldn't.' make abstract pain concrete and scannable. Readers can quickly see themselves in the list.
- Cliffhanger endings that truncate mid-sentence. The second post cuts off with 'what the heck is happe...' which forces clicks and extends engagement time. This is a soft CTA that doesn't feel salesy.
- Story openings with a surprise reveal. The fifth post ('I've been into EAD for as long as I can remember, but every now and then I hear stories that just blow my mind') sets up curiosity, then delivers the payoff (4 people managing 2,000 employees' spend). The contrast between expectation and reality drives engagement.
Steal this for your own LinkedIn
- Start your next post with a direct quote from a customer or founder expressing a specific pain point. Don't paraphrase it, quote it verbatim. This makes the problem feel real and invites readers to validate it in the comments.
- When you have a statistic, pair it immediately with a time window for action ('before budget planning starts' or 'there's still time to fix this'). This converts awareness into urgency without sounding desperate.
- Use bullet points to itemize the cost of inaction, not the benefits of action. Instead of 'benefits of good financial data,' write 'You say no to opportunities you should take. You say yes to stuff that you shouldn't.' This makes pain concrete and scannable.
- End a post mid-thought or with a cliffhanger rather than a full conclusion. The second post cuts off with 'what the heck is happe...' which forces readers to click or scroll, extending engagement time and signaling that more value is coming.
- Open with a relatable frustration, then use the phrase 'The crazy part is that this is completely fixable' to shift from problem to solution. This two-move structure validates pain, then releases it with hope, which drives comments from readers who feel seen.
- Use casual, slightly exasperated language ('It sucks, a lot,' 'That's essentially putting lipstick on a pig') to sound like a peer who has seen this problem 100 times, not a consultant selling a solution. This builds trust and lowers defensive barriers.
Compare Kathy with…
Get the full Kathy Svetina playbook
Hook templates, content calendar, posting cadence, and the exact frameworks they use - delivered to your inbox.
Posting patterns
Inconsistent posting (0.8 posts per week, with 0 posts in the last 30 days) suggests Kathy prioritizes quality and depth over consistency, or is in a period of lower activity. This is a vulnerability: more frequent posting would likely increase total engagement even if per-post engagement stayed flat.
Posts perform best on Sunday at 1 UTC (which is roughly 8 PM ET Saturday or 5 PM PT Friday), suggesting an audience that engages with professional content on weekends, likely founders and finance leaders catching up on reading.
Long-form posts (180-350 words) average 26 engagement vs. 20 for medium and 17 for micro, indicating this audience wants depth and context. The sweet spot is long enough to tell a story and explain the why, but short enough to read in 2-3 minutes on mobile.
Engagement by day
Content mix
avg 22 engagements per post
avg 18 engagements per post
Kathy's 60% problem-solution, 20% numbered list, 10% micro format mix works because her audience (finance leaders and founders) are problem-aware but solution-skeptical. The problem-solution format validates their pain first (building trust) before offering a fix, which is more persuasive than leading with the solution. The numbered lists and micro posts provide tactical relief and variety, preventing the feed from feeling repetitive, but they underperform the long-form problem-solution posts, suggesting her audience prefers depth and story over quick tips.
