I built Gachi over a weekend because I had a very narrow problem that kept annoying me.
The name comes from the Korean word for together. That felt right because the tool is not only about counting votes. It is about getting buy-in, surfacing enthusiasm, and seeing whether a group is with you before the meeting moves on.
I needed a hot take from a large group on a call.
That sounds simple, but the available solutions were either too expensive, too elaborate, too survey-ish, or too disruptive to the flow of a meeting. I did not need a full research platform. I needed to put features in front of a group, open voting one feature at a time, and see whether the room was impressed.
The Sales-Team Signal
The first use case was my sales team.
Sales teams are underused product sensors. They spend their days in demo rooms, objection handling, procurement conversations, competitor comparisons, and the long silences after a feature fails to land.
When a salesperson says a feature would wow in a demo, I listen. When the room looks at a feature and shrugs, I also listen.
That does not mean the feature is bad. Not every feature is supposed to knock someone out of a chair. Some features are table stakes. Some get a critical job done. Some matter deeply to an operations user and not at all to an executive buyer. Some are necessary scaffolding for more visible work later.
But the reaction matters. Gachi makes it visible.
The Scale Matters
Gachi's default voting scale is not a generic one-to-five satisfaction score. It is framed around sales impact:
- Not relevant
- Nice to have
- Table stakes
- Strong differentiator
- Deal maker
That language is doing product work.
It helps separate "this is useful" from "this changes the deal." It creates room for the boring-but-necessary feature. It also forces a team to admit when something we were excited about internally does not obviously matter to the buyer.
That is humbling, which is usually a sign the tool is doing something useful.
The Weekend Version
The first version had to stay small:
- Create a feature vote.
- Add feature names.
- Choose live or async voting.
- Share a participant link.
- Open one feature at a time.
- Show vote status.
- Save voting scales.
- Export the results to CSV.
That was enough to make it useful.
I did not want to build a prioritization suite. I wanted a room instrument. Something a product manager could use while the conversation was still alive.
What This Taught Me
The most useful products often start as one weirdly specific workflow.
Gachi is not trying to replace customer discovery, win-loss analysis, roadmap planning, or product strategy. It answers one question quickly:
How did the room react?
That signal is not the whole truth. But it is a real input. A feature that gets a strong sales reaction deserves a different conversation than a feature that lands flat. A feature that lands flat may still be important, but then the burden shifts to business case, strategic necessity, or operational value.
That line of thinking led directly into my next project, Tuki, which is about placing those signals into a broader prioritization system.
Gachi catches the spark. Tuki helps decide what to do with it.