Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How to sell software #15

Open
Julian-Dumitrascu opened this issue Dec 11, 2023 · 0 comments
Open

How to sell software #15

Julian-Dumitrascu opened this issue Dec 11, 2023 · 0 comments

Comments

@Julian-Dumitrascu
Copy link

Julian-Dumitrascu commented Dec 11, 2023

On 16 November 2023 LinkedIn let me know that somebody would like to connect with me, which means e.g. that they would become able to use their chat module with me, and to invite me to groups and events. I like the last thing because I like public talks.
She represents a team who can provide services to the Sol teams. They know two of my e-mail addresses. They shared with LinkedIn address 2. Had they used address 1, I would have accepted her request and wouldn’t have started this conversation yet.

  1. Some of the reasons not to use e-mail:
    1.1 Some people have more than one address.
    1.2 Some people change their address.
    These actions make it more difficult to interact remotely.
    I’d like to have only one point of contact / inbox in one computer program. What about you?

  2. Her team can improve how they manage data.

  3. She wants to sell us data management software.
    3.1 When you want to sell me software, let me use it with you!
    3.2 Let me log in with my account with GitHub!
    Otherwise, use the e-mail address I share with you only when I enable e-mail notifications!

  4. I’ve tried to change an e-mail address in my account with LinkedIn. They sent me a code, which I pasted into their input field.
    4.1 When I pressed the button Submit, it didn’t submit the code.
    4.2 Software developers keep making unpleasant surprises. This time: This field has buttons for increasing / decreasing the number.
    It’s not the only thing to improve about Microsoft software.

  5. I’ve started 8 conversations with the team of LinkedIn “helpers”.
    I don’t remember them solving any of these issues, so I avoid the cost of asking them to solve this one. LinkedIn has more than nine issues.
    Sol Computing can help you avoid issues like the ones in sections 1 to 5.

  6. I don't like these things.
    6.1 On 17 November 2023 I saw that she cancelled our talk.
    I didn’t feel good at all.
    We keep our appointments with you, and we are willing to agree with you on just about anything that we are going to do together.
    6.2 An employee of hers wrote to me that he’d like us to talk.
    Why did she try to replace herself?
    I want to talk with the founders about their vision for this service, so that we understand what benefits and what costs we can expect. Any employee can leave a team at just about any moment; they are not responsible for what happens after they split. We want to conclude agreements with the people responsible for their influence on us and on our other trading partners. We are responsible for our influence on your actions.
    6.3 One can read in his LinkedIn profile, under his name: Revenue
    I can’t talk with someone’s revenue. I can talk with revenue officers.
    I can understand his role. It is more important that I don’t feel good about their possible message: “Give us money!”
    We’ve seen many people send such messages before the time is ripe for this topic.
    We can decide to use their software once they sell me on it.
    We want to discuss many topics that matter to us. They are related to benefits we want from data management. We want software that is more helpful when people want to carry out such activities. We've rarely seen such promising software, so we're willing to try theirs.
    6.4 He sent me 3 e-mail messages.
    Not e-mail again! See 3.1!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant