A startup's browser word processor became Google Docs

The writer's problem

Sharing a manuscript for comment in the mid-2000s usually meant emailing a file back and forth, with each recipient returning their own edited copy and someone left to reconcile the differences. A small startup team had built a word processor that ran inside a web browser instead of on one person's computer, so a document could stay in one place while several people looked at, and changed, the same live version. The practical problem it addressed was version drift: whose copy of the file is the current one.

What the documents show

Google's own Official Google Blog post, dated 9 March 2006, announces that the Writely team, previously a startup called Upstartle making 'a collaborative word processor that runs in a web browser,' had become 'part of Google,' noting the Writely beta had launched in August 2005. A second Google blog post, dated 11 October 2006, announces that Google had integrated Writely with Google Spreadsheets to launch 'Google Docs & Spreadsheets,' describing it as 'one place where you can create, store, share and publish your documents and spreadsheets online,' with documents kept 'always online' so collaborators could give feedback without emailing copies.

Google's current help page for Docs, retrieved 16 September 2026, describes the present-day product simply as 'an online word processor that lets you create and format documents and work with other people,' without retelling the Writely acquisition; the origin story lives in Google's own 2006 posts, while the current documentation focuses only on how to use the product today.

The editorial choice

Tracing today's always-saved, multi-editor document back to a specific 2006 acquisition and merger, rather than treating collaborative editing as though it simply always existed, is an editorial choice that gives credit accurately: a small team's browser-based word processor, not a later branding effort alone, established the core mechanism, one live document, several editors, no emailed copies, that current AI writing features now operate inside of.

What stays with the author

Which collaborators can see or edit a shared document, and when, remains a setting the document's owner controls and is responsible for. Neither the 2006 announcements nor the current help page addresses how that same always-online, multi-editor model should handle disclosure once one of the editors making changes is an AI feature rather than a person.

• Who can currently see or edit this shared document, and does that match who should?
• Is a change attributed to a named collaborator, or unclear about its source?
• Does describing a feature as new overlook a mechanism this product has had since 2006?

A startup's small team and a brief announcement post are an unglamorous origin for a tool now central to daily collaborative writing, but the mechanism they built, one always-online document, many editors, no emailed copies, is the one every later writing feature has had to fit inside.