erader

5 ms·

1.
by erader 7mo ago
For my initial system I'm not building full historical service history, insurance policies, etc. because it's a serious amount of scope on top of the core value prop, which is point-in-time "is this a good quote?". When
2.
by erader 7mo ago
First, I've spent a ton of time becoming opinionated about a normalized data model that supports the product experience I'm trying to build. This applies both to the extraction (line items, warranty sections, vendors, etc.) and th
3.
by erader 7mo ago
I've been working on something like this the last few months specifically around service quote analysis (repairs, construction, hvac, auto, etc.) and it's really cool. I think LLM analysis is the way to go because the amount of co
4.
by erader 6y ago
We actually recently changed our jobs page! Here's the right link: https://jobs.lever.co/coalitioninc
5.
by erader 7y ago
Cool! Another weird thing I've noticed when feature requests are capped for customer teams, is that customer teams will "game" the system. At scale, customer facing ICs will do things to benefit them personally. It's not
6.
by erader 7y ago
As a PM that has started my career in Support/Success... I don't think I could ever advocate a strict two-request limit. Customers (and customer teams) are a non-stop firehose of feature requests. It's important for the produ
7.
by erader 9y ago
This is exactly how our team likes to operate :) Taking only 'requests' leads to a whole range of potential problems: - Feature bloat with random one-off buttons and gizmos - Product teams getting in the habit of ignoring requests
8.
by erader 9y ago
My list is too long to share, but let me give you a very simple example. On most chat platforms, the widget displays an "mail" button or something similar that allows the visitor to send the transcript to themselves for reference
9.
by erader 9y ago
I totally agree with that sentiment, but I find it hard to swallow coming from Intercom. Even as their customer, I find that they don't like to solve any problem that doesn't fit within their 'philosophy'. I've subm
10.
by erader 9y ago
Totally. It should be in the GTM checklist for every product/feature
11.
by erader 9y ago
I would hardly say it's supports job to focus on one thing at at time. Most people that reach out to support are calling about a specific question or problem. Yes therapy calls do happen. They're not terribly common, but you'
12.
by erader 9y ago
Hi there! Support manager here. I've been leading support teams for years, led support QA teams, built troubleshooting processes and worked very closely with dev teams. A lot of what I wanted to bring up doesn't apply so much to
13.
by erader 10y ago
Congrats Ryan! Glad to see another face from OP in the Bay Area
14.
by erader 10y ago
You're right, I've seen the type of Orgs in SF where 15-18/hr is the base wage and it's not healthy (for the organization or the people who are working there). For the most part, I've seen that the type of Orgs with
15.
by erader 12y ago
That's great. Yeah, I just wanted to bring forward that I use a pretty slim criteria for when I'm deciding to unfollow an account on SC. Essentially, if that account is not posting or reposting any tracks that I'm interested
16.
by erader 12y ago
Great layout and design, but honestly how is this much different than Soundcloud? The little things like the history and play queue feature are great, but what would make me want to prefer this to SC, in which I've already curated a bi
17.
by erader 12y ago
Definitely +1 on the "view all notes" options. Knowing full well that Ghostnote was intended for people like me that don't necessarily use structure for note-taking and need the context, I don't want to find my self in a
18.
by erader 12y ago
Great platform. Used this religiously while in college at Davis. Luckily, there was an active community of people updating the pages, which allowed the Wiki to essentially replace Yelp for looking up business info.