Two clients. Two very different goodbyes...

The week isn't over yet, but it's already been a rough end to the month.
Two clients. Two very different goodbyes...
Client 1:
"Thanks, Serhii.
Mobizy.io (my mCommerce startup) helped us launch online sales and opened up a big new channel for us. We really appreciate it. But we've decided to build our own IT team and infrastructure, so we'd like your help with the migration"
Client 2:
I spent the whole month helping them optimize and move their infrastructure so it wouldn't depend on my team. I asked them directly about their plans, because a lot of marketing work is set up in advance with outside vendors (scheduled payments, etc.)
Their answer: "No, we're happy working with you and we'll continue. It's just about owning the infrastructure". Yesterday, my team was locked out of everything. Then I got a call telling us to stop immediately, with no prior notice.
Honestly, I'm fine with both.
But my respect always goes to transparency, whatever happens next.
That's just how I do business.
Q1: How's your week going?
Q2: Which client have you met more often?
Our search queries are longer than our help articles.
We analyzed 840,000 in-product search queries and compared them to our documentation titles.
Median search query: 7 words
Median help article title: 4 words
Top search query: "how do I share a folder with someone outside my company"
Our help article for that was titled "Sharing." Users were typing full sentences. We had written nouns.
When we rewrote the top 50 article titles to match the actual query phrasing, search-to-article click rate rose from 19% to 44%, and "search abandoned" sessions dropped 31%. We had been optimizing for how we organize knowledge, not for how people ask for it.
Our users copy-paste more than they click.
We instrumented interaction types across 1.4 million sessions over 60 days. We expected clicks and taps to dominate.
Click/tap: 61% of interactions
Keyboard input: 24%
Copy: 9%
Paste: 6%
Then we looked at which sessions had the highest task completion. Sessions with heavy copy-paste had a 2.7x higher completion rate than sessions without it. Users were moving data between our product and somewhere else a spreadsheet, an email, a doc, another tool.
We had no feature for this. No "copy as" option, no export to clipboard, no paste-aware import. Our users had built an integration out of the clipboard because we had not built one. The clipboard was our most-used API and we had never designed for it.
What makes an early growth loop sustainable?
I have been thinking about growth as a learning loop rather than a channel checklist. For an early product, what signals help you decide whether to deepen one acquisition path or test a new one? I find that repeated customer conversations and small experiments usually reveal more than broad reach.
If you lost everything and had to start from zero, how would you get back?
There's always a lesson in failure.
If anyone went through the situation of having lost everything, would love to hear about your story on how you got back on track! If not, would still love to hear about your hypothetical approach.
Built an AI crypto trader. The API bans were instant.
I used an AI assistant to write a spot trading bot with stop-loss logic. The backtesting looked amazing.. The minute I deployed it live the exchange banned my API key. The AI had built a polling loop that hammered the endpoint 50 times a second of using WebSockets. It wrote logic but completely ignored infrastructure reality. Anyone else learn the way that LLMs don't understand rate limits?
Should you ever rely on a vendor's status page for Critical API Integrations?
We got hit hard recently because a partner API quietly changed their token lifespan and rate limits without any notice in their changelog. Trust was completely broken after customer data got affected and a few users churned.
We stopped relying on their status updates entirely and set up our own automated health checks every few minutes to catch silent failures early.
What's your rule for handling third party services that constantly push unannounced breaking changes?
How do you keep your knowledge base from becoming a cluttered mess as your product evolves?
We realized our support team was ignoring our official documentation because half the articles covered old features or outdated UI. Answering tickets took longer because people had to double-check everything verbally.
We spent time cutting our docs down to just the core essentials and archiving the rest. Trimming the clutter reduced our ticket response time by nearly 40%.
Do you have a scheduled routine for retiring old support docs, or do you just wait until the clutter becomes overwhelming?
How do you pinpoint the exact moment a new user actually gets value?
We used to celebrate high onboarding completion rates assuming those users were fully setup and happy. But after analyzing churn we realized finishing a walkthrough doesn't mean the user solved their problem.
Shifted our focus to tracking "first real accomplishment" instead of setup steps. If a user creates their first live invoice or exports a report that's when they actually convert into a long-term user.
Is building an MVP still about building the minimum product?
I've been thinking about how the definition of MVP is changing. In the past, building an MVP usually meant spending weeks or months creating the smallest version of a product that could test an idea. Now, with AI tools, someone can build a working prototype in days or even hours. But I wonder if the bottleneck has moved: Is the MVP still the product itself? Or is it now the fastest way to test whether users actually care? How much should founders build before talking to customers? I've noticed that it's easier than ever to create something functional, but much harder to know whether you're building the right thing. For founders who have launched MVPs:
What was the biggest lesson you learned from your first version?