Sharing AI-generated drafts: a 60-second workflow

The AI workflow has a missing piece. You ask Claude for a one-pager, it writes a great one-pager, you save the file, then you sit there wondering how to get it in front of the two people who need to sign off. The default answers (Slack the file, paste into Google Docs, screenshot and email) all add 5 to 15 minutes of friction per file.

This is the workflow we use internally and recommend to customers. Three steps. Under a minute end to end. Works for any .md or .html file an AI hands you.

Step 1 (10 seconds): drop the file

Open Vela Docs in your browser. Drag the file from your desktop onto the page. It renders immediately. Cream background, readable typography, headings styled like a normal document instead of raw Markdown syntax.

That's the file rendered. You can stop here if all you need is to read it cleanly.

Step 2 (20 seconds): share the link

Click Share at the top right. First-time only, sign in with Google or email magic link (two clicks). The file uploads, you get a docs.vela.partners/d/... URL. Copy it.

That URL is the entire share artifact. No file attachment, no PDF export, no "I'll put it in Notion later." The recipient clicks once and sees the same rendered document you do.

Step 3 (30 seconds): drop the link wherever the team lives

Paste into Slack, Linear, email, Notion, wherever your team actually responds. Add one line of context:

• For sign-off: "Q3 plan from the AI run. Land any objections by Thursday."
• For copy review: "First draft of the landing page hero. Inline-comment anything that reads off."
• For research: "Notes from the Acme call written up. Skim for what's worth following up on."

Anyone clicking the link can read without an account. To leave comments, they sign in (one click). They highlight text, hit the Comment button, type. Notifications come back to you via email and the Vela Docs bell menu.

What this replaces

The non-Vela equivalent of this workflow today is one of:

• Copy-paste into Google Docs. Markdown formatting partially survives. Code blocks die. Comment workflow works but the file's no longer .md.
• Convert to PDF and email. Now nobody can edit. Comments come back as Slack thread or email reply, not anchored to a sentence.
• Push to GitHub / Notion. Workflow tax if it's a one-off file. Wrong tool for a draft you're showing once.
• Don't share, just summarize verbally in the meeting. The AI output never gets reviewed by the people who'd have caught the mistakes.

Where the 60-second number breaks

First-time setup adds a one-time 15 to 30 seconds for sign-in. After that, every subsequent share is the 60 seconds described above. If you do this five times a week, you save somewhere between 30 minutes and an hour depending on how many people are in the loop.

The bigger value isn't the time saved on any single file. It's that drafts that previously sat in your downloads folder ("I'll send this around later") now actually go around.

One short takeaway

Drop, share, paste. Three steps, three buttons. The AI did the writing; this workflow gets it past the inbox.