Slidewright

What the company appears to be: Slidewright is a self-reported open-source tool built by one developer (Michael Gritzbach) that uses AI (specifically OpenAI Codex) to generate editable PowerPoint presentations from ideas, briefs, or templates. It claims to produce native, semantic PowerPoint objects with strong formatting integrity and editability.

What changed: The project was submitted as part of the OpenAI 2026 hackathon. It is described as a proof-of-concept tool that has achieved several internal test milestones but lacks any external validation or commercial traction.

Single most important open question: Is there evidence that Slidewright’s approach to PowerPoint generation solves real problems for users beyond the author's own testing environment?

The description states that Slidewright is an open-source Codex skill and plugin that turns an idea, brief, visual reference, or controlled template edit into a native, editable PowerPoint file.

It claims to:

• Preserve text as native runs with formatting (bold, italic, color, size).
• Maintain semantic objects like shapes, groups, charts, tables, connectors, notes, and reading order.
• Retain existing decks' fonts, colors, masters, layouts, placeholders, logos, spacing, and recurring chrome.
• Use symmetric margins and conventional whole-point typography.
• Prevent issues like clipping, font changes, or layout collapse after editing.
• Include an optional executive-review mode with partner comments.
• Be built using GitHub Actions, Node.js, OOXML, OpenAI Codex, PowerPoint, and Python.

Inference: The tool appears to be a code-based compiler that translates user input into structured PowerPoint files using AI and deterministic pipelines. It is not a SaaS product or hosted service but rather an open-source developer tool.

The author states:

• Slidewright began with the question: “can Codex generate the editable artifact with the same discipline we expect from production code?”
• The project positions itself as solving problems with PowerPoint editing, particularly around formatting integrity and editability.
• It emphasizes that it is not about image generation but about document integrity and semantic fidelity.

Inference: The positioning evolved from a hackathon experiment into a tool focused on editable PowerPoint output, aiming to improve upon common issues in PPTX workflows (e.g., broken layouts, font inconsistencies, poor editability). It is not positioned as a replacement for PowerPoint but as a way to generate better PowerPoint files.

The description does not name specific customers or personas. However, it implies:

• Developers or technical teams who work with AI tools and want to integrate them into workflows.
• Presenters or consultants who rely heavily on PowerPoint and seek more reliable generation methods.
• Users who value editability over visual polish.

Inference: The ICP likely includes technical users, such as developers, consultants, or content creators working in environments where PowerPoint is used extensively but with poor editability outcomes. There is no evidence of a defined buyer persona beyond the author’s own use case.

The description states:

• Slidewright is an open-source tool.
• It includes code and installation instructions on GitHub.
• No pricing, licensing model, or monetization strategy are mentioned.

Inference: There is no evidence of a business model or pricing structure. The tool is presented as open source, suggesting no direct revenue path at this stage.

The author states:

• Built with GitHub Actions, Node.js, OOXML, OpenAI Codex, PowerPoint, Python.
• Uses a semantic specification, compiler, and linting pipeline.
• Implements OOXML inspection, visual comparison, and PowerPoint save/reopen tests.
• Public CI reproduces builds on clean Windows, macOS, and Linux hosts.
• Has 318/318 release tests and 15/15 destructive-control tests.
• Includes native font embedding and two real PowerPoint save/reopen cycles.

Inference: The tool is built with a strong technical foundation focused on deterministic output, format integrity, and testability. It uses AI as a core component but emphasizes code-based control over the generation process.

The description states:

• 318/318 release tests and 15/15 destructive-control tests.
• 26/26 repair-free PowerPoint fixtures plus 13/13 repair controls.
• Four licensed template families, 39 slides, 542 artifact receipts, and 195 hash-bound full-size reviews.
• Native font embedding and two real PowerPoint save/reopen cycles with exact visible-style retention.
• Lossless structural ingestion for four licensed decks covering master/layout/theme hierarchy, text runs, tables, charts, diagrams, notes, and recursive reading order.
• 11/11 public CI jobs passing on the exact release commit.
• 54 of 58 deliberately strict product and complaint-derived goals currently proven.

Inference: The tool has undergone extensive internal testing and validation. However, there is no evidence of external adoption, customer feedback, or real-world usage beyond the author’s own environment. It is a proof-of-concept with strong engineering rigor but no commercial traction.

The description does not mention competitors or direct market positioning. It implies that the tool addresses issues in current PowerPoint workflows, particularly around:

• Editability.
• Formatting integrity.
• AI-based generation of PPTX files.

Inference: The competitive context is not clearly defined. It may compete with tools like Canva, Google Slides, or other AI-powered presentation generators, but no direct comparison or market analysis is provided.

• No commercial traction or revenue: The tool is open-source and has no evidence of customer adoption.
• Single-person team: Only one developer (Michael Gritzbach) is involved in the project.
• Limited external validation: All claims are self-reported; there is no third-party verification or user feedback.
• Unclear path to monetization: No business model or pricing strategy is evident.
• Niche use case: The tool targets a specific, narrow problem (editable PowerPoint generation) and may not scale beyond its core audience.

1. What specific problems in current PowerPoint workflows does Slidewright solve that users are currently unable to address?
2. How is the tool being used outside of internal testing? Are there any early adopters or feedback from users?
3. What is the long-term vision for Slidewright beyond the hackathon project? Is there a plan to build a commercial product or service?
4. How does Slidewright handle compatibility with different versions of PowerPoint or other platforms (e.g., Google Slides, Keynote)?
5. Are there any plans to monetize or commercialize this tool, and if so, how?