The fastest way to evaluate Office SDK is to watch one business workflow move across the editor surfaces: a brief in notes, the same work in Word, the numbers in Excel, and the result in PowerPoint. Then bring your own files to a guided session.
A sample Office surface for products that keep a document beside the work around it.
Use these pages to decide which workflow, format, and ownership boundary should be validated first.
The core editors story walks a single illustrative workflow through the notes, Word, Excel, and PowerPoint surfaces, so you see the boundaries between preview, editing, and review without installing anything.
A guided walkthrough runs your representative files through the same surfaces and pauses on the integration points your product cares about: context, callbacks, and where results land.
One workflow description, two or three representative files, and the system that owns storage and permissions. With these, the session ends at a proof-of-concept plan instead of a slide deck.
The output of a good demo is narrow: the workflow to prove first, the formats to validate, and the environment to run the proof of concept on.
An Office SDK demo is a walkthrough of one workflow across the editor surfaces, ending with a scoped proof-of-concept plan for your own files and infrastructure.
Notes, Word, Excel, and PowerPoint views appear in one continuous workflow narrative.
A workflow description, representative files, and the storage owner make the session concrete.
The session ends with the workflow, formats, and environment for the first proof of concept.
| Format | Best for | Preparation |
|---|---|---|
| Self-guided story | Understanding the surfaces at your own pace | None — open the core editors story |
| Guided session | Your files, your integration points | Workflow description and representative files |
| Proof of concept | Validating the workflow end to end | An evaluation environment and a named owner |
