Get AI summaries of any video or article — Sign up free
A System For Winning More Freelance Proposals [Notion Template Linked] thumbnail

A System For Winning More Freelance Proposals [Notion Template Linked]

Landmark Labs·
5 min read

Based on Landmark Labs's video on YouTube. If you like this content, support the original creators by watching, liking and subscribing to their content.

TL;DR

Use the template’s “key project outcomes” field to mirror the client’s stated goals, then back it up with specific “key deliverables.”

Briefing

A strong freelance proposal does two jobs at once: it helps clients understand and feel confident about what’s being proposed, and it creates a clear record of agreed scope, outcomes, and timeline for later reference. To make that repeatable, the workflow centers on a pre-built Notion project proposal template that’s designed to be edited quickly, shared in multiple formats, and tracked over time.

The template is built around filling in a few key fields. A proposal title anchors the document, while highlighted bracketed sections are meant to be replaced with the freelancer’s own wording or adjusted using provided dummy text. The proposal summary section focuses on the project’s core business details: expected start and completion dates, budget, and a set of “key project outcomes” written in the client’s language. Those outcomes are intentionally framed as what the client wants to achieve—such as improving website click-through rates—rather than generic deliverables like “build a new website.”

Deliverables get more concrete. The “key deliverables” area lists what the client will actually receive at the end of the engagement, including tangible assets and, if relevant, calls such as discovery or consultation sessions. The template also supports a project overview that can be shown as a timeline (with phases like discovery/positioning/market research, build, and handover) or switched to a table view. A callout box can be used to flag scheduling needs for specific phases, and additional sections can be added or removed depending on the freelancer’s service style.

To set expectations, the proposal includes a “how we’ll work together” section where terms like NDAs, process steps, and payment structure can be specified—whether payments are fully up front, split into milestones, or handled in another agreed division. The document ends with final words and next steps so the client knows what happens after reviewing the proposal.

Sharing options are built in. The proposal can be sent as a Notion page by entering the client’s email address, with permission settings that typically prevent duplication as a template, allow comments, and avoid search engine indexing for sensitive documents. If appropriate, it can also be published to the web via Notion’s publishing feature. For broader compatibility, it can be exported as a PDF.

For repeat business, proposals are tracked in an “all proposals” database. Creating a new proposal from that database preloads the template and lets the freelancer attach context such as the client name, bid information, and links to relevant intro calls or websites. Instead of a standalone status field, the system can link proposals to bids and other records and optionally connect to an external or internal CRM using Notion relation fields. That CRM linkage enables sorting contacts by outreach status and tracking proposal stages such as “proposal sent,” with the overall flow described as moving through conversation, active, or archived states.

Cornell Notes

The workflow uses a pre-built Notion project proposal template to turn client conversations into a structured, editable proposal that’s easy to share and later verify. Key fields include timeline, budget, client-specific outcomes, and concrete deliverables, plus a project overview (timeline or table) and a “how we’ll work together” section covering NDAs, process, and payment terms. Sharing can be done as a Notion page (email or web publishing with careful permissions) or exported as a PDF. Proposals are tracked in an “all proposals” database and can be linked to bids, intro calls, and websites for context. For deeper tracking, proposals can connect to a CRM via Notion relation fields so contact and proposal status can be managed alongside other pipeline data.

How does the template make proposals more persuasive and less vague?

It separates “key project outcomes” from generic deliverables. Outcomes are written in the client’s own goals—e.g., improving click-through rates—so the proposal reflects what the client explicitly wants to achieve. Deliverables then list what will be handed over at the end (assets, decks, or even calls like discovery/consultation), making the scope concrete.

What sections help a client visualize how work will progress?

The “project overview” section supports a timeline view with phase callouts such as discovery/positioning and market research, then build, then final handover and delivery. It can also switch to a table view. The template allows adding or removing distinct sections so the structure matches the freelancer’s service model.

What expectation-setting details should be included beyond scope?

The “how we’ll work together” guidance is where NDAs, process steps, and payment terms are specified. It’s also where the proposal can clarify payment timing and structure (for example, fully up front or split into percentages) and outline next steps after the client reviews the proposal.

What are the main ways to share the proposal from Notion, and how should permissions be handled?

A Notion page can be shared by entering the client’s email address, with permissions typically preventing duplication as a template, allowing comments, and avoiding search engine indexing for sensitive documents. If sharing publicly is acceptable, Notion publishing can be used. For compatibility, the proposal can be exported to PDF via the export option in the top-right menu.

How does the system track proposals after they’re sent?

Proposals are managed in an “all proposals” database. A new proposal page is created from that database, preloading the template and capturing fields like client name, bids, linked intro calls, and related websites. Returning to the database later provides a history of what was proposed and connected context.

Why isn’t a standalone proposal status field required in the database?

Status can be handled through relationships to other records and, optionally, through a linked CRM. By using Notion relation fields, proposals can connect to CRM contacts and other pipeline data, enabling sorting by outreach status and tracking stages like “proposal sent,” then conversation/active/archived flow.

Review Questions

  1. When writing “key project outcomes,” what should be prioritized over simply describing the service (e.g., “build a new website”)?
  2. What permission choices matter most when sharing a sensitive proposal as a Notion page?
  3. How does linking proposals to a CRM change how status and contact tracking can be managed?

Key Points

  1. 1

    Use the template’s “key project outcomes” field to mirror the client’s stated goals, then back it up with specific “key deliverables.”

  2. 2

    Populate timeline and budget early so the proposal sets clear expectations before the client commits.

  3. 3

    Use the project overview timeline (or table view) to show phases such as discovery, build, and handover in a way clients can quickly scan.

  4. 4

    Add expectation-setting terms in “how we’ll work together,” including NDA willingness, process steps, and payment structure.

  5. 5

    Share proposals as Notion pages with controlled permissions (no template duplication, comments allowed, avoid search indexing for sensitive docs) or export as PDF.

  6. 6

    Track each proposal in an “all proposals” database and link it to bids, intro calls, and relevant websites for context and follow-up.

  7. 7

    If a CRM is available in the Notion workspace, link proposals via relation fields to manage contact and proposal stages alongside the rest of the pipeline.

Highlights

The template’s core improvement is separating client-specific outcomes from generic deliverables, so the proposal reads like it’s built from the client’s priorities.
A timeline-based project overview lets clients see work phases at a glance, with optional callouts for scheduling needs.
Notion sharing is treated as a permissions problem: duplication is typically blocked, comments are allowed, and search indexing is avoided for sensitive proposals.
Proposal tracking is strengthened by linking context—bids, intro calls, and websites—inside an “all proposals” database.
CRM integration is handled through Notion relation fields, reducing the need for a standalone status field and enabling pipeline-style sorting.

Topics

  • Freelance Proposals
  • Notion Template
  • Client Outcomes
  • Proposal Tracking
  • CRM Integration