Talk about your next project
Sail Research executive brief

The lesson

Open a manifesto by naming the trade-off your market gets wrong, then show why the conditions behind that choice have changed before you introduce your product.

The move

Under the plain heading 'Manifesto', the first paragraph states that every AI workload trades latency against throughput and that early generative AI optimized for speed. The second paragraph turns on the claim that 'a large and growing share of AI work isn't waiting on a human at all', naming deep research, code review, security review, evals and embeddings, and concludes that 'shaving milliseconds off a single response buys you nothing.' The essay then moves into Sail's platform claims, including token budgets that go '10x further' and Sailboxes 'over 3x cheaper', and ends on 'maximizing your intelligence per dollar.' A 'Join us' hiring section, a team photo, the two founders and backer logos follow.

Why it works

  • Our readFraming the argument as a trade-off gives the reader one decision to judge, latency or throughput, before any product appears.
  • Our readListing named asynchronous use cases lets an engineer check the claim against their own workloads instead of accepting a general trend.
  • Our readPlacing the founders, team and backers after the essay puts people behind the argument without interrupting it.

What not to copy

Don't copy Sail's throughput thesis, its inference and Sailbox claims or its hiring list. Keep the order of a short manifesto: name the trade-off, show what changed, then present the product as the consequence of that shift.

More executive briefs

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.