AI for Developers

I Vibecoded E-Signature in an Afternoon

Not a demo, an actual feature in a real app. I blocked out an afternoon and needed about forty minutes, with working code roughly ten minutes in. Here is the honest timeline.

Alex Martinez
Alex MartinezDeveloper Relations & Automation Lead
June 5, 20266 min read

“Add e-signatures” used to mean blocking out a week. I gave it an afternoon, using an AI coding agent and the TurboDocx Quickstart Skill, and barely touched the afternoon. Working code landed about ten minutes after I installed the skill, and the first real signature went out a few minutes later. The integration was the fast part. The careful part, as it should be, was the review and the edge cases.

Here is the real timeline, so you can calibrate your own expectations.

Start to finish, minute by minute

1:00

Install the skill, grab a key

Ran npx skills add TurboDocx/quickstart and signed up for a free account. Pasted the API key into .env. Two or three minutes, most of it waiting on the signup email.

1:10

Working integration, done

One prompt. The agent detected the framework, installed the SDK, and wrote the module plus an example route. The code was finished about ten minutes after the skill went in.

1:14

First real signature

Ran the example, sent a test contract to my own inbox, signed it, and watched the completed PDF and audit trail come back. Working end to end in under fifteen minutes.

1:30

Webhook and edge cases

Added a completion webhook so the app reacts when a document is signed, then handled the decline and expiry paths. This part, not the integration, is where the remaining time went.

1:40

Review and ship

Read the diff like a normal PR, confirmed the key was server-side only, and merged. Done long before the afternoon was.

The one command that starts the clock

Everything above starts here:

npx skills add TurboDocx/quickstart

After that, it is plain English in your agent. The full step-by-step is in the Claude Code guide and the Cursor guide, and the deeper walkthrough lives in Vibecode an E-Signature Flow.

What actually took the time

The agent wrote the happy path in minutes. What little time remained went to the things that make a feature production-ready, not the SDK wiring:

Verifying the webhook signature before trusting a completion event
Storing the signed PDF and audit trail somewhere durable
Handling declined and expired documents, not just signed
Confirming the API key only ever lived in the serverless layer

That split is the point. Letting the agent handle the boilerplate freed up the afternoon for the judgment calls that actually deserve a human.

Related Resources

Start your own afternoon

Install the Quickstart Skill and prompt your agent. Your first 5 signatures each month are free.