Talk about your next project
Motherduck content marketing

The lesson

Rewrite your team's academic paper as a plain-English web summary that states the problem, the method, the results table and the limits, then ties the work back to your product.

The move

A monospace title sits over the date, the authors and an 'Overview' that frames the idea: have the LLM write code once instead of processing every row, citing 'up to 37 points improvement on F1 score'. 'The Problem with Per-Row LLM Processing' and 'The Code Generation Approach' follow, the second with a numbered Generate, Verify, Rank list. 'What Works (and What Doesn't)' gives a benchmark table comparing PBE, per-row LLM and code gen, then admits weak spots in entity matching and error detection, with a diagram splitting code-solvable from code-not-solvable tasks. 'The Routing Vision', a sketched 'describe your transform' mockup, 'Why This Matters for MotherDuck' and an 'About' note on the workshop and GitHub code close the piece, while a side table of contents and a 'Get the full document' card with a 'View Paper' button stay alongside.

Why it works

  • Our readA section titled 'What Works (and What Doesn't)' reports the low scores next to the wins, so a technical reader is more likely to trust the strong numbers.
  • Our readOne table puts the paper's method beside two baselines on each benchmark, so a reader can compare results without opening the PDF.
  • Our readThe 'Why This Matters for MotherDuck' section comes after the findings, so the research reads as research first and connects to the product only at the end.

What not to copy

Don't copy MotherDuck's benchmarks, the routing architecture or the duck-themed design. Keep the order of problem, method, results table, honest limits and product tie-in, with a persistent table of contents and a link to the full paper.

More from Motherduck

More content marketing

Steal it for your brand.

Tell us what you want to make. We’ll talk through how to put these ideas to work for your brand.