logoalt Hacker News

znpy • today at 5:05 PM • 9 replies • view on HN

I am not affiliated in any way with framework (and I don’t even own framework hardware) but i’d like to offer a different perspective: support is an expensive part of the business, with an unpredictable volume of work, for which hiring can often be “hard”.

If you need to have strong technical people in support, you’ll be overspending in salaries for people that will likely move fairly soon to better positions (a lot of tech people started in support, i did myself).

If otherwise you don’t spend enough you get to keep the books in check but then you have support people that are not very technical and mostly read from a script.

And there are a ton of other things that happen behind the curtains as well.

Support seem easy but trust me, it isn’t.


Replies

reticulates • today at 5:19 PM

I have extensive support experience, you're right, support is not easy, that said, there is a very easy win: hire enthusiastic support staff that are overqualified. Customers don't like slow support but slow support is forgivable if it is good support. Framework's support as described in the post is a disaster, the worst type of support. Bad support compounds: if your support agents are doing the bare minimum to move a ticket along, they're pissing off customers and missing insight that would be valuable to the teams responsible. A customer support team of 2 technical people will deliver more for the company than a customer support team of 10 untrained people.

The quick fix for any company in this situation is to require that technical people across the company take responsibility for customer support. Of course, they don't want to, hardware designers and software engineers can't imagine anything worse, but they've got to be exposed to how real customers are experiencing their work to have any hope of doing a good job. The exposure can be direct (in a crisis) or indirect (through technical support staff relaying).

If I were the Framework CEO, I'd be taking over customer support myself. A nightmare, but necessary to understand why their support is so bad.

➕ show 4 replies
msteffen • today at 5:51 PM

I agree that support is hard.

Since you seem to have experience with this, the principle that I've seen work "best" in my own limited experience (and I wonder how it matches with your experience) is to keep the barriers between support and product development as low as possible:

1. keep the company as small as possible in general (which lowers all communication barriers everywhere, and helps with cash flow—fewer salaries, smaller office, low overhead)

2. Early on, have the same engineers doing product development and support. Later, have heavy, regular communication between the teams (including managers and senior ICs on both sides. Maybe rotating the managers would work? I don't know. Once you have more than one level, I don't know anymore, but maybe do the same thing with directors and senior managers?). This hurts growth, because you're understaffed to begin with, and you're impeding the staff you have by giving them tons of unplanned support work. But IME it means that product development is happening at the right level of abstraction.

If the product you're building requires big company support (or training or product development), and the revenue it brings in can only support a small company, then you should change what you're building. It's very hard to change what you're building if the company is very big.

So if, for example, support is boiling because your product is flaky, and engineering is too small and too busy to fix all the problems at a reasonable pace, you probably have a design problem(s) and expanding will make it more entrenched. Instead, you should simplify the product. Then expand (with an understanding of the real costs of different parts of your vision), and repeat.

switchbak • today at 5:11 PM

It being hard is no excuse for not doing it. Building long bridges is hard, doing surgery is hard. Creating a new computer company is hard. That doesn’t excuse you having a support organization that costs the company’s reputation and future viability.

sharts • today at 5:13 PM

No company comes to mind in terms of paying support people well.

This is unfortunate because, especially for technical folk, support interaction is the backbone of user experience.

If they could innovate here a lot of things could be overlooked. Costco + early Amazon often did this pretty well tho.

➕ show 2 replies
orwin • today at 5:27 PM

I have a counterexample, from a small company, Gong galaxy. The support is genuinely helpful, have more knowledge than anybody should expect, and is fast to respond. Even when the mistake was clearly mine they replaced the equipment I broke, and tbh, I felt like talking to the sales team each time I contacted support (and once I thought I talked to a fiberglas/epoxy expert). And I know it's not only me, a friend has had the exact same experience.

I wonder if it's because it is a small enough team that they have the correct person respond to support calls each time, but it was the best experience I ever had.

arichard123 • today at 5:38 PM

With my support experience there was a lot of inefficiency in communications. They could save a lot of time with a form that asks for some standard information.

Also I had to make videos and photos and then email them which couldn't handle large files so I had to organise my own hosting and share links.

Basically they don't seem to have thought it through yet

dk1138 • today at 5:21 PM

Not only is support not easy, it is increasingly expensive.

Products are priced and launched with an initial BOM cost and anticipated labor cost for repairs. Prior to the AI buyout, service and support was already running into real issues with the costs of labor increasing very quickly. Now, the cost of service parts has also skyrocketed. This means that the initial overhead in the cost of the machine is no longer able to cover the intended dollars put aside for repair.

This is not just happening in computers. This is everywhere. Support and service were struggling everywhere coming out of COVID, prior to the jump in component costs due to labor. Now it is a bloodbath as logistics costs have also jumped due to fuel costs. Add into this that the vast majority of manufacturers build in lower-cost labor environments, but repair generally happens locally near customers. In these situations they are facing repairs that can cost more than building a new machine.

The future of support is going to be grim for the coming years.

➕ show 1 reply
nrp • today at 5:25 PM

It is not easy. However, it is necessary to get it right regardless.

bayarearefugee • today at 5:09 PM

> Support seem easy but trust me, it isn’t.

This is true of most jobs. That doesn't mean I expect companies where the job is required to routinely fail at them, mostly because they are unwilling to invest proper resources.

Framework is not unique in having shitty support. It is an absolute epidemic, which is why companies are able to get away with it. But the fact that almost everyone sucks at it doesn't mean we shouldn't call the problem out loudly when we see it.