Week 8 of 8

Lead Capture Assets: Forms, Documents, QR Codes, and Social Media

Forms, documents, QR codes, and social media are the assets that feed the completed CRM system from the front end. Build them last, once the structure behind them is ready.

By this week the CRM has pipelines, tags, communication plans, calendars, workflows, and clean data. Only now is it safe to build the front-end assets that will send new contacts into that structure.

Every lead capture asset should have a defined path: what fields it collects, what tag it applies, which workflow catches it, which pipeline stage it creates, and what the contact receives immediately after.

This is the final week because lead capture assets should not be built before the system behind them exists. A form, QR code, document, or social media post is only useful if the contact lands in the right place, receives the right follow-up, gets the right source tag, and moves through the right pipeline path.

Why This Matters

Front-end assets built in isolation create orphan contacts with no follow-up. Every form, QR code, or social post should have a defined path into the CRM.

What Usually Goes Wrong

Forms with no workflow connection
QR codes pointing to a page that no longer exists
Social posts driving traffic to a form with no thank-you action
Documents sent without a tracked status
No source tag, so lead source reporting is impossible
Duplicate forms across pages that quietly compete for the same lead

The Completed System Behind Every Asset

Every lead capture asset should connect back to the structure built in the previous weeks.

Before publishing any asset, confirm:

Week 1: Which pipeline and stage should this create or update?
Week 2: Which tags, custom fields, or custom values does this need?
Week 3: What communication should happen immediately after submission?
Week 4: Should this lead book an appointment?
Week 5: Which workflow catches and routes this lead?
Week 6: Is the data clean, properly sourced, and safe to contact?
Week 7: Is there an email or campaign follow-up connected to this path?

Note

This is why lead capture assets come last. The front end should feed a system that is already ready.

Forms: Rules Before You Build

Only collect fields the workflow actually needs
Add a consent line that describes what the contact will receive
Always connect the form to a workflow with a source tag and an opportunity action
Set a thank-you action: a page, a redirect, or an inline message
Test the full path with a test contact before publishing

Good form fields

Name
Email
Phone, if SMS or calling is part of follow-up
Business name, if relevant
Service or interest
One qualifying question
Consent checkbox or consent language
Optional notes field, only if the team will use it

Bad form fields

Questions no one reviews
Long intake questions before the person has committed
Sensitive information that is not needed yet
Duplicate fields already captured elsewhere
Fields that do not map cleanly into the CRM

A form should be short enough to complete and structured enough to route the lead correctly.

Thank-You Actions and Confirmation Paths

A form submission should never end with silence.

After submission, decide what the person sees or receives:

Inline thank-you message
Redirect to a thank-you page
Redirect to a calendar booking page
Confirmation email
Short SMS confirmation, if consent exists
Download or resource delivery
Internal notification to the team
Pipeline stage creation or update

Note

The thank-you action should match the promise made on the page, post, QR code, or form. If the asset says “get the guide,” the guide should be delivered. If it says “book a call,” the next step should make booking obvious.

Documents and Signed Assets

Documents include proposals, agreements, estimates, intake forms, applications, waivers, onboarding forms, and other assets that need to be sent, viewed, completed, approved, or signed.

Documents should not disappear after they are sent. They should have a tracked status so the team can see what happened.

Proposal sent

Moves the opportunity to Proposal Sent.

Proposal signed

Moves the opportunity to Won or Onboarding.

Application completed

Creates an internal review task.

Document declined

Creates a follow-up task or Lost / Not a Fit stage.

Draft
Sent
Viewed
Completed
Signed
Declined
Expired
Needs review

Note

A signed document is not just a file. It is a business event that should update the CRM.

QR Codes

QR codes are physical-world entry points into the CRM. Treat them like campaigns, not decorations.

Point every QR code to a URL you control, not a third-party shortener
Use a unique link per placement so the source tag identifies where the scan happened
Test every QR code on a real phone before it goes to print or public display
Plan for what happens if the destination URL changes later
Document where it will appear
Document what URL it points to
Document what source tag it applies
Document what form, calendar, or page it opens
Document what thank-you action happens
Document what workflow catches the lead
Document who owns replacing it if the destination changes

Note

Use different QR links for different placements when reporting matters. A QR code on a trade show flyer should not use the same source as a QR code on a front desk sign.

Social Media Paths

Every social post that asks for action should point to a specific CRM path: a form, a booking link, a document request. Generic 'DM us' or 'visit our site' posts leak leads.

A social media path should be specific enough that the CRM can understand where the lead came from.

Use per-channel source tags (source-instagram, source-linkedin) via unique links
Confirm the destination has a working thank-you and workflow
Match the message tone across the post, the destination, and the confirmation
Instagram post → landing page form → source-instagram
LinkedIn post → consultation calendar → source-linkedin
Facebook ad → lead form → source-facebook-ad
TikTok bio link → offer page → source-tiktok
YouTube description link → training signup form → source-youtube

Note

Avoid sending every post to the homepage unless the homepage is the correct conversion path. A clear post should lead to a clear destination.

Asset Testing Checklist

Before any asset goes public, test the full path like a real contact.

For each asset, verify:

The link opens correctly
The page loads on mobile
The form submits correctly
The thank-you action works
The contact is created or updated correctly
The source tag is applied
The correct pipeline stage is created or updated
The correct workflow starts
The immediate confirmation sends
The internal notification sends
The booking link works, if used
The document status updates, if used
The unsubscribe or consent language appears where needed
The reporting source is visible

Note

Do not publish the asset until the full path works from click or scan to CRM record.

Reporting Back to Source

The whole reason to tag by source is so the business knows what actually produces leads and clients. Once these assets are live, the team can finally answer where leads come from, which sources convert, and where to invest more.

Source reporting should help the business answer:

?Which form produced the lead?
?Which QR placement produced the scan?
?Which social channel produced the contact?
?Which campaign produced the booking?
?Which source produced the highest-quality opportunities?
?Which source created leads but no clients?
?Which asset should be improved, paused, or scaled?

Note

The goal is not just to count leads. The goal is to understand which assets create real business outcomes.

What to Build

Forms with clear required fields, consent, thank-you actions, and workflow connections
Documents used for the right scenarios and tracked to completion
QR codes that point to controlled URLs with source tracking
Social paths that tie each post or channel to a specific CRM destination
Unique source tags or source values for each meaningful asset
Pipeline and workflow connections for every asset
Immediate contact confirmation and internal notification paths
A mobile testing routine for every asset
A source reporting view that ties leads back to the asset that produced them
A final system audit showing how Weeks 1 through 7 connect to the asset

Before You Build in the CRM

Plan the lead capture path before creating the asset. Do not start with the form builder, document tool, QR generator, or social planner. Start with the path.

Start outside the CRM. Use a document, spreadsheet, whiteboard, Figma board, or your preferred AI assistant to map the full lead capture journey. Put the asset on the left, then map the destination, fields, source tag, pipeline stage, workflow, confirmation message, internal notification, and reporting view.

Your lead capture plan should answer:

?What is this asset supposed to accomplish?
?Where will this asset be used?
?Who is the intended audience?
?What destination should it send people to?
?What fields need to be collected?
?What fields should not be collected?
?What consent language is needed?
?What source tag should be applied?
?What custom field should be updated?
?What pipeline stage should be created or updated?
?What workflow should start?
?What communication should the contact receive immediately?
?What internal notification should the team receive?
?What thank-you action should happen?
?What happens if the person books?
?What happens if the person does not book?
?How will this asset show up in reporting?
?How will this path be tested before launch?

Note

Suggested AI prompt: “I am planning a CRM lead capture asset before building it. Help me map the full path for a form, document, QR code, or social media link. Identify the destination, fields to collect, fields to avoid, source tag, custom fields, pipeline stage, workflow, confirmation message, internal notification, thank-you action, consent language, booking path if needed, reporting view, and full testing checklist. Make sure the asset connects cleanly to the CRM system already built.” Lead capture assets should feed the CRM system, not create disconnected contacts.

Step-by-Step Training

1
Decide what the front-end asset should accomplish inside the CRM.
2
Identify the audience and source.
3
Choose the asset type: form, document, QR code, social path, booking link, or landing page.
4
Decide what destination the asset should point to.
5
Decide which fields need to be collected.
6
Remove fields that are not needed.
7
Add consent language where needed.
8
Decide the source tag or source value.
9
Decide which pipeline stage should be created or updated.
10
Decide which workflow should catch the lead.
11
Decide what confirmation the contact should receive.
12
Decide what internal notification the team should receive.
13
Configure the thank-you action.
14
Build the form, document, QR code, or social path.
15
Test the path on desktop and mobile.
16
Send a test lead through the full path.
17
Confirm the contact record, tags, fields, pipeline stage, workflow, notification, and confirmation all work.
18
Confirm the source reporting view captures the lead correctly.
19
Turn on the asset publicly only after the end-to-end test passes.
20
Document the asset and where it is used.

Practical Exercise

Part 1: Build the Form and Its Path

Create the form and every downstream action:

1
Draft required fields
2
Remove unnecessary fields
3
Add consent language
4
Build the form
5
Configure the thank-you action
6
Connect the workflow
7
Apply source tag
8
Create or update opportunity
9
Send internal notification
10
Send contact confirmation
11
Test the full submission path

Part 2: Extend the Path to QR and Social

Now expand the same path to physical and social channels:

1
Generate a QR code with a unique source link
2
Test the QR code on a real phone
3
Create a social post per channel with unique source links
4
Send a test lead through each channel
5
Confirm the correct source tag lands in the CRM
6
Confirm the correct workflow starts
7
Confirm the correct pipeline stage updates
8
Confirm the thank-you action works

Part 3: Final System Audit

Review the asset against the full 8-week system:

1
Pipeline stage is correct
2
Tags and fields are correct
3
Communication path is correct
4
Calendar path is correct if booking is involved
5
Workflow starts and stops correctly
6
Imported or existing contacts are handled safely
7
Email follow-up is connected if needed
8
Source reporting is visible
9
Mobile experience works
10
Team notification works
11
The path can be explained clearly to another person

Done Means Done Checklist

✓The asset has a clear purpose
✓The intended audience is defined
✓The destination is correct
✓The form only asks for necessary fields
✓Consent language is included where needed
✓The thank-you action is tested
✓The workflow is connected and tested
✓The source tag or source value is applied
✓The contact enters the CRM correctly
✓The correct tags and fields are applied
✓The correct pipeline stage is created or updated
✓The correct confirmation message sends
✓The correct internal notification sends
✓The booking link works if used
✓The document status updates if used
✓The QR code works on a real device
✓The social post points to the correct destination
✓Desktop and mobile paths are tested
✓Source reporting is visible and useful to the team
✓The full path can be explained from asset to CRM outcome

Common Mistakes

Watch for these

Publishing a QR code before testing it
Building a form and forgetting the workflow that catches it
Sending documents without a tracked status
Posting on social without a specific CRM destination
Reusing the same generic source tag across every asset
Building lead capture assets before the CRM structure is ready
Using the same generic form for every offer
Collecting fields the team never uses
Forgetting the thank-you action
Sending QR codes directly to temporary or uncontrolled URLs
Printing QR codes before testing them
Posting on social without a source-specific path
Using one generic source tag for every channel
Forgetting to connect document status to pipeline movement
Not testing the asset from a real phone
Not checking the contact record after submission
Launching the asset before workflow and reporting are verified

Related SOPs

Forms and Surveys
Social Planner
Payments and Documents
Workflows
Pipelines and Opportunities
Tags and Custom Fields
Calendars
Email Campaigns
Conversations

Final System Check

Before you consider the 8-week build complete, confirm the system can answer these questions:

?Where do leads enter?
?What pipeline stage do they enter?
?What tags and fields are applied?
?What communication do they receive?
?What calendar path do they follow?
?What workflow routes them?
?What data hygiene rules protect the record?
?What campaign or follow-up happens next?
?How does the team know what happened?
?How does the business report on the source?

Note

If the system can answer those questions clearly, you have built more than a CRM. You have built an operating path the team can understand, maintain, and improve.

You have reached the end

You finished the 8-week Build-Before-Automate training path.

You now have the structure to keep improving the CRM without guessing: pipelines, tags, fields, communication maps, calendars, workflows, clean data, campaigns, and lead capture assets.

Next step:

Explore the SOP Library Review the Templates Run a quarterly CRM audit