Hacker News new | ask | show | jobs
by photon_off 2309 days ago
I have no idea, but I can say with certainty it depends on the size of your target audience. Find a way to reach them and continually refine your landing page so that your funnel is as optimized as possible. Speaking of which...

I can give you my initial first impressions of your landing page:

1) I am utterly confused as to what this is or how it works. Something about splitting proceeds. I will scroll, surely it will be explained.

2) I scrolled past the gigantic top fold and found "Find members, set percentage share, and get paid Let Korabo handle the splitting of proceeds and delivering actionable analytics to you". What are members, and how does Korabo help me find them? Splitting proceeds of what? Analytics?

I managed to find the tiny menu in the upper right, and now I better understand what this app is for, and actually I think it could be useful to some groups of people. On further thought, is anybody willing to pay somebody else to split the proceeds? It seems easier for some group of people to simply do this manually, as organizations have been doing since the dawn of time.

Anyway here's my feedback:

- Your landing page is about 1/50th as good as it could be. It's not bad, but to actually get people to trust you enough to do work (eg: sign up), you need to get them excited.

- Having somebody sign up requires a very high degree of interest. You're lucky if somebody cares enough to scroll past the fold, or even click on a link for more info. Signing up is an order of magnitude more difficult. So you're going to have to put a lot of work into showcasing the right things in the right places.

- Show the key points above the fold -- all the stuff on your "how it works" and "what it costs" pages should just be on the front page, and clicking should scroll down.

- A picture is worth 1000 words, so feature the product, and not a stock photo. If you could show one killer screenshot that immediately shows me what the app does and makes it clear that it's useful for my use case, then you'll see 10x improvement in conversion rate from what you have now.

- Improve your tagline. "Sell together" is fine, but I cannot fathom how an app would help me do that -- so maybe "Sell together, split the proceeds".

- To improve trust factor -- Get a logo and favicon.

- If you could show a demo of the app without forcing me to sign in, I'll be more likely to actually sign in.

Suggestions for finding users:

- Firstly, do the things above. You only get one chance at a first impression, and as it stands I would not trust your app with doing checkout processing for me.

- For yourself, clearly define your target audience. It seems to be small groups of people bootstrapping some service or products. You should have a better idea of this than me, but for example say it's "yoga studios". Reach out to management in yoga studios and ask for feedback. Go to a relevant subreddit and find users that work at yoga studios and ask for feedback.

- Asking for feedback, and parsing feedback is a whole game, too. Realize that you are incredibly biased in your knowledge of your problem domain and your apps features. Assume everybody you show this to knows nothing, even if it's something they'd be interested in. So if you want general landing page feedback, you'd ask: "Is it clear what this does?" -- if you want feedback from prospective customers you'd ask: "Do you think this could help you? Why/Why not?" or "What would prevent you from using this?"

Good luck.

1 comments

Thanks a lot for the detailed and constructive feedback.

Yes, I have been struggling in trying to communicate the functionality of the application in a few words & images. This resulted in including the “tiny” menu (LOL!), which is becoming more clear that it's probably not the correct medium for delivery.

All the ideas you mentioned with respect to the landing page, I am going to take into account for sure. They all make sense. One reason, I was trying to keep it as simple as possible was that I just don't have the skills to design and integrate a well-flowing landing page. The current landing page is only using React components and MaterialUI for styling which probably is very apparent to the professional eye. I think with more work I can get it into the right form, but was trying to balance timing of spending money for professional work and user acquisition. In other words, I wanted to see that the app was getting some sign ups before actually spending cash, but seems like I am dealing with a chicken and egg problem to a certain extent.

Your comment “as it stands I would not trust your app with doing checkout processing for me.” really resonates. Will put more work in for sure.

Thanks again for the candid response.

You're welcome, and I'm glad I could revive this post a bit, too :)

I am genuinely curious though, who is this app for? For what group of people is splitting proceeds really so daunting of a task that they would prefer to pay a company to do it for them?

The idea literally came up as I watched my wife split proceeds from a workshop she held with a couple of other instructors.

Seemed like a hassle to translate the % splits to actual amounts, figure out/confirm wiring details, and then decide when to wire...I would also think the other instructors were wondering when their share was going to hit.

So I stood there thinking, what if she could pre-set percentage share, and have software split the proceeds on a per payment basis so she doesn't have to worry about getting the split amounts right and the disbursement of proceeds. Her partners wouldn't have to wait either.

Felt like the software solution would be killing many birds with one stone.

A light bulb went off in my head, as I registered a problem, and as any sane individual would nose-dived into building an app!

My wife isn't using it at the moment as her yoga studio/business is in Japan, and Stripe doesn't allow for a platform to be in a different country then its connected accounts and I chose the US to release.

The users aren't being charged to use the application. The app will absorb the costs and lump it into a fee that is charged to the final consumer.

That all said, maybe this doesn't generalize outside this particular example and the problem is too specific to her situation...

In summary, the app is for any group that is receiving proceeds from the sale of a service or product, that wants to avoid the hassles of splitting proceeds after the fact.

I think I understand when this is most relevant: when there are many different things being sold that each need to have a different split. In my mind I was thinking of a team that sold multiple products, but where the split would always remain the same.

> In summary, the app is for any group that is receiving proceeds from the sale of a service or product, that wants to avoid the hassles of splitting proceeds after the fact.

Be careful here. The app is for a narrower group than that. As mentioned above, it's probably only relevant if the group has multiple offerings where the splits are different... otherwise you're just a middleman that does, um, division.

> The users aren't being charged to use the application.

While this is technically true, the app adds a cost to the final consumer, which is the same as the business "charging" the user. I don't see this as a "feature". Basically, it's an additional cost to the business -- it should be up to the business to include a separate line item on the charge vs. just increasing their price to the consumer.

In other words, allow the business to choose "show additional fee" or not. Businesses probably prefer just increasing prices to showing the user an additional "fee".

Thanks again for the feedback. The middleman that does division is a good one!...but actually may be the simple reality...

I am going to take all this feedback and have a think.

Thanks again.