There s one thing we re really good at as builders: we constantly try to improve our work and our product every single day. But an honest question I often ask myself is: do we put the same effort into updating ourselves?
At Murror, we re a small team of around five people. For me, it s important not only to improve the product, but to continuously update my mindset, skills, and learnings and share them openly with the team.
I try to communicate everything I learn, ask questions, and clarify problems as much as possible, so the product we re building becomes better, clearer, and more convincing for our users.
To do that, I try to practice a few things consistently:
First of all, thank you so much for all the support and feedback on launch day, I really appreciate it.
I just shipped a new update to stillmail.
You can now send a letter to a friend and they can read it instantly through a secure magic link, no sign-up required. The link only opens that specific letter.
I just want to say thank you to everyone who supported the PingPrompt launch.
We finished #10 of the day and got featured on Product Hunt among 463 products launched yesterday. This means a lot, especially because this was PingPrompt s first public launch whitout audience, competing alongside some truly great apps.
We also gained 102 new followers, plus new trial users and subscriptions. Thank you for the trust and for taking the time to try something new.
1. Startup founders get lost in legal, accounting, and administrative tasks after incorporation, leading to stress and risks due to the lack of a clear, step-by-step plan.
2. The owner of a relaunched bar on the French coast cannot attract an audience in the evening due to the legacy of its past format (nightclub) and its isolated location.
We often see launch posts, milestones, and success stories. What we don t see as much are honest breakdowns of products that quietly stalled or failed.
I feel there s a lot of learning hidden there about timing, assumptions, and trade-offs.
The github repo can be found here: https://github.com/basejump-ai/b...
A little more history on what led us to this point. We started working on Basejump in 2023 and always had the goal to eventually open source. It took us almost 3 years, but we're really happy with what we're giving to the community.
A detailed description of a systemic pain point in the B2B segment has come to ProblemHunt. This is not a classic user request but rather an analysis from a consultant. We can't publish it as a standard problem, but it's too profound to ignore. Let's examine it as a case study. Before publication, all unnecessary information was removed while preserving the important details and essence.
With today s tools, translation (UI, copy, even video) is no longer the hard part.
What slows us down instead are things like tax, legal compliance, hiring, support, payments sometimes even geopolitics. The moment users show up from a new country, a product problem turns into an operating one.
Today, I read in the news that OpenAI is considering "expanding its data footprint" and possibly buying Pinterest, as there is a lot of data on it just for the sake of users finding inspiration (which can be key for purchase decision making and understanding personas Pinterest has 600M+ users).
I also take into account how Pinterest started to resent the proliferation of AI content there users do not like it so much (as far as I know, OpenAI also wants to have its own social network, and Sora curation is a bit reminiscent of that)
I have been cranking out apps for the past few years and loving it. Then one morning a week or 2 ago I got a little ambitious and decided to build a desktop email client because outlook was so-so and superhuman was ridiculously expensive.
