For now, the plainest name there is — lowercase, unfussy, and honest about what it collects. It leaves the spark → shipped story to the mark and the product. A more distinctive, ownable name can come later (a crew52 workshop already has a clean candidate in the wings); this identity is built to carry one.
A note is a spark; a spark is worthless until it catches. Every other tool is a bucket that collects sparks and lets them go cold. This is the mechanism that catches the spark and turns it into a merged pull request. We don't help you listen better. We make the idea actually catch.
a lightbulb that is also a sprocket — with the spark that ships (a checkmark) lit inside
feedbackKeep clear space equal to the bulb's radius. Let it glow on dark. Use the filament-check lit in Filament orange. Use the teal variant only for “agent/active” contexts.
Don't recolor the mark purple/blue, stretch it, add a drop-shadow, place it on a busy photo without a scrim, or rebuild the wordmark in a different typeface.
one hot spark · a warm-dark canvas · teal for the machinery · green only for shipped
Always put dark Ink on the orange — never white. Ink on Filament is ≈6.6:1 (passes AA); white on Filament is 2.4:1 (fails everything). If you need light text on orange, use Ember Deep behind it. Body text is Ink on Paper (≈17:1) or Paper on Ink.
a distinctive display, a warm workhorse, and code as a first-class citizen
Wordmark, headlines, section titles. Distinctive and a little handmade — chosen precisely because it is not the default geometric sans. Weights 500–700, tight tracking.
A warm, humanist grotesque that keeps every screen legible and friendly without tipping into corporate-geometric. It carries the “we read every note” warmth into running text. The quick brown fox jumps over the lazy dog.
The one line of embed code is the product's single most persuasive object, so it's typeset like a poster. Mono also wears every status: new in progress resolved
a sharp teammate who writes good commit messages and actually likes people
| Lead with the verb and the outcome |
| Talk dev-to-dev: “paste one line,” “opens a PR,” “⌘+Enter” |
| Keep warmth human and specific — “we read every note” |
| Say exactly what happens next |
| Be generous about pricing, self-host, and data |
| “AI-powered platform,” “revolutionize,” “seamless,” “leverage” |
| Over-exclaim or fake enthusiasm (one confetti, one thank-you) |
| Bury the human under status-robot speak |
| Overpromise the agents — they “draft a PR for review” |
| Purple gradients, stock teams, “enterprise-grade” filler |
the system in motion
For developers, indie hackers, and small teams sick of duct-taping a form, a spreadsheet, and a Slack webhook — feedback is the one-paste widget whose notes close the loop into a pull request your team or coding agents ship. Unlike Formspree (collects), Canny (counts votes), or Intercom (heavy), the wedge is the loop, not the inbox.