Turn a complex product into something people can actually adopt. We don't just use documentation software; we bring the writers and developers who build the portal, and we hand it back live on your domain.
Harshil Patel, Rucha Ghalsasi and Vedant Vyas founded Paperkraft in 2026. One of the three is on your project from the first call to the last page. Work comes in two shapes: a fixed-scope project, scoped once and delivered, or a monthly retainer where your engineers drop rough notes into a channel and finished pages come back.
Harshil spent five years writing developer documentation — in-house at Atlan and Appsmith, freelance for Twilio, DigitalOcean, Neptune AI, Activeloop and Middleware. The same thing was true at all of them. Documentation belonged to the whole team, which meant it belonged to nobody, and it lost every planning meeting to work that had a deadline attached.
Tooling was never the bottleneck. Mintlify, Docusaurus and GitBook will all get a searchable docs site running in an afternoon. Deciding what goes on it is the actual work — and half of what belongs there only exists in an engineer's head, so getting it out takes someone who knows which question to ask.
So we sell the finished docs, not the hours. You hand us the product. We hand back the docs, live on your domain.
Documentation fails when it is everyone's job. On our engagements it is one named person's, from the outline through to the last page.
Every code sample runs against a live or staging API before it publishes. If it fails, the page does not go out. That rule has no exceptions.
Not a folder of drafts, and not a tool for you to learn. A docs site live on your domain that your team can extend without us.
No account manager, no handoff to a junior after you sign.

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.
Rucha spent six years in enterprise go-to-market, working with buyers who wanted a business case before a signature. She owns the commercial side here: scoping what an engagement covers, pricing it, and staying on the account after the last page ships. If you are still deciding whether we are a fit, she is who you talk to first.

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 on every one that does.
For larger engagements we bring in senior technical writers we have worked with before. They are scoped on the call and named on the invoice, never a surprise.
One call to see what you have and what it is costing you. Or start with a free score and no conversation at all.