We built Lucid Signing because we kept running into the same wall on client projects. A business needs signatures on eight documents a month. Every platform on the market either charges per envelope, makes the signer create an account, or both, and neither is defensible at that volume.
One: the free plan has to be a real plan
A fourteen-day trial tells you nothing about whether people will use a thing, because everybody behaves differently when a clock is running. Three documents a month, forever, unwatermarked, tells you a great deal: the people who stay are people the product genuinely fits, and the people who upgrade do it because they outgrew it rather than because they were pushed.
Two: the person you are not charging matters most
The signer never pays us and never signs up, and they are the whole product. If signing is awkward on a phone, the sender stops sending. So the signing experience got the disproportionate share of the design work: one link, no account, no app, works on whatever browser is already open.
The user with no account and no invoice is usually the one who decides whether the paying user renews.
Three: security has to be in the database
Access control that lives in the interface is decoration. Ours is row-level security in Postgres, so a query for a document you are not party to returns nothing regardless of what the application layer believes. It is more work up front and it is the only version that survives a mistake in the application code.
What it changed about client work
Running our own product means we operate what we build: the on-call, the migrations, the bill at the end of the month. Everything we now recommend to clients about hosting, backups and cost control is something we do to ourselves first, which is a different kind of confidence to having read about it.