<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Sophia Falck-Ytter on Medium]]></title>
        <description><![CDATA[Stories by Sophia Falck-Ytter on Medium]]></description>
        <link>https://medium.com/@s.falckytter?source=rss-fede7d683276------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*7ZnNrl4hYO3RNFereRvqzQ.png</url>
            <title>Stories by Sophia Falck-Ytter on Medium</title>
            <link>https://medium.com/@s.falckytter?source=rss-fede7d683276------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 00:20:54 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@s.falckytter/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[AI Made MVPs Cheaper to Build. It Also Made Them Harder to Launch.]]></title>
            <link>https://medium.com/@s.falckytter/ai-made-mvps-cheaper-to-build-it-also-made-them-harder-to-launch-71213fbf60b7?source=rss-fede7d683276------2</link>
            <guid isPermaLink="false">https://medium.com/p/71213fbf60b7</guid>
            <category><![CDATA[product-launch]]></category>
            <category><![CDATA[lean-startup]]></category>
            <category><![CDATA[mvp]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[startup-lessons]]></category>
            <dc:creator><![CDATA[Sophia Falck-Ytter]]></dc:creator>
            <pubDate>Mon, 21 Sep 2026 06:35:09 GMT</pubDate>
            <atom:updated>2026-09-21T06:35:09.891Z</atom:updated>
            <content:encoded><![CDATA[<p><em>I always thought the point of an MVP was to launch early, get real users, and learn. Then we started building an AI product, and I started questioning one part of that logic.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YqZFis0aDgofPQ-8FFy14w.png" /></figure><p>We could launch our product today.</p><p>We’re choosing not to.</p><p>We’re building a new part of Filently called Deep Clean. It looks at an existing Google Drive, analyzes the documents and folders, and proposes a cleaner structure.</p><p>The technology works. The workflow works. And the results have improved a lot over the last few weeks.</p><p>But when <a href="https://medium.com/u/8e0f7b912368">Valentin</a> and I test it, we still sometimes look at a proposed folder structure and think: <em>I wouldn’t be happy with this as a customer.</em></p><p>That’s where I’m stuck.</p><p>Because everything I’ve learned about building startups tells me we should launch.</p><h3>Launch early. Learn fast.</h3><p>That’s what I was taught, and it makes sense.</p><p>Don’t spend six months building something in isolation. Build the smallest version you need, put it in front of real customers, and let them show you where you’re wrong.</p><p>It’s one of the best ways to avoid one of the most expensive mistakes a startup can make: spending months building something nobody actually wants.</p><p>We experienced that ourselves with Filently. Before we launched, we thought we understood what customers would need. Then real users arrived and showed us where our assumptions were wrong. Some of the most useful things we’ve learned came from watching what people actually did with the product, not from what they told us beforehand.</p><p>So I still believe in launching early.</p><p>But building Deep Clean has made me question one part of the equation.</p><blockquote><strong>The product has to be good enough for the feedback loop to work.</strong></blockquote><h3>What happens if it isn’t?</h3><p>Imagine we launch Deep Clean too early.</p><p>A customer connects their Drive, lets Filently analyze thousands of files, and gets a proposed folder structure. The structure isn’t terrible. But it’s also not good enough. There are too many folders, some documents are grouped in ways that don’t make sense, and the result doesn’t quite match what the customer expected.</p><p>What happens next?</p><p>They might tell us. They might explain which folders they would change or what they expected instead. That would actually be useful. We could learn from it and improve the system.</p><p>But they might also just close the tab.</p><p>They might decide that Filently doesn’t work for them and never come back. They might cancel without telling us why. And then we haven’t really learned what we wanted to learn.</p><p>We don’t know whether the underlying idea was wrong, whether the result was simply not good enough yet, or what would have made the experience valuable to them.</p><p>That’s the part I hadn’t really thought about when I first learned the MVP playbook.</p><blockquote><strong>The feedback loop itself has a minimum quality threshold.</strong></blockquote><p>Below that threshold, the loop looks something like this:<br><strong>Bad core experience → user leaves → little or no feedback → little learning</strong></p><p>Above it, it looks very different:<br><strong>Good core experience → user engages → encounters limitations → gives meaningful feedback → learning</strong></p><p>The product doesn’t have to be finished for that second loop to happen. It just has to deliver enough of the promised value for the user to stay engaged with it.</p><h3>I thought being a startup would buy us some patience</h3><p>There’s another thing I’ve learned since launching Filently.</p><p>I expected people to give us a little more slack because we’re a startup.</p><p>They don’t, at least not in the way I imagined.</p><p>Most users don’t know how big our team is. They don’t know how long we’ve been working on a feature. They don’t know which parts of the product are still experimental. They don’t see the conversations Valentin and I have about what we’re building next.</p><p>They just see the product in front of them.</p><p>And honestly, that makes sense. If I sign up for a new software product, I don’t automatically lower my expectations because the company is young. I care about whether the thing I came for works.</p><p>I can forgive missing features. I can forgive a few rough edges. But if the main thing I wanted doesn’t work well enough, I’m probably not going to stick around long enough to have a thoughtful conversation about what could be better.</p><h3>There is no founder sitting across the table</h3><p>This matters particularly because Filently is product-led.</p><p>Someone can discover us, sign up, connect their Google Drive and start using the product without ever speaking to us. That’s a huge advantage. We don’t need to convince every customer through a sales process before they can experience the product.</p><p>But there is a downside too.</p><p>In a direct sales process, the human relationship can buy you some patience. A founder can sit across from an early customer and explain what you’re building, tell them what’s still rough, ask them what they think and make them feel like they’re part of the process.</p><p>We’re trying to bring more of that human element into Filently ourselves. But ultimately, the product still has to stand on its own.</p><p>For many of our users, the product is the first conversation they have with us.</p><p>And if that conversation goes badly, there may not be a second one.</p><h3>AI changes the equation again</h3><p>At the same time, the environment we’re building in has changed.</p><p>AI has made it dramatically faster to build software. Two founders can prototype, develop, test and iterate at a speed that would have required a much larger team a few years ago.</p><p>That’s one of the reasons I’m excited to be building a company right now.</p><p>But the same technology is changing what users <strong>expect</strong> from software.</p><p>People are getting used to tools that can write for them, analyze documents, summarize information, search through large amounts of data and automate tasks that previously required manual work.</p><p>They don’t see how quickly we built something. They see what it does.</p><p>And if you’re building in an existing market, they already have an idea of what a good result should look like.</p><p>That’s important for Filently.</p><p>We’re not inventing the idea of organizing documents. People have been creating folder structures and naming files for decades. We’re trying to automate a job they already understand.</p><p>That means our customers come with expectations.</p><p>They know what a useful folder structure looks like. They know what it feels like when a file is in the wrong place. They know how much time a messy Drive costs them.</p><p>We inherit those expectations whether we want to or not.</p><h3>The core experience matters more than the feature list</h3><p>This is where my thinking about MVPs has changed.</p><p>I don’t think an MVP needs more features today. It never did.</p><p>The whole point was always to build the smallest version that lets you test your most important assumption.</p><p>But I think the thing you build has to clear a certain quality threshold before that test becomes meaningful.</p><p>A product can be missing half of its roadmap and still be a great MVP. If the one thing it promises works well enough, customers can use it, find value in it and tell you what they want next.</p><p>The opposite is also true. You can have a perfectly functioning product with a reasonable number of features and still not have an MVP that works as a learning vehicle if the core experience isn’t good enough to keep people engaged.</p><p>That’s the distinction I’m starting to care about.</p><p>Not feature completeness.</p><p><strong>Core experience quality.</strong></p><h3>For AI products, trust makes the threshold even higher</h3><p>With Deep Clean, there’s another layer to this.</p><p>We’re asking Filently to make decisions about someone’s documents. Not just to suggest a sentence or summarize a piece of text, but to look at an existing Drive and decide how the files should be organized.</p><p>Those files can be invoices, contracts, financial information, customer documents, employee records and other sensitive business information.</p><p>So we’re asking for a certain amount of trust.</p><p>That doesn’t mean the product needs to be perfect. There will be mistakes and edge cases. That’s part of building an AI product.</p><p>But there’s a difference between an occasional bad result and a system where you’re never quite sure whether the result will make sense.</p><p>For us, the question is therefore not simply whether Deep Clean can produce a folder structure.</p><p>It can.</p><p>The question is whether the <strong>average result is good enough</strong> that we’d actually trust it with our own files.</p><p>And that’s a much more useful question when deciding whether we’re ready to launch.</p><h3>So we’re waiting</h3><p>This is the slightly uncomfortable part.</p><p>We could launch Deep Clean now and learn from customers.</p><p>Part of me really wants to do exactly that. I know how valuable real usage is. I know there are things we won’t discover until other people use the product in ways we didn’t anticipate.</p><p>But when Valentin and I test it and still sometimes think <em>this isn’t quite good enough yet</em>, I don’t think we should simply call it an MVP and move on.</p><p>Not because we need perfection.</p><p>We don’t.</p><p>There will always be edge cases. There will always be things customers do that we didn’t anticipate. And there will always be another improvement we could make.</p><p>But we need to know that the core experience has reached a level where the feedback we get from customers will actually help us improve it.</p><p>So Valentin is still working on the quality of the results.</p><p>Not more features.</p><p>Not a bigger scope.</p><p>Just better results.</p><p>And it’s getting noticeably better.</p><p>We’re trying to find that point where a customer can use Deep Clean, get enough value from it to keep using it, and then tell us what they would change.</p><p>That’s the point at which feedback becomes useful.</p><h3>What “viable” means to me now</h3><p>I still believe in the old MVP principle.</p><p>Build less. Launch early. Talk to customers. Don’t spend a year building something in isolation.</p><p>But I’m starting to think we sometimes focus too much on the <em>minimum</em> and not enough on the <em>viable</em>.</p><p>The goal isn’t simply to put something in front of users as quickly as possible.</p><blockquote>The goal is to put something in front of them that is good enough for reality to teach you something useful.</blockquote><p>That’s probably where I’m landing for now.</p><p>We don’t need Deep Clean to be perfect before we launch it.</p><p>We need it to be good enough that when a customer tells us what’s missing, they’re talking about the product we actually built, rather than telling us that the product simply didn’t work.</p><p>And I think that’s a different threshold.</p><p>One we’re still figuring out.</p><p><em>Sophia Falck-Ytter is Co-Founder of Filently, an AI filing layer for Google Drive that automatically identifies, renames, and organizes documents. She’s building the company with her co-founder Valentin Uhrmeister and figuring out, in real time, what it means to build an AI product users can trust. Follow the build: </em><a href="https://filently.com/"><em>filently.com</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=71213fbf60b7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Keep Your Job, No Matter How Bad It Is.]]></title>
            <link>https://blog.startupstash.com/keep-your-job-no-matter-how-bad-it-is-c6d5dbe6a175?source=rss-fede7d683276------2</link>
            <guid isPermaLink="false">https://medium.com/p/c6d5dbe6a175</guid>
            <category><![CDATA[career-change]]></category>
            <category><![CDATA[startup-lessons]]></category>
            <category><![CDATA[personal-development]]></category>
            <category><![CDATA[entrepreneur]]></category>
            <category><![CDATA[entrepreneurship]]></category>
            <dc:creator><![CDATA[Sophia Falck-Ytter]]></dc:creator>
            <pubDate>Fri, 21 Aug 2026 21:21:01 GMT</pubDate>
            <atom:updated>2026-08-21T21:21:01.195Z</atom:updated>
            <content:encoded><![CDATA[<p><em>That was the headline someone sent me last week. I’d just given up a six-figure CEO job to live out of a suitcase. Here’s why I think it’s one of the most expensive pieces of advice you can follow.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5K3ITXbPwsyN-fTN-2uMbw.png" /></figure><p>It came from a German magazine (Der SPIEGEL), sent to me by a friend. And my first thought was pretty simple. What a terrible thing to tell people.</p><p>The message underneath it was this. Prioritize security. Stop dreaming. Don’t chase what you actually want, because it’s too risky. I get why it lands right now. The job market is rough, and fear is easy to sell. But as life advice, I think it’s one of the most damaging things you can hand someone.</p><p>Here’s why I take it personally.</p><h3>My mother wanted me to become a civil servant</h3><p>Where I come from, a government job is the definition of safe. A pension. A title. Nothing to worry about, ever. That’s what my mother always hoped I’d pick.</p><p>So when I went into the startup world after university instead, she was worried. She had a point, on paper.</p><p>Luckily it worked out. The company grew. I ended up running it as CEO. Secure job, six-figure salary, plenty of freedom. By every measure she cared about, I had made it.</p><p>And then I told her I wanted to give it all up.</p><p>Not for another job. Not for a bigger title. For a question mark. I wanted to leave, go abroad, and figure out what I actually wanted from my life. No plan. Just time to think.</p><p>She was shocked all over again.</p><p>I understood the reaction. I was walking away from the exact thing she’d spent her whole life teaching me to want. But I couldn’t shake one feeling. “Everything right on paper” and “right for me” had stopped being the same sentence.</p><p>So I quit. I gave up my apartment. I packed a suitcase.</p><h3>The part nobody warns you about</h3><p>Here’s where the story gets uncomfortable for the “play it safe” crowd.</p><p>I’m now living out of that suitcase and off my savings. My co-founder <a href="https://medium.com/u/8e0f7b912368">Valentin Uhrmeister</a> and I started a company called <a href="https://filently.com/?utm_source=medium&amp;utm_medium=blog&amp;utm_campaign=keep-your-job">Filently</a>. We’ve hit our first milestones. We are nowhere near safe.</p><p><strong>And I have never been happier.</strong></p><p>That’s not just a nice feeling I’m projecting onto my choices after the fact. A Cornell study once looked at what people regret most across their entire lives. The result stuck with me. People are not haunted by the risks they took. They’re haunted by the dreams they never chased.</p><p>And the researchers’ own favorite example of that regret? Settling for a safe career instead of following a passion.</p><p>We keep postponing the thing we actually want. Always waiting for a better moment. Until the waiting itself becomes the regret.</p><p>Read that back next to the headline. “Keep your job, no matter how bad it is” is basically a recipe for manufacturing the single regret people carry longest.</p><p>There’s a quieter finding too. People who work on their own thing report higher job satisfaction than employees. It holds no matter how much they earn or how many hours they put in. The driver isn’t the money. It’s the autonomy. The feeling that your days are yours.</p><p>Which is almost exactly my experience. I earn less than I did as a CEO. I own my time completely. It turns out the second one was doing most of the heavy lifting all along.</p><h3>Why we’re wired to stay</h3><p>I don’t think this is just my story. I think it’s cultural.</p><p>In Germany, security sits at the very top of the pile. Risk is something you avoid. Failure is a stain, not a step. You can feel it in small talk, in family dinners, in the way people say “but is that <em>secure</em>?” before they ask if it makes you happy.</p><p>In places like the US, more people start things. And when they fail, it reads as part of the path, not a verdict on who they are. Roughly half of people in Germany name fear of failure as a reason not to start a business at all. That fear isn’t a personal flaw. It’s the water we swim in.</p><p>I don’t believe we’re less brave. I think we’re just told, constantly, that we shouldn’t be. Headlines like that one are that message, dressed up as protection.</p><h3>This isn’t “quit your job”</h3><p>Let me be clear, because it’s easy to misread.</p><p>Security is real and it matters. Not everyone can walk away from a steady income, and plenty of people shouldn’t. Kids, rent, health, a hundred honest reasons. I’m not romanticizing recklessness, and I’m not pretending my path is the smart bet on a spreadsheet.</p><p>What I’m pushing back on is the blanket version. The idea that dreaming itself is the danger. That the grown-up move is to want less.</p><p>Because here’s the trade the headline forgets to mention. When you play it safe, you don’t actually delete the risk. You just swap it for a quieter one. The risk of sitting somewhere in thirty years, asking yourself, what if I’d just tried?</p><p>That’s the risk the research says we regret most. And it’s the one nobody puts in a headline.</p><h3>Back to my mother</h3><p>She still worries. That part didn’t magically resolve.</p><p>But the last time we spoke, something had shifted. She wasn’t asking whether it was secure. She was asking what I was building, and whether I was happy. For a woman who wanted a civil servant for a daughter, that’s a small revolution.</p><p>I don’t think the goal was ever to prove her wrong. She spent her life being ready for everything, and she gave me that instinct too. I just aimed it somewhere she didn’t expect.</p><p>Being prepared was never only about picking the safe thing. Sometimes it’s about being ready to bet on yourself when the paper says don’t.</p><p>So I’ll leave you with the question I keep asking myself.</p><p>When was the last time you took a risk that looked unreasonable on paper?</p><p><em>Sophia Falck-Ytter is Co-Founder of </em><a href="https://filently.com/?utm_source=medium&amp;utm_medium=blog&amp;utm_campaign=keep-your-job"><em>Filently</em></a><em>, an AI filing layer for Google Drive that automatically identifies, renames, and organizes your documents. She gave up a comfortable CEO job to build it. Follow the build: </em><a href="https://filently.com/"><em>filently.com</em></a></p><p><em>Sources: Davidai &amp; Gilovich (2018), “The Ideal Road Not Taken,” Cornell University / Emotion. Self-employment and job satisfaction research based on the European Values Survey. Fear-of-failure and founding-rate figures: Global Entrepreneurship Monitor (GEM) 2024.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c6d5dbe6a175" width="1" height="1" alt=""><hr><p><a href="https://blog.startupstash.com/keep-your-job-no-matter-how-bad-it-is-c6d5dbe6a175">Keep Your Job, No Matter How Bad It Is.</a> was originally published in <a href="https://blog.startupstash.com/">Startup Stash</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[My Mother Had Everything Under Control. Except One Cardboard Box.]]></title>
            <link>https://medium.com/@s.falckytter/my-mother-had-everything-under-control-except-one-cardboard-box-193786fb13e6?source=rss-fede7d683276------2</link>
            <guid isPermaLink="false">https://medium.com/p/193786fb13e6</guid>
            <category><![CDATA[startup-lessons]]></category>
            <category><![CDATA[personal-development]]></category>
            <category><![CDATA[google]]></category>
            <category><![CDATA[productivity-hacks]]></category>
            <category><![CDATA[entrepreneurship]]></category>
            <dc:creator><![CDATA[Sophia Falck-Ytter]]></dc:creator>
            <pubDate>Thu, 04 Jun 2026 11:31:04 GMT</pubDate>
            <atom:updated>2026-06-04T11:31:04.062Z</atom:updated>
            <content:encoded><![CDATA[<p><em>She raised us, built a career, drove us to every lesson. She just never tamed her own paperwork. Here’s how she finally did, and what it taught me about scanning versus filing.</em></p><p>My mother taught me to be ready for anything. Be independent. Learn the skills you’ll actually need in life. And she didn’t just say it. She lived it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qHKM-_ZtfRD-cnD7dyZx2g.png" /></figure><p>She went back to work early, not long after my sister and I were born. This was a time when her colleagues raised their eyebrows and said things like, “But you’re married, you don’t need to work.” She did it anyway. She drove us to every practice and every music lesson. She sat with us through homework she’d already done thirty years earlier. She held the whole thing together.</p><p>She always had everything under control.</p><p>Almost everything.</p><p>The older I got, the more I noticed the little cracks. My mother is a creative, sunny person, the kind who remembers everyone’s birthday and never the deadline. And she has exactly one nemesis she’s never beaten: keeping her paperwork in order.</p><p>For years her filing system was a cardboard box. Mail came in, bills got paid, and then the paper went into the box. Out of sight, out of mind. It worked beautifully, right up until the one day a year when it really, really didn’t.</p><p>Tax season.</p><p>And here’s the thing that always surprised me. The hard part was never the tax return itself. It was the digging. Tipping the box out onto the kitchen table. Building little piles. Hunting for that one receipt from March that she was sure she’d kept. A solid hour of prep before the actual work could even start. By the time she was ready to begin, she was already done.</p><p>That box isn’t really about my mother, though. It’s about all of us. Most people have a box. A few are still cardboard. But most of them have quietly moved onto a phone, into a downloads folder, into a Google Drive that’s slowly become the exact same thing with a search bar bolted on. The shape changed. The dread didn’t.</p><h3>First, get the paper off the table</h3><p>When I told my mum about Filently, she lit up. A system that replaces the old box and gets everything ready on its own? Yes, obviously, where do I sign.</p><p>But here’s the part nobody tells you: before any software can help, the paper has to get into the cloud in the first place. And this is where most of us pile on steps we don’t need. For years my own routine was: open a scanning app, scan the thing, airdrop it to my laptop, rename it, drag it into Google Drive. Every time. For every document. I was 30 when I realized I’d been making this so much harder than it had to be.</p><p>The Google Drive app already has a scanner built in. You don’t need CamScanner, Adobe Scan, or Microsoft Lens. If Drive is on your phone, you’ve already got everything you need.</p><p>Here’s the whole thing in four steps:</p><p><strong>1. Open Google Drive and tap the “+”.</strong> Bottom right corner, the blue button. Choose “Scan document.”</p><p><strong>2. Hold your camera over the document.</strong> Drive finds the edges and snaps it on its own, no shutter button. Got more pages? Just keep going.</p><p><strong>3. Name the file.</strong> Drive will suggest something like Scanned 4 June 2026 at 16:14:07.pdf. Which tells absolutely nobody anything.</p><p><strong>4. Pick a folder and save.</strong> Tap the location field, choose where it goes, hit Upload. It lands in your Drive as a PDF.</p><p>That’s it. No extra app, no airdrop, no laptop sitting in the middle of it all.</p><h3>The half that scanning leaves behind</h3><p>But here’s the trap, and it’s the exact same one my mother’s cardboard box set every April. Scanning solves how the paper gets in. It does nothing about what happens next.</p><p>That default filename, Scanned 4 June 2026 at 16:14:07.pdf, is just the digital version of tossing the paper into the box. Rename every scan by hand and you&#39;ve added the old chore right back in. Skip it, and your Drive quietly fills up with files you&#39;ll never find again in six months. Either way you haven&#39;t escaped the box. You&#39;ve just made it technically searchable and practically useless.</p><p>This is the whole reason we built Filently.</p><p>You drop the scan into your Filently Inbox folder in Google Drive, and Filently takes it from there. It reads the document, figures out what it is (invoice, contract, receipt, ID, whatever it happens to be), applies your naming convention, and files it in the right folder. You hand it over exactly as it came off the camera. It comes out the other side named properly and in the right place.</p><p>So the real workflow is short:</p><ol><li>Open Google Drive, tap “+”, scan the document.</li><li>Save it to your Filently Inbox folder.</li><li>Filently names and files it for you.</li></ol><p>Scan with Drive. File with Filently. Setup takes about 2 minutes, and your files never leave your own Google Drive. There’s no new system to migrate into and nothing to untangle later if you change your mind.</p><h3>Why such a small thing matters</h3><p>One scan feels like nothing. But if you run any kind of business on paper (signed contracts, receipts, invoices, inspection reports), it’s happening dozens of times a month. And every one of those is a file that needs a name and a home. Ten scans a week, ninety seconds each, and you’re an hour a month into something that should take seconds.</p><p>Honestly though, the minutes aren’t even the worst of it. It’s the tiny decision you make every single time something new shows up: where does this go? Take that decision away and the whole thing gets quiet. Paper goes in, the right thing comes out, and you stop thinking about it.</p><h3>Back to the box</h3><p>These days my mum scans her documents straight from her phone and lets Filently rename and file them. No more kitchen-table panic. The box is gone.</p><p>The point was never that tax returns are fun. The point is that the worst part of tax season was never the return. It was the box. And the box, it turns out, was always optional.</p><p>My mother spent decades being ready for everything except this one little corner of her life. She finally sorted it, not by turning into a different person, but by letting a system handle the part she’d always hated. And I think that might be the most honest version of “be prepared” there is. You don’t have to win every battle yourself. You just have to stop fighting the ones a tool can fight for you.</p><p>Delete the scanning app. Scan with Drive. Let Filently take it from there.</p><p>I was 30 when I figured out the scanning part. My mum was quite a bit older when she made peace with the filing part. You really don’t have to wait that long for either.</p><p><em>Sophia Falck-Ytter is Co-Founder of </em><a href="https://filently.com/?utm_source=medium&amp;utm_medium=article&amp;utm_campaign=tax-season-story&amp;utm_content=bio-link"><em>Filently</em></a><em>, an AI filing layer for Google Drive that automatically identifies, renames, and organizes your documents. She built it partly so her mother would never have to empty that cardboard box onto the kitchen table again. Follow the build: </em><a href="https://filently.com/"><em>filently.com</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=193786fb13e6" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What My First Muay Thai Fight Taught Me About Building a Startup]]></title>
            <link>https://blog.startupstash.com/what-my-first-muay-thai-fight-taught-me-about-building-a-startup-d0ebed153214?source=rss-fede7d683276------2</link>
            <guid isPermaLink="false">https://medium.com/p/d0ebed153214</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[startup-lessons]]></category>
            <category><![CDATA[sports]]></category>
            <category><![CDATA[personal-growth]]></category>
            <category><![CDATA[entrepreneurship]]></category>
            <dc:creator><![CDATA[Sophia Falck-Ytter]]></dc:creator>
            <pubDate>Tue, 26 May 2026 05:59:33 GMT</pubDate>
            <atom:updated>2026-05-28T08:46:33.151Z</atom:updated>
            <content:encoded><![CDATA[<p><em>I lost. Here’s why it was worth it.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2V8RZ1JXJDpp7hww3CJvqA.png" /></figure><p>I didn’t know who I was fighting until I showed up.</p><p>In Muay Thai, especially in Thailand, you often know who the possible opponents are, but not exactly who you’ll face until the day. Four female fighters were on the poster. I didn’t know which one would be my opponent.</p><p>My Kru (trainer) had told me not to think about it. “Prepare well, then it doesn’t matter who stands across from you.” So I trained without a face in mind. 5 kilometers running before training, then 90 minutes of Muay Thai, 30 minutes of conditioning and strength work. Then I opened my laptop and worked. Then another run in the evening. Then I did it again the next day.</p><p>The fight was at Koh Samui International Stadium. A professional venue, with a real crowd and real promotion. Posters with my face on them, all over the island. I’d drive past them on the way to training and it felt completely surreal. But it also made it real in a way that nothing else had. There was no version of this where I could quietly back out. I was already on the wall. The date was set.</p><p>When fight day came, I found out: my opponent was Thai. Over ten years of experience. Likely heavier than me.</p><p>Round one went well. I landed good kicks, kept my range, didn’t let her get close. I was sharp, controlled, calm — surprisingly calm, actually. More than I expected. For a moment, I thought I could win this.</p><p>Round two, she rolled over me. A body shot landed clean. I went down.</p><p>I got back up. Still dizzy, but thinking: I need to find something, because she’s stronger in the pocket than I am. So I threw a switch head kick. Landed it clean.</p><p>She just ate it. Poker-faced. Didn’t even blink. Classic Thai style.</p><p>One more push from her and I was down again. The referee stopped it. TKO.</p><p>What happened next is one of the things I love about Muay Thai: both her trainers and mine came into the ring to check on me. No hostility, no drama. Just people making sure everyone was okay. Sport as it should be.</p><p>I lost my first fight.</p><p>And I learned more in those two rounds than in months of comfortable training.</p><p>A bit of context, because it matters.</p><p>I discovered Muay Thai in my late twenties on a holiday in Thailand. Fell for it, kept training when I got back to Switzerland. When I moved to Thailand in July 2025 to build <a href="https://filently.com/?utm_source=medium&amp;utm_medium=article&amp;utm_campaign=muay-thai-startup&amp;utm_content=bio-link">Filently</a> remotely, I kept going. By the time I turned 31, I wanted to know where I actually stood. Not in the gym, where everyone knows you and pulls their punches a little. In a real fight.</p><p>Some people will read this and think: how do you have time for that while building a startup? Aren’t you supposed to be locked in, 24/7, no distractions?</p><p>Maybe that works for some founders. It doesn’t work for me.</p><p>I need an outlet to come back to ideas with fresh eyes, to maintain energy over months and years, and to not burn out somewhere quiet where no one notices until it’s too late. Sport has always been that for me. Muay Thai especially, because it demands full presence. You cannot be in the gym and simultaneously worry about your conversion rate. For 90 minutes, the problem is clear and physical and right in front of you.</p><p>That’s not a distraction from the work. That’s what makes the work sustainable.</p><p>But the more I trained, the more I noticed something else. It wasn’t just that Muay Thai gave me energy for the startup. The two were teaching me the same things. Different context, same lessons. What works in the gym works in building a company. And what fails in one tends to fail in the other too.</p><p>Here’s what I mean.</p><h3>Lesson 1: You don’t get to choose your opponent</h3><p>The promoter chooses your opponent. Not you, not your coaches. The first time I saw mine was on the fight posters hanging across the island. With four girls fighting that night, I had no idea who I’d be facing. So I focused on what I could control: clean Muay Thai, no fancy techniques, and the weapons I knew worked. Switch kicks to close the bag. Keep it simple, keep it sharp.</p><p>In business, it’s the same. You don’t get to choose your competition. When we launched Filently, the field was real: established enterprise DMS systems with budgets that dwarfed ours, self-built automation setups like Zapier, and small niche tools solving parts of what we do.</p><p>Established players have resources and professional presence that a startup can’t match. But they also carry weight — complex structures, legacy decisions, slow processes. That’s what makes them inflexible. A startup doesn’t win by out-resourcing them. It wins by moving faster, staying focused, and finding the space they’re too heavy to reach.</p><p>For Filently, that’s Google Drive. Not all cloud storage. Not every file management problem. Just this one: getting Google Drive users organized, without migration, without complexity, without switching tools. That’s our switch kick. It’s strong. We’re building on it before we move to the next thing.</p><p>My boxing still needs work. I can’t perfect both at the same time. Neither can a startup.</p><h3>Lesson 2: The crisis before the calm</h3><p>Five days before the fight, I fell apart a little.</p><p>Not dramatically. But the questions got loud. Am I ready? Can I actually do this? What if I get hurt? What if I embarrass myself? I had one day where I couldn’t shake it, where the nerves just sat on my chest and I couldn’t train around them.</p><p>I let it happen. I cried. I didn’t push through it or try to logic my way out. I just let myself feel it.</p><p>And then it passed. The next day I was back on the mat. The days after that, I was stronger going into sessions than I’d been in weeks. Even at fight day, I was calm.</p><p>I think that crisis day was a key part of the preparation. Not a detour from it.</p><p>Starting a company has the same kind of days. The moments where you wonder if you’re actually cut out for this, if the idea holds, if you’ve made a terrible mistake. Those days are uncomfortable. But I’ve noticed they tend to come right before something clicks. The anxiety is often your mind stress-testing the commitment.</p><p>The mistake is trying to skip it.</p><h3>Lesson 3: Hard work is the only thing that creates calm</h3><p>The crisis passed. But calm doesn’t come from surviving a hard day. It comes from the work you put in every day before it.</p><p>When I stepped into the ring, I wasn’t nervous. I was focused. I had put in the work, I knew what I could do, and there was nothing left to second-guess. The outcome was no longer in my hands in the way it had been during training. All that work had already happened. Now I just had to show up and trust it.</p><p>I’ve felt this before. When we launched Filently publicly, after months of building and weeks of beta testing, there was a moment where <a href="https://medium.com/u/8e0f7b912368">Valentin Uhrmeister</a> and I just had to press publish. The work before that moment either held or it didn’t. But we knew it was an important step to reach the next growth stage.</p><p>You can’t manufacture calm. You can only earn it.</p><h3>Lesson 4: Discipline is doing it when there’s no obvious reason to</h3><p>Three hours of training every day sounds like a lot, because it is. There were days I didn’t want to run. Days I was tired and had a backlog of things to do. And the idea of training even though my body begged for rest felt unnecessary.</p><p>But consistency in Muay Thai isn’t optional. It’s the method. The same combination, hundreds of times, until your body stops thinking and just moves. You don’t improve by training when you feel like it. You improve by showing up when you don’t.</p><p>Building something new works the same way. The days I feel inspired are easy. The days I send another outreach message for the fifteenth time, or rewrite a landing page section I’ve already rewritten twice, or respond to a customer issue at 9pm, those are the days that actually count.</p><p>There’s no secret frequency. Just: do the work. Do it again. Don’t stop.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mj0UZge95SXa14D6mR0f3Q.jpeg" /></figure><h3>Lesson 5: Jai Su = fight with your heart, not just your body</h3><p>There’s a concept in Thai boxing called Jai Su. It roughly translates to “fighting spirit” or “big heart.” In Thailand, it’s one of the most respected qualities a fighter can have. It doesn’t mean you win. It means you don’t stop.</p><p>When I took that body shot in round two and went down, there was a moment where the smart option was probably to stay down. She had more experience, more weight, more rounds in her legs than I had in my whole life.</p><p>I got up.</p><p>I didn’t give up. Even hurt, I tried to push back. Maybe there was still a chance.</p><p>Some of the best moments in building Filently have been about never giving up and showing big heart. When our early conversion numbers were lower than expected. When a feature didn’t work the way we thought it would. When a customer churned. You don’t pivot away from those moments. You get back up and figure out what they’re telling you.</p><p>Heart is what keeps you in the ring long enough to get better. To learn.</p><h3>Lesson 6: A loss tells you exactly what to work on</h3><p>This is the part I actually appreciate most.</p><p>I now know I need to get better against heavy-armed pressure fighters. I didn’t know that before the fight. I couldn’t have known it from sparring in the gym, where the variables are controlled. I needed a real opponent under real conditions to show me the gap.</p><p>Before we launched Filently publicly, we thought we understood our users. We had built personas and talked to beta testers. Then we launched, real customers arrived, and we found out what we actually didn’t know yet.</p><p>We get new trial users every day. But we lose too many of them on the journey to becoming paid customers. The data is telling us we’re not yet meeting expectations well enough at key moments in the experience. We now know exactly what to fix. Because we saw it happen, we restructured our roadmap around it. A loss in the real world is more actionable than any assumption made before it.</p><p>You can’t identify every gap in advance. Some things only reveal themselves under pressure. And sometimes it has to hurt a little to improve faster.</p><p>The goal isn’t to avoid the loss. It’s to use it.</p><h3>Lesson 7: Get in the ring before you’re ready</h3><p>Thai children start fighting young. Not because their trainers are reckless, but because the ring teaches things that training never can. The discomfort, the stakes, the irreversibility of a real moment — those are conditions you can only learn inside.</p><p>I waited until I felt “ready” to have my first fight. Looking back, there’s no amount of training that would have made me feel completely ready. I would have kept finding reasons to wait.</p><p>The same thing is true with launching. With publishing. With sending the email. With making the decision. There’s always one more thing you could refine.</p><p>At some point, the only way to find out what you’re actually made of is to show up and find out.</p><p>If you win, you celebrate. If you lose, you learn. Either way, you find out something you couldn’t have known from the outside.</p><p>I lost my first fight. I’m going to fight again.</p><p>Not because I know for sure next time I’ll win. Because I know I’ll learn something I couldn’t learn any other way.</p><p>That’s true of fights. It’s true of startups. It might be true of most things worth doing.</p><p><em>Sophia Falck-Ytter is Co-Founder of </em><a href="https://filently.com/?utm_source=medium&amp;utm_medium=article&amp;utm_campaign=muay-thai-startup&amp;utm_content=bio-link"><em>Filently</em></a><em>, an AI filing layer for Google Drive that automatically identifies, renames, and organizes your documents. She’s fighting digital bureaucracy when not fighting in the ring. Follow the build: </em><a href="https://filently.com/"><em>filently.com</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d0ebed153214" width="1" height="1" alt=""><hr><p><a href="https://blog.startupstash.com/what-my-first-muay-thai-fight-taught-me-about-building-a-startup-d0ebed153214">What My First Muay Thai Fight Taught Me About Building a Startup</a> was originally published in <a href="https://blog.startupstash.com/">Startup Stash</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How I Stopped Being Available 24/7 — And Started Reaching Users Better]]></title>
            <link>https://medium.com/@s.falckytter/how-i-stopped-being-available-24-7-and-started-reaching-users-better-fbd467c4a7b4?source=rss-fede7d683276------2</link>
            <guid isPermaLink="false">https://medium.com/p/fbd467c4a7b4</guid>
            <category><![CDATA[product-lifecycle]]></category>
            <category><![CDATA[saas]]></category>
            <category><![CDATA[productivity-tools]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[startup-lessons]]></category>
            <dc:creator><![CDATA[Sophia Falck-Ytter]]></dc:creator>
            <pubDate>Thu, 30 Apr 2026 07:37:31 GMT</pubDate>
            <atom:updated>2026-04-30T07:37:31.369Z</atom:updated>
            <content:encoded><![CDATA[<p><em>From manual founder DMs to a full automated lifecycle. What I learned building Filently’s user communication from scratch.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cUMG6f-xJxHXfuSLeh_nNg.png" /></figure><p>In <a href="https://medium.com/@s.falckytter/what-one-month-after-public-launch-actually-taught-us-4c49f48ea422">my last post</a>, I wrote about what our first month after public launch actually taught us: the AI anxiety we didn’t see coming, and why intent-based onboarding changed how we think about users. This one is about what we did about it.</p><p>When we launched Filently in March 2026, I did what most early-stage founders do: I handled everything manually.</p><p>Every new trial user got a personal message from me. I watched our dashboard, noticed when someone signed up, and wrote to them directly. It felt right. It felt personal. It felt like the kind of founder-led hustle you’re supposed to do in the early days.</p><p>And for a while, it worked. Sort of.</p><h3>The Problem With Being Human</h3><p>Here’s the thing about manual outreach: it only works if you’re there.</p><p>I’m not always there. I eat. I sleep. I live in a timezone. And by the time I saw a new registration and reached out, hours had often passed. Sometimes a full day.</p><p>The response rate? Close to zero.</p><p>That’s when I started paying attention to our data more carefully. And what I found changed everything.</p><p>Users who didn’t rename and file at least one document within the first hour of signing up were essentially gone. Not maybe gone. Not probably gone. <em>Gone.</em></p><p>The activation window wasn’t a day. It wasn’t even a few hours. It was a sprint. And if no one was there to guide them through it, they’d quietly disappear and never come back.</p><p>Meanwhile, users who <em>did</em> hit our trial limit converted at a dramatically higher rate. Once someone had used Filently enough to run into the cap, the product had done its job. They’d seen the value. The conversation at that point wasn’t about convincing them. It was just about making the next step easy.</p><p>Two completely different moments. Two completely different jobs to be done. And I was handling both the same way: too late, too generic, too human.</p><h3>What a User Lifecycle Actually Means</h3><p>I’d heard the term “user lifecycle” before. I’d probably even used it in a deck somewhere. But I hadn’t really built one.</p><p>So we sat down — my co-founder <a href="https://medium.com/u/8e0f7b912368">Valentin Uhrmeister</a> on the technical side, me on the communication side — and mapped it out properly. What does a user actually experience from registration to becoming a paying customer? Where do they drop off? What do they need at each point?</p><p>We identified six stages: Trial, Activation, Engagement, Churn Prevention, Paid and Advocacy. And within those, we built 10 automated workflows, each triggered by specific user behavior.</p><p>Not by time alone. By behavior.</p><p>That distinction matters more than it sounds. A time-based message (“Hey, you signed up 3 days ago!”) is generic. A behavior-based message (“You’ve uploaded your first batch, here’s what to do next”) is relevant. One feels like a newsletter. The other feels like someone’s paying attention.</p><h3>The Stack We Chose (and Why)</h3><p>We’re a bootstrapped startup. We don’t have an enterprise marketing budget, and we didn’t want to over-engineer something we’d have to maintain forever.</p><p>Our setup:</p><ul><li><strong>Featurebase</strong> for in-app chat, surveys, help center, and roadmap feedback</li><li><strong>Zapier</strong> as the connector between our app events and the messaging tools</li><li><strong>Brevo</strong> for email automation</li></ul><p>It’s not glamorous. But it’s lean, it works, and the total cost fits comfortably within our early-stage budget. More importantly, it lets us segment by what actually matters: what’s the user’s stated goal, and where are they stuck?</p><p>The segmentation by intent — something I wrote about in my last post — flows directly into the lifecycle. Same four variants, now also driving when and what we say.</p><h3>What I Got Wrong First</h3><p>A few things I’d do differently:</p><p><strong>I started with copy before understanding the triggers.</strong> I spent time writing beautiful onboarding emails before we’d properly defined what event should fire them. Get the logic right first. The words can come second.</p><p><strong>I underestimated how fast the first hour matters.</strong> Our initial first trigger was set to go out two hours after registration. Then we looked at our activation data — median time to first upload was six minutes. Six minutes. We’re now rethinking the whole first-hour sequence.</p><p><strong>I tried to do too much in each message.</strong> Early drafts were long. Warm, founder-voiced, personal — but long. Users in the activation window don’t want a letter. They want one clear next step.</p><h3>What Changed</h3><p>Since building the lifecycle, I no longer watch the dashboard waiting to manually reach out. The system is there at 2am when someone in a different timezone signs up. It’s there when I’m at the gym. It’s there when I’m finally not thinking about Filently for five minutes.</p><p>More importantly: it’s there <em>within minutes</em>, not hours.</p><p>I don’t have conversion data yet to share — the system is fresh. But the behavior is already different. Users are getting further in the flow. The activation window is being caught more consistently. And I’m spending less time on reactive outreach and more time on the product itself.</p><h3>The Honest Part</h3><p>Building a lifecycle doesn’t mean you stop being present. It means you’re present in the right moments, with the right message, even when you physically can’t be.</p><p>I still read every support message personally. I still jump in when something needs a human response. The automation handles the predictable moments — the lifecycle touchpoints we can design for. The human part handles everything else.</p><p>That’s the split that actually works.</p><p><em>Sophia Falck-Ytter is co-founder of </em><a href="https://filently.com/?utm_source=medium&amp;utm_medium=inline-link&amp;utm_campaign=content-organic&amp;utm_content=How-I-Stopped-Being-Available-247"><em>Filently</em></a><em>, an AI filing layer for Google Drive that automatically identifies, renames, and organizes your documents.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fbd467c4a7b4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What One Month After Public Launch Actually Taught Us]]></title>
            <link>https://medium.com/@s.falckytter/what-one-month-after-public-launch-actually-taught-us-4c49f48ea422?source=rss-fede7d683276------2</link>
            <guid isPermaLink="false">https://medium.com/p/4c49f48ea422</guid>
            <category><![CDATA[startup-lessons]]></category>
            <category><![CDATA[build-in-public]]></category>
            <category><![CDATA[saas]]></category>
            <category><![CDATA[onboarding]]></category>
            <category><![CDATA[product-launch]]></category>
            <dc:creator><![CDATA[Sophia Falck-Ytter]]></dc:creator>
            <pubDate>Mon, 06 Apr 2026 08:10:17 GMT</pubDate>
            <atom:updated>2026-04-06T08:10:17.496Z</atom:updated>
            <content:encoded><![CDATA[<p><em>The two things we didn’t see coming, and why they’re changing how we build.</em></p><p>We launched <a href="https://filently.com/?utm_source=medium&amp;utm_medium=article&amp;utm_campaign=launch_learnings">Filently</a> publicly in early March 2026, first as a web-based product, and since April also on the <a href="https://workspace.google.com/marketplace/app/filently/101494202473?flow_type=2&amp;hl=de">Google Workspace Marketplace</a>.</p><p>Before launch, we spent months obsessing over the things founders are supposed to obsess over: pricing, onboarding flow, feature completeness, positioning. We ran beta tests. We collected feedback. We thought we understood our users.</p><p>We were wrong about two things that turned out to matter more than almost anything else.</p><h3>1. AI anxiety is real, and we underestimated it completely</h3><p>Here’s a question I didn’t expect to spend significant time answering in month one:</p><blockquote><em>“Will Filently process my files without asking me first?”</em></blockquote><p>And its close relatives:</p><blockquote><em>“What happens to my data? Who sees it? Is it used to train AI?”</em></blockquote><p>These weren’t edge cases. They came up constantly, in support chats, in trial conversations, in direct messages from users who had signed up, explored the product, and then… stopped. Not because the product didn’t work. Because they weren’t sure they trusted what it would do with their files.</p><p>Two fears dominated:</p><p><strong>Fear #1: Loss of control.</strong> Users worried that once they connected their Google Drive, Filently would start renaming and moving files automatically, without asking, without reviewing, without a way to undo. The idea of an AI autonomously touching their documents felt genuinely unsettling to more users than we expected.</p><p>The reality: Filently has a review step. Nothing gets filed without confirmation (unless you want us to). But we had buried that information. It wasn’t the first thing someone saw. It wasn’t the headline. We assumed users would discover it during onboarding and feel reassured. Instead, many had already made up their minds before they got there.</p><p><strong>Fear #2: Data privacy.</strong> “Where does my data go? Is it used to train AI models?” This one surprised me more. We’re GDPR-compliant, CASA Tier 2 certified, we process in EU cloud infrastructure, and we explicitly do not use customer data for AI training. We had this documented. In our privacy policy and help center article. Which nobody reads.</p><p>What we learned: trust isn’t built by documentation. It’s built by surfacing the right information at the right moment. A user who is mid-onboarding, deciding whether to connect their Drive, needs to see three sentences about data privacy. Not a link to a policy page.</p><p>The fix isn’t technical. It’s editorial. We’re now treating trust-building as a UX layer, not a legal one.</p><figure><img alt="Filently upload screen showing trust signals: ‘You confirm before anything moves’, hosted in the EU, GDPR compliant, data never used for AI training." src="https://cdn-images-1.medium.com/max/1024/1*VCezUlQ2BUQXQy-uk2sZPw.png" /><figcaption>We moved trust signals out of the privacy policy and into the product. Users see this before anything happens.</figcaption></figure><h3>2. Not all users want the same thing, and we were sending everyone down the same path</h3><p>When users sign up for Filently, we ask them one question during onboarding: what are you trying to do?</p><p>Four options:</p><ul><li>Organize files going forward (new uploads)</li><li>Tidy up existing files</li><li>Build a naming convention and folder structure from scratch</li><li>Just exploring</li></ul><p>We didn’t have this question from day one. We added it because we realized we needed to understand our users better, and we couldn’t have a 1:1 conversation with every single one of them. So we built it in as a proxy.</p><p>What we didn’t fully realize at the time: these four answers represent fundamentally different user journeys. Not just different messaging, but different product flows, different definitions of success, and different reasons to churn.</p><p>We’ve since adapted the in-product flow accordingly. The next step: doing the same for our lifecycle communication.</p><p><strong>The case that made this obvious: “Tidy up.”</strong></p><p>A user selecting “tidy up” has existing files they want organized. They’re not planning to upload new documents. They want to point Filently at their current Google Drive chaos and have it make sense of what’s already there. That’s a completely different workflow.</p><p>We were sending these users the same onboarding messages as everyone else. Messages about uploading files. CTAs about filing new documents. Naturally, several of them concluded that Filently didn’t do what they came for, and left.</p><p><strong>The broader pattern:</strong></p><figure><img alt="Table showing four Filently onboarding intents: Organize new (correct flow), Tidy up (wrong flow), Build from scratch (generic nudge), Explore (no quick overview) — illustrating the mismatch between user intent and what we were actually delivering." src="https://cdn-images-1.medium.com/max/1024/1*eR4tuSCo2PU-t62_X7hD-w.jpeg" /></figure><h3>The underlying insight: intent-based lifecycle messaging</h3><p>Most SaaS products have one onboarding flow. Maybe two, if they’ve split by company size. What we realized is that segmenting by intent, even with just four simple variants, reduces friction at exactly the point where users otherwise drop off.</p><p>The concept is straightforward, but the implementation isn’t. In practice, we’re tracking a combination of signals: the intent selected at onboarding, the state of a user’s existing folder structure, what they’ve already done in the product, and whether they’ve come back at all. Each combination routes to a different message variant, with its own timing and priority logic. Simple idea. Real engineering work (thank you <a href="https://medium.com/u/8e0f7b912368">Valentin Uhrmeister</a>!).</p><p>The insight that changed how we think about this: generic nudges don’t just underperform. They actively signal to the user that you don’t understand them. A “tidy up” user who receives a message about uploading new files doesn’t think “oh, this doesn’t apply to me.” They think “this product isn’t for me.”</p><p>That’s a different kind of damage.</p><h3>What we’re changing</h3><p>On the AI anxiety front: we’re redesigning the trust layer in onboarding. Privacy and control information moves from policy pages to the moments in the flow where users are actively forming their opinion. Short, specific, human.</p><p>On the intent front: we’re building out four distinct lifecycle message variants triggered by onboarding intent. Each one speaks to where that specific user is trying to go, not where we want to take them.</p><figure><img alt="Filently onboarding screen asking ‘What brings you here?’ with four options: Keep new documents organized, Tidy up my Drive, Build a system from scratch, Just exploring." src="https://cdn-images-1.medium.com/max/1024/1*tzDmeosn22hd-T3EKqhC6g.png" /></figure><p>Neither of these is a big product change. Both of them required us to stop assuming our users had the same mental model we did.</p><p>That’s probably the core lesson from month one: the gap between what we built and what users understood about what we built was much larger than we expected. Closing that gap is now our primary job.</p><p><em>Sophia Falck-Ytter is Co-Founder of Filently, an AI-powered filing layer for Google Drive that eliminates manual file organization. Follow the build at </em><a href="https://filently.com/?utm_source=medium&amp;utm_medium=article&amp;utm_campaign=launch_learnings"><em>filently.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4c49f48ea422" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[MVP Feedback: Why We Actively Seek Out Pain, Not Polite Praise]]></title>
            <link>https://blog.startupstash.com/mvp-feedback-why-we-actively-seek-out-pain-not-polite-praise-92cd07f3fb97?source=rss-fede7d683276------2</link>
            <guid isPermaLink="false">https://medium.com/p/92cd07f3fb97</guid>
            <category><![CDATA[startup-lessons]]></category>
            <category><![CDATA[the-mom-test]]></category>
            <category><![CDATA[build-in-public]]></category>
            <category><![CDATA[mvp]]></category>
            <category><![CDATA[feedback-form-templates]]></category>
            <dc:creator><![CDATA[Sophia Falck-Ytter]]></dc:creator>
            <pubDate>Wed, 04 Feb 2026 06:57:25 GMT</pubDate>
            <atom:updated>2026-05-28T08:47:12.724Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*H7nyKE-lQrkYw8Z7" /><figcaption>Photo by <a href="https://unsplash.com/@joszczepanska?utm_source=medium&amp;utm_medium=referral">Jo Szczepanska</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>At <a href="https://filently.com/">Filently</a>, we’re building the autonomous nervous system for documents: an intelligent filing layer that makes manual file naming and organization obsolete.</p><p>But we’re still in the MVP stage.</p><p>And in this phase, polite feedback is the biggest enemy of progress.</p><h3>What We Really Care About</h3><p>What truly interests us isn’t whether people “like” our product. We want to know:</p><ul><li>Where does friction occur?</li><li>What costs time, nerves, or money?</li><li>Where does the current workflow break down?</li></ul><p>That’s why we’ve established a clear feedback process for our first testers, inspired by <em>The Mom Test</em> and Sean Ellis’s Product-Market Fit framework.</p><h3>Our Feedback Philosophy: Don’t Be Polite, Be Real</h3><p>We open our survey with a clear message:</p><blockquote><em>“We’re not looking for compliments; we’re looking for the truth.”</em></blockquote><p>This sets the tone immediately. We want our early users to know that their criticism is more valuable than their praise. If a feature is a lifesaver, we need to know so we can double down. If something feels like a grind, we need to know so we can kill it.</p><p>This is intentionally provocative, but it works. It gives people permission to be honest, even brutally so.</p><h3>Our Focus: Eight Questions That Cut Through the Noise</h3><h3>1. Goal-Oriented Discovery: “What was your main goal?”</h3><p>We don’t assume we know why people use Filently. Instead, we ask them to tell us:</p><ul><li>Automate naming of new files</li><li>Auto-filing to correct folders</li><li>Clean up existing chaos (coming soon)</li><li>Just exploring</li><li>Something else entirely</li></ul><p>This reveals whether our perceived value proposition matches reality. Are people using Filently for what we <em>think</em> they need, or have they discovered an entirely different use case?</p><h3>2. Context Matters: “Business, Personal, or Both?”</h3><p>Understanding the context shapes everything: from pricing to features to messaging. A freelancer organizing client invoices has completely different needs than someone sorting family photos.</p><p>This simple question helps us segment feedback and identify patterns across different user groups.</p><h3>3. Document Types: The Devil in the Details</h3><blockquote>“What kind of documents are you organizing?”</blockquote><p>This open-ended question is critical. The difference between organizing invoices versus contracts versus ID cards versus receipts isn’t just semantic. It affects naming conventions, folder structures, compliance requirements, and automation logic.</p><p>Every document type is a potential micro-vertical we need to understand deeply.</p><h3>4. The Competitive Reality Check</h3><blockquote>“How did you solve this problem last time?”</blockquote><p>This is straight from <em>The Mom Test</em>. We’re not asking hypotheticals. We’re asking about actual behavior: what did you <em>do</em> last week when you faced this problem?</p><p>The answers reveal our true competition: manual renaming, ignoring the problem entirely, paying a VA, using ChatGPT, or cobbling together scripts and shortcuts.</p><h3>5. Quantifying the Pain</h3><blockquote>“How much time or money do you spend on your current process each month?”</blockquote><p>This is where we transform vague frustration into concrete ROI. When someone says “3 hours per week,” we can calculate that Filently could save them 12+ hours monthly, worth hundreds of dollars for most professionals.</p><p>This number also helps us understand willingness to pay. If someone spends $50/month on their current solution, our $29 Professional tier becomes an easy decision.</p><h3>6. Finding the Friction</h3><blockquote>“Which part of Filently felt the least natural or took the most time?”</blockquote><p>Every moment of hesitation is a design flaw. Every extra click is technical debt. Every “wait, how do I…?” moment is a signal that we haven’t yet built the invisible UI we’re aiming for.</p><p>This question makes friction visible and measurable.</p><h3>7. The Product-Market Fit Litmus Test</h3><blockquote>“How disappointed would you be if you couldn’t use Filently tomorrow?”</blockquote><p>This is the Sean Ellis question, and it’s the most important one in the entire survey.</p><p>Our goal: ≥40% answer “very disappointed.”</p><p>Below that threshold, we don’t yet have product-market fit. We have something people tolerate or find mildly useful, but not something they genuinely need. Above it, we know we’re solving a real, painful problem and we can focus on scaling rather than pivoting.</p><p>This single metric cuts through all the noise.</p><h3>8. Willingness to Pay (Revealed Preference)</h3><blockquote>“Are there other tools you currently pay for to support this step?”</blockquote><p>People lie about what they’ll pay for. But they don’t lie about what they <em>already</em> pay for.</p><p>If someone is already spending money on their current solution (whether it’s a VA service, a premium Google Workspace account, or a document management system) they’ve revealed their willingness to pay. Our job is to offer better value.</p><h3>The Follow-Up: Going Deeper</h3><p>We close with an invitation:</p><blockquote>“Would you be open to a 15-minute exchange to walk us through your specific use cases?”</blockquote><p>Not everyone will say yes. But the ones who do are our most valuable users: the ones experiencing genuine pain, the ones who want Filently to succeed because they need it to exist.</p><p>These conversations go deeper than any survey can. They reveal the context, the edge cases, the “yeah, but…” moments that only emerge when someone walks you through their actual workflow.</p><h3>Why Tally?</h3><p>For our surveys, we’re using <a href="https://tally.so/">Tally</a>. I discovered it through a podcast and immediately appreciated its strong UX: quick to set up, focused, and free. Exactly right for the MVP stage.</p><p>The tool stays invisible, which is precisely what we need. Our users should focus on their pain points, not navigate complex survey logic.</p><h3>Why This Matters: Building in Public</h3><p>This feedback process is part of our broader commitment to building Filently in public. We’re transparent about our challenges, our metrics, and our learning process.</p><p>Digital bureaucracy (the endless cycle of manual file naming, searching, and reorganizing) is a universal problem. The solution won’t come from building in isolation. It comes from deeply understanding the exact moment when someone thinks: “There has to be a better way.”</p><p>And that moment is almost always painful.</p><p>So we don’t seek praise. We seek pain.</p><p>Because pain is the signal. Pain tells us where to build next.</p><p>And pain, quantified and understood, becomes the ROI calculation that turns Filently from a “nice-to-have” into a “can’t-live-without.”</p><h3>What About You?</h3><p>If you’ve gone through a similar feedback journey, I’d love to hear: What surprised you most when you ran the numbers? Did your analytical answer match your intuition, or did they conflict?</p><p><strong>Are you drowning in Google Drive chaos?</strong> Join our waitlist at <a href="https://filently.com/">filently.com</a> and be among the first to test the filing layer that finally makes sense.</p><p><em>Sophia Falck-Ytter is Co-Founder of Filently, an AI-powered filing layer that eliminates manual file organization. She’s overly confident in her startup idea but thankfully lets user feedback prove it. Follow the build: </em><a href="https://filently.com/"><em>filently.com</em></a><em> | Free tool: </em><a href="https://cleanname.io/"><em>cleanname.io</em></a><em> | Connect on </em><a href="https://www.linkedin.com/in/sophia-falck-ytter/"><em>LinkedIn</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=92cd07f3fb97" width="1" height="1" alt=""><hr><p><a href="https://blog.startupstash.com/mvp-feedback-why-we-actively-seek-out-pain-not-polite-praise-92cd07f3fb97">MVP Feedback: Why We Actively Seek Out Pain, Not Polite Praise</a> was originally published in <a href="https://blog.startupstash.com/">Startup Stash</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[I Told My Co-Founder Our Prices Were Too Low. Then I Changed My Mind.]]></title>
            <link>https://medium.com/@s.falckytter/i-told-my-co-founder-our-prices-were-too-low-then-i-changed-my-mind-a7ab220734ef?source=rss-fede7d683276------2</link>
            <guid isPermaLink="false">https://medium.com/p/a7ab220734ef</guid>
            <category><![CDATA[build-in-public]]></category>
            <category><![CDATA[pricing-strategy]]></category>
            <category><![CDATA[saas]]></category>
            <category><![CDATA[bootstrapping]]></category>
            <category><![CDATA[startup-lessons]]></category>
            <dc:creator><![CDATA[Sophia Falck-Ytter]]></dc:creator>
            <pubDate>Mon, 26 Jan 2026 03:32:05 GMT</pubDate>
            <atom:updated>2026-01-26T04:10:12.377Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>How I went from “let’s keep it affordable” to “we need sustainable unit economics” in 48 hours of analysis.</strong></p><p>Two days before we finalized our pricing, I told <a href="https://medium.com/u/8e0f7b912368">Valentin Uhrmeister</a> we should go lower.</p><p>“Under $20 for the main tier,” I said. “We need to be accessible. Get users first, optimize later.”</p><p>At the time, it felt right. That’s what every startup advice article tells you, isn’t it? Be the affordable option. Especially when you’re about to launch an MVP — <em>a minimum viable product</em>.</p><p>But that thought lingered:<br>Is it actually okay to price “cheap” just because the product is early?</p><p>Lower prices feel good for potential customers. But could <em>we</em> afford them?</p><p>Because I deeply love numbers, I did what I always do when something feels off: I started calculating what a <strong>defensible pricing model</strong> would really look like — not emotionally, but mathematically.</p><p>What I found changed everything.</p><h3>TL;DR</h3><ul><li>Almost launched at $6/$24/$39 → 2.8x blended LTV/CAC = not bootstrappable</li><li>New pricing: $9/$29/$79 → 3.5x LTV/CAC = sustainable margins</li><li>Key formula: (CAC × 3) / retention months = your pricing floor</li><li>Read on for the full spreadsheet breakdown</li></ul><h3>Starting Point: Intuition vs. Reality</h3><p>Let me show you where we started.</p><p>Valentin had already proposed a pricing tier that felt safe:</p><ul><li>Personal: $6/ month</li><li>Professional: $24/ month</li><li>Team: $39/ month.</li></ul><p>Three tiers. Document limits that made sense (25 / 250 / 1,000 docs). A clear value ladder.</p><p>But “clear structure” doesn’t mean “viable business model.”</p><p>I opened a new spreadsheet and wrote down a single question at the top:</p><p><strong>“Can we actually bootstrap on these unit economics?”</strong></p><p>Not “will this work with investor money” or “could this work if everything goes perfectly.” Can we build a sustainable, self-financing business at these price points?</p><p>I spent the next six hours researching:</p><ul><li>Reading SaaS postmortems on pricing mistakes</li><li>Analyzing CAC benchmarks for our category (document management, productivity tools)</li><li>Studying companies at a similar stage (pre-launch, B2B, freemium or trial-based)</li></ul><p>The consensus was surprisingly clear:<br><strong>CAC in our market: $100–$300 per paying customer.</strong></p><p>I chose <strong>$150</strong> as our baseline — combining research with my own experience. It wasn’t perfect, but it was my most honest estimate.</p><p>Let’s see if I’ll be right ;)</p><p>Now the real work began.</p><h3>The Calculation That Changed Everything</h3><p>Here’s what I plugged into the spreadsheet.</p><p>I took our three-tier structure and calculated what each tier would actually cost us to acquire and serve:</p><h3>The Original Pricing Structure ($6 / $24 / $39)</h3><p><strong>Personal at $6/month:</strong></p><pre>Customer Acquisition Cost: $150<br>Monthly Gross Margin: ~$5.75 (after COGS)<br>Months to Break Even: 26 months<br>Conclusion: Cannot use paid acquisition. Loses money.</pre><p><strong>Professional at $24/month:</strong></p><pre>Customer Acquisition Cost: $150<br>Monthly Gross Margin: ~$22<br>Months to Break Even: 6.8 months<br>18-Month LTV: $396<br>LTV/CAC Ratio: 2.64x<br>Conclusion: Barely sustainable. Below the 3x benchmark.</pre><p><strong>Teams at $39/month:</strong></p><pre>Customer Acquisition Cost: $150<br>Monthly Gross Margin: ~$36<br>Months to Break Even: 4.2 months<br>18-Month LTV: $648<br>LTV/CAC Ratio: 4.32x<br>Conclusion: Good margins individually, but...</pre><h3>The Problem With This Model</h3><p>At first glance, Teams looked great with a 4.32x LTV/CAC ratio. But here’s what the spreadsheet revealed:</p><p><strong>Expected Customer Distribution:</strong></p><ul><li>Personal: 10–15% of customers</li><li>Professional: 70–80% of customers (our target segment)</li><li>Teams: 5–15% of customers</li></ul><p><strong>The Brutal Reality:</strong></p><ul><li>10% of customers lose money (Personal tier, no paid acquisition possible)</li><li>75% of customers generate minimal margin (Professional at 2.64x)</li><li>15% of customers are highly profitable (Teams)</li></ul><p><strong>Blended unit economics:</strong></p><pre>Weighted Average LTV/CAC: ~2.8x<br>Weighted Average Payback: ~6.5 months</pre><p>This is the classic “death by a thousand paper cuts” scenario.</p><p>Yes, we’d be technically profitable. Yes, the average looks “okay.”</p><p>But here’s what 2.8x really means for a bootstrapped company:</p><ul><li>Almost no buffer for mistakes</li><li>Can’t afford failed marketing experiments</li><li>One bad quarter could kill cash flow</li><li>No room to invest in product development</li><li>Constantly living paycheck-to-paycheck</li></ul><p><strong>This pricing structure only works if you have investor money.</strong> Which defeats the entire point of bootstrapping.</p><p>I stared at these numbers for an hour. Then I asked myself:</p><p><strong>“What if we moved away from ‘budget’ positioning entirely?”</strong></p><h3>Remodeling the Entire Structure</h3><p>Once I realized the original pricing didn’t work for bootstrapping, I started experimenting.</p><p>What if we raised prices across all three tiers, but positioned based on value instead of being the “affordable option”?</p><h3>The New Pricing Structure ($9 / $29 / $79)</h3><p><strong>Personal</strong> <strong>at $9/month:</strong></p><pre>Monthly Gross Margin: $8.75<br>Payback Period: 17 months<br>Strategic Role: Organic acquisition only. &quot;The Net.&quot;<br>Decision: No paid ads to this tier. Product-led growth only.</pre><p><strong>Professional at $29/month:</strong></p><pre>Monthly Gross Margin: $26.50<br>Payback Period: 5.6 months<br>LTV (18 months): $477<br>LTV/CAC Ratio: 3.18x<br>Strategic Role: &quot;The Growth Motor&quot; — primary paid acquisition target</pre><p><strong>Teams at $79/month:</strong></p><pre>Monthly Gross Margin: $69<br>Payback Period: 2.2 months<br>LTV (18 months): $1,242<br>LTV/CAC Ratio: 8.28x<br>Strategic Role: &quot;Profit &amp; Anchor&quot; — best margins, anchors perception</pre><h3>Why This Changes Everything</h3><p><strong>Old structure ($6/$24/$39):</strong></p><ul><li>Blended LTV/CAC: ~2.8x</li><li>Requires investor funding to survive lean periods</li><li>Competing on price = “budget tool” perception</li><li>Personal tier is a loss leader that can’t be advertised</li><li>Professional tier has razor-thin margins</li></ul><p><strong>New structure ($9/$29/$79):</strong></p><ul><li>Blended LTV/CAC: ~3.5x (based on expected distribution)</li><li>Healthy margins support bootstrapped growth</li><li>Competing on ROI = “professional tool” perception</li><li>Clear acquisition strategy: organic for Personal, paid for Professional+</li><li>Professional tier has sustainable margins for scaling</li></ul><p>The difference isn’t just the numbers. It’s the <strong>strategic implications</strong>:</p><p>At the old pricing, we’d need to be profitable from Day 1 or have investor cash to bridge the gap. Every acquisition dollar would need to be perfect. Every churn would hurt.</p><p>At the new pricing, we have room to:</p><ul><li>Test marketing channels and fail</li><li>Invest in customer success</li><li>Build features customers actually want</li><li>Weather seasonal fluctuations</li><li>Make mistakes and learn</li></ul><p><strong>That’s the difference between a fragile business and a resilient one.</strong></p><h3>The Annual Payment Multiplier</h3><p>But here’s where it gets even better. With aggressive annual discounts (2 months free = 17% off):</p><p><strong>Professional annual customers:</strong></p><ul><li>Pay $290 upfront (vs. $348 over 12 months)</li><li>Cover their $150 CAC immediately</li><li>Generate $110 profit on Day 1 (after CAC and first year COGS)</li><li><strong>Each annual customer finances the acquisition of the next customer</strong></li></ul><p><strong>Teams annual customers:</strong></p><ul><li>Pay $790 upfront (vs. $948 over 12 months)</li><li>Generate $520 profit on Day 1 (after CAC and first year COGS)</li><li>Can finance 3+ new customer acquisitions immediately</li></ul><p>This is the “cashflow hack” that makes bootstrapping viable. You’re not waiting 6–12 months to break even. You’re breaking even (and profiting) the moment someone chooses annual billing.</p><p>If just 40% of customers choose annual (typical for B2B SaaS), your effective payback period drops dramatically:</p><ul><li>Professional: From 5.6 months → ~3 months blended</li><li>Teams: From 2.2 months → ~1 month blended</li></ul><p>Suddenly, growth doesn’t require a war chest. It becomes self-financing.</p><figure><img alt="SaaS Pricing Strategy: When the Unit Economics finally smile back" src="https://cdn-images-1.medium.com/max/1024/1*uF-hcSeH6SnLSwCC6Q6C4Q.png" /></figure><h3>The ROI Reframe: Selling Outcomes, Not Features</h3><p>But here’s where the analytical approach intersected with psychology: <strong>customers don’t care about our CAC</strong>.</p><p>They care about their own ROI.</p><p>So I ran a different calculation: <strong>What is Filently actually worth to our customers?</strong></p><h3>For an Individual (Personal Tier)</h3><p>Conservative estimate:</p><ul><li>Manual file organization: 1.5 hours/month saved</li><li>At $30–40/hour value of time: $45–60/month in saved effort</li></ul><p><strong>They pay $9. They save $45–60.</strong></p><p>ROI: <strong>5–7×</strong></p><p>Pitch: <em>“Save an hour of paperwork for the price of two coffees.”</em></p><h3>For a Freelancer (Professional Tier)</h3><p>Conservative estimate:</p><ul><li>Manual renaming and filing: 4 hours/month</li><li>Searching for misnamed files: 3 hours/month</li><li>Re-organizing folders: 2 hours/month</li><li>Duplicate management: 1 hour/month</li><li><strong>Total: 10–12 hours/month saved</strong></li></ul><p>At $40/hour (conservative freelancer rate): <strong>$400–480/month in value</strong></p><p><strong>They pay $29. They save $400–480.</strong></p><p>ROI: <strong>14–17×</strong></p><p>Pitch: <em>“Save nearly two full workdays a month. A no-brainer.”</em></p><h3>For a Team (Teams Tier)</h3><p>Conservative estimate:</p><ul><li>3-person team, each saves 3 hours/month = 9 hours total</li><li>At $40/hour blended rate = $360/month in productivity</li><li>Plus compliance/audit security value = ~$500–1,000/month in risk reduction</li><li><strong>Total value: $860–1,360/month</strong></li></ul><p><strong>They pay $79.</strong></p><p>ROI: <strong>11–17×</strong></p><p>Pitch: <em>“The value of a part-time employee for $79 + peace of mind on audits.”</em></p><h3>The Three-Tier Architecture: Psychology Meets Spreadsheets</h3><p>Once I had the core pricing figured out, I needed to design how the tiers work together.</p><p>This is where behavioral economics meets unit economics.</p><h3>Why Three Tiers Work</h3><p><strong>Anchoring Effect</strong>:</p><ul><li>Without Teams at $79, Professional at $29 gets compared to $0 (doing it manually)</li><li>With the $79 anchor, $29 becomes the “smart middle choice”</li></ul><p><strong>Revenue Distribution</strong>:</p><ul><li>Personal ($9): 10–15% of customers → low friction entry, organic only</li><li>Professional ($29): 70–80% of customers → core revenue, paid acquisition</li><li>Teams ($79): 5–15% of customers → high-value anchor, best margins</li></ul><p><strong>Strategic Clarity</strong>:</p><ul><li>Personal = “The Net” — catches organic traffic, covers costs, can’t be advertised</li><li>Professional = “Growth Motor” — where we make money, where we invest in acquisition</li><li>Teams = “Profit &amp; Anchor” — premium tier makes $29 feel reasonable, generates outsized profit</li></ul><h3>The Document Limits Aren’t Random</h3><p>Each tier maps to real usage patterns:</p><ul><li><strong>25 docs/month</strong> = Personal use (taxes, receipts, household admin)</li><li><strong>250 docs/month</strong> = Full-time freelancer (client work, invoices, contracts)</li><li><strong>1,000 docs/month</strong> = Team operation (multiple clients, shared workflows, compliance needs)</li></ul><p>The limits aren’t about restricting value. They’re about helping customers self-select into the tier where they’ll get the most value — and where we can sustainably serve them.</p><h3>What I Got Wrong Initially</h3><p>Let me be honest about my mistakes in this process:</p><h3>Mistake #1: Confusing “Accessible” With “Viable”</h3><p>My initial instinct was: “Let’s keep it under $20–25 for the main tier so we’re accessible.”</p><p>But “accessible pricing” without sustainable unit economics is just slow suicide.</p><p>At $24/month for Professional (where 75% of revenue would come from):</p><ul><li>LTV/CAC of 2.64×</li><li>Below the 3.0× sustainability benchmark</li><li>Zero room for error</li></ul><p>At $29/month:</p><ul><li>LTV/CAC of 3.18×</li><li>Above the benchmark with buffer for mistakes</li><li>Can actually invest in growth</li></ul><p>That $5 difference ($24 → $29) translates to:</p><ul><li>21% more revenue per customer</li><li>20% better LTV/CAC ratio</li><li>Ability to test acquisition channels without fear</li></ul><p>And psychologically? The customer paying $29 isn’t doing math against $24. They’re calculating ROI: “Am I saving 10+ hours a month?” If yes, $29 is a steal.</p><h3>Mistake #2: Treating CAC as “Someday” Cost</h3><p>I initially thought: “We’ll focus on organic growth first, so CAC doesn’t matter yet.”</p><p>Wrong. Even with the best SEO and content strategy:</p><ul><li>Organic growth is slow and unpredictable</li><li>Competitive markets eventually require some paid acquisition</li><li>You need to know your unit economics BEFORE you’re forced to scale</li></ul><p>Better to build pricing that works at scale from Day 1, even if you’re not there yet.</p><p><strong>Planning to bootstrap doesn’t mean planning to stay small.</strong> It means building economics that let you grow without external capital.</p><h3>Mistake #3: Underestimating the Psychology of Positioning</h3><p>This is the one that surprised me most.</p><p>At $6/$24/$39, we’re signaling: “We’re the affordable option. We compete on price.”</p><p>This attracts customers who:</p><ul><li>Shop primarily on price</li><li>Expect minimal support</li><li>Churn faster when they find something cheaper</li><li>Don’t value the product highly</li></ul><p>At $9/$29/$79, we’re signaling: “We compete on ROI. We’re worth what we cost.”</p><p>This attracts customers who:</p><ul><li>Understand value and make buying decisions on outcomes</li><li>Are willing to pay for quality</li><li>Stay longer because they see real benefit</li><li>Become advocates because it genuinely helps them</li></ul><p>Same product. Different customer psychology. Completely different business trajectory.</p><h3>The Final Framework: How to Price Analytically</h3><p>If you’re facing a similar pricing decision, here’s the process I’d recommend:</p><h3>Step 1: Know Your True CAC</h3><ul><li>Research your category’s benchmarks ($100–200 for us)</li><li>Don’t assume organic growth will save you</li><li>Use conservative estimates (better to be pleasantly surprised)</li></ul><h3>Step 2: Calculate Minimum Viable Pricing</h3><pre>Minimum Price = (CAC × 3) / Expected Lifetime (months)</pre><p>For us: ($150 × 3) / 18 months = <strong>$25/month minimum</strong></p><p>But this is just the <em>floor</em>. You also need to factor in:</p><ul><li>Gross margin after COGS (server costs, processing, etc.)</li><li>Support costs per customer</li><li>Desired payback period (we targeted 6 months or less for the main tier)</li></ul><p>When I added operational costs, our true minimum became <strong>$28–29/month for Professional</strong>.</p><h3>Step 3: Calculate Customer ROI</h3><ul><li>What problem are you solving?</li><li>What’s it worth in time/money/risk?</li><li>Price should deliver 5–10× ROI to customer</li></ul><p>For us:</p><ul><li>Personal: 5–7× ROI</li><li>Professional: 14–17× ROI</li><li>Teams: 11–17× ROI + peace of mind</li></ul><h3>Step 4: Model the Complete Structure</h3><p>Don’t just price one tier in isolation. Calculate blended economics:</p><pre>Blended LTV/CAC = (% Tier 1 × LTV₁ + % Tier 2 × LTV₂ + % Tier 3 × LTV₃) / CAC</pre><p>For us:</p><ul><li>Old structure: 2.8× blended (not viable for bootstrapping)</li><li>New structure: 3.5× blended (sustainable with margin for error)</li></ul><h3>Step 5: Optimize for Cashflow</h3><ul><li>Annual discounts aren’t just “nice to have” — they’re survival tools</li><li>15–20% off feels generous to customers</li><li>Pulls cash forward, finances next customer acquisition</li><li>Turns growth from cash-intensive to self-financing</li></ul><h3>Step 6: Design Strategic Roles</h3><p>Each tier should have a clear job:</p><ul><li>Entry tier: Capture organic traffic, convert from trial</li><li>Core tier: Generate bulk of revenue, target for paid acquisition</li><li>Premium tier: Anchor pricing perception, capture high-value segments</li></ul><h3>Where We Landed</h3><p>After 48 hours of analysis, we settled on:</p><ul><li><strong>Personal</strong>: $9/month or $90/year (25 docs) — organic acquisition only, “The Net”</li><li><strong>Professional</strong>: $29/month or $290/year (250 docs) — primary growth driver, “The Growth Motor”</li><li><strong>Teams</strong>: $79/month or $790/year (1,000 docs, 3 users) — includes admin rights, centralized billing, shared folders, “Profit &amp; Anchor”</li></ul><p><strong>Annual discount</strong>: 2 months free (17% off) — pulls cash forward, improves payback</p><p><strong>Expansion revenue</strong>: $9 per additional seat in Teams tier — enables account growth</p><p><strong>Acquisition strategy</strong>:</p><ul><li>Personal: Organic only (PLG, SEO, free trial conversions)</li><li>Professional: Primary paid acquisition target</li><li>Teams: Upgrade path from Professional</li></ul><p>Is this perfect? I don’t know yet. We launch in late January 2026.</p><p>But I know it’s <strong>defensible</strong>.</p><p>Every number has a rationale. Every tier has a strategic purpose. The blended unit economics support bootstrapped growth with healthy margins.</p><p>And most importantly: I can confidently explain to customers why it costs what it costs, because it’s based on the value we deliver and the business we need to build — not just what we hoped to charge.</p><h3>The Takeaway</h3><p>Pricing isn’t about picking numbers that feel right. It’s about:</p><ol><li><strong>Understanding your real acquisition costs</strong> — not hoping they’ll be lower</li><li><strong>Building sustainable unit economics</strong> — especially if bootstrapping</li><li><strong>Mapping price to customer value</strong> — charge based on outcomes, not features</li><li><strong>Modeling the complete structure</strong> — don’t optimize one tier in isolation</li><li><strong>Designing for the business you want to become</strong> — not just where you are today</li></ol><p>My gut said “keep it accessible with budget pricing.”</p><p>The spreadsheet said “you need sustainable margins to bootstrap successfully.”</p><p><strong>I’m trusting the spreadsheet.</strong></p><p>Because the goal isn’t to be the cheapest option. It’s to be the option that:</p><ul><li>Delivers so much value that price becomes secondary</li><li>Has unit economics that support long-term growth</li><li>Can be built without external capital</li><li>Creates a resilient business, not a fragile one</li></ul><p><strong>What about you?</strong> If you’ve gone through a similar pricing journey, I’d love to hear: What surprised you most when you ran the numbers? Did your analytical answer match your intuition, or did they conflict?</p><p>Connect with me on <a href="https://www.linkedin.com/in/sophia-falck-ytter">LinkedIn</a> or check out what we’re building at <a href="https://filently.com/">filently.com</a>. We’re launching soon, and I’m documenting the whole journey.</p><p><em>Sophia Falck-Ytter is Co-Founder of Filently, an AI-powered filing layer that eliminates manual file organization. She spends too much time in spreadsheets and occasionally remembers to update the website. Follow the build: </em><a href="https://filently.com/"><em>filently.com</em></a><em> | Free tool: </em><a href="https://cleanname.io/"><em>cleanname.io</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a7ab220734ef" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>