Contact

Show me where it breaks.

Send the product, the reader, and the page that is making people guess. If the brief asks for polished words before anyone understands the behavior, I'll say so.

// Twitter / X
@ninadwrites
// Response Time
Within 24 hours

// What to expect on the call

We'll identify the reader decision the page needs to support.
I'll ask what evidence, product access, and engineering review exist.
I'll tell you if the brief is aimed at the wrong problem.
The call is 30 minutes. I won't waste your time.
// Book a Call
30-minute intro call

Tell me what the product does, who is stuck, and what the existing content gets wrong. That is enough for a useful first conversation.

Open Booking Calendar →
// I work best with
DevTools companies whose audience is developers
Technical teams willing to let the writer inspect the product
Teams willing to trade empty volume for tested work
Founders who want a real argument, not consensus dressed as insight