docspawn docspawn
Book a demo
1 · Templatehandover-report.pdf
Create your template
AI drafts the fields, you validate them — 10 minutes once, reused for every document.
DatesPhotosSignatureCheckbox grid
Without docspawn
20min / doc
With docspawn
~2s / doc
New Document automation, finished

The last piece of every document workflow.

Bring a document once and let AI do the heavy lifting to turn it into a reusable template. Then feed docspawn the data — it comes out the other end as a finished, branded document, delivered to the right inbox.

AI turns your document into a reusable template — feed it data, get finished branded documents in the right inbox.

Every new record in your CRM or Google Sheet is a document ready to be sent.
1 · Templatehandover-report.pdf
Create your template
Let AI do the heavy lifting — 10 minutes once, reused for every document.
DatesPhotosSignatureCheckbox grid
2 · InputYour data
Feed docspawn the data
Form filling
in-app, or shared with clients
External data
Google Sheet · CSV · XLSX · CRM
→ maps straight onto your template
3 · OutputTo: client@acme.inc
PDFhandover-report.pdfSent
delivered to the right inbox, recipients from the form
Generated 09:41Sent 09:41Signed
Document library24 docs
12 Sent6 Signed6 Generated
docspawn
Spawned in seconds
FleetoraNorwoodAxiom FieldCargolaneVantage Inspect
The last mile

Data is easy now.
Documents still aren't.

AI drafts, extracts, and structures information in seconds. Turning that into a correctly formatted, branded, delivered document is still manual, slow, or breaks the tools you already pay for. docspawn is built for that last mile.

+
Generating the data
AI and your systems now do this in seconds.
Formatting the document
Someone copy-pastes into Word for 20 minutes, per document.
Sending it, on brand
Four tools and a Zapier chain that breaks quietly.
+
docspawn does it in one flow
Detect, capture, generate, and send. No glue.
1Set up once

Ten minutes once. Every document after that takes seconds.

From your PDF to a reusable template — docspawn works from the documents you already use. No developers, no rebuild.

1
Upload your PDF
The real document you already use, however complex.
2
AI drafts, you validate
AI detects the fields as a first draft — then you review, edit, and validate each one. Your judgment stays in charge.
3
Type every field
Dates, photos, signatures, checkbox grids — each field gets a smart type.
4
Link data groups
Smart fill: one value cascades into every linked field.
5
Set the rules — done
Recipients, branding, conditional logic. Set once, then reuse it.
PDF
Drop your real PDF
However complex — tables, photo grids, multi-page.
3 pagestablescheckbox grids
2Input

Feed it data — or let it collect the data for you.

Data reaches docspawn two ways: connect external data with Data2Doc, or collect it with forms using Form2Doc. Both map straight onto your template.

Data2Doc — connect your data

Connect your data. The documents send themselves.

Connect your Google Sheet or CRM to docspawn and get documents sent automatically — or upload a CSV / XLSX and batch-generate from it. Every new record is a document ready to be sent: on a schedule, on every new entry, or on demand.

Sfleet-log — Google Sheet● Synced
ContractVehicle
FL-2026-0417Kangoo
FL-2026-0418Porteur 19T
PDF
handover-report.pdf
✓ Generated and sent · +47 more in this batch
auto
Scheduled on a cadence you setTriggered every new entry, instantlyManual one document or a whole batch, on demand
Form2Doc — collect with forms

A form goes out.
A document comes back.

Fill the form in the app and watch the PDF build itself in a live preview beside it. Or share an external form — clients and providers fill it on their phone, no login, signature included. Either way, the document is generated and delivered to the inbox instantly.

In-app formLive PDF previewExternal linkNo loginSignature
docspawn — Fill: handover-report
Form
Client
RUNCAR SAS
Invoice ref
INV-2026-114
signature ✓
Submit
Live previewlive
docspawnACME FLEET
ClientRUNCAR SAS
Invoice refINV-2026-114
M. Blanc
updates as you type
Stamp & annotate

Mark the damage on the drawing, not in a paragraph

Drop stamps straight onto a car or building drawing — one tap per defect — and annotate site photos on the spot. All of it is baked into the generated PDF: every job comes back with the proof inside the paperwork.

1 Stamp the drawing2 Annotate photos3 Baked into the PDF
scratchdentchip — window
works with your own drawing — car, building, machine3 stamps
External links

Send it to anyone. No account, no app.

Generate a link and share it with clients, providers, or drivers. They open it on their phone, fill, and sign — completely anonymous, no login.

docspawn.app/f/x7Kq3vCopy
ClientProviderDriver✓ signed on their phone
One submission, two results

The document — and its data

Every submission generates the branded PDF into the right inbox, and lands the structured data in your library — nothing to re-type.

PDFhandover-report.pdf→ inbox
MVT00062668→ data library
3Output

Submitted at 09:41.
In their inbox at 09:41.

Your document is delivered automatically to the right inbox. Keep track of all that happens in docspawn.

docspawnACME FLEET
scratch
M. Blanc
docspawn
Acme Fleet via docspawn
to client@acme.inc — pulled from the form
09:41
Your vehicle handover report — FL-2026-0418
Hello — the signed handover report for FF-575-QV is attached. Photos and signature are inside.
PDF
handover-report.pdf
branded · photos & signature inside · 1.2 MB
Sent
Generated09:41
Sent09:41
Opened10:02
Signed10:15
…and everything is stored and searchable
Document library24 docs
handover-report.pdfSent
inspection-04.pdfSigned
Data library
RecordClientDocs
MVT00062668RUNCAR SAS3
MVT00062667Acme Fleet2
Sealed at generation

Anyone can generate a document. We can prove where it came from.

A signing tool meets your document once it already exists, so the strongest thing it can say is that the file has not changed since. docspawn is what produced the document, and that is a different claim entirely. Turn sealing on and a document is sealed as it is made, not afterwards.

Integrity after the fact
What a tool that receives a finished file can attest
This file has not changed since I first saw it.
The source record, the template version and the moment of creation were already gone by the time the file arrived.
Provenance at origin
What the system that produced the file can attest
This document was produced from this data, by this system, at this moment, and has not changed since.
docspawn holds the source record, the template version and the timestamp at the moment the document comes into existence, and seals it there.

European law grades proof in three levels

eIDAS grades electronic signatures and seals by how much verified identity sits behind them. The vocabulary is worth knowing before anyone sells you one.

SESSimple electronic signature
Admissible
A signature collected with an audit trail and no certificate behind it. A court will accept it, and the burden of proving who signed falls on whoever relies on it. This is the level docspawn collects today.
AESAdvanced electronic signature
Strong
The signer is authenticated, the signature is uniquely linked to that person, and any later change to the document is detectable. Enough for most commercial agreements.
QESQualified electronic signature
Equal to handwriting across the EU
A qualified certificate issued by a trust service provider on the EU trusted list, with the key held in certified hardware. The burden of proof reverses onto whoever disputes it.

A seal is not a signature

A signature says a person agreed. A seal says an organisation issued this. Because a seal is applied by the issuer rather than collected from a human, it can be applied at the moment a document is generated, which is something a signature can never do. It proves who issued the document, not who signed it.

You can seal any document docspawn generates with a qualified electronic seal and a qualified timestamp, applied as the document is produced. Signatures are a separate question: docspawn collects simple electronic signatures today, and advanced level is on the roadmap.
How proof of origin works →

eIDAS is European Union law. Sealing is an option you turn on. The seal proves a document's origin and integrity; it does not verify who signed it. This is not legal advice.

Coming soon

The document layer for AI and automation

Let Claude Code, any CLI, n8n, or Zapier hand docspawn one reference number and get back a finished, branded PDF in ~2 seconds. docspawn looks up the record, fills every field — vehicle, client, dates — and returns a signed link, ready to send.

~2s
generation round-trip
3 calls
login → lookup → PDF, the whole loop
1 → 7
fields filled from one value
Claude CodeAny CLIDevice-flow loginn8nZapierMCP
On the roadmap: auto-email delivery and analytics queries over everything docspawn has collected.
Get early access
docspawn cli
$ docspawn login → Enter code FKTP-QRZM at demo.docspawn…/device ✓ approved$ docspawn generate vehicle-handover \ --set "NumeroMouvement=MVT00062668" --json → matched record MVT00062668: FF-575-QV · RUNCAR SAS · 2 dates7 fields auto-filled from 1 value → branded PDF ready in 2s ✓ https://cdn.docspawn…/handover.pdf
What you get

Everything it takes to finish a document

Built for the genuinely complex documents that other tools choke on.

Pixel-accurate complex PDFs
Tables, checkbox grids, annotated photos, signatures, multi-page, from your own file.
AI field detection
Upload a PDF and let AI find and pre-fill the fields. No rebuilding by hand.
Web, mobile & voice capture
Built for the field. Fill on a phone, or dictate it, with a live preview.
Documents on autopilot
Connect a Google Sheet so each new row generates and sends a document.
Conditional logic & triggers
Documents adapt to the input and append proof pages only when needed.
Generate and distribute
Auto-email the branded PDF to the right recipients with a custom message.
Collect from anyone, no login
Public form links so third parties upload PDFs and IDs into your library.
Bulk from spreadsheets
Turn a table into a batch of documents in one run.
A data layer, not a folder
A filterable library with saved views, versions, and an audit trail.
Where teams use it

One engine, every document-heavy workflow

Vehicle inspection
Check-out report with photos, grids, and signature — signed before the truck leaves the yard.
Field service reports
Job sheets and safety checks — the client has the PDF before the tech leaves the site.
Delivery notes
Proof of receipt emailed the moment it's signed — no end-of-day paperwork pile.
Contracts & applications
Agreements and onboarding from one intake — back signed the same day.
Why docspawn

The piece the other tools leave out

Form builders, document engines, and field apps each own one slice. docspawn connects them.

VSForm builders
Great at collecting data, but simple PDFs, no complex layouts, logic, or live-data automation.
+ docspawn keeps your exact document and adds logic and live data.
VSDocument engines
Powerful generation, but they need developers and stop before distribution.
+ docspawn is no-code and sends the finished document for you.
VSField-capture apps
Strong on mobile, but locked to their template builder, not your PDF.
+ docspawn starts from your real PDF, and adds voice.
Pricing

Pricing that scales with pages, not seats.

No per-user fees — pay for the documents you spawn. We're finalizing tiers with our first customers; get in early and shape them.

Talk to us
FAQ

Common questions

What is docspawn?

docspawn covers the last mile between data and a delivered document. You bring a document you already use, AI drafts its fields for you to validate, and from then on you feed docspawn data and get back a finished, branded document delivered to the right inbox.

How long does it take to set up a template?

About ten minutes, once per document. You upload your PDF, AI drafts the fields as a first pass, you review and validate each one, then set recipients, branding and conditional logic. Every document generated after that takes roughly two seconds.

Does docspawn work with my own PDF?

Yes. You upload the real document you already use, however complex: tables, checkbox grids, annotated photos, signatures and multi-page layouts. docspawn keeps your exact document rather than asking you to rebuild it in a template builder.

How does AI field detection work?

AI reads your uploaded PDF and detects the fillable fields as a first draft. You then review, edit and validate each field, and give it a type such as date, photo, signature or checkbox grid. Your judgment stays in charge of the final template.

Can someone fill in a document without an account?

Yes. You can share a public form link so a client, subcontractor or any third party fills the document and uploads files without a login and without installing an app.

Can docspawn generate documents in bulk from a spreadsheet?

Yes. Connect a Google Sheet, CSV or XLSX and each row becomes a document, or turn a whole table into a batch in one run. Connected to a live sheet, every new row can generate and send its document automatically.

Is there an API or an MCP server?

An MCP server and an API are on the roadmap, not released yet. The intent is that Claude Code, any CLI, n8n or Zapier can hand docspawn one reference number and get back a finished, branded PDF.

How is docspawn priced?

Pricing scales with pages rather than seats, so there are no per-user fees. Tiers are being finalised with the first customers.

About

Who builds docspawn?

docspawn is built by tec.tech, a software studio in La Réunion that builds its own products rather than reselling other people's.

tec.tech
A software studio based in La Réunion (France), registered as a SAS under SIRET 893 286 435 97450.
More about tec.tech →
Other products from the same studio
memrly, LapseGuard, Supabrain and Vidspawn are built by the same team.
Talk to the team
Write to hello@tec.tech and you reach the people who build docspawn.
hello@tec.tech →
docspawn

Send us your most complex PDF.

We will show you that exact document detected, filled, generated, and delivered, in a 20-minute demo.

Book a demo