About Paperkraft
Paperkraft is run by the people who write, test and ship documentation for software teams. The people on your first call are the people writing your pages. There is no bench, no handoff, and no account manager in between.
Our story
We spent years inside software teams watching the same thing happen. Documentation was everyone’s responsibility, which meant it was nobody’s. It got written in a rush before a launch, then quietly went out of date while support answered the same questions by hand.
The work is not hard because writing is hard. It is hard because it needs someone to read the code, sit with the support queue, decide what the reader actually needs, and then keep all of it true after the next release.
So we built a studio that does exactly that, and nothing else. We take on a small number of clients at a time, because that is the pace at which we can do this properly.
The team
Harshil Patel
Founder & CEO
5+ years in SaaS and API documentation, driving quality and structure. Improved the docs at Atlan, Appsmith, Kita and more
Harshil wrote code before he wrote documentation, which is why the repo gets read before the outline does. Five years on developer products: in-house at Atlan and Appsmith, freelance for Twilio, DigitalOcean, Neptune AI, Activeloop and Middleware. He decides what goes in the outline before anyone writes a word, and he is on every first call.
Vedant Vyas
Co-founder & COO
5+ years in delivery and operations, verification and docs automation
Vedant came from business analysis, turning messy operational data into decisions a team could act on. Delivery is his job now: scoping, coordinating with your engineers, and the pipeline that runs every code sample against a live API. If a sample fails, the page does not go out, and he signs off.
How we work
We agree the map first: what pages exist, who each one is for, and where a reader lands. A page written into the wrong structure is wasted work, however well written it is.
Every instruction is followed on a clean setup and every code sample is executed against a live API. If it does not run, the page does not go out.
Plain language for customers, precision for developers. Never writing to sound clever, and never assuming knowledge the reader has not been given yet.
Docs follow your release cycle. The value of documentation is measured a year later, when it still describes the product people are actually using.
A good fit when
Probably not a fit when
If that is where you are, we will say so on the first call rather than take the project.
A 30-minute call with Harshil. We look at your product and the docs you have today, then tell you what is worth writing first.
Book a call