Secure Messaging.
Direct messages and channels for your team, end-to-end encrypted and built right into the workspace where you write. Messages are encrypted on your device before they leave it, so ProWriter can never read your chats. Like a team chat, but built on HIPAA-grade, 21 CFR Part 11 infrastructure.
End-to-end encrypted
Every message is encrypted with keys that live on your device, not on our servers. ProWriter cannot read your channels or your DMs, even if asked to.
Channels and DMs
Spin up channels scoped to a team or a single workspace, or message a teammate directly. Conversations sit in the same place as the documents you are working on.
Real-time
Typing indicators, presence, delivery and read receipts, and unread counts keep the conversation live across everyone's devices.
We cannot read your messages.
Keys are generated on your device. Messages are encrypted before they leave your machine. Decryption happens only on the recipient's device.
Keys on your device.
Each conversation has its own key, shared securely between members using public-key exchange. Messages are encrypted with that key and signed by the sender, so recipients can verify who sent what. Your private keys never leave your device unencrypted.
↓ encrypt with R. Franklin's public key
↓ sign with S. Cooper's identity key
In transit→ ciphertext only, TLS 1.3 + E2E layer
ProWriter servers⊘ cannot decrypt
⊘ cannot subpoena to readable text
On R. Franklin's device↓ decrypt with R. Franklin's private key
↓ verify S. Cooper's signature
→ plaintext shown
What's inside.
The messaging primitives your team expects, channels, direct messages, and live status, with end-to-end encryption underneath all of it.
- CHChannels & DMs
Create channels scoped to a whole team or a single workspace, or send a one-to-one direct message.
- E2EEnd-to-end encryption
Messages are encrypted on your device and signed by the sender. ProWriter's servers only ever hold ciphertext.
- KEYKey backup & recovery
Your private keys are protected by a PIN and a set of recovery questions, so you can restore access on a new device without exposing them.
- DEVMulti-device
Register the devices you use, and revoke one at any time so it can no longer decrypt your conversations.
- RTLive status
Typing indicators, presence, delivery and read receipts, and unread counts across the conversation.
Why not just use Slack?
- Not end-to-end encrypted by default
- Provider holds the encryption keys
- Admins and employees can access content
- Chat lives separate from where you write
- Not tied to your documents or workspace
- End-to-end encrypted by default · always
- Keys live on your device, not our servers
- ProWriter cannot read your channels
- In the same workspace as your documents
- Team and workspace channels, plus direct messages
87% less drafting and review time per CSR section.
A biopharma team developing CAR-T cell therapy for AML compared ProWriter with its in-house workflows, manual drafting and a generic AI tool, across five ICH E3 CSR sections. Each section was timed from reference gathering to hand-off for CMO sign-off, human review included.
- Median reduction in time per section vs. manual drafting
- 87%
- Median reduction in time per section vs. manual drafting
- Median time per section with ProWriter, vs. 4.25 hours manually
- 27 min
- Median time per section with ProWriter, vs. 4.25 hours manually
- Approximate reduction vs. a generic AI tool (about 1.5 hours per section)
- ~70%
- Approximate reduction vs. a generic AI tool (about 1.5 hours per section)
- Redaction needed. The generic AI tool workflow took 15 minutes to 5 hours per document.
- 0
- Redaction needed. The generic AI tool workflow took 15 minutes to 5 hours per document.
One company, five CSR sections, March 2026; four participants (the client's CMO, senior and associate medical writers, plus a ProWriter medical writer, who drafted the ProWriter versions). The client's senior medical writer ran QA/QC and the CMO signed off every version. Not a controlled trial. Redaction time is excluded, and generic AI tool times are approximate, as reported by the client's team. Customer name withheld on request.
Chat that's actually private.
Built into the workspace where the documents live.