The reason drafting feels slow is rarely the writing. It's the gathering. The right context for the email lives in three Slack threads. The proposal you sent last quarter that the new one should mirror is buried in Drive. The opening line of the newsletter is meant to reference a thing you wrote three months ago that you can't quite find. By the time the source material is in front of you, you've spent forty minutes and haven't written a sentence.
This guide is about drafting in the same place your notes live. The source material is already there. The agent helps you pull what you need. The draft happens on a page that has all of the context one click away. You stop being the assistant who finds the material and start being the writer who shapes it.
What drafting in your notes app actually changes
Drafting in a notes vault changes three things:
- The source material is already in arm's reach. The customer call you had on Tuesday is on a page. The proposal template lives in your library. The previous newsletter that you're referencing is searchable. You don't have to leave the app to assemble the context.
- The agent can pull from your real material. Your past proposals, your past emails, your past newsletters. The drafts that come out are grounded in your actual voice and your actual prior work, not in a generic template the AI invented.
- The draft lives where it can be referenced again. Six months later when you're writing a similar email, the draft you sent today is searchable and quotable. Each draft becomes a future reference.
The shape that holds: a "Drafts" section, a "Templates" section, a "Sent" section if you want to archive what shipped, and the agent reading across all of it. The reference layer that feeds drafting — saved hooks, openers, CTAs — is its own discipline; see how to build a swipe file in your notes app.
The templates section — the patterns you reach for
Most drafting work is variations on patterns you've used before. The cold-outreach email to a senior buyer. The proposal for a six-week consulting engagement. The newsletter intro that opens with a personal note and pivots to the topic. Most writers have those patterns in their head; few have them written down.
A "Templates" section in the vault makes them explicit. One page per template. Each page describes what the template is for, the structure, and the conventions you've decided work — the opener, the length range, the tone, the way you handle the call to action.
When you ask the agent to draft a cold email, it reads the cold-email template page first. The output respects your specific approach, not a generic template. As your sense of what works evolves, you update the template page. The next draft reflects the new thinking.
The templates aren't fill-in-the-blank forms. They're documented conventions. The agent uses them as guidance for the structural decisions that would otherwise drift inconsistently across drafts.
Drafting an email — the operational flow
You need to send an email. Open a new page in the "Drafts" section. Type at the top who it's to and what it needs to do — "to Maya at Acme, declining the partnership but leaving the door open for the spring cohort."
Below that, drop in or link the source material — the previous email thread you're responding to, your notes from the call you had with her last month, the proposal you'd considered sending. PDFs auto-convert to markdown via docstrange so attachments become searchable text.
Now ask the agent: "From the source material on this page and the conventions in the email-decline template, draft the email. Keep it warm and short. Reference the spring cohort opening as a real follow-up, not a polite throwaway."
You get a draft. You read it. Most of the structure is there. Two sentences sound generic — you replace them with sentences that sound like you. You change one phrase that's too soft. You send.
The whole flow took six minutes. Most of that was your editing. The assembly and the structural draft happened in seconds because the source material was already on the page and the conventions were already in the template.
Drafting a proposal — the higher-stakes case
Proposals are slower because they're longer and more is riding on them. The drafting flow is the same shape, with one extra step: pulling from past proposals. (For the broader client-context shape that feeds proposals — briefs, calls, deliverables — see AI notes for client work.)
Open a new page in "Drafts." Type the brief at the top — who it's for, what they need, the scope you're proposing, the price range, the timeline. Drop in any source material — their RFP, your notes from the discovery call, links to past projects that are similar.
Ask the agent: "Find every proposal I've sent in the last year for engagements similar to this one. Pull the strongest sections from each — the framing of the problem, the scope language, the way I described methodology, the pricing rationale. Don't write the proposal — lay out the reference material so I can write from it."
You get a structured shortlist of your own past best work, organized by section. You write the proposal from those references. The voice is yours because you're writing. The structural decisions are informed because your past best moves are right there. The proposal that would have taken half a day takes two hours and reads better than the half-day version, because the half-day version usually included thirty minutes of staring and forty-five minutes of trying to remember what you did last time.
For complex proposals with appendices, an inline database via the :::database::: directive can hold the line-item scope or the deliverables list. Embedded directly in the proposal page so the document is one page, with the table living alongside the prose. Easier to update than a separate spreadsheet.
Drafting a newsletter — the recurring case
Newsletters are the test case for whether drafting in your notes app actually pays off. Unlike a one-off email or proposal, a newsletter happens on a cadence. The drafting work compounds — or it doesn't — over months.
A "Newsletter" section in the vault, with a sub-page per issue. Each issue page holds the brief at the top — what's the topic, what's the angle, what's the takeaway — and the draft below.
The agent's first job is mining your recent material. "Read everything I've added to the vault in the last week — meeting notes, drafted ideas, saved articles, comments I made on other people's work. What three themes are most ready to become a newsletter issue?" You get a shortlist grounded in what you've actually been thinking about, not a brainstorm from cold.
Once you've picked the angle, the agent helps with the draft. "From the material on the inbox page and my newsletter-template conventions, draft the next issue. 600 words. Open with the personal observation from Tuesday's note, build to the central claim, close with the question."
The draft lands. You edit. You publish. The issue page now holds the brief, the draft, and (after publication) any reader replies that came back. Six months later when you're writing a similar issue, this one is searchable.
For long-running newsletters, the back catalog is a real asset. "Find every newsletter issue in the last year where I touched on the relationship between productivity and slowness. Pull the strongest paragraphs." You see your own evolution on the topic. The new issue can extend or revisit, intentionally rather than accidentally. If your newsletter is part of a multi-channel publishing rhythm, content repurposing across platforms covers how the same source feeds short-form versions.
Drafting from your own past work — the voice question
The risk with agent-drafted anything is that the voice flattens. Generic. Smoothed. AI-shaped. The defense is that the agent is drafting from your actual material — your past emails, your past proposals, your past newsletters — not from a generic template trained on the open web.
When the source material in the vault is in your voice, the drafts come out closer to your voice. When you carefully edit each draft, the published version is yours. Over months, the drafts get closer to first-pass good, because the agent has more of your material to learn the patterns from and your conventions pages get sharper.
For voice-critical drafts — an apology email, a sensitive client message, a piece you're putting your byline on — write the first pass yourself, then ask the agent for a structural critique. "Read the draft on this page. Tell me where the argument weakens. Tell me what I'm assuming the reader knows that I haven't established." That's a useful critique that doesn't risk flattening the voice.
The "Sent" archive — your drafting becomes future reference
A small habit that pays off: when you send a draft, copy the final version onto a "Sent" sub-page with the date and recipient. Five seconds of work. Six months later, when you're writing something similar, that archived version is searchable.
The agent makes the archive useful. "Find every email I've sent declining a project, ranked by how warmly I framed the door staying open. Pull the best two." You get a quick reference without scrolling through your sent folder. The archive becomes an evolving guide to what your actual best work looks like in each genre.
When drafting is faster, you draft more
The deeper effect of drafting in your notes vault isn't that any one draft is faster. It's that you stop avoiding drafts. The newsletter you'd been putting off because you didn't have an angle gets started because the agent surfaces three angles from your last week's material. The proposal you were dreading because of the assembly work becomes a two-hour task instead of an evening. The thank-you email you keep meaning to send to a customer gets sent because the agent draftd it from the call notes.
The compounding effect is more drafts shipped, more thinking written down, more of your actual mind on paper. The vault holds it all and stays queryable. The drafts that get sent become reference material for the drafts that come next.
A drafting practice that holds
The system only pays off if the templates exist, the source material is in the vault, and you actually use the agent. The habit is small: ten minutes when you set up — write your top three templates. Five minutes per draft — let the agent do the assembly, you do the editing. A few seconds when you send — archive the final to "Sent."
The agent doesn't replace the writing. It does the gathering and the structural draft. The voice and the judgment stay yours. You ship more, faster, and the archive grows into a working asset.
Try Docapybara free — sign up, drop in a draft you've been putting off and one past version of something similar, and ask the agent for a structural draft.