You can always tell. The rhythm flattens, every paragraph resolves into the same tidy takeaway, and nothing in it could only have been written by one person. Which is why most writers who try it end up rewriting the draft completely and deciding the whole thing costs more than it saves.
Generating prose is the one part you shouldn't outsource. What's worth handing over is the work that eats the day. Learning a subject well enough to say something true. Finding sources that hold up. Turning one piece into the five formats it owes. Strawberry is a browser, so it can research across real sites and the tools you're signed into, and learn your voice from what you've already published.
What Strawberry can help you do
Not sure where to start? Tell your companion what you are working on and it can suggest the most useful first step. See the skill
Know the subject
Writing that falls flat usually fails on substance rather than style. The author read three summaries, found nothing anyone else had missed, and wrote around the gap.
Strawberry can follow a subject past the first page of results, into documentation, filings, forums, archives, and the logged-in tools you already pay for. What you want out of that isn't coverage. It's the one detail worth building a piece around: the contradiction, the number smaller than everyone assumes, the thing practitioners say that the marketing doesn't.
Map an unfamiliar subject
See the main positions, who is worth reading, and which arguments are already exhausted.
Research one organization
Separate what a company claims about itself from what is independently supported.
Sound like yourself
Give your companion two or three pieces you're happy with and it works from your actual voice. Your sentence rhythm, how much you qualify, whether you use humor, what you refuse to say. That's a different exercise from asking for a tone, and it's the difference between a draft you edit and a draft you bin.
It won't invent a quotation, a statistic, or a person to make a paragraph land. For anything going out under your own name, that matters more than any amount of fluency.
Make one piece go further
A finished piece usually owes several more: the newsletter version, the thread, the talk, the client-facing one-pager. Most of that work is mechanical, which is exactly why it gets done badly or not at all.
Adapt it across channels
Rework the same argument for the places you actually publish, without compressing it into something generic.
Turn it into something presented
Move from a written argument to a talk or deck when the audience needs to watch rather than read.
Decide what is next
The hardest editorial question is what to make next, and most people answer it from whatever they read that morning. A plan built from what's actually worked, and what you haven't covered yet, beats that.
Keep what works
Voice is the part worth protecting. Once your companion has it right, that calibration can be saved along with the sources you trust, the structure you tend to use, and how blunt you want the feedback. The next piece starts from there rather than from a cold start.
If you write with an editor, a team, or a client, the accepted voice and standards can be shared so the work stays recognisably yours no matter who briefs it.