OpenDocBot puts your own model connection inside Word, Excel and PowerPoint

The document already has an editing interface. OpenDocBot puts a model connection beside it, inside Word, Excel and PowerPoint, instead of asking a team to copy its work into one more separate window. The spreadsheet gets a sidekick in its task pane, while the work remains available in the Office interface that the team already uses.

The maker’s introduction describes an Office task-pane add-in that changes documents through Office.js. It connects to a configured provider or local endpoint. The useful separation is between the interface where work happens and the service answering the request; switching that service doesn’t require switching word processors.

There is a cost trap worth avoiding before anyone forwards the word free to procurement. The add-in’s free tier covers individuals and teams up to 30 users, while model usage is billed separately by the provider. An organization can remove one per-seat charge from consideration and still have a usage bill. A team still has to estimate the model usage generated by the documents it wants to process before comparing the total with another arrangement.

The license documentation makes the boundary explicit. Larger deployments require a commercial license. The project describes its license as fair-code or source-available and distinguishes it from OSI open source. Publicly readable code is useful for review, but it doesn’t dissolve a usage limit when the thirty-first person arrives.

Compatibility is another line to read before testing. The release supports Microsoft 365 desktop and web, and excludes perpetual Office 2016, 2019 and 2021. A working copy of an older Office suite does not make the add-in supported there. That matters for the office where “we already own it” is both a licensing strategy and a hardware retirement policy.

For an evaluation, the first useful task would be something with an obvious before and after on a copy of a document. A table cleanup is easier to inspect than an enthusiastic request to improve an entire financial model. The goal is learning what the tool changes, how clearly that change is presented, and whether somebody can reject a bad suggestion before it becomes tomorrow’s reference file.

OpenDocBot offers approval for modifying actions and a suggestion mode in Word and Excel; PowerPoint lacks that suggestion mode. Those controls answer different questions. An approval prompt asks whether a proposed change may run, while review comments let the person apply content changes through the document workflow. A slide deck deserves its own evaluation rather than inheriting the word processor’s result.

The maker says requests go directly from the Office machine to the configured provider. That narrows which service receives document content; it doesn’t make the chosen provider disappear from the data path. Self-hosting the interface and choosing an endpoint are separate decisions. An IT review would need to cover both without treating either word as a magic privacy stamp.

If a team already has a suitable endpoint and Microsoft 365, the appeal is being able to test the same document interface against that existing arrangement. What remains to establish is whether the changes are useful enough, and reviewable enough, for the documents that actually leave the office.

The cells still need supervision.