toast76

LEGO is an adjective. Never call it Legos.

Hi folks, I posted this > 4 months ago, but we've been through a couple of pivots since then.

I'm really happy where it's landed now and think the response has been much better this time around.

Smidge allows you to have quick and easy video conversations with customers from inside your app.

As a web user, I'm tired of seeing chatbots and chat widgets everywhere. If I want to read something, I'll read the docs. If I want to ask a question, I really just want to ask a person and get my answer as quick as possible.

As a founder, it's so hard to get customers into a conversation. We spend so much time deflecting them to KB articles and bots that we've lost the ability to engage with them 1:1 and that's what https://smidge.app is intended to do. We funnel users to the right team member and tee up a call instantly in-app.

Would love feedback whether video is a thing for folks (particularly early stage where you prob don't have a success team yet). We've found quick 5-minute conversations to be incredibly valuable.

(posted here 4mths ago with a different focus: https://news.ycombinator.com/item?id=24835602)

Yep absolutely. You bucket users on your end and just pass through the user Id and the segment name. Then mirror the segment as call groups on our end e.g. segment='high value'

You can also use Smidge without sending us any PII, but obviously segmentation will be limited.

Also in the next couple of weeks, with just a user id, you will be able to place a call directly from Zendesk (for example) without us knowing anything about the user.

Yeah I can understand that. This early version requires calls be routed via a server, but being webrtc it can be P2P. We'd like to provide recording and transcription in the near future (with the appropriate user permissions).

Down the track I believe we can deliver a self-hosted solution.

Sorry, we are still working on the landing page.

We don't show the user anything until you call them (so as to not interfere with drift/intercom etc). When you call them the current UI is like a mobile call UI.

EDIT: we are working on user initiated calling as we speak (it will show availability of support staff/CSRs)

Audio-only calling is in the next week or two

(Shameless plug) https://smidge.app

We had this problem with our product (BugHerd) and built a solution for it. Our success rate was ~1% and we thought we could do better.

We created a JS embed that you install in your web app. It allows you to segment your users and place a call with them from within your app (using webrtc). Unlike email/calendly/zoom square dance, Smidge has a 17-20% success rate to call. It's been huge for us and we're now opening to beta. Would love feedback

(Screensharing, "request a call" and page/user calling coming soon!)

Hi folks, my name is Alan, I’m the founder of Smidge (previously founded BugHerd, Usabilityhub/Fivesecondtest and ahem RightGIF)

https://smidge.app

As a founder, I’ve always found it hard to find customers willing to have a conversation about our products. The vast majority of users ignore chat apps and don’t respond to emails, but we keep using these tools because it’s cheap and easy to implement. It’s a habit, but it’s becoming less and less effective. I talked to dozens of other founders and found the same problems over and over again. We talk to customers during pre-sales and during support, but that’s about it. We talk to solve and sell, but rarely to learn. I wanted to do better. So I came up with Smidge.

Smidge is instant 1:1 video chat with users from within your app. No email, no Calendly links, nothing for your users to install. Just quick easy conversations.

You install our JS in your web app and we start keeping track of who is active in your app. When you want to talk to a customer, you simply click the “call” button and we robodial users one at a time until someone answers. It sounds intrusive, but in our experience, the users of BugHerd have loved it. It’s easy for them to decline or ask to be called another time (if they decline, we won’t ever call them again). If you optionally provide user meta data, you can create call groups to segment users into buckets. Helpful for getting your CSRs on to high value clients or helping people through onboarding.

We’ve been using it on BugHerd and the response has been pretty great. Previously we’d send out an email with a Calendly link, and out of 2000 odd emails, we’d get maybe 10-20 people on to a Zoom call. So < 1%. Smidge’s success rate is around 15-20%. That means within about 3 minutes of sitting down, you’re on a video call with a user. Until now that’s never been possible (unless you collect ph number at sign up). Our product team now typically talk to 1 customer each per day. That adds up to 250 customer conversations per year that simply weren’t happening before, and it requires no planning, just some spare time to make a call.

Very keen to get some more folks trying it, and of course I’d love your feedback. I’ll be watching here, but you can also email me at alan@smidge.app

Coming soon:

- recording/transcription to help you get insights into ProductBoard or Dovetail.

- Request a call with a specific user from a link (to allow you to hook that into Zendesk, intercom or other support apps).

- Page groups (so you can get CSRs to call folks on certain pages)

- and screen-sharing/remote-control.

I know GIFs are not exactly an "important social good", but I do like the idea of keeping RightGIF independent. We definitely want to integrate with Teams of course, so there will no doubt be conversations to be had there :)

Thank you! My hope is to be able to support as many platforms as we can, or even open up the API in way that allows users to roll their own.

Yeah, privacy for us has always been #1. It means we will need to monetise, but all indications are that teams are willing to pay a small amount for that privacy. We have the benefit of not wanting to get rich.

LOL... I forgot it even existed. It was a hackathon project that never made it past being a hackathon project :) I'm glad someone remembers it though!

As majority owners, we certainly could have continued to run the company indefinitely as a "lifestyle business" (and there's not much anyone could have done about it). But my belief is that if you take investment you have a responsibility to those investors to return their capital come hell or high water.

At the time, we didn't entirely know whether there were still growth opportunities or what else we could try if we kept going. But we knew we wanted to keep trying. Some of our investors wanted out, and we gave them (and all the other investors) the opportunity to sell their shares back to us. It means everyone who wanted it got their money back (which for an investor is not actually a very good outcome, but better than $0), and we got to keep the company. I'm appreciative of them allowing us to do it.

Errr... no... just no.

Digital Agencies get the most value (because they tend to have more projects on the go), but any web team wanting feedback from stakeholders will enjoy it.

It was a pivot that failed.

Even though we were growing quickly, the data showed that we'd landed on a local maxima with the original product. Our churn rate was around 3%/mth and the vast majority of churn was "because we don't have a project in QA". We felt we could address that with a different offering (you'd call it a pivot). That pivot failed to deliver a product that resonated the way the original did.

Fortunately, we hadn't shut down the original product (which was still growing), and so the mistake was not fatal.

Surprisingly accurate :)

Thanks for sticking around :) I know it's frustrating to see so little action over such a long period of time. We're slowly rolling out a bunch of stuff which we really should've added years ago... We have some other wish list items we're working on at the moment, but a "user dashboard" is on our roadmap I promise! :)

(founder here) Definitely not dead! Far from it! Profitable and still growing.

September was our largest single month growth since April 2014 and we'll easily beat that this month. Lots has changed with the app in the last 12 months and lots happening as we speak. If you haven't looked for a while, drop in and take a look!

Anything that makes it more convenient for people to get from A to B in a _car_ will, of course, create more traffic. Convenience increases usage.

Uber/Lyft may make it unnecessary for some folks to own a car, but a reduction in car ownership does not mean a reduction in car usage.

Fun puzzle, but I had the same problem. Example: https://imgur.com/a/t4T5l The solution is valid, but the expected result has the two dots in a different position. EDIT: I just realised, although it isn't clear in the instructions, that the shape of the boats is an implied part of the solution.

Work with other startup founders, mentor students, assist at an accelerator, teach a course at your local university.

In my experience, sharing the (limited) knowledge I have gained has helped me realise I actually know more than I give myself credit for. Even if you're only six month ahead of another founder, you've got six months of knowledge to share. Share it, and you'll realise how much you've actually learned.

Backblaze (and others) don't support backing up from a NAS, which, for a family, is impractical.

My father used to (and probably still does) call out "spectacles, testicles, wallet and watch" before leaving the house.

No, it wasn't quick. It is way way too late. It shouldn't require someone to publicly shame them before taking action. Acting now, after what was known privately is now public, is a cynical effort to appease the masses whilst continuing to condone ongoing practices within their organisation.

The people involved should've been fired long ago, and for Kalanick to come out and say what happened is "against everything Uber stands for and believes in", thus suggesting he was unaware, only serves to reinforce his failure as leader. Blame ultimately lies with the CEO, no matter what.

Women shouldn't need to put their careers on the line to publicly shame a company before justice is seen.

(edit: apologies to the parent, was not pointing fingers at you...anger was misdirected)

Article bashing React, written by the author of the library he suggests you use instead.

Jay hasn't done sufficient self promotion here. Neptune's Pride 2 is one of my favourite multiplayer games ever. It's a turn based "board game", somewhat akin to Risk, that can take weeks to complete.

If you work in a team you must play it. It is guaranteed to end in tears (In a hopefully good way). https://np.ironhelmet.com/#landing

Errr... no it's not. It's reassuring their customers that the service they pay for will continue to operate. As one of those customers, I'm glad to hear it.

I'm not affiliated, and whilst I'm generally super sceptical of hardware kickstarters, this gets my backing!

Nice.

Some feedback: I had some problems with the auto-complete on the front page search. I typed and hit enter expecting to go to a search results page, but instead it must've selected the top result in the autocomplete and took me to that page instead.

When i got to a results page (Jasper Fforde in this case) and selected one of the books it too me to a "finding prices" page, but the page title is Page Not Found. Back button didn't seem to work after getting there either... had to manually go back to search results

The search results page didn't seem to be in any particular order. Again, looking at Jasper Fforde, was hard to know if there is a new book available here especially as there are a couple of different series he's written.

When i did find a book, was surprised there was only a listing from book depository, and then a message saying "oops ebay error". No amazon?

In all it's a nice interface/app, but I'm not entirely sure why I wouldn't just use goodreads (which you seem to be leveraging anyway).

Happy to have a chat if you want to catch up at some point, it's been a while :)