Building with our design partners
Most vendor pages in this spot show you a wall of logos and a row of numbers. We cannot do that honestly, so we will not do it at all. PaperlessZen™ is in early beta. We do not have named customers, case studies, testimonials, or metrics to put in front of you yet, and we would rather tell you that plainly than dress up borrowed proof.
Here is what we can do instead. We can run a working pilot on your own documents in week one, and let you judge the product on your own paper. We are building with a small set of design partners, and we hold the same honesty standard in how we sell as we do in the product itself.
What a design partner gets
A design partner is not a beta tester we forget about. You work directly with the people building the product, and what you tell us changes what ships.
What we give a design partner
Direct access to the team building PaperlessZen, not a support queue.
Real influence on the roadmap, so the features you need move up the list.
A pilot on your own documents in week one, not a staged demo on sample data.
Honest answers about what is shipped today versus what is still planned, every time you ask.
That last point matters most. When you ask whether we can do something, you get a straight answer about whether it exists now or is on the roadmap. We will not blur the two to win a pilot. You can read more about how the product works on how it works.
What we ask in return
A design partnership only works if it runs both ways. We are honest about our side, so we are honest about yours too.
Real documents
A scoped set of your own agreements or records to pilot on, so we are solving your actual document pain and not a demo version of it.
Candid feedback
Tell us what is slow, confusing, or missing. Blunt is useful. Polite silence is not.
Patience
This is an early product. Some edges are rough, and some things you want are still ahead of us. We will always tell you which is which.
Real documents
A scoped set of your own agreements or records to pilot on, so we are solving your actual document pain and not a demo version of it.
Candid feedback
Tell us what is slow, confusing, or missing. Blunt is useful. Polite silence is not.
Patience
This is an early product. Some edges are rough, and some things you want are still ahead of us. We will always tell you which is which.
None of this locks you in. A pilot runs on a scoped set of your documents, and if the product is not right for you, you can walk away and we return or delete what you gave us. You can read exactly how a pilot works on the pilot page.
Who we build with
We are clear about who we are building for, and we are careful not to dress our intentions up as a client list.
We started with advancement teams at research universities, because the pain there is the sharpest we know. A single gift agreement can create obligations that run for decades and outlive everyone who negotiated it, and those promises get honored from memory when the document is unsearchable. From that starting point, we are building outward to regional universities, community college foundations, and nonprofits with the same problem at a smaller scale.
To be precise about it: these are the partners we want to work with and are building for. They are not existing customers we are quietly claiming. When we can point you to a real institution using PaperlessZen, and that institution is comfortable being named, we will. Until then we will not imply one exists.
The way in is the same for all of them. You bring a pilot box, a scoped set of your own documents, and we make it searchable while you watch. It is the method we describe on the pilot page, and it is how a design partnership starts.
We would rather earn your trust on your own documents than borrow it from someone else's logo.
The usual vendor proof, and ours
There is a standard way software gets sold, and there is the way we would want to be sold to. We chose the second one.
The usual vendor proof
A wall of logos you cannot verify from the outside
A staged demo on tidy sample data that is not your data
Numbers and quotes chosen to impress, not to inform
Our proof
A pilot on your own documents, in week one
Straight answers about what is shipped versus planned
Nothing invented, so there is nothing you have to take on faith
This is the same stance we take across the company. You can read more about what we believe and why on about PaperlessZen.
Become an early partner
If early appeals to you, there are three ways in, from lightest to fullest.
- Join the early access list if you want to stay close and decide later.
- Book a demo if you want to talk it through with the team first.
- Start with a pilot box if you are ready to see it work on your own documents.
Whichever you choose, you will get honest answers and a product you helped shape. That is the whole offer, and we would rather keep it small and true than large and borrowed.
Frequently asked questions
Do you have case studies, customer references, or logos to show us?
Not yet, and we will not manufacture them. PaperlessZen is in early beta and we are building with a small set of design partners. We would rather run a pilot on your own documents than point you at proof you cannot verify. As we grow and partners are comfortable being named, we can arrange a conversation. We will not invent one before then.
What does being a design partner actually involve?
You get direct access to the team, real influence on the roadmap, and a pilot on your own documents in week one. In return we ask for real documents to work on, candid feedback, and patience with an early product. It is a mutual arrangement, not a sales funnel.
We are not a research university. Are you only building for them?
We started with advancement teams at research universities because their document pain is the sharpest we know. We are building outward from there to regionals, community college foundations, and nonprofits. If your team has decades of paper and questions you cannot answer fast enough, we want to hear from you.
Is our pilot data safe, and can we walk away?
Yes. A pilot runs on a scoped set of your documents, every action is logged, and access is role-based. If the product is not right for you, you can walk away and we return or delete your pilot documents. Nothing about being early locks you in.
Why would we take a risk on a product this early?
Because early is when your input shapes what gets built. A design partner today has more say in the roadmap than a customer will in a year. And the pilot is on your own documents, so you judge it on your own paper before you commit to anything.