The AI-era Office

Write a sentence.Get a deck, doc, or sheet — as a link.

Stop exporting .pptx and chasing 'can you re-send it?'Deck, doc, sheet — all live web pages. Send one link. Nothing to download, nothing to install.

plain.app/d/client-pitch
live preview
Client Pitch · 03 / 18

Why now is the right moment

  • The inflection point has arrived
  • Our advantage is unique
  • The window closes in six months
confidential · client meeting
deckdocsheet
Try it live · no signup
0/200

Demo · 5 free / day · Full power in the workspace

INTRO · NO. 02

See Plain in two minutes.

Deck, doc, and sheet — all shipped as shareable web pages. Markdown is the source, a link is the product. Watch the full loop in the video: one prompt in, one link out.

1080p · subtitled · Watch on YouTube
THREE FORMS · NO. 04

Three web pages — not three files.

Office bundled them for 40 years, but they are three fundamentally different web forms. File becomes web — still three jobs.

No. 01

Deck

Scrolling slideshow · Persuasion
dramatic arc

A viewpoint as a story, page by page. Long hero, embedded media, presentation mode — .pptx never can.

How you know it worksDecisions changed

AI writing .pptx ≠ telling a story. Form is nothing if it doesn't move people.

No. 02

Doc

Long-form with media · Explanation

Markdown source, web render. Inline flowcharts, tables, video, read start-to-finish.

How you know it worksKnowledge transferred

Blocks suit composition, not long-form. Plain returns long-form to itself.

No. 03

Sheet

Data dashboard · Computation
C2
=IF(B2<0.6,flag)

Not cells — a data story panel. KPIs, time series, funnels, SQL, all around one question.

How you know it worksInsight discovered

Collab tables pulled Excel toward a database, lost the reasoning. Plain shows "why this number."

Your analysis was always one — deck for client, doc for team, sheet for what-if.

ONE SOURCE · NO. 05

One source, three web pages. Edit anywhere — the link updates.

AI writes Markdown. Plain renders three pages. Every edit is a structured patch — diffable, rollback-able.

01SOURCE

Markdown is the source

AI is great at structured text. You can read and edit it too.

# 季度复盘
## Q2 看了三件事
02PATCH

JSON-Patch is the edit

Every edit = one RFC 6902 patch — diffable, rollback-able.

[{"op":"replace",
 "path":"/title",
 "value":"Q3 计划"}]
03OUTPUT

Web is the artifact

Ship a link, not a file. One URL, always the latest.

inplain.app/s/abc123

AI is the brain, Plain is the hands. You write. I ship a link.

EVERY SURFACE · NO. 06

One link, four surfaces.

Browser writes. Desktop edits. CLI batches. AI agents call in. One source.

Web

Open inplain.app · zero install · main entry

inplain.app/app

Desktop

Tauri · offline edits · local archive · macOS / Windows

Plain.app

CLI

Batch generate / export · drop into CI/CD

$ plain deck generate

MCP

Claude Code / Cursor connect · let your AI use Plain

claude mcp add plain

// All four surfaces share the same documents.source

PROJECT · NO. 07

One project, many files, one conversation.

A project is context: one client, one launch. The deck / doc / sheet inside share brand, assets, chat.

PROJECTS
  • Pancake client pitch
  • Q2 retro
  • GTM plan
Pancake client pitch3 files
Client roadshow v3
deck
Strategy memo
doc
Conversion funnel dashboard
sheet
PROJECT CHAT
Translate last week's pitch to Chinese, keep all numbers
Done. I'd also swap the sheet headers to Chinese to match
Sure. Add one more page for Q3 KPIs while you're at it
// Project chat is independent from workspace chat

Files share brand / asset / chat — change theme, all three switch.

You don't open "report v3.pptx." You finish "Pancake pitch."

Archive project = one click archives everything, history restorable.

OFFICE FALLBACK · NO. 08

Link is the artifact. But when the recipient lives in Office, we have a clean fallback.

The artifact is a link. But moments hit: client systems block externals, boss needs print, recipient only takes PowerPoint. Each degrades cleanly into .pptx / .docx / .xlsx — layout intact, fonts crisp.

Decks

.pptx
  • Fonts and sizes preserved; opens natively in PowerPoint / Keynote / WPS
  • Charts stay editable, not screenshots
  • Tables stay tables, not flattened images
Download sample

Docs

.docx
  • Heading hierarchy preserved; works in Word's outline view
  • Code blocks, quotes, lists keep their structure
  • Embedded diagrams convert to high-res images
Download sample

Sheets

.xlsx
  • Panels split into separate sheets, structure clear
  • Formulas preserved; recipients can keep computing
  • Charts re-render, not fuzzy screenshots
Download sample
Honest degradation list
  • Scroll-based motion is lost
  • Embedded video becomes a link
  • Real-time collab goes offline
Why switch

They make slides. Plain makes the work.

Plain.AI deck toolsOffice + email
What you sendOne link, always the latestSlides you still exportFiles you re-send
Deck, doc & sheetAll three, one sourceDecks mainlyThree separate apps
Edit once → everything updates
Opens on any deviceOften breaks
Office export (.pptx / .docx / .xlsx)VariesNative
Markdown source · git-diffable
FAQ · NO. 09

Frequently asked

Writing one is easy. The hard part is what comes after. Versioning? Changing one thing without breaking others? The client can't open it? Plain picks up where AI ends — your work lives in a project, you share a link instead of a file, with comments / version history / rollback built in. One source grows into deck / doc / sheet web pages.
Because a link lives on the server — every open shows the latest. A file lives on one machine and ends up as v8-final-FINAL2.pptx. Links don't break on mobile / tablet / print. Files lose fonts and shift layout. When the recipient is still on Office, we provide .pptx/.docx/.xlsx fallbacks — but the artifact is always the link.
Drag them in. Plain takes over structure / styles / images, then you can edit in Plain to share a link or export back to .pptx/.docx. No starting from scratch.
Yes. We run compatibility tests across common styles before every release. Files generate in native Office format, open cleanly in PowerPoint / Keynote / WPS. We accept the degradations (animations gone, embeds gone) but keep structure + text + main visuals readable.
Yes. npm i -g @inplain/cli — then `plain deck generate` to create, `plain export` to ship .pptx/html. Drop it into CI/CD. CLI shares the same documents.source as web; artifacts are identical.
Yes. Plain ships an MCP server. Add it in Claude Code / Cursor and your AI can call Plain directly to generate / edit deck / doc / sheet. Built for agent workflows that need document generation.
Yes. Tauri-based desktop for macOS / Windows. Shares the same UI / data with web but supports offline editing and local archive.
A project is a context container — one client, one topic, one launch. The deck / doc / sheet inside share brand / asset / chat history. You don't dig through folders; you work inside the project. Archive project = one-click archive everything, history restorable.
Yes. Multiple editors in the same project, with comments and rollback. Share links for read-only access by non-users. Team plan priced per seat.
Free gives you 200 credits per month, enough for daily use. Pro $20/mo (1,200 credits), Max $100/mo (7,500 credits with priority access to the strongest model), Team $25/seat/mo (1,500 credits per seat). Need more? Top up any amount, credits never expire. See the Pricing page for details.