Use Case

Automate Freelancer Contracts

Automate freelance contracts, SOWs, and service agreements with a single API call. Send for e-signature in seconds.

The problem

Freelancers send the same contracts repeatedly — NDAs before discovery calls, Statements of Work before projects start, service agreements before retainers begin. Each one requires manual editing, PDF export, email attachment, and follow-up chasing.

The solution

Template your contracts as markdown and send them via API. Change the names, dates, and rates programmatically. The recipient gets a signing link, signs in under 60 seconds, and both parties receive a SHA-256 certified PDF.

What you need to know

Freelancer contract automation eliminates the most time-consuming part of running a freelance business: the paperwork between landing a client and starting work. The average freelancer sends 3-5 contracts per month — NDAs, service agreements, and statements of work. Each takes 20-30 minutes to prepare manually.

The hidden cost of manual contracts: Beyond the time spent editing templates and chasing signatures, manual processes introduce errors. Wrong dates, incorrect rates, outdated terms, and missing clauses are common. A single error in a contract can cost more to resolve than an entire month's revenue.

What freelancers should automate first: Start with your most-sent document. For most freelancers, that's either an NDA (sent before every discovery call) or a service agreement (sent before every project). Template it once as markdown, then send it with different variables for each client.

Markdown as a contract format: Markdown is ideal for contracts because it's readable, versionable, and easy to template. Unlike Word documents or PDFs, markdown templates can be stored in version control, reviewed in pull requests, and generated programmatically from any programming language.

Legal validity: E-signed freelancer contracts are legally binding under ESIGN (US), eIDAS (EU), and ECA (UK). The SHA-256 certificate provides stronger evidence of signing than a wet-ink signature, including exact timestamps, IP addresses, and tamper-proof integrity verification.

Example document template

Markdown template
# Service Agreement

This agreement is between **{{clientName}}** and **{{freelancerName}}**
for {{serviceType}} services at a rate of **{{rate}}/hour**.

## Scope of Work
{{scopeDescription}}

## Terms
- Net {{paymentTerms}} payment terms
- {{revisionRounds}} rounds of revisions included
- Agreement valid for {{duration}} from signing date

## Termination
Either party may terminate with {{noticePeriod}} written notice.

Replace the {{variables}} with your application data and send via API.

Send it with one API call

curl
curl -X POST https://signb.ee/api/send \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "content": "YOUR_RENDERED_MARKDOWN",
    "senderName": "Your Name",
    "senderEmail": "you@company.com",
    "recipientName": "Recipient Name",
    "recipientEmail": "recipient@email.com"
  }'

Why this approach works

  • Send contracts in seconds, not hours
  • Dynamic content — change rates, scopes, and terms per client
  • No PDF editing software needed
  • Legally binding with SHA-256 audit trail
  • Free for 5 documents/month — enough for most freelancers

Related reading

FAQs

How do I automate freelancer contracts with e-signatures?

Template your contracts as markdown and send them via API. Change the names, dates, and rates programmatically. The recipient gets a signing link, signs in under 60 seconds, and both parties receive a SHA-256 certified PDF.

Can I send freelancer contracts for e-signature via API?

Yes. Template your contracts as markdown and send them via API. Change the names, dates, and rates programmatically. The recipient gets a signing link, signs in under 60 seconds, and both parties receive a SHA-256 certified PDF. The signed document includes a SHA-256 certificate with timestamps, IP addresses, and a cryptographic integrity hash.

Are e-signed freelancer contracts legally binding?

Yes. Electronic signatures on freelancer contracts are legally valid under ESIGN (US), eIDAS (EU), and ECA (UK). Each signed document includes a SHA-256 certificate with timestamps, IP addresses, and a cryptographic hash that proves the document hasn't been altered after signing.

What contracts should freelancers automate first?

Start with your most frequently sent document — typically an NDA (sent before discovery calls) or a service agreement (sent before projects). Template it as markdown with variables for client name, rates, scope, and dates. You'll recoup the setup time after sending just 2-3 contracts.

Can I customise contracts for each client?

Yes. That's the core benefit. Your markdown template includes variables like {{clientName}}, {{rate}}, and {{scopeDescription}} that are populated dynamically for each client. Every contract is customised, but you never manually edit a template again.

Related resources

Try Signbee — free, no credit card.