1The story
On an ESA project Carlos, our founder, found himself with a stack of ECSS documents to deliver in a few weeks, and a tool, Word, that belonged to another age. Engineers had AI and software workflows for everything else. For documentation they still had templates, e-mail and copy-paste.
So he built a pipeline: documents written in Markdown, kept in Git, turned into the deliverable PDF and a readable wiki by industry-informed AI tools. When his colleagues saw the speed and the quality of what came out, they all switched to it and made it the team's workflow.
If one team could drop the frustrating part of documentation, the whole industry could. papyro is that pipeline, made into a product, so that engineers spend their time on the work they came for: designing, testing, calculating, simulating, building.
Builds the product and keeps it true to the ECSS standards. Test engineer, system analyst and ESA-project systems engineer before papyro.
LinkedIn ›
Enterprise sales and go-to-market. Years of selling software to large organisations, now taking papyro to the companies that need it.
LinkedIn ›Advisors. Senior systems and product-assurance engineers who test every round and keep the ECSS reading honest.