Tech editorial
A premium SaaS aesthetic. Oversized sans headlines, electric-blue accent used sparingly, generous whitespace. Reads as "well-funded, modern, default-credible."
Editorial magazine
A literary publication aesthetic. Italic serif headlines on warm cream paper, masthead with volume/issue, drop-rule columns. Reads as "thoughtful, considered, written by humans for humans."
Terminal brutalist
A developer-tool native aesthetic. Monospace headlines, near-black background, phosphor-green accent, ASCII frames, manpage layout, blinking cursor. Reads as "shipped by engineers, for engineers."
Where each direction wins or loses
| B · Tech editorial | C · Editorial magazine | D · Terminal brutalist | |
|---|---|---|---|
| Reads as | Well-funded SaaS, default-credible, modern | Considered, written by humans, "we have taste" | Shipped by engineers, for engineers, opinionated |
| Audience fit | PMs, eng-leads, mid-market buyers | Founders, researchers, design-literate buyers | Senior devs, devtool buyers, HN crowd |
| Strengths | Familiar, scales to investors, never wrong | Unmistakable, hard to confuse with anything else | Signals technical depth, matches the product |
| Risks | Forgettable — could be any YC company's site | Reads "magazine" not "product" — softer CTA pull | Polarising — non-devs may bounce; founders may read as "toy" |
| Pricing page | Reads as "real product, real prices" | Reads as "thoughtfully priced", less transactional | Reads as "no-BS pricing, terminal output" |
| Waitlist conversion | High — buyers trust this look reflexively | Medium — distinctive but the form is quieter | High among devs — they recognise their tribe |
| "AI default" risk |
Moderate — needs custom touches to escape boilerplate | Low — almost no AI site looks like this | Low — almost no AI site looks like this |
| Effort to build | Lowest — closest to off-the-shelf SaaS components | Higher — italic serif type and rule-based layout takes care | Medium — monospace is forgiving, ASCII detail takes patience |
I'd ship D — Terminal brutalist. With one caveat.
Your buyer is a developer with a stack of scrapers that keeps breaking. The product is a CLI. The output is JSON. Every signal you can send that you understand their world raises trust and shortens the path to a paid plan. Option D speaks that language fluently — the monospace, the $ prompt, the // comment eyebrows, the manpage features section. It's also the version that's hardest to mistake for a generic AI tool, which matters given how many sites with "AI agent" in the hero look exactly the same right now.
The caveat: a fully-monospace site can read as "indie / toy" to a non-developer buyer (eng managers approving the spend, finance reviewing the invoice). If we discover later that the conversion path is going through a non-dev approver, option B is a safer fallback — it's the option that nobody ever gets fired for picking.
Option C is the strongest aesthetic of the three, but it's the wrong fit for a transactional CLI tool. I'd save it for the user guide and the long-form writing — a "publication"-style essays page would look extraordinary in that voice, and we lose nothing by keeping the landing page tactical.