This is a short post with a simple message: we are actively launching pilots, and we are in conversations with several companies about theirs. If your team builds decks for a living, we want gedonus inside your workflow next.
Why pilots, and why now
We published the motivation before we built the pitch. Our cost model of deck production found that roughly half of a pitchbook's cost is revision churn: pages rebuilt because the model moved, review that rereads a deck instead of reading a diff. Those are exactly the two parameters gedonus attacks, and a pilot is where that claim gets tested against a real team's decks instead of ours.
A pilot with us is deliberately small: a handful of people who build decks every week, running gedonus inside PowerPoint on real work, with a direct line to the team that builds it. We watch where it saves an hour and where it fails, and the roadmap follows what we see. Feedback has shaped this product since before it had a name; a pilot is that loop, formalized.
Who we're starting with
The first cohort skews toward smaller firms, and especially investment banking teams. That is pilot mechanics, not target market. A pilot lives or dies on iteration speed: we need short paths to a decision and direct access to the people who actually build the decks, and smaller teams have both by construction. IB teams add the highest deck volume and the least patience for rework, which makes them the fastest place to learn.
The product itself is aimed at finance teams of any size. If you run a PE, consulting or corporate team whose weeks disappear into decks, the same pilot applies. Larger organizations tend to join later cohorts, after the early ones have done the fast iteration for them: that is sequencing, not preference.
What we ask, and what you get
We ask for three things: real decks, honest feedback and a decision-maker in the room. In return you get generation, shape-level diffs and cited figures inside PowerPoint, and a product that still bends: what fails you in the first week shapes what we build in the second, because pilot feedback goes straight to the people building the engine.
If you want your deck-driven workflows significantly faster and less error-prone, request a demo and we will scope a pilot from there. A two-line email to info@gedonus.com works too.
