Comparison
Sentway and Google Docs
Google Docs is hard to beat for collaborative writing, and link sharing makes it easy to get a draft in front of somebody. Sentway does something different with the finished document: it publishes it as a web page on its own address, decides who may open it, and records the reading of it as something you can query.
What Google Docs is good at
- Several people drafting and commenting in the same document
- Suggestion mode, version history and inline discussion
- Getting a draft in front of a colleague in seconds
Nothing below is a criticism of that. Sentway is shaped around a different job, and the table sets out where the two differ.
The difference in one line
A shared document is a place to work on words. A Sentway page is a published artefact with an access rule and a visitor record.
Most people who use both draft in Docs and publish through Sentway when the document is finished and going outside.
What changes when it becomes a page
A document sent as a link is read in a document viewer. A Sentway page is served as the design your AI built, which for a proposal, a pitch or a report is usually the difference between something that reads as a draft and something that reads as finished.
It also stops being anonymous. The gate can ask for an email address, verify it with a magic link, or admit only the addresses you named, and Sentway checks that on the server before any content is sent.
What your AI can read back
These are the tools your AI calls afterwards. Plan requirements are read from the live tool catalogue.
- get_analyticsFree plan
- list_visitorsPro: Visitor timelines
- get_visitor_activityPro: Visitor timelines
- get_submissionsFree plan
A realistic run
You and a colleague finish the proposal in Docs. You paste the text to your AI and ask it to build and publish a Sentway page behind verified email capture.
You send one link. Later you ask your AI whether the client opened it, and it answers from the visitor record rather than from your inbox.
Side by side
| Capability | Sentway | Google Docs |
|---|---|---|
| Primary job | Publishing a finished document as a gated web page | Writing and editing a document together |
| Authoring | Your AI, over MCP | People, in a collaborative editor |
| How the reader sees it | A designed page on its own address | A document in a viewer |
| Access control | Public, email capture, verified email, allowlist, or password | Link sharing and account permissions |
| Knowing it was read | Visits, active time and per-visitor timelines | Not what a document editor is for |
| Collecting answers | Forms, worksheets, uploads and task lists on the page | Comments, or a separate form tool |
Which one to reach for
Use Google Docs when
- The document is still being written and other people are writing it.
- You need comments, suggestions and a full edit history.
- The reader is a colleague who should be able to edit it too.
Use Sentway when
- The document is finished and going to a client or an investor.
- You want it to look like a designed page rather than a draft.
- You want to know it was opened, by whom, and for how long.
Questions people ask
- Do I have to rewrite the document?
- No. Give the text to your AI and ask it to publish it. Markdown is served with Sentway's typography template if you want the plain route, and HTML or JSX if you want the designed one.
- Can I update the page after sending the link?
- Yes. Your AI publishes a new snapshot and the same link serves it. Publishing is atomic, so no visitor sees a partly updated site.
- Is the page private by default?
- Access is whatever you set. If you choose a gate, content is never sent to a browser that has not passed it. Nothing is hidden client side.
Read next
If the job in front of you is a page that goes out to somebody and comes back with an answer, connect your AI to Sentway and ask it to publish one.