Google Sheets CRM: How to Build One in 2026

Build a google sheets crm with the right fields, formulas, views, and automations, and a clear exit to a real CRM.

0 - Minute Read

A founder has a handful of promising conversations, but the details are split between email, a notes app, and someone's memory. You want a pipeline you can use this afternoon, not another login or a setup project.

A Google Sheets CRM can give those conversations a shared home, provided the team treats the file as a temporary operating system rather than a forever template. Its value comes from clear ownership, consistent updates, and a written rule for when to move on.

When a Google Sheets CRM Is Enough

Verdict: Sheets is enough when one person owns updates and the pipeline is simple. As more people edit or the team needs structured activity history, permissions, or dependable follow-up automation, it becomes the wrong tool.

Situation

Stay in Sheets

Move on when

One person owns every update

Yes, if that person keeps each deal current

Follow-ups depend on memory or the owner can't keep the file current

Two people in one shared file

Only with one schema owner and filter views

Version conflicts or missed next steps appear

Team logging calls, emails, and meetings

Poor fit

Activities need an owner, a timeline, and permissions

Need sequences, a dialer, or an audit trail

No

Outreach and reporting must survive staff changes

The file's job is to keep the company, contact, stage, amount, owner, next step, and last touch current the same day something changes. If those fields don't help someone decide what to do next, don't add them. Sheets has a generous workbook cell limit, but slowness, conflicting edits, and missed follow-ups can become a problem long before raw capacity does.

A labour-hire agency has different handoffs and records than a small product sales team. If that's your setting, this guide to CRM tools for labour-hire panel agencies can help you compare tools built around that work. For a broader view of fitting the process to a B2B sales team, see CRM approaches for B2B sales.

Pick your row before copying any template. If the work already requires sequences, controlled access, or a reliable history of who changed what, don't try to solve that by adding columns.

Columns and Tabs That Hold the Pipeline

Start with four tabs: Companies, Contacts, Deals, and Activities. Each row should represent one record or one interaction, not a mixture of both. Keep the Dashboard out of this working schema for now.

Tab

Required columns

Field types

Why it exists

Companies

Company, Domain, Industry, Employee band, Owner, Status, Company ID

Text, dropdown, short ID

One row per account so deals don't duplicate the firm

Contacts

Full name, Email, Phone, Role, Company ID, Source

Text, email, dropdown

People stay attached to a company even when the deal changes

Deals

Deal name, Company ID, Stage, Amount, Close date, Probability, Next step, Next date, Owner

Dropdown, currency, date, text

The pipeline and the only list reviewed each week

Activities

Date, Type, Related deal, Note, Outcome

Date, dropdown, short text

A log of calls, emails, and meetings without a second tasks app

Keep account and contact records distinct

On Companies, use one row for each firm. Set Status to Customer, Prospect, or Churned, and give each company a short ID such as ACME. Put that same ID on its Contacts and Deals rows. A stable ID prevents “Acme Ltd” and “ACME” from becoming separate accounts because someone typed the name differently.

For Contacts, record the person's full name, email, phone, role, company ID, and Source. Use a clear source label such as inbound, outbound, or referral. If you're designing an intake process for a service business, this example of how doulas gather client birth preferences shows why a deliberate set of questions is more useful than a free-form notes dump.

Make each deal actionable

Keep the sales stages to New, Qualified, Proposal, Negotiation, and Won or Lost. More stages often add the appearance of precision without giving the team a different action to take. The Deals tab also needs an amount, close date, probability, owner, next step, and next date. Use dropdowns for Stage and Owner, currency for Amount, dates for Close date and Next date, and plain text for Next step.

Activities is a separate row for each Call, Email, or Meeting. Include its date, related deal, a short Note, and the Outcome. Don't add a separate Tasks tab, a product catalog, or a long notes field yet. Those additions create more places to maintain information before the team has shown it needs them.

Every open deal must have a Next date, or it doesn't belong on the board.

How to Build the Workbook in One Sitting

A woman working on a laptop, importing spreadsheet data into a CRM workbook to manage business deals.

Build the file around live work, not placeholder companies. A useful first version is plain, controlled, and easy to inspect.

  1. Create the workbook and tabs. Name the file CRM 2026 and add Companies, Contacts, Deals, and Activities. Separate tabs keep account records from deal records, so sorting or updating one doesn't scramble the other.

  2. Add the headers and freeze row one. Paste in the fields from the schema and freeze the header row on every tab. That keeps the field names visible while you scroll and makes it harder to paste data under the wrong column.

  3. Set up dropdowns with data validation. Add approved values for Status, Stage, Type, Source, and Owner. Restrict Stage to the five agreed choices, including Won and Lost. This prevents small spelling variations from breaking filters and summaries.

  4. Create Company IDs and reuse them. On Companies, enter a short ID for each account, such as ACME. Use that code on related Contacts and Deals rows. Don't rely on retyping company names to connect records.

  5. Use filter views, not whole-sheet sorts. Save a view for My open deals and another for Next date this week. A whole-sheet sort can misalign rows if someone selects only part of the data; filter views let people examine their work without rearranging the shared file for everyone.

  6. Protect the header row and Company ID column. Keep editors from renaming fields or accidentally changing account identifiers. Assign one person to approve structural changes so formulas and saved views don't stop working.

  7. Match access to the job. Give edit access to people responsible for updating records. Give comment access to people who only need to review or leave feedback. Broad editing access makes accidental changes more likely.

  8. Enter live deals, including a Lost one. Populate the file with actual work before building summaries. Include a lost deal so the team records an outcome rather than leaving every failed opportunity open indefinitely.

  9. Agree on the update rule. Before a call ends, the owner records the Next step and Next date. This prevents a promising conversation from looking active in the spreadsheet while having no planned follow-up.

You're done when the file has the agreed tabs and headers, invalid stages are rejected, and a saved filter view shows the work due this week. Test the views with real rows before inviting the team.

A short walkthrough can help you check the setup before you share it:

Formulas Views and Daily Hygiene

A spreadsheet becomes useful as a CRM when it surfaces action without making someone reread every row. Keep formulas small and visible, and check the inputs they rely on.

Pull company names and catch overdue work

Use XLOOKUP on the Deals tab to retrieve the company name from Company ID. That gives people a readable account name without making them retype it, while the ID remains the connection between records.

Set a simple rule for Next date: Won and Lost deals should have it blank; every other deal needs a date. Add conditional formatting to highlight a Next date earlier than today when the deal is still open. The color is a prompt to check the record, not proof that the owner has already followed up.

Summarize stages and pipeline

Use COUNTIF on Stage to count deals in New, Qualified, Proposal, and Negotiation. Use SUMIF to total Amount for each stage. For a weighted pipeline, multiply Amount by Probability on open deals only. Store Probability as an agreed dropdown value rather than letting each person estimate it differently.

Avoid placing ARRAYFORMULA across entire columns in a shared file. Keep calculations to the rows in use or a compact summary block; oversized formulas make troubleshooting harder and can slow editing.

For a wider set of habits that keep records usable over time, see this guide to CRM database management.

Protect the inputs

One person should own new columns and changes to the schema. Nobody should sort the whole shared sheet; use filter views instead. Add a conditional format to Contacts to flag duplicate email addresses, and flag deals with no recent activity for review rather than deleting them.

On Friday, take a short hygiene pass: fill blank owners, resolve blank Next dates on open deals, and check deals that skipped Proposal. Correct the record with the owner instead of moving a stage to make the report look tidy.

Automate Email Calendar and Follow-Ups

Automate only tasks that have a clear rule and a simple way to test. Leave judgment calls, such as whether a deal is ready for negotiation, with the owner.

Start with a small Apps Script that reacts to edits on Deals and writes an editor and date into a Last touched field. Test it on one row first. If someone renames a column or changes the sheet structure, the script may stop writing to the intended place without making the failure obvious.

Next, schedule a weekday reminder using a time-driven script, Zapier, or Make. It should email each owner a short list of open deals whose Next date is today or overdue. Keep the message focused on records that need action, not a dump of the entire pipeline. A renamed field can break the automation, so inspect the output after structural edits.

A hand filling out a CRM deal table with an update stamp, calendar, and clock icons illustrated.

For new contacts, choose one inbound route: a form, a Gmail label, or a web form that appends a Contacts row with Source set to inbound. Don't build several overlapping automations that all create records for the same person. Duplicate writes are easy to miss until the team starts contacting the same lead twice.

Calendar automation needs a clear owner, too. When Type on Activities is Meeting, you can create a Google Calendar event containing the contact and deal name. If people won't keep the calendar and sheet in sync, log the meeting after it happens instead. Two partly updated records are worse than one reliable activity log.

Don't automate stage changes, amount edits, or row deletion. Those actions need human judgment and a clear history. Zapier or Make can also start costing more as lead volume grows, and two people editing the same row can still overwrite each other. For a wider view of where automation fits in sales work, read about sales pipeline automation.

Before inviting the team, change one deal and confirm Last touched updates. Send one overdue reminder to yourself and create one test calendar event. If any test fails, fix that specific path before adding more automation.

A Monday Dashboard You Can Trust

Keep the Dashboard focused on decisions, not decoration. Use a Pivot table or a QUERY pointed at Deals so the summary stays tied to the working records rather than copied values.

Measure

What it should show

Common misread

Open deals by stage

Counts for each active stage

Counting Won or Lost as active work

Open pipeline

Amount for deals that aren't Won or Lost

Including closed deals or counting Companies as deals

Weighted pipeline

Open deal Amount multiplied by Probability

Treating a rough probability as a promise

Stuck deals

Open rows with no recent touch

Assuming a missing activity means the deal is dead

Add a compact activity line showing Call, Email, and Meeting entries from the recent working period. A quiet calendar and a large Proposal stage can mean the amounts are stale, not that the pipeline is healthy. Conversely, a small Negotiation stage with owners already scheduled for their next conversations may be in good shape.

Check the arithmetic with a small hypothetical example: an open deal worth 10,000 at 30% contributes 3,000 to weighted pipeline; another worth 20,000 at 50% contributes 10,000; one worth 5,000 at 10% contributes 500. Together, the weighted total is 13,500. Keep Won and Lost deals out of that calculation.

For more on the limits of interpreting pipeline figures, see this explanation of sales forecasting. The Dashboard is a review aid, not a forecast the team should promise to anyone.

A hand-drawn illustration of a CRM dashboard screen on a desk labeled with Monday branding.

Move to Stamina When the Sheet Breaks

Write the exit trigger into the workbook's operating notes: move when another person edits daily, the pipeline no longer fits a simple weekly review, follow-ups require sequences rather than reminders, or leadership needs to know who changed a stage. Any one of those is a reason to migrate, not to add another tab.

  1. Export each tab to CSV while its headers still match the field map.

  2. Map the records deliberately. Companies become companies, Contacts become people, and Deals become deals. Keep Company ID as the join between them.

  3. Choose what history to carry over. Activities may remain a thin history unless you import the log. Don't spend time rebuilding old notes by hand when a clean current record matters more.

  4. Freeze the spreadsheet at launch. Make it view-only when the new system goes live, so two pipelines don't drift apart.

Stamina has people, companies, and deals as objects, with pre-built fields and custom fields for text, numbers, dates, checkboxes, and dropdowns. Records can hold an activity timeline of emails, replies, calls, and meetings with AI-generated summaries and suggested next steps. Its Workflows product can enrich records, trigger sequences, route leads, and move contacts through a pipeline based on signals and replies.

Not every business needs the same kind of order management. If your work is centred on made-to-order food rather than a sales pipeline, this guide to software for cottage food preorders may help you assess that different workflow.

If your row in the opening table already says move on, export this week rather than redesigning the file.

Stamina brings people, companies, deals, activity history, and workflow automation into one system, so your team can move beyond spreadsheet reminders and manual handoffs. Visit Stamina to see whether it fits the next stage of your CRM process.

A founder has a handful of promising conversations, but the details are split between email, a notes app, and someone's memory. You want a pipeline you can use this afternoon, not another login or a setup project.

A Google Sheets CRM can give those conversations a shared home, provided the team treats the file as a temporary operating system rather than a forever template. Its value comes from clear ownership, consistent updates, and a written rule for when to move on.

When a Google Sheets CRM Is Enough

Verdict: Sheets is enough when one person owns updates and the pipeline is simple. As more people edit or the team needs structured activity history, permissions, or dependable follow-up automation, it becomes the wrong tool.

Situation

Stay in Sheets

Move on when

One person owns every update

Yes, if that person keeps each deal current

Follow-ups depend on memory or the owner can't keep the file current

Two people in one shared file

Only with one schema owner and filter views

Version conflicts or missed next steps appear

Team logging calls, emails, and meetings

Poor fit

Activities need an owner, a timeline, and permissions

Need sequences, a dialer, or an audit trail

No

Outreach and reporting must survive staff changes

The file's job is to keep the company, contact, stage, amount, owner, next step, and last touch current the same day something changes. If those fields don't help someone decide what to do next, don't add them. Sheets has a generous workbook cell limit, but slowness, conflicting edits, and missed follow-ups can become a problem long before raw capacity does.

A labour-hire agency has different handoffs and records than a small product sales team. If that's your setting, this guide to CRM tools for labour-hire panel agencies can help you compare tools built around that work. For a broader view of fitting the process to a B2B sales team, see CRM approaches for B2B sales.

Pick your row before copying any template. If the work already requires sequences, controlled access, or a reliable history of who changed what, don't try to solve that by adding columns.

Columns and Tabs That Hold the Pipeline

Start with four tabs: Companies, Contacts, Deals, and Activities. Each row should represent one record or one interaction, not a mixture of both. Keep the Dashboard out of this working schema for now.

Tab

Required columns

Field types

Why it exists

Companies

Company, Domain, Industry, Employee band, Owner, Status, Company ID

Text, dropdown, short ID

One row per account so deals don't duplicate the firm

Contacts

Full name, Email, Phone, Role, Company ID, Source

Text, email, dropdown

People stay attached to a company even when the deal changes

Deals

Deal name, Company ID, Stage, Amount, Close date, Probability, Next step, Next date, Owner

Dropdown, currency, date, text

The pipeline and the only list reviewed each week

Activities

Date, Type, Related deal, Note, Outcome

Date, dropdown, short text

A log of calls, emails, and meetings without a second tasks app

Keep account and contact records distinct

On Companies, use one row for each firm. Set Status to Customer, Prospect, or Churned, and give each company a short ID such as ACME. Put that same ID on its Contacts and Deals rows. A stable ID prevents “Acme Ltd” and “ACME” from becoming separate accounts because someone typed the name differently.

For Contacts, record the person's full name, email, phone, role, company ID, and Source. Use a clear source label such as inbound, outbound, or referral. If you're designing an intake process for a service business, this example of how doulas gather client birth preferences shows why a deliberate set of questions is more useful than a free-form notes dump.

Make each deal actionable

Keep the sales stages to New, Qualified, Proposal, Negotiation, and Won or Lost. More stages often add the appearance of precision without giving the team a different action to take. The Deals tab also needs an amount, close date, probability, owner, next step, and next date. Use dropdowns for Stage and Owner, currency for Amount, dates for Close date and Next date, and plain text for Next step.

Activities is a separate row for each Call, Email, or Meeting. Include its date, related deal, a short Note, and the Outcome. Don't add a separate Tasks tab, a product catalog, or a long notes field yet. Those additions create more places to maintain information before the team has shown it needs them.

Every open deal must have a Next date, or it doesn't belong on the board.

How to Build the Workbook in One Sitting

A woman working on a laptop, importing spreadsheet data into a CRM workbook to manage business deals.

Build the file around live work, not placeholder companies. A useful first version is plain, controlled, and easy to inspect.

  1. Create the workbook and tabs. Name the file CRM 2026 and add Companies, Contacts, Deals, and Activities. Separate tabs keep account records from deal records, so sorting or updating one doesn't scramble the other.

  2. Add the headers and freeze row one. Paste in the fields from the schema and freeze the header row on every tab. That keeps the field names visible while you scroll and makes it harder to paste data under the wrong column.

  3. Set up dropdowns with data validation. Add approved values for Status, Stage, Type, Source, and Owner. Restrict Stage to the five agreed choices, including Won and Lost. This prevents small spelling variations from breaking filters and summaries.

  4. Create Company IDs and reuse them. On Companies, enter a short ID for each account, such as ACME. Use that code on related Contacts and Deals rows. Don't rely on retyping company names to connect records.

  5. Use filter views, not whole-sheet sorts. Save a view for My open deals and another for Next date this week. A whole-sheet sort can misalign rows if someone selects only part of the data; filter views let people examine their work without rearranging the shared file for everyone.

  6. Protect the header row and Company ID column. Keep editors from renaming fields or accidentally changing account identifiers. Assign one person to approve structural changes so formulas and saved views don't stop working.

  7. Match access to the job. Give edit access to people responsible for updating records. Give comment access to people who only need to review or leave feedback. Broad editing access makes accidental changes more likely.

  8. Enter live deals, including a Lost one. Populate the file with actual work before building summaries. Include a lost deal so the team records an outcome rather than leaving every failed opportunity open indefinitely.

  9. Agree on the update rule. Before a call ends, the owner records the Next step and Next date. This prevents a promising conversation from looking active in the spreadsheet while having no planned follow-up.

You're done when the file has the agreed tabs and headers, invalid stages are rejected, and a saved filter view shows the work due this week. Test the views with real rows before inviting the team.

A short walkthrough can help you check the setup before you share it:

Formulas Views and Daily Hygiene

A spreadsheet becomes useful as a CRM when it surfaces action without making someone reread every row. Keep formulas small and visible, and check the inputs they rely on.

Pull company names and catch overdue work

Use XLOOKUP on the Deals tab to retrieve the company name from Company ID. That gives people a readable account name without making them retype it, while the ID remains the connection between records.

Set a simple rule for Next date: Won and Lost deals should have it blank; every other deal needs a date. Add conditional formatting to highlight a Next date earlier than today when the deal is still open. The color is a prompt to check the record, not proof that the owner has already followed up.

Summarize stages and pipeline

Use COUNTIF on Stage to count deals in New, Qualified, Proposal, and Negotiation. Use SUMIF to total Amount for each stage. For a weighted pipeline, multiply Amount by Probability on open deals only. Store Probability as an agreed dropdown value rather than letting each person estimate it differently.

Avoid placing ARRAYFORMULA across entire columns in a shared file. Keep calculations to the rows in use or a compact summary block; oversized formulas make troubleshooting harder and can slow editing.

For a wider set of habits that keep records usable over time, see this guide to CRM database management.

Protect the inputs

One person should own new columns and changes to the schema. Nobody should sort the whole shared sheet; use filter views instead. Add a conditional format to Contacts to flag duplicate email addresses, and flag deals with no recent activity for review rather than deleting them.

On Friday, take a short hygiene pass: fill blank owners, resolve blank Next dates on open deals, and check deals that skipped Proposal. Correct the record with the owner instead of moving a stage to make the report look tidy.

Automate Email Calendar and Follow-Ups

Automate only tasks that have a clear rule and a simple way to test. Leave judgment calls, such as whether a deal is ready for negotiation, with the owner.

Start with a small Apps Script that reacts to edits on Deals and writes an editor and date into a Last touched field. Test it on one row first. If someone renames a column or changes the sheet structure, the script may stop writing to the intended place without making the failure obvious.

Next, schedule a weekday reminder using a time-driven script, Zapier, or Make. It should email each owner a short list of open deals whose Next date is today or overdue. Keep the message focused on records that need action, not a dump of the entire pipeline. A renamed field can break the automation, so inspect the output after structural edits.

A hand filling out a CRM deal table with an update stamp, calendar, and clock icons illustrated.

For new contacts, choose one inbound route: a form, a Gmail label, or a web form that appends a Contacts row with Source set to inbound. Don't build several overlapping automations that all create records for the same person. Duplicate writes are easy to miss until the team starts contacting the same lead twice.

Calendar automation needs a clear owner, too. When Type on Activities is Meeting, you can create a Google Calendar event containing the contact and deal name. If people won't keep the calendar and sheet in sync, log the meeting after it happens instead. Two partly updated records are worse than one reliable activity log.

Don't automate stage changes, amount edits, or row deletion. Those actions need human judgment and a clear history. Zapier or Make can also start costing more as lead volume grows, and two people editing the same row can still overwrite each other. For a wider view of where automation fits in sales work, read about sales pipeline automation.

Before inviting the team, change one deal and confirm Last touched updates. Send one overdue reminder to yourself and create one test calendar event. If any test fails, fix that specific path before adding more automation.

A Monday Dashboard You Can Trust

Keep the Dashboard focused on decisions, not decoration. Use a Pivot table or a QUERY pointed at Deals so the summary stays tied to the working records rather than copied values.

Measure

What it should show

Common misread

Open deals by stage

Counts for each active stage

Counting Won or Lost as active work

Open pipeline

Amount for deals that aren't Won or Lost

Including closed deals or counting Companies as deals

Weighted pipeline

Open deal Amount multiplied by Probability

Treating a rough probability as a promise

Stuck deals

Open rows with no recent touch

Assuming a missing activity means the deal is dead

Add a compact activity line showing Call, Email, and Meeting entries from the recent working period. A quiet calendar and a large Proposal stage can mean the amounts are stale, not that the pipeline is healthy. Conversely, a small Negotiation stage with owners already scheduled for their next conversations may be in good shape.

Check the arithmetic with a small hypothetical example: an open deal worth 10,000 at 30% contributes 3,000 to weighted pipeline; another worth 20,000 at 50% contributes 10,000; one worth 5,000 at 10% contributes 500. Together, the weighted total is 13,500. Keep Won and Lost deals out of that calculation.

For more on the limits of interpreting pipeline figures, see this explanation of sales forecasting. The Dashboard is a review aid, not a forecast the team should promise to anyone.

A hand-drawn illustration of a CRM dashboard screen on a desk labeled with Monday branding.

Move to Stamina When the Sheet Breaks

Write the exit trigger into the workbook's operating notes: move when another person edits daily, the pipeline no longer fits a simple weekly review, follow-ups require sequences rather than reminders, or leadership needs to know who changed a stage. Any one of those is a reason to migrate, not to add another tab.

  1. Export each tab to CSV while its headers still match the field map.

  2. Map the records deliberately. Companies become companies, Contacts become people, and Deals become deals. Keep Company ID as the join between them.

  3. Choose what history to carry over. Activities may remain a thin history unless you import the log. Don't spend time rebuilding old notes by hand when a clean current record matters more.

  4. Freeze the spreadsheet at launch. Make it view-only when the new system goes live, so two pipelines don't drift apart.

Stamina has people, companies, and deals as objects, with pre-built fields and custom fields for text, numbers, dates, checkboxes, and dropdowns. Records can hold an activity timeline of emails, replies, calls, and meetings with AI-generated summaries and suggested next steps. Its Workflows product can enrich records, trigger sequences, route leads, and move contacts through a pipeline based on signals and replies.

Not every business needs the same kind of order management. If your work is centred on made-to-order food rather than a sales pipeline, this guide to software for cottage food preorders may help you assess that different workflow.

If your row in the opening table already says move on, export this week rather than redesigning the file.

Stamina brings people, companies, deals, activity history, and workflow automation into one system, so your team can move beyond spreadsheet reminders and manual handoffs. Visit Stamina to see whether it fits the next stage of your CRM process.

Share this article

Share this article

Send a shareable link to your team or anyone who might find it useful.

Send a shareable link to your team or anyone who might find it useful.

Copy link

Copied

Share directly to

Table of contents

Give Your Business the Stamina it needs to Thrive