Automate Lead → Invoice with Make

Freelancers do not need a 40-module enterprise scenario. They need a reliable path from someone showed interest to invoice sent and logged. Make (formerly Integromat) is a strong fit when that path has branches: qualify → nurture or book → proposal → won/lost → invoice → reminder.

This guide is a step workflow you can adapt — not a single universal blueprint. Tools named below are examples; swap for what you already pay for. For platform choice, read Make vs Zapier and Zapier alternatives.

Outcome map

Stage	Automation job	Human job
Lead in	Capture + tag source	Skim spam / bad fit
Qualify	Route by budget/size	Decide pursue / pass
Booked	Create project stub	Run discovery
Proposal	Task + reminder	Write & send proposal
Won	Create invoice draft	Confirm amounts
Paid	Mark won + file	Say thanks / kickoff

AI can draft proposal or follow-up text inside this pipeline — see proposal follow-ups and AI invoice generators — but money fields stay human-approved.

Prerequisites

A form or scheduler (Tally, Typeform, Calendly, etc.)
A place for records (Airtable, Notion database, HubSpot free, Google Sheet)
Invoicing tool with an API/module Make supports (or email + manual create as interim)
Clear statuses: new, qualified, proposal_sent, won, lost, invoiced, paid

Draw the statuses on paper before opening Make. Most “automation debt” is fuzzy status design.

Scenario overview (modules)

Trigger: New form submission / new booked call
Normalize: Map fields to your CRM schema
Filter: Hard disqualifiers (e.g., “student project, $50 budget”)
Create/update record in CRM
Notify: Slack/email to you with a one-screen summary
Router: Path A booked call vs Path B nurture
After proposal sent (manual status change or button): schedule follow-up tasks
On won: create invoice draft + folder/doc links
On invoice sent: schedule reminder if unpaid
On paid: update status, optional kickoff checklist

Build this in vertical slices. Ship steps 1–5 this week; add invoicing after your CRM statuses are trustworthy.

Step-by-step build

1. Capture clean inputs

Required form fields that save future pain:

Name, email, company
Project type (controlled list)
Budget band (bands beat free text)
Deadline / urgency
How they found you
Checkbox consent for email follow-up

Optional: link to brief or deck. Avoid twenty optional fields that drop conversion.

2. Deduplicate

Before creating a new CRM row, search by email. Update existing leads instead of cloning them. Freelancers get the same person from Instagram, referral, and form — duplicates break invoice history.

3. Qualification filter

Use Make filters:

Budget band below your floor → status lost_auto + polite pass template
Enterprise-looking domain + high budget → priority notify
Missing email → halt (do not invent)

4. Project stub on qualified

When status becomes qualified or a call is booked:

Create Notion/Airtable project with empty discovery notes
Attach UTM/source
Create a kickoff doc from template

5. Proposal reminders (not auto-send)

When you set proposal_sent (manually or via a “sent” button in your CRM):

Schedule a task at +4 business days: “Follow up proposal — ”
Optional: generate a draft email in Gmail/Drafts for you to edit

Do not auto-email commercial follow-ups until you trust the copy. Drafts beat regrets.

6. Won → invoice draft

On won:

Pull fee, currency, line items from the CRM fields you typed
Create invoice draft in your invoicing tool
Notify you: “Approve & send invoice for ”

Auto-send invoices only if your amounts are formula-perfect and tax settings are correct. Most solos should approve once.

7. Payment reminders

If status invoiced and unpaid after N days:

Reminder task or draft reminder email
Escalate once, then personal nudge

Keep tone aligned with how you actually speak. Paste AI drafts carefully.

8. Paid → close the loop

On paid (Stripe webhook, invoicing module, or manual status):

Status paid
Create kickoff checklist
Optional: invite to shared folder / Slack connect

Error handling Make users skip

Incomplete data paths: If invoice amount empty, route to error Slack — do not create $0 invoices
Idempotency: Prevent double invoices on status flicker (search existing open invoice first)
Timezone: Business-day delays matter for follow-ups
Secrets: API keys in Make connections, not in scenario hardcoding shared with freelancers you hire later

How AI fits without breaking trust

Useful:

Summarize form answers into a CRM “snapshot” field
Draft discovery questions
Draft follow-up emails into Drafts

Risky:

Auto-pricing from vague form text
Auto-sending contracts or invoices
Uploading full contract PDFs into random AI modules without policy review — see AI contract review

Minimal viable scenario (weekend build)

If you only have four hours:

Form → CRM row + email notify
Manual status proposal_sent → create reminder task in Todoist/Notion
Manual status won → Slack you “create invoice”
Stripe/invoice paid → status update

That already removes the “I forgot to follow up / invoice” failure mode — the expensive one — without boiling the ocean.

Testing checklist

Submit fake lead → appears once in CRM
Disqualified lead does not create invoice path
Proposal reminder fires only after status change
Won with missing amount fails safely
Paid webhook/update does not duplicate kickoff tasks

Bottom line

Make shines when your lead → invoice path has filters and branches. Start with capture, dedupe, notify, and status hygiene; add invoice drafts and reminders second. Keep humans on money and client-facing sends. For broader tool context, see best AI automation tools for small business.