Why We Built Papyrus Doc
If you've ever priced out e-signature platforms for a small team, you've probably noticed a pattern. Per-envelope fees that make costs hard to predict. API access locked behind the most expensive tier. Free plans so limited they barely work as a proof of concept.
We kept running into this on client projects. The signing workflow itself is straightforward, but the pricing around it made it hard to recommend anything without a big budget attached.
So we built Papyrus Doc — an e-signature platform with flat monthly pricing, generous document allowances, and API access on every plan.
Three Plans, Same Core Features
Every Papyrus Doc plan includes templates, API access, webhooks, and team workspaces. The plans differ in document volume and team size:
Free — 5 documents per month, 1 user. No credit card required.
Pro — $16/mo (annual). 750 documents per year.
Business — $39/mo (annual). 3,000 documents per year with advanced security features.
No per-envelope fees, no per-user pricing on Pro, no surprise overages.
API Access on Every Plan
This was the biggest reason we built Papyrus Doc. Most platforms treat API access as a premium feature, something you unlock after a sales call or by upgrading to an enterprise tier.
Every Papyrus Doc plan includes API access, including the free tier. The API makes it easy to send documents from pre-defined templates, check signing status, and receive webhook notifications when documents are completed. If you have a workflow that needs signatures, you can integrate it without upgrading to a higher plan.
How It Works
The signing workflow is three steps:
Create — Upload a PDF or use a reusable template. Drag and drop to place signature fields, date fields, and text fields where you need them.
Send — Add signers and choose parallel or sequential signing order. Recipients get an email with a secure signing link.
Sign — Recipients draw or type their signature in the browser. No account needed. Once everyone has signed, you get a finalized PDF with a full audit trail.
For documents you send repeatedly, the template system lets you define fields and roles once. After that, sending a new document is just assigning recipients to roles — through the UI or the API.
Try It Out
Papyrus Doc is live at papyrusdoc.com. The free plan includes 5 documents per month with API access, so you can try the full workflow without committing to anything.
Isaac Earl
// Lead DeveloperRelated Posts
-
Development Building Multi-Tenant SaaS with Laravel and SpatieA practical guide to building multi-tenant SaaS applications where users belong to multiple organizations, using Laravel and Spatie multitenancy package with subdomain-based routing.
Read More -
Development Stateless Social Authentication with SocialiteLearn how to use Laravel Socialite for stateless social authentication in APIs, ideal for SPAs or mobile apps that don’t rely on sessions.
Read More
Don't let your project stall
We respond within one business day. No spam.