Peer-review response polish

The rebuttal letter is harder to write than the paper.
We help you finish both.

A revise-and-resubmit decision is the moment when papers get accepted or rejected for tone, not science. We polish the response-to-reviewer letter without weakening your defence, without conceding what you shouldn’t, and without sounding defensive about the things you should concede.

Tuned to 14 journal review conventions Citation-safe across the reply Audit log for co-authors to review
The underserved part of academic writing

Nobody trained you for this part.

You learned to write papers in your PhD. You did not learn to write rebuttal letters. Yet the rebuttal is what determines whether 18 months of work gets published or gets bounced. Reviewer #2 is irritated by something subjective in your tone. Reviewer #3 wants you to do an experiment that’s impossible. The editor’s patience for a defensive author is finite.

Generic AI writing tools approach this exactly wrong: they soften your defence into concessions, or they sharpen your concessions into combat. We’ve seen what a successful rebuttal looks like across 14 journal families. That’s what we polish to.

The four-part rebuttal

What gets accepted, structurally.

Across 1,400 accepted rebuttals in our reference corpus, four structural patterns appear in 90%+ of them. We polish each section to that pattern, with the right tone for each.

01

Cover paragraph: thank, summarise, signal

Brief, sincere thanks. One-paragraph summary of the major changes. Signal that you took the review seriously. Polished for warmth without sycophancy.

02

Per-comment table: structured response

Reviewer comment quoted verbatim → your response → exact line numbers / paragraph references in the revised manuscript. Polished for clarity, never restating the comment as your own claim.

03

Defensible disagreements

When you disagree (and you will), the language matters. We polish to “we respectfully maintain” calibrated for the journal’s norms, not generic deference. Some journals reward direct disagreement; others don’t. We know which.

04

What you cannot do, gracefully

Sometimes a reviewer asks for an experiment that’s impossible (no funding, animal-ethics constraint, the patient cohort is closed). The language that gets these accepted is specific. We polish to it.

A real example

A disagreement that got accepted.

From a Bioinformatics submission, 2025. Used with author permission.

Response to Reviewer #2, comment 4
Accepted after revision
Before · the author’s draft

We strongly disagree with Reviewer 2’s assertion that our model is overfit. As we clearly stated in Section 3.4, we ran extensive cross-validation. We are not sure why the reviewer missed this. The model is rigorously validated and the criticism is unfounded.

After · polished rebuttal

Thank you for raising the overfit concern. We agree that the original §3.4 left the validation procedure underdescribed; we’ve expanded it (lines 312-348 in the revised manuscript) to make the 5-fold stratified cross-validation explicit, including the held-out test set never seen during model selection. We respectfully maintain that the model is not overfit, but we recognise that the original presentation made this hard to verify.

Strategies Open with acknowledgement Point to specific lines, not vague sections Hold the position; concede the presentation End with humility, not capitulation
Guard rails

What the polish will never do.

Won’t weaken your defence

Generic polish tools soften “we maintain” into “we appreciate the reviewer’s perspective.” That reads as conceding. We don’t do that.

Won’t alter your line references

Every “lines 312-348” in your rebuttal is a contract with the editor. We extract these as protected entities and reinsert them verbatim.

Won’t restate the reviewer’s comment as your own

A common mistake is paraphrasing the reviewer’s words back as your finding. Editors notice. We keep the quote / response boundary visible.

Pricing

Per rebuttal, or as part of a submission cycle.

One rebuttal

$39 · one document

A single response-to-reviewer letter, up to 4,000 words. For when you just need this one polished.

  • 1 rebuttal letter up to 4,000 words
  • Tuned to the target journal’s conventions
  • Line references protected
  • Co-author-ready audit log
  • Two revision passes included
Polish one rebuttal
Most chosen

Paper + rebuttal bundle

$59 · one submission cycle

Save $9 vs buying parts ($29 paper + $39 rebuttal = $68)

The manuscript polish for the resubmitted paper, plus the rebuttal letter, polished as one cycle.

  • Manuscript polish up to 10,000 words
  • Rebuttal letter up to 4,000 words
  • Consistent voice across both documents
  • Line-reference cross-check between rebuttal and revised paper
  • One signed Disclosure Bundle covering the cycle
Start a cycle

Submission-Cycle Retainer

$149 · 120 days, full cycle

For PIs and corresponding authors who want the full pre-submission → rebuttal → cover-letter cycle managed end-to-end.

  • Pre-submission manuscript polish
  • Rebuttal letter polish, multiple rounds
  • Cover letter polish
  • 120-day workflow window
  • Audit log for the entire cycle
Start a retainer
From corresponding authors

A different kind of polish.

“Reviewer 2 was rough on us. My first draft of the rebuttal had me sounding defensive. Rewritelyapp didn’t soften the defence, it made the defence land better. The paper was accepted in the second round.”

Dr. R. Vasquez · Postdoctoral fellow, ETH Zürich · published in Bioinformatics

“The line-reference protection alone is worth the price. I’ve seen rebuttals get rejected because a polished version shifted the ‘line 312’ reference to a paragraph that no longer existed in the revised manuscript. Rewritelyapp doesn’t make that mistake structurally.”

Dr. M. Pham · Assistant Prof., NUS

Polish the document the editor reads first.

The rebuttal letter is what flips a revise-and-resubmit into an acceptance. $39 per rebuttal, $79 for the paper + rebuttal cycle.

Polish a rebuttal →