A paid service from the CodesSavvy team
Setup and migration
nodshake setup and migration is a paid service from CodesSavvy, the team that runs nodshake. We build nodshake signing into your app or workflow, look after it once it is live, and move your integration from your current e-signature provider, so your own developers do not have to build it. Templates and other features are scoped on request. Each project is quoted and agreed in writing before work starts.
What you get
Signing that works, without your own team
- A written scope and quote before any work starts
- Signing working in your own app or workflow
- Anything else you need, such as templates or notifications, scoped in writing first
- A handover that explains what was built
- Optional ongoing support, agreed in writing
Quoted per project and agreed in writing before work starts.
What we do
We build it in
A one-time implementation of nodshake signing in your app or workflow, done by our team instead of yours.
- Connecting your product through the nodshake API (set up on request)
- Signing inside your own product
- Templates and notifications, on request and agreed in the written scope
We look after it
Ongoing support for your signing workflow, so nobody on your side has to sit and maintain it.
- Changes to how your signing flow works
- Fixes when something breaks
- New documents, and templates on request
We move you over
Code-level help moving from your current provider, such as DocuSign, Adobe Acrobat Sign or Dropbox Sign.
- Moving your integration code to nodshake
- Your templates, on request and scoped in writing
- Moving your workflow
- Exporting your completed documents and their certificates
How it works
- Step 1
A call
Tell us what you sign, where signing has to happen and what you use today.
- Step 2
Written scope and quote
We send a written scope and a quote for the project. Nothing starts until you agree it.
- Step 3
We build
Our team does the work agreed in the scope, in your app or workflow.
- Step 4
Handover and support
We hand it over and explain how it works. If you want ongoing support, we agree that in writing too.
Who it is for
Companies that need signing done, not another project
Teams without spare developers
You need signing in your product or workflow, but nobody on your team has time to build or maintain it.
Companies switching provider
You want to leave your current e-signature provider and need help moving the integration and workflow.
Large companies
Rollout across departments, on request, with scope, security questions and handover agreed in writing.
Agencies building for clients
You build products for clients and want signing handled by a team that runs the signing service.
Migration and price
Switching does not change documents you already signed
Documents you completed with your current provider keep their signatures and that provider's certificate of completion. Signatures cannot be moved between providers, so we do not transfer them. Download each signed document and its certificate before you close your old account; we help you export them and store them where you choose.
Price
Setup, support and migration are paid work. Quoted per project and agreed in writing before work starts. Signing itself is priced per signed document, as on the pricing page.
Questions
- Is it paid?
- Yes. Setup, support and migration are paid work, separate from the price per signed document. Quoted per project and agreed in writing before work starts.
- Do I need developers?
- Our team does the build agreed in the scope. We need someone on your side to give us access to your app or systems and to answer questions about how your workflow should run.
- How long does it take?
- It depends on what you need built or moved. We give you a timeline in the written scope, before work starts.
- What happens to documents signed on my old provider?
- Documents you completed with your current provider keep their signatures and that provider's certificate of completion. Signatures cannot be moved between providers, so we do not transfer them. Download each signed document and its certificate before you close your old account; we help you export them and store them where you choose.
- Can you work with our stack?
- Tell us what your app is built with and where signing has to happen. We say plainly in the written scope what we can do, before you agree to anything.