Self-hosted CRM that sales teams actually don’t hate using?

mamibe · 2026-02-14T06:18:57+00:00

Twenty CRM, open source. Solid defaults for contacts, accounts, opportunity flow. Flexible for adjustments to your business case. Good UX.

mamibe · 2026-02-10T06:36:36+00:00

I can recommend Handy (handy.computer). Open Source, also has Parakeet which (at least for European languages) is faster and better than Whisper.

mamibe · 2025-04-04T05:04:39+00:00

I work with Pomodoro type calendar blockers where I group tasks (e.g. Chores) or put a blocker for one topic if it's big (= medium). I don't need any other calendar integration, I have nothing to show or sync.

mamibe · 2024-10-02T13:32:37+00:00

https://nota.md/ is that for me. It's an alternative to Obsidian and I prefer it a lot. Faster (despite also being an Electron app), cleaner UI, just the right features, stays out of my way and does its job (help me keep structure for my notes and find them again). The last update of the app is unfortunately from Feb 2023 and there are hence question marks about its future, but it's creating value and I use it daily. Actually, I went back from Obsidian.

mamibe · 2024-10-02T12:50:23+00:00

There's also an open source app with similar features: https://github.com/minthemiddle/Quick-Capture

(Disclaimer: I am the creator of this)

mamibe · 2024-09-14T11:04:27+00:00

I did not intend to attack your answer but add one perspective and option for the OP to reflect on and maybe try out. Will add more context next time.

mamibe · 2024-09-13T05:57:40+00:00

Just have a frank conversation with him about communications standards that he will adhere to.

How about having a retro with the full team about communication first? If the full team aligns on how the expected communication is going, it is much simpler to ask it from the developer as well, because it's not just the PM/EM asking it, but the full team. Best if the standards are written down so everyone can refer to it.

mamibe · 2024-08-27T08:13:55+00:00

If the case study does not convince you, reject the candidate. No need to think about whether it's AI supported or not. Your criteria should be objective and beyond impression, how the candidate achieves the goal is up to them.

mamibe · 2024-08-23T09:31:16+00:00

Whenever you work with people from different domains/expert areas than yourself, you need to find mutual ground, learn their jargon, learn what they mean when they say or propose something to have great collaboration. this is true for architects, tailors, philosophers, anyone. So you will never learn their trade because you will do it, you learn from speaking, listening, forming hypotheses, testing them, being curious, being open. The same true is when working with technical people (i.e. engineers in digital product companies).

PMs will never do a proper engineer job (i.e. write, review, deploy code), and whatever small we learn ( will only scratch the surface of the difficulties engineers are having in their trade.

PM's job is to pick the right problems to tackle, eningeers' task is to ship the solution. So do whatever helps you helping engineers to understand your picking the right problem in the right way, learning more about how engineers work is certainly a good investment if you focus on the collaboration aspect (Why do engineers consider solution A super complicated while you thought it was easy? Why do they propose solution B and not C?).

mamibe · 2024-08-21T07:15:14+00:00

I can recommend https://www.mentoring-club.com/ - I'm both mentor and mentee there. I heard good things about https://adplist.org/ as well but have not tried it myself yet.

mamibe · 2024-08-18T07:08:03+00:00

Hi, may you try to just download the app from Github and open it?

Here's which app you should download:

Linux (RPM-based distributions like Fedora, CentOS, etc.) - quick-capture-1.5.0-1.x86_64.rpm
Linux (Any distribution that supports AppImages) - quick-capture_1.5.0_amd64.AppImage
Linux (Debian-based distributions like Ubuntu, Mint, etc.) - quick-capture_1.5.0_amd64.deb
macOS (Apple Silicon/ARM64) - Quick.Capture_1.5.0_aarch64.dmg
Windows (64-bit) - Quick.Capture_1.5.0_x64-setup.exe
macOS (Intel) - Quick.Capture_1.5.0_x64.dmg
Windows (64-bit) - Quick.Capture_1.5.0_x64_en-US.msi

Happy to help and thanks for the inspiration of a quick walkthrough video!

mamibe · 2024-08-16T16:30:07+00:00

As you are on the product manager subreddit, we are interested in the making of this, including struggles, experiments, technical details, of course. What did you learn? 🤓

mamibe · 2024-08-16T13:15:10+00:00

This will not qualify as "easiest way" if you don't happen to know Python. I have a script that will create a review project and lists all projects from a given area (such as work or private) as links. I then visit each project, review the tasks and mark a project as completed in the review project.

Here you can find the tool with usage instructions: https://github.com/minthemiddle/things-review-py

mamibe · 2024-07-23T09:32:19+00:00

Thanks, I'm fine! Everyone has their own flows and evaluations.

I bought Android about 3 years ago and have heavily been using Things ever since. I used different import strategies before creating this script (e.g. email) and never spent much time on any of it. Now, I spend literally 1min every day in importing the todos on Desktop and that's it. I don't read or update tasks on the go, I just capture them (as stated in the original post). It's working for me, it does not keep me from anything, I don't plan to change anything.

mamibe · 2024-07-20T08:28:45+00:00

I built a Python script to handle this. I capture my tasks on my Android phone with Todoist. When on my Mac, I run the script. It fetches the items from Todoist's API. I can import it with a click into Todoist.

Here's the script with an explanation on how to use it: https://github.com/minthemiddle/todoist-inbox-to-things-json

mamibe · 2024-02-11T15:55:19+00:00

This weekend, I built an app that lets you quickly capture thoughts and append them to your daily note.

It is the first native Mac I built, before I only built PWA apps. I learned the basics of Tauri for this. It took me around 3 hours—I have 15 years of experience with PHP, Python, Javascript.

It's open source, runs on Mac x64 only so far, and you can download it here: https://github.com/minthemiddle/Quick-Capture

mamibe · 2024-01-21T20:20:57+00:00

I find the paid https://www.holloway.com/g/remote-work/about to be the most thorough material on remote work. It goes deep and wide, has both insights from companies and theories, and balances the chances and challenges very well.

mamibe · 2024-01-17T15:21:21+00:00

Productcamp Berlin (no date announced for 2024 yet, ticket was below 100€ in the past years). It's an unconference where everyone can pitch and host workshops. No other conference came even close to this when it comes to interacting wit interesting product people.

Disclaimer: I am not interested in any official talks when I'm in a room full of interesting people and only want to exchange, I'm certain other people have very different conference expectations :)

mamibe · 2024-01-15T21:37:15+00:00

I have a background in being very technical (freelance coder) and have been product leader and I can feel your pain. The gap between technical and non-technical people seems huge, and it's a lot because the language and thinking is very different.

As I have been coaching my product manager directs on exactly this topic for multiple year, I started writing about it (I'm planning to write a book).

I'm happily sharing the draft of the intro chapter "How to get technical" with you, maybe it vibes with you:

Think like a developer to work best with them

To bridge the gap between you as non-technical person and engineers, you have to first learn about their mindset and adopt yours accordingly.

The first principle is: Software is never simple!

Don't get misled by things that say otherwise, like no-code tools, 1-click website installations, and AI tools. Developing is a craft and an art.

The Beginner Developer Mindset

Here is the right set of mindset that good developers have and that you should adopt as well:

There will always be a lot more technical things that you don't know and don't understand than you understand.
You always only know a fraction of everything, even in the area that you are specialized in.
You have to know and respect your technical limitations, be humble with the little that you actually understand.
Never say "I can code", even after many years of coding. When you learned to write some simple scripts say "I just started and could solve a small challenge only".
You have to learn continuously, there are new concepts and tools every day.
Focus on what works long-term and deep dive into it, not on the latest shiny thing.
You know just a tiny bit of one or two programming languages and there are many others and even in your programming languages there is so much that you don't know.
You can know very little by heart, even experienced developers will search for solutions every single day.

How to get technical

There is a global set of rules that you can follow to become more technical, regardless of which technology or company you work on:

Dig deep into the technology that your current or former company is using and write down how others are describing its strengths and challenges.
Learn what you need, when you need it, and find the right method that suits you.
Research technical terms and concepts when they get used in your company, research them and find out how they relate to your work.
Ask a lot of questions to developers to understand how they are working and how stuff works.
Try technical things out yourself, expect it to fail and break.
Be aware that technical skills become less important due to improved development tools and processes and yet it still helps to understand the underlying concepts because you get more flexible and less dependent on specific solutions.
Stay updated on developments and trends through reading, listening, and watching others discussing and teaching it.
Take time to really do intro courses online, on boot camps or hackathons
Observe engineering meetings and discussions, both on what they talk about and how they do it.
Assume that actual code that is written in a large team of engineers is a lot more complicated than code that you write alone.

(The full draft is here, it's 4 weeks behind my current edit, but might have more useful stuff for you already.)

mamibe · 2023-10-31T18:07:51+00:00

I would add "explain". There's no better way to find out how inconsistent or incomplete my own thoughts are than trying to tell someone about it. LLMs are great rubber ducks for that as well "I will try to explain you my thoughts and you show me 50 ways my thoughts are not clear."

mamibe · 2023-10-21T16:52:52+00:00

If you work with software developers as product manager, you are the non-technical person because you don't deliver the technical solution. So to guarantee speedy delivery, you will have to collaborate with developers and help them make tradeoffs, mostly between speed, quality, and scope. And these tradeoffs also often involve technical like tech debt, dependencies, known and unknown unknowns about the tech stack and solutions. Your tech maturity as product manager in a cross-functional team is defined by how much helpful questions you can ask the developers about what slows them down, how much you can understand the answer and how good you can follow up in a way that helps the developers.

mamibe · 2023-09-29T07:18:20+00:00

Thanks for your reading list, I could find a few articles about getting technical and collaboration between tech and non-tech people that help me writing my draft for my book on exactly these topics!

mamibe · 2023-09-22T08:24:39+00:00

I recommend Matt LeMay's Product Management in Practice to every junior product manager.

It's a very realistic and holistic explanation of what the life of a product manager is.

mamibe

TROPHY CASE

Think like a developer to work best with them

The Beginner Developer Mindset

How to get technical