Sample Kit #1: llmspeed
Unsolicited sample, not an endorsement. Ship Plainly made this as a portfolio example from public information only. The maker hasn't seen, asked for, or approved it, and isn't affiliated with us. Facts are from the sources below as read Oct 17, 2026 (~11:30 AM CDT).
Sources (public)
- Show HN post: https://news.ycombinator.com/item?id=50127979 ("Show HN: Llmspeed – feel how fast a local LLM runs before you buy the hardware", posted Oct 16, 2026, 11:36 PM CDT. 183 points / 60 comments at time of reading)
- Site: https://llmspeed.dev/ (title, meta description, footer text)
- Repo linked from the site: https://github.com/nicorobinreal/llmspeed
What the public pages say: You pick hardware and a model, and it "simulates tokens/sec and time-to-first-token from verified benchmarks for GPUs, Macs, and more." Measured numbers come from community benchmarks (r/LocalLLaMA, localscore.ai and more). Others are "derived from similar setups or projected from specs." It's open source.
What the HN thread asked for (paraphrased): whether the numbers match real use (one commenter reported their M2 Ultra running faster than the listed M3 Ultra estimate), harness/library versions per benchmark, multi-GPU and hybrid setups, PCIe generation, prefill speed for agentic coding, and older cards like the RX580. The maker replied, asked for model/quant details, and shipped new benchmarks during the thread.
1. Teardown: what's working, what we'd change
Working:
- The hook is a feeling, not a spec sheet: "feel how fast a local LLM runs." That's rare and sticky.
- The maker shipped fixes in the thread. That's great HN behavior.
What we'd change:
- Lead with trust, because accuracy is the #1 objection. The site already separates "measured" from "derived/projected", but that note lives in small print. Put a measured-vs-projected badge on every result and link each measured number to its source.
- Name the buyer moment. "Before you buy" is right. Make it concrete: "Thinking about a 5090, a Mac Studio, or a used 3090? Feel each one first."
- Prefill is the next headline. Agentic-coding users said time-to-first-token on long prompts matters more than output speed. If it's on the roadmap, say so.
- The crawlable page text is one sentence. The page is a JS app, so search engines and AI answer engines see little. Add a short static "How the numbers work" section and an FAQ.
2. Positioning brief
- For: people about to spend real money on local-LLM hardware (GPU, Mac, mini-PC)
- Problem in their words: "Will this actually feel fast enough, or am I buying a space heater?"
- What it replaces: scrolling r/LocalLLaMA benchmark threads, or renting a cloud GPU to try it (a commenter suggested exactly that)
- One-line promise: See and feel the tokens/sec of a model on a machine before you buy it.
- Proof points (public): benchmark sources named; open source; measured vs. projected labeled
- Objections to pre-empt: accuracy, harness differences, multi-GPU, prefill
3. Product Hunt set
Tagline options (≤60 chars):
Feel local LLM speed before you buy the hardware(48)Watch a model type at your future GPU's real speed(50)Tokens/sec you can feel, for GPUs and Macs(42)
Description (≤500 chars):
Pick a GPU or Mac and a model, and llmspeed streams text at the speed that setup gets, including time-to-first-token. Numbers come from community benchmarks (r/LocalLLaMA, localscore.ai and more). Each result is labeled measured or projected, so you know how much to trust it. It's free and open source. Built for anyone about to spend real money on local AI hardware and wondering if it'll feel fast enough.
(408 chars. The "labeled measured or projected" line assumes the badges from teardown point 1 are live. Otherwise, cut it.)
Maker first comment: outline + draft (rewrite in your own words before posting; see R5):
- Why you built it (the moment you nearly bought the wrong hardware, if true)
- How the numbers work: measured vs. projected, plus sources
- What's not modeled yet (multi-GPU, prefill on long prompts, harness differences)
- One specific ask: "What hardware/model combo should we add next?"
Draft: "Hey PH, I built llmspeed because tokens/sec numbers didn't tell me what a model would feel like. Pick hardware and a model and it types at that speed. Measured numbers come from community benchmarks. Projected ones are labeled. Not modeled yet: multi-GPU and long-prompt prefill. What combo should I add next?"
Likely questions: How accurate is this? → measured vs. projected and sources. Why is my machine faster? → harness/quant differences, plus an invite to submit a benchmark. Multi-GPU? → roadmap. Is it open source? → repo link. Will you add prefill? → honest yes/no.
4. X launch thread
- Ever wondered if a $2,000 GPU would actually feel fast running a local LLM? I built a page that shows you before you buy. 🧵 [video: two setups typing side by side]
- Pick hardware. Pick a model. llmspeed streams text at the tokens/sec and time-to-first-token that setup gets.
- Where the numbers come from: community benchmarks (r/LocalLLaMA, localscore.ai and more). If there's no measurement, it's projected and labeled that way.
- It surprised me how different "40 tok/s" and "12 tok/s" feel when you watch them. [gif]
- What it doesn't do yet: multi-GPU, long-prompt prefill. Both came up on HN and I'm working through them.
- Free and open source: [repo link]. Try it: llmspeed.dev
- What hardware + model combo should I add next? Replies get read.
(Post 4's "surprised me" line is a maker-voice placeholder. Keep it only if true.)
5. Reddit (2 posts)
A) r/LocalLLaMA. Rule summary (third-party summary, verify sidebar on the day): self-promotion is limited to about 10% of your activity, affiliations must be disclosed, and no engagement-farming (https://threadfox.vip/rules/localllama). Only post if the account participates there regularly.
- Title:
I built a page that streams text at the tok/s your hardware would get, and I need help checking the numbers - Body: "Disclosure: I made this. It's free and open source. llmspeed lets you pick a GPU/Mac + model and watch text stream at the benchmarked speed. Measured numbers come from this sub's benchmark threads and localscore.ai, and anything else is labeled projected. Where I need you: if your real numbers differ from what it shows, reply with hardware, model, quant, and backend and I'll correct it. Known gaps: multi-GPU, prefill on long prompts. [link]"
- Why it fits: it asks the sub for its expertise (benchmarks) instead of pitching.
B) r/SideProject. No sub-specific self-promo rule found; sitewide norms apply and bare links do badly (https://oneup.today/tools/reddit-self-promotion-checker/sideproject).
- Title:
I made a "feel the speed" simulator for local LLM hardware. Here's what I learned from 60 HN comments - Body: 3 short lessons from the HN feedback (accuracy labeling, prefill matters for coding agents, people want multi-GPU), then the link.
6. Show HN
Already posted. Here's what we'd keep or change for a future "major overhaul" repost (HN says minor updates usually don't qualify; https://news.ycombinator.com/showhn.html):
- The title was good: concrete and benefit-led. Keep the "before you buy" frame.
- Add a first comment from the maker on day one that explains the data sources and limits. The post had no text body, and the accuracy questions arrived before an explanation did.
7. Hero rewrite
- Headline: Feel how fast a local LLM runs before you buy the hardware.
- Subhead: Pick a GPU or Mac and a model. Watch it type at real benchmarked speed, with every number labeled measured or projected.
- CTA: Try a setup →
- Bullets: Tokens/sec and time-to-first-token · Sources on every measured number · Free and open source
8. Launch-day checklist (if doing a PH launch)
- [ ] Measured/projected badges live; static "How the numbers work" section and FAQ live
- [ ] 12:01 AM PT launch (2:01 AM CDT); first comment posted by the maker in their own words
- [ ] X thread at 8 AM CDT with the side-by-side video
- [ ] Reply to every comment within the first hours. No upvote asks anywhere.
- [ ] Log every accuracy report in a public issue so fixes are visible