Who this is for

You own the rollout or the business outcome. You do not plan to write code. You want your team to start sending real documents for signature inside your product.

What success looks like today

Two quick wins:

1. Invite your engineering team so they can plug Firma.dev into your app.

2. Create your first Customer Workspace so each customer’s documents and usage stay separate.

Step 1: Invite your engineering team

Send them this note with links:

Subject: Can you add e‑signing to our app this week?

We’re using Firma.dev It’s a simple API with embedded editors so setup is fast.

Pricing is pay‑as‑you‑go at $0.029 per envelope, first 25 are free.

Docs and starter guide:
- Complete setup: https://docs.firma.dev/guides/complete-setup-guide
- Sending a signing request: https://docs.firma.dev/guides/sending-signing-request
- Embeddable template editor: https://docs.firma.dev/guides/embeddable-template-editor

Goal: send our first signing request from staging.

Thanks!

Your first 25 envelopes are included for implementation and testing, and live use costs $0.029 per envelope. No minimums, no subscriptions.

Step 2: Create a Customer Workspace

Think of a workspace as a clean room for one customer’s documents and usage. It keeps templates, signing activity, and analytics separate and easy to report on. You can create as many as you need. 

If you prefer to click rather than call APIs, that is fine. Ask your team to create your first workspace named after a customer or sandbox account. Engineers can create it in seconds and will get a workspace‑scoped key behind the scenes to keep actions isolated to that workspace.

What your engineers will do next

They will pick one happy‑path document like an NDA or order form and:

• Create a reusable Template either with the embedded visual editor or via API.

• Send a Signing Request (see docs) based on that template.

• Deliver the signing view inside your product or redirect to a hosted page.

• Turn on Webhooks so your app reacts when a document is viewed, signed, or completed.

You do not need to manage any of that. Your role is to pick the first document and define what “done” means.

Why teams choose Firma.dev

• Costs that make sense. Pay $0.029 per envelope. First 25 are free so you can test end to end before paying.

• Clean separation by customer. Workspaces keep data, templates, and usage private per customer with no cross‑workspace exposure.

• Security and trust. Firma.dev is designed to align with ESIGN and UETA in the U.S., eIDAS SES and AdES in the EU and UK, GDPR for data protection, and HIPAA contexts in healthcare.

Your checklist

• Pick the first document to automate

• Invite engineering with the note above

• Create your first Customer Workspace

• Confirm webhooks are on so your system knows when a document is signed

That is it. Once the first signing request goes out, your team can refine the flow and add more templates.

👉 Get started with Firma.dev today - no credit card required.