Story 1 — Proudest moment

Year three or four. A 500-person mid-market customer came in with a problem her product was not built to solve cleanly. Three months of engineering work to address. Her Head of Sales at the time wanted her to commit and build it later. Sarah got on the call with the customer's VP of HR and told them the truth: the product does X/Y/Z well, what they need is different, here are three competitors who solve it natively. She lost the deal. The team saw it. It changed how the company talks to customers — it became real, not just a slogan.

Story 2 — The decision that still bothers her

Three months ago. A promising SDR she had hired and trained personally was missing volume targets. Sarah avoided the hard conversation, let the Head of Sales handle performance management, and the SDR found out through review cycles that she was on a Performance Improvement Plan. She left feeling blindsided. Sarah hid behind process instead of being direct with someone she liked. She holds herself to a standard of directness she failed to meet that quarter and still struggles with.

Story 3 — Greatest frustration

Last month. An early engineer of five years brought her a customer feature request, framing it as urgent and deal-critical. Sarah asked whether he had pushed back on it. He had not — he just collected the requirement and brought it up. He defaulted to "Sarah will figure it out" instead of coming with a position. That is exactly how she stays the bottleneck. The standard he violated: think before you bring a problem. Come with a position, not just an input.

Story 4 — What she refused

Customer success manager. Solid retention numbers, but systematically telling customers what they wanted to hear — saying yes to features that did not exist, over-promising on timelines, claiming features were coming when they had not been decided. Sarah found out from a customer complaint, not from her. Sarah fired her. Other founders would have let it slide because the numbers looked good. She could not — tolerating it would teach the team that the standard is "hit the number," not "tell the truth."

Story 5 — Invested without guarantee

First two years. Building the product herself. Everyone told her to hire a CTO earlier; funding was there. She did not. She wrote almost all the code because she needed to understand the problem at the deepest level — to know what was actually hard versus what customers thought was hard. Read HR workflows. Sat with customers using competing products. Built things, threw them away, rebuilt them. No guarantee it would work. It is also why she still gets frustrated when people bring her half-baked thinking.

Story 6 — Anti-model

A peer founder. Raised bigger rounds, built a bigger company. Smart, but optimizes for looking like he has it figured out. Presents strategy in board meetings like it is carved in stone even when it changed three weeks ago. Tells the team one thing and investors another. Takes credit for wins, distances himself from problems. Hires executives who will not challenge him because he needs them to validate his vision. Talks about transparency and psychological safety constantly but performs it instead of living it. What she would never do: pretend to certainty she does not have, build a culture where people are afraid to disagree.

Story 7 — How she wants to be remembered

Legacy at Pillar HR. "She actually cared about solving the problem, not about being right. She'd change her mind if you showed her data. She told you the truth even when it cost her. She expected you to think, not just execute. And she didn't waste your time."

What she never wants said. "She was all over the place." "She burned people out because she couldn't delegate." "She was smart but you could never trust what she said because it changed every week." Worst: "She made you feel stupid for disagreeing with her." She also wants to be remembered as honest about what she did not know, not "she had all the answers."