They have spent massive marketing dollars to create a trusted brand. They have even gone to court and won cases creating legal precedent their software can be trusted in contract law.
If your a CFO or company legal department, are your really going to use another service just because it saves you $2-3 per month … but from an unknown company?
(I’m not hating on the product. Just pointing out the dynamics at play)
Absolutely this. This is a business of trust, which means you need certifications, marketing presence, squeaky clean legal documents, and brand recognition before you get anywhere with your customers.
That doesn't mean it's impossible to do, but recognize that technical features that are fun to build are maybe 20% of that journey.
I don't get what the AI agent is for - the way I know of DocuSign is to use it to legally effectively sign documents such as contracts. Those would typically be prepared by (human) legal experts. I'm wondering what niche has documents that are critical enough that they need legally effective signing but uncritical enough that you can trust an unaccountable AI agent with drafting them?
> the way I know of DocuSign is to use it to legally effectively sign documents such as contracts.
Now imagine that, but with AI. Now you can ask an LLM to expand on the main points in the contract. The person you’re sending it to can ask an LLM to summarize that expansion. You both can arrive at a different conclusions because after all, a break in communication is eventually going to happen between any 2 parties. Might as well super charge it.
Looking at your privacy policy - it appears that your statements are about protecting the account info (the firm or person who has signed up for Signly)
What about protecting the form data itself? If I were to use this in a medical scenario, are you HIPAA compliant? Or if the form included a social security number and date of birth - what steps are you taking to protect the person filling out the form against identity theft?
I presume it’s supposed to be “sign-ally” or something to that effect? Really strange choice for a b2b app imo. Seems like it’d be better for an iPhone app name than anything.
I also came here to say this. If you really want to compete with Docusign, you’d probably benefit from a name that decision makers can obviously pronounce. It seems silly, but it will be a barrier for some.
The current problems we're having are DS covering up adjacent text with their input box. You can specify a starting width, which helps sometimes. But they have a minimum font size of 9pt and minimum input box height of 22px and we often need to go smaller.
Why is this important to us? We're filling in official state forms and we cannot change them in any noticeable way to give their input box more room. Some states have crammed everything together and we have to work around their poor design as best we can.
That DS provides traceability, viewing history, and cryptographic signatures is nice for us, and may help one day in case of a lawsuit. It's not a must-have for us, but likely was important for them given they originated in the real-estate document area (lots of disputes there, I'm guessing)
What could help us is making the input box translucent, or hiding it until the user navigates to it (perhaps leave a small marker so they know they have to provide a value there).
So far as the templating, we've got that solved with Fluent (née Autotag). Most of their competitors are doing simple word replacement (mail-merge) but they allow us to add logic like if-else and select-case to our templates. You should look into doing that too.
Sounds interesting! Those tools preserve the original document's style — do the documents you sign follow a specific legal format or design that needs to be maintained?
I currently use GrabSign, which doesn't have a great UI tbh, but I've never tried docusign.
I'm not sure I understand your comparison to traditional process.
It looks like you are not taking a PDF as an input. So I am supposed to write my documents in sgnly? Curly braces makes sense to engineers, I don't think the average person really understands that (though I could be wrong).
Why is what you are doing 10x better than docusign?
"Up and running within a week?" I was getting documents signed with grabsign within 20 mintues. But maybe I'm not the target user, but then who is?
Maybe I'm confused about what Docusign does, and I know they do more than just manage signatures, but how do most people know/use them?
Also the sgnly domain, though nice and short, doesn't give me a lot of confidence for a b2b app.
Maybe I’m just not your target customer but I honestly have no idea why I would want to replace DocuSign or how your tool is different. You may want to clarify your positioning.
I don’t really understand what this is from the landing page. Is it a signature tool where you’re signing an arbitrary existing document? If so, I need to know whether it’s legally appropriate for my situation, and that means eIDAS for me.
Alternatively, is it a tool to manage writing contracts and other documents, and soliciting legally binding signatures? If so, I need to understand it more.
SaaS are now adding e-sigs as a feature (Box, Google, etc.) Some workflows still need DS but it’s fewer and fewer. Box, I think, can be CFR11 compliant.
The idea goes as follows: We take any existing signed document, remove the variables of your choice, and create a new, identical document template. You can then use it for signature purposes.
Additionally, we automatically fill in repetitive information using the data we collect previously.
You can't have an AI that fills in things automatically and then expect a signature on that document to be legally binding.
As soon as you modify the content or suggest what someone fills in, you are no longer a disinterested third party. Ask any notary or go look at DocuSign, they explicitly won't advise you on how to complete a form aside from basic things like making sure a field isn't blank or contains a number and not a string.
* You aren't clear about the goal. The middle of your screen says "Redefining Document Signing" in smaller font but in a blue pill. Immediately under that in large font it says "Turn PDFs toContract Templates in seconds". Which is it? Those are not the same thing.
* Then there's "5x faster document workflows — AI that auto-fills, explains, and builds reusable templates in seconds." Which is yet another thing that is discreet from the above.
* If you're going to have features based on AI, you need to be very clear and very loud about how and to what extent your any AI feature has access to my data. I need a super-charged privacy policy there, and I want you to be terrified of the consequences of violating your promises.
* "Get Up and Running Within A Week" That's forever to sign a document, which I think is the central purpose of this service?
* Your comparison slider between the traditional process and yours is comparing two very different things: what looks like a government form and an email. I can't take anything away from that.
* At the top of the page there's a "give us your email for early access" box, but at the bottom there's a whole form. What do I get from one that I don't get from the other?
Basically, your site isn't clear about the focus of this service. I would guess the template things are the primary use-case you're interested in. And in general the landing page doesn't inspire confidence. Tell me about security. Tell me that you take having and working with my data seriously.
The name "sgnly" makes me think it is an electronic signing service, but from your description it seems it converts documents into templates (and partially fills them?). Perhaps consider a name change?
There have been many attempts to compete with DocuSign in the past. Most of these fail because they miss the point that it isn’t really about digital signatures.
PDFs allow signing documents via encrypted certificate and PDF editing allows the creation of arbitrary signature fields on the fly. It’s all you need. It’s what the military has been using for all its business for more than a decade.
Certain areas of the military still use DocuSign even though they can do signatures better without DocuSign, because it isn’t about the signatures. It’s about the API DocuSign provides as a chain of enterprise automation regards to high quantity purchasing and fulfillment.
The lovable favicon makes me trust it less. It means the code is not done by an accountable human that can do something if my documents get leaked or your site hacked.
We transform the PDF into a template and identify automatically the variables. We automatically fill in repetitive information using the data we collect in previously docs.
We take any existing signed document, remove the variables of your choice, and create a new, identical document template. You can then use it for signature purposes.
Additionally, we automatically fill in repetitive information using the data we collect.
If someone sent my mom a link to a site called Sgnly to sign a document, she'd assume it was phishing and delete the message. I'd probably do the same.
Loosest privacy policy ever. As for the AI element, is there no option to opt out? Assuming this start-up is US-based, so you won't be getting any EU customers so, GDPR and EU<>US Data Transfer, EU AI Act 2025 etc.
Tech firms can’t just do that, someone in the relevant government (either state or county, depending on how the courts and their supporting administrative services are organized in your state) has to both have the motivation and funding, then either in-house or outsourced solutions can be sought.
tiffanyh|11 months ago
Hint: it’s not e-signature / pdf contracts.
DocuSign is in the trust business.
They have spent massive marketing dollars to create a trusted brand. They have even gone to court and won cases creating legal precedent their software can be trusted in contract law.
If your a CFO or company legal department, are your really going to use another service just because it saves you $2-3 per month … but from an unknown company?
(I’m not hating on the product. Just pointing out the dynamics at play)
Valodim|11 months ago
That doesn't mean it's impossible to do, but recognize that technical features that are fun to build are maybe 20% of that journey.
Source: been there, done that
t_mann|11 months ago
eddythompson80|11 months ago
Now imagine that, but with AI. Now you can ask an LLM to expand on the main points in the contract. The person you’re sending it to can ask an LLM to summarize that expansion. You both can arrive at a different conclusions because after all, a break in communication is eventually going to happen between any 2 parties. Might as well super charge it.
imglorp|11 months ago
No thanks. Just authenticate the parties and record their agreement.
steveBK123|11 months ago
crimsonnoodle58|11 months ago
Also an open source DocuSign alternative that we use is DocuSeal. Not affiliated, just a fan.
https://www.docuseal.com/
sanarothe|11 months ago
https://github.com/AntonOsika/gpt-engineer
I believe I have identified the culprit.
gigagorilla|11 months ago
jppope|11 months ago
sabaimran|11 months ago
theothertimcook|11 months ago
PanMan|11 months ago
chiph|11 months ago
What about protecting the form data itself? If I were to use this in a medical scenario, are you HIPAA compliant? Or if the form included a social security number and date of birth - what steps are you taking to protect the person filling out the form against identity theft?
Jekjerowes|11 months ago
[deleted]
morgenkaffee|11 months ago
I am a fan of replacing docusign as a principle though.
esaidm|11 months ago
recursive|11 months ago
jfengel|11 months ago
I suspect that at one point they were hoping to use the .ly TLD, but that fell through and they had their hearts set.
dillydogg|11 months ago
kulahan|11 months ago
CoastalCoder|11 months ago
etothet|11 months ago
chiph|11 months ago
Why is this important to us? We're filling in official state forms and we cannot change them in any noticeable way to give their input box more room. Some states have crammed everything together and we have to work around their poor design as best we can.
That DS provides traceability, viewing history, and cryptographic signatures is nice for us, and may help one day in case of a lawsuit. It's not a must-have for us, but likely was important for them given they originated in the real-estate document area (lots of disputes there, I'm guessing)
What could help us is making the input box translucent, or hiding it until the user navigates to it (perhaps leave a small marker so they know they have to provide a value there).
So far as the templating, we've got that solved with Fluent (née Autotag). Most of their competitors are doing simple word replacement (mail-merge) but they allow us to add logic like if-else and select-case to our templates. You should look into doing that too.
esaidm|11 months ago
admiralrohan|11 months ago
mrweasel|11 months ago
pedalpete|11 months ago
I'm not sure I understand your comparison to traditional process.
It looks like you are not taking a PDF as an input. So I am supposed to write my documents in sgnly? Curly braces makes sense to engineers, I don't think the average person really understands that (though I could be wrong).
Why is what you are doing 10x better than docusign? "Up and running within a week?" I was getting documents signed with grabsign within 20 mintues. But maybe I'm not the target user, but then who is?
Maybe I'm confused about what Docusign does, and I know they do more than just manage signatures, but how do most people know/use them?
Also the sgnly domain, though nice and short, doesn't give me a lot of confidence for a b2b app.
kieloo|11 months ago
esaidm|11 months ago
noodlesUK|11 months ago
Alternatively, is it a tool to manage writing contracts and other documents, and soliciting legally binding signatures? If so, I need to understand it more.
esaidm|11 months ago
sangupta|11 months ago
Molitor5901|11 months ago
xnx|11 months ago
DaiPlusPlus|11 months ago
It is: S/MIME is well-supported.
Anything else is not a "real" signature, as far as I'm concerned.
mc32|11 months ago
contravariant|11 months ago
nextts|11 months ago
AI generated and legally air tight don't sit in the same room for me right now. But not sure about your target audience. Have you asked them?
Or is your target audience AI investors ;) ?
Also I associate PH with "Is Beta" even though that may not be a fair assumption.
esaidm|11 months ago
esaidm|11 months ago
The idea goes as follows: We take any existing signed document, remove the variables of your choice, and create a new, identical document template. You can then use it for signature purposes. Additionally, we automatically fill in repetitive information using the data we collect previously.
mike_d|11 months ago
As soon as you modify the content or suggest what someone fills in, you are no longer a disinterested third party. Ask any notary or go look at DocuSign, they explicitly won't advise you on how to complete a form aside from basic things like making sure a field isn't blank or contains a number and not a string.
Gerardo1|11 months ago
* Then there's "5x faster document workflows — AI that auto-fills, explains, and builds reusable templates in seconds." Which is yet another thing that is discreet from the above.
* If you're going to have features based on AI, you need to be very clear and very loud about how and to what extent your any AI feature has access to my data. I need a super-charged privacy policy there, and I want you to be terrified of the consequences of violating your promises.
* "Get Up and Running Within A Week" That's forever to sign a document, which I think is the central purpose of this service?
* Your comparison slider between the traditional process and yours is comparing two very different things: what looks like a government form and an email. I can't take anything away from that.
* At the top of the page there's a "give us your email for early access" box, but at the bottom there's a whole form. What do I get from one that I don't get from the other?
Basically, your site isn't clear about the focus of this service. I would guess the template things are the primary use-case you're interested in. And in general the landing page doesn't inspire confidence. Tell me about security. Tell me that you take having and working with my data seriously.
cuu508|11 months ago
achempion|11 months ago
austin-cheney|11 months ago
PDFs allow signing documents via encrypted certificate and PDF editing allows the creation of arbitrary signature fields on the fly. It’s all you need. It’s what the military has been using for all its business for more than a decade.
Certain areas of the military still use DocuSign even though they can do signatures better without DocuSign, because it isn’t about the signatures. It’s about the API DocuSign provides as a chain of enterprise automation regards to high quantity purchasing and fulfillment.
oschvr|11 months ago
For a prototype it's ok.
unknown|11 months ago
[deleted]
jreynan|11 months ago
esaidm|11 months ago
brailsafe|11 months ago
esaidm|11 months ago
Additionally, we automatically fill in repetitive information using the data we collect.
alexpadula|11 months ago
numbers|11 months ago
esaidm|11 months ago
biwills|11 months ago
esaidm|11 months ago
kylephillipsau|11 months ago
lyingnig|11 months ago
[deleted]
gbraad|11 months ago
Sorry, but that is a bad name. Looks like a typo. Just saying. If you pronounce this the way you want it, you have to add "without the i".
nosioptar|11 months ago
dzonga|11 months ago
esaidm|11 months ago
mmwako|11 months ago
junto|11 months ago
esaidm|11 months ago
JumpCrisscross|11 months ago
Does this really help?
esaidm|11 months ago
austinallegro|11 months ago
jhnam88|11 months ago
shirajg|11 months ago
tonymet|11 months ago
dragonwriter|11 months ago
0x69420|11 months ago
zebo123|11 months ago
[deleted]