Case study · Community platform
SalesFit — a community and company review platform
3 days
build time — studio brief, no client rounds
4 screens
feed, question board, reviews, admin
Live
open it in your browser
Challenge
Four screens with genuinely different jobs — a social feed, a question board, a statistics-heavy review section, and an operator console — had to read as one product, at a density that would not look thin next to the established review sites people already use.
Solution
A restrained design system defined before any screen was drawn: white ground, ink-grey scale, a single accent colour, applied across all four screens, with the admin console deliberately inverted to a dark sidebar so operators always know which side of the product they are on.
Results
A specification document became a clickable, deployed product in three days — enough for anyone to judge the screen structure and the visual tone with their own eyes instead of reading a description of them.
- Client
- Self-initiated studio project
- Scope
- Product UI · four screens incl. admin
- Stack
- Next.js · React · TypeScript · Tailwind
A vertical community lives or dies on information density
People researching an employer do not want atmosphere, they want the things a salary table leaves out — how leads actually arrive, how incentives are structured, what the team is like on a bad quarter. A general review site cannot hold that, and a thin vertical community looks like a placeholder. So the target was density: a curated feed of active posts on the home screen, per-category star ratings with a distribution chart on company pages, and a strengths-and-weaknesses split that gives a reader something to disagree with. The bar was simple — put it next to the mature services in the same market and it should not look like a prototype.
The admin console is part of the product, not an appendix
Community products are usually shown as the public feed and nothing else, which is exactly the half that is easy. The half that decides whether a community survives is moderation: who reviews reported posts, how company records are edited, what an operator sees when volume spikes. The console here carries that work and is styled in deliberate contrast to the public side, because an operator switching between the two should never have to check which one they are looking at.
Why three days was enough
This is a self-initiated studio project: we set the brief ourselves, then held it to production standards — a defined design system, complete screens rather than a happy path, and a deployed result on a live URL. With a client, a product of this size runs longer, because your review rounds are part of the build and your data model is not something we get to invent. What carries over is the method: see the structure and the tone as a working screen first, and judge it before anyone signs anything.
Want to see one screen of your product built this way before you commit to anything?
sww@celis.co.kr