The issue is nearly written. What's stopping you is the small stuff that decides everything: what the subject line says, what the preview text does next to it, and whether the whole thing holds together well enough to send to two thousand people.
Write your format down once — two lead pieces and a round-up, five fixed rubrics, an essay, bare links, whatever yours is. Every week joris researches and drafts that issue, in that shape, subject line and inbox preview included.
A newsletter is a shape your readers learn, and it isn't the same shape as anyone else's. So the structure is a line you write, not a layout we chose: the same routine, the same research, told two completely different ways below. Change the line and next week arrives in the new shape.
Three vendors moved list price inside a fortnight and none of them put out a press release. If you're on an annual commit, the number you signed is now above market.
The first cut came from the vendor with the least to lose — a 12% reduction on committed-use pricing, published as a footnote on the pricing page rather than announced.
If your renewal is inside ninety days, this is the strongest negotiating position you'll have all year. Two questions worth asking your account manager…
The flagship tier dropped to $3 per million tokens, matching last year's mid-tier on quality. Two competitors followed inside 48 hours.
If inference is a line in your COGS, a 50% cut is margin you keep or pass on.
There is no layout builder and no settings screen — you describe the issue the way you'd describe it to a person who's writing it for you. These are the pieces it understands, and they combine.
You give it your voice and a past issue up front, and every note you leave steers the next one. Over a few issues it converges on your tone — because, unlike a fresh chat, it remembers what you told it last time.
Yes. It reads the live web at draft time and attaches a source to each section, so the issue is grounded in what's current — not a model's stale memory. Keep or cut the sources.
Each draft has a one-click “Copy as Markdown” that lifts the whole issue — paste it straight into Substack, Beehiiv, Ghost, or your ESP. That is the export: joris has no webhooks or integrations, so nothing leaves the app without you pasting it.
No — it kills the blank page. You get a strong, sourced first draft on schedule; the editing, judgement and voice are yours. A first draft on time, every time — not autopilot publishing.
Yes, and that's the point of the template: you say “2 main pieces, ~250 words each, then 5 links with one line on each” and the issue arrives tiered — the leads set as leads, the tail set as a tail. Say “bare links, no blurbs” and the blurbs go. Say “5 things this week, numbered” and it's numbered. The format is a sentence you write, not a layout we picked.
Images and charts — joris writes words, so a visual is something you add after. Nothing ESP-specific either: no merge tags, no tracking links, no scheduled send. If your format needs something further out than that, a blank routine renders whatever you describe as plain markdown.
Same engine. Describe the format you publish and joris drafts to that structure on your cadence — it shapes the output to how you ship.
People who run this routine tend to add one of these within a fortnight.
A set of finished drafts each week — one platform each, hook first, only the hashtags that earn their place.
Explore →Different job, different document. Tell us the output you'd want waiting for you and we'll build the template.
Ask us →A monthly investor update. A Friday internal digest. A client-facing brief with their name on it. Anything where the writing is a habit you keep breaking — describe it and we'll design the output template.
Write your format down once — leads, briefs, round-ups, rubrics, whatever yours is. Every week the whole issue is waiting in that shape, subject line and all, for you to sharpen and send.
Start free