Selling Software, How?

I visited your site and, to be honest, to me it is unclear why I would should choose your solution over for example PostgreSQL.

* "Fast": up to 130.000 TPS (inserts apparently) sounds a lot, but I'm not sure it is, see for example http://akorotkov.github.io/blog/2016/05/09/scalability-towar.... Maybe I'm comparing apples with oranges, but since your statement is not backed up by anything I can verify myself this does not stand out as a feature to me. It also sits in a spot where it is too high for startups to be relevant and too low for potential global players since it seems to be the limit, and as you can see in the link, even PostgreSQL provides a way to scale way beyond that number. Maybe your solution can be clustered, but I see no mention of this.

* If I need an in-memory DB, I usually need it for caching or for tests. The first use case is mostly covered by Redis (but I admit being able to use SQL for cache retrieval has some appeal), the second use case (tests) is questionable, since I either use your DB all the way or I'd have a separate DB for tests, which is a not very inviting thing to have to me.

* You state that your DB is not only in-memory only but also can?(is always?) be persisted via Redis. How is that working, what are consequences for conflicts, transactionality etc.? I don't find much about this topic, just a reference that it is "[on] par with incumbent databases such as Postgres or MySQL".

* Lastly, you should mention that the SQL dialect is SQlite. I'd hate having to learn another SQL dialect and I guess many of my peers would do the same.

I'd suggest you switch the focus from "fast in-memory DB" to "Run SQL queries on cached data to allow more leeway to your real SQL database". This sounds appealing to me, provided there are some real-life examples how this can work (e.g. a demo project).

If you go this way, I'd also probably also drop (or not focus) "being able to persist cached data" to automating cache-refreshes consistently, since this would probably be needed.

Hi, 1. Not a developer so please forgive any tech mistakes; 2. I looked on ahrefs on some of the keywords you mentioned and some more (e.g. "how to query redis with sql") - there are some searches but very limited (I would say up to 300-400/month in the US total). That's not a lot, but I don't know if it's the beginning of a trend or the end of it (devs can say that). 3. Regardless, I understand you do have users (when I say a user I mean retained users). If so, you need to talk to them, understand exactly what problem you are solving them. You can incentivize them with gift-cards or just sweet-talk your way to have a phone call with them; That's the most important thing. 4. Once you are on the call, do everything to understand what problem are you solving them + what they want you to add to the product. 5. That's the process. I did it with a social app in which I texted any user who did a meaningful action. It wasn't fun, but that's the way to do that. Get them to talk to you. Hope that helps.

> I want to avoid to just work in the tech without any marketing... But I don't know what kind of marketing I should do.

It sounds to me like you need to find a partner who is into doing that sort of thing. That's what I did. As a bonus, someone who is into this sort of thing likely will be able to give you solid information about how to change your product in order to appeal to a broader audience.

Don't forget the first law of business: be totally honest with yourself about what you can't (or don't want to) do well, and fix that gap by finding people who are good at and enjoy those things.

Go read the book "Way of the Wolf" by Jordan Belfort. Thats all you need to get started. Read it twice.

Also, disregard any opinion that gives feedback on your site or product. Talk to real customers (after reading the book).

[random advice from the internet]

"Get in your car" and go see your users instead of sitting at your desk. Seeing is the best way to really understand context and understanding the context in which your customers operate is important for B2B sales. If you can't afford to visit potential customers then it is likely that either the project is under-capitalized or that the project is not economically viable. Under-capitalization and economic viability don't matter for a hobby project. But they matter greatly for a business venture.

I'd join YC Startup School, or at least watch the previous sessions videos. Lots of good stuff in there.

How big is the problem? Is it in your potential customers' top 3 pains? Or is this just a nice to have feature for Redis?

> I really believe that there is a market for this, I needed it years ago when developing my own app and people are using it in production (or at least are keeping instance up).

What evidence do you have that a market exists? Do you know how much your users are using the product?

I visited your site. You're not selling software. You're selling support.

Why would someone buy support from you rather than someone with a track record with a popular database? Do you know what people that make those purchase decisions look for? I'm not going to speculate, since I don't make those decisions, but your post makes it sound like you haven't figured out what you're selling or why someone should buy it from you.

Relevant question: how to start a custom software development company? i.e. scale the work to several [hired] devs - ensure the constant flow of new projects/clients, etc... Does setting up a nice website help a lot? Will it bring new costumers?

Please stop spamming.