3
16 Comments

I built a free e-signature tool that doesn't make you create an account — would love feedback

Hey IH,

I built Docracy after getting frustrated sending a one-off NDA and hitting a wall of "create an account," "start your free trial," "add your payment method" — for something I needed to sign once.

What it does: upload a PDF (or start from a free template), drag on signature/date fields, send it. Whoever you send it to doesn't need an account either — they just click the link and sign. The whole thing disappears after 9 days, since most one-off agreements don't need to live forever in someone's dashboard.

It's genuinely free for the basic flow — no card, no trial countdown. Paid tier exists for people who need more (unlimited signers, reusable templates, team accounts, white-label, Zapier/MCP automation) but the core "sign this one thing" use case stays free and always will.

Where it's at right now: fully built and live, but zero real users so far — you're some of the first people hearing about it. I've been heads-down on the product (free template library, AI contract tools, Zapier + MCP integrations for Claude/ChatGPT) and haven't done much on the "actually tell people" side yet, which is honestly the harder part for me.

Try it: [docracy.io] — genuinely curious whether the no-signup angle actually matters to people, or whether I'm solving a problem only I have. If you try it, I'd love to know: did it feel faster than whatever you used last time, and what almost made you bounce?

posted toAvatar for product Docracy
Docracy
  1. 1

    one thing separate from the positioning debate: if the document is gone after 9 days, what proves the signature later? for a real NDA/contract, "we signed this" needs to survive a dispute months out, even for a one-off user who'll never come back. worth keeping a signing certificate forever even on the free tier: doc hash, timestamp, signer IP, not the content itself. costs almost nothing to store and it's the difference between "we have a tool" and "we have evidence."

    1. 1

      Your document is not gone because it is in your inbox. You can also connect it to Box, Google, or OneDrive. So it is not gone; it is with you.

  2. 1

    Re: "am I solving a problem only I have" - I built a browser extension with the same no-account, no-server design (in my case zero network calls at all, not just no signup), and the honest answer from my side is that the no-account part isn't the pitch, it's a precondition for the pitch. Nobody has emailed me saying "I chose you because you don't require signup." But it removes the one thing that would've made me personally bounce off a "sign a document once" tool - three sign-up screens for a five-minute task is a real, if silent, reason people never even start.

    Alfie's point about the bridge to power users is the sharper version of this: the no-account path is what gets someone to finish their first document, the account-requiring stuff (templates, audit trail, teams) is what gets them to come back. Different jobs, both real.

    1. 1

      Thanks for your help and information!

  3. 1

    I also tried to make an app using different tools which help to play simple games.
    Can anybody check it out and guide me with their feedback?
    i will share tool link if any supportive individuals are here?

      1. 1

        im unable to share the link

        how can i share with you?

  4. 1

    Alfie nailed the positioning tension here. The "no signup" angle is genuinely useful for 1-off signings, but real estate agents and contract managers don't think "I need no-account signing" - they think "I need to send 20 contracts safely this month."

    The bridge is to let casual users discover the power features live instead of dead-ending them at launch. When someone finishes their first signing, that's the moment to reveal "save templates, bulk send, audit trail, white-label" without friction - not promote it upfront where it confuses the core positioning.

    The 9-day expiry is actually smart here - it filters for users who genuinely only need it once. But for repeat users (your paid tier), that becomes friction. Two different flows solving for two different user types, which is hard to communicate as one product at launch.

  5. 1

    "Free, no-signup" is perfect for the person who needs one signature a year. But the buyer who actually pays for e-signature tools is the real estate agent who sends 20 contracts a month, needs templates, audit trails, and client branding. Your positioning trains the high-volume buyer to think "this is for casual use, not my business" — and they close the tab before they discover you actually have those features.

  6. 1

    The 9-day disappearance is actually the part I’m most curious about.

    What made you decide the one-off user wants the document gone afterward, rather than simply wanting the signing process to require no ongoing account?

    1. 1

      Very easy: if it is not signed within 9 days, it will normally never be signed. In the paid version, you can send a lot more reminders...

      1. 1

        That makes sense. Have you seen enough usage yet to know whether most unsigned documents genuinely become irrelevant after those 9 days, or is that cutoff still based mainly on your assumption?

        1. 1

          I have been working in the e-signature field for nearly 10 years. In the paid version, you have 90 days, and in the free version, 9 days. My experience, I have analysed lots of signature processes in the last 10 years, 9 days are enough and if it is important, then people are also willing to a paid subscription.

          1. 1

            That background makes the 9-day choice much more interesting. I’d like to continue the conversation outside the thread. What’s the best email to reach you on?

            1. 1

              You can reach me at founder@chasa. io — happy to continue the conversation.

              1. 1

                Thanks! I’ve just sent it over.

                Looking forward to hearing your thoughts whenever you have a chance.