Short answer
If you do not have a full CRM process yet, start with a Jotform-to-Google-Sheets intake workflow. It gives you one structured place to see new leads, project details, status, owner, and next action. Then use Make only for the handoffs that are worth automating.
Who this workflow is for
- Freelancers and consultants who collect project details before a call.
- Small agencies that need to route quote requests to the right person.
- Local service businesses that want fewer messy email threads.
- Cross-border sellers or service teams that need a simple shared lead tracker.
This workflow is not meant to replace a CRM forever. It is a low-friction way to stop losing details while you are still shaping the sales process.
The workflow map
| Step | Tool | What should happen |
|---|---|---|
| 1. Customer submits details | Jotform | Capture the required intake fields without asking for everything at once. |
| 2. Submission becomes a row | Google Sheets | Store each request in a shared tracker with status and owner fields. |
| 3. Automation checks the row | Make | Clean the data, apply conditions, and decide which next step should run. |
| 4. Owner gets notified | Email, Slack, or task app | Send only the details needed to take the next action. |
| 5. Qualified leads move forward | CRM or email tool | Create a contact, add a tag, or start a follow-up sequence when the lead is ready. |
What to collect in the form
Ask for enough information to route the request, but not so much that good leads abandon the form. A practical intake form usually includes contact details, project type, timeline, budget range, file upload if needed, and one open-ended question.
- Name, email, company, and website.
- Service or product interest.
- Timeline, budget range, or urgency level.
- Current problem or desired outcome.
- File upload only when it directly helps the next step.
Google Sheets columns to start with
| Column | Purpose |
|---|---|
| Submitted date | Shows how long the lead has been waiting. |
| Name and email | Basic contact identity. |
| Service interest | Helps sort requests by offer or team. |
| Budget or project size | Helps prioritize without deleting smaller opportunities. |
| Source | Shows whether the lead came from ads, referral, SEO, social, or partner links. |
| Status | New, reviewed, replied, booked, quoted, won, lost, or paused. |
| Owner | The person responsible for the next step. |
| Next action date | Prevents the request from disappearing after the first reply. |
| Notes | Short context that does not fit neatly into structured fields. |
How Make fits into the workflow
Make is useful when the intake workflow needs more than a direct form-to-sheet sync. For example, you can send high-value requests to a different inbox, create a CRM contact only when the email field is valid, or notify the owner when a lead asks for a fast timeline.
Use Make for the handoff, not the whole business
Start with one scenario: new Jotform submission, add or update a Google Sheets row, then send an internal notification.
Step-by-step setup
- Create the Jotform form and keep required fields limited to what the team truly needs.
- Create a Google Sheet with clear column names before connecting anything.
- Send a few test submissions and check whether the data is readable in the sheet.
- Create a Make scenario that watches new submissions or new rows.
- Add a step that formats important fields such as name, email, timeline, and source.
- Add one notification step for the owner or team inbox.
- Test with realistic examples, including missing fields and duplicate emails.
- Turn it on only after you know what happens when a form is incomplete.
Common mistakes
Too many form questions. Long forms create better internal records but fewer completed submissions. Keep the first version lean.
No status field. A spreadsheet without status quickly becomes another inbox. Add simple stages from day one.
No owner field. If nobody owns the row, nobody owns the follow-up.
Automating before the workflow is clear. If the team does not know what should happen manually, Make will only move confusion faster.
When to move from Sheets to a CRM
Google Sheets is a good starting point, but it becomes fragile when multiple people are editing records, leads need repeated follow-ups, or you need a clear pipeline view. Move to a CRM when you need deal stages, reminders, contact history, and reporting that a sheet cannot reliably maintain.