Why We Built InkRider
We did not set out to replace Word. We set out to embrace it and make selective automation native to how professionals already write.
We've all been there: staring at a massive Word document that needs to be updated for the new quarter. The numbers have changed, the charts need replacing, and the summary text needs tweaking based on those new numbers. It's tedious, error-prone, and mostly not the work you were hired to do.
We realized that while tools for software engineers have evolved rapidly, the tools for professionals who write documents (lawyers, financial analysts, researchers, operators) have largely stayed the same: Word for the deliverable, everything else on the side.
We Love Word. We Fix What Hurts.
InkRider is not a bet against Word. It is a bet on Word: the editor people already leverage and trust for layout, redlines, and final send.
What hurts is treating the entire document as manual when only part of it should be. Tables that should track a model. Fees that should match a CSV. Sections that should appear or disappear from rules, not from Contract_v9_FINAL_Jane.docx.
We wanted to embrace that workflow and make it an order of magnitude better, not push teams into a separate render factory.
The Problem with "Generate PDF"
Many companies solve automation by removing Word from the equation. Web apps spit out a PDF. That can work for static packs.
It fails the moment someone needs a custom paragraph for one client, a layout tweak before the board meeting, or a partner edit at 11 p.m. If the artifact is frozen, Word's strength (collaborative, visual revision) is gone.
What InkRider Does Instead
We put a Jupyter-powered notebook inside the document session. You mark what should be programmatic. Everything else stays typing, thinking, negotiating.
- Stay in Word: Fetch, calculate, and insert without leaving the file your stakeholders already use.
- Automate what should repeat: Anchored cells own tables, figures, and computed prose. Re-run when data changes.
- Protect what should stay human: Drift indicators and careful anchoring so manual edits are visible, not accidentally erased.
- Keep a normal
.docx: Share, redline, and approve like any other matter.
The Bigger Idea
Not everything in your document should be code. The best documents are mixed: judgment in prose, reliability in the blocks that must match the data.
InkRider exists to hold both in one place. We're just getting started, and we can't wait to see what you build with it.