I have a really cool new plugin on the way and I am currently looking for some feedback!
Plug-in:
Drag and drop contract & agreement builder
Why did I build this?
From 2019 -2020 I struggled with finding a way to let users create emails in app instead of having to use things like sendgrid templates, the on market choices at the time were very slim and the builders that did exist were more so web builders over email builders.
In 2020 I released my drag and drop email builder here.
Over the last few years I’ve encountered the same issue with contract & agreement builders, unfortunately there really isn’t anything on market that can be integrated built specifically for this. We’ve used a hack around solution for a long time that was “good enough”. Essentially using my email builder for display and signature flows in app OR vanilla bubble creation.
Solutions like this don’t produce print ready PDFs, they don’t automatically page break, they don’t have much of the functionality you’d have from something like docusign.
Docusign, panda doc, etc: the problem
I’ve encountered a primary problem with signature apps like this, on multi tenant apps there is no way for users to build the contract/agreement inside of the bubble application itself.
The solution (features):
Over the last few months I’ve been building out a built from scratch drag and drop contract/agreement builder. In its current state it’s fully working but not released, here’s the current feature set.
Full drag and drop
automatic page breaking algorithm
Smart page breaks. Ex) You will not break page mid word or sentence, page breaks will apply to content in a user friendly way.
Print ready PDF export
Beginner friendly & implements into bubble in 15 minutes.
25+ pre built templates
merge tags /dynamic content
15+ elements including pricing tables/quote tables/signature/etc
custom primary color & branding.
Feedback request
I have a few questions on what the community would like to see.
Signature flows:
There’s 2 ways I can set this up that i am still indecisive on.
1) Stand alone builder
In this case you receive the PDF and the JSON, the builder will not have a signature element or input elements of any kind. Rather it’s the developers responsibility to setup a dedicated signature page and flow and UI using your typical signature pad and input style and then use an action I provide called “attach signatures to document”. (I will have a copy paste template for sig flows)
Cons:
Developer must build signature request UI flow/page
No ability to use signature or input elements on agreements.
Pros
Allows you to build your own signature Ui
I do not have to store ANY documents that are built which maintain privacy for your users and compliance issues for me.
More customization for you in your flow including reminders and such.
No API keys, whitelisted domain, etc will be needed. Stand alone approach.
2) Complete builder + sig flows.
In this setup I’m considering rather than the developer having to build signature flows rather they will simply add a separate element from my plugin “signature request page” that displays the corresponding doc signature request page on your app.
This gives a combo approach to docusign where developers will be able to implement in both a multi tenant builder & signature features simply by adding 2 elements into their app. A builder element and a display element.
The pros:
Easier setup for developers
No need to build signature flows
Signature & input elements on builder will exist.
Cons:
Less flexibility.
I have to store docs on our server = reduced privacy & increased compliance requirements.
Webhook setup required for dev to receive docs.
In this case you’ll also need to whitelist URLs, generate API key, etc.
Does anyone have feedback on which style setup they’d like to see or what would be most useful? Feature requests? Feedback?
Sneak peaks:
Expected release: 30-60 days
Expected pricing: 1 price point (unknown), unlimited usage & documents.
