Resources

Wave CRM: Features, Sales Pipeline, and Product Demo

Explore Wave CRM: contacts, companies, sales pipelines, prospecting, outreach, and proposals. See all the feature areas and watch the product demo.

Taylor Owen
16 min read

Wave CRM brings contacts, companies, deals, prospecting, and proposals into one workspace. Keep track of who you are talking to, which account they belong to, what an opportunity is worth, and what needs to happen next.

A useful CRM should help the next conversation. Before a call, you should be able to find the decision-makers, review the previous discussion, see the proposal, and understand who owns the follow-up. Wave CRM connects those records with the communication and execution tools around them.

This guide covers Wave CRM’s feature areas, from contact and account management to sales pipelines, outreach, proposal creation, and reporting. The product demo follows a fictional team working with Cedar Labs on a 30-person workspace rollout.

Watch the Wave CRM product demo

The 42-second showcase uses a populated sample workspace with eight companies, 12 contacts, nine deals, six proposals, and an eight-person prospect list. It follows the relationship from a pipeline overview into contact details, conversation logs, deal notes, prospecting, and proposal tracking.

Illustrative demo built with Wave’s actual UI components and fictional data. Navigation and scene layouts are composed for the presentation. No customer records were changed, outreach sent, or proposals shared.

What is Wave CRM?

Wave CRM is the customer relationship workspace inside Wave. Contacts represent people; companies represent the accounts they belong to; deals represent opportunities with a value, owner, and pipeline stage. Prospecting helps organize potential customers and outreach, while Proposals supports the documents that carry an opportunity toward a decision.

These objects serve different purposes. Morgan Lee is a contact. Cedar Labs is the company. The Cedar team workspace opportunity is a deal. Its $36,000 proposal is a separate document linked to the relationship. Keeping those distinctions clear makes the records useful as the buying team or scope changes.

CRM sits alongside Wave’s other tools, including Mail, Phone, Projects, and Chat. Connected communication, account tasks, and shared work can provide the context around a customer relationship. Available actions depend on workspace access, connected accounts, and the services configured for your organization.

Explore the guide: Contacts and companies · Customer context · Deals · Prospecting · Proposals · Getting started · FAQs

Manage contacts and companies

1. Contact records with useful identity details

Contact records hold the information needed to recognize and reach a person: name, job title, email, phone, location, and associated company. Expanded properties and identity editing support additional details such as separate name fields, office and mobile numbers, website, address information, and birthdate.

Start with the details that affect the next interaction. In the demo, Morgan Lee is Cedar Labs’ VP Operations and the owner of the workspace evaluation. That role gives the team context for the questions Morgan asks and the people who should join the proposal review.

Contact information can change during a sales process. Keep the person’s role and company association current so the record remains useful after the first conversation.

2. Company records for the account behind the people

Company records provide an account view with a name, website or domain, primary contact information, location, company size, revenue field, description, and owner. Expanded properties include industry and additional business and social information when available.

The Companies table makes the account list scannable. It shows the company, log count, status, revenue, size, and owner. Inline controls let the team update key properties without opening every record.

Use the company record to explain the account, then link the people involved. Cedar Labs has both Morgan Lee and engineering lead Reese Miller associated with the opportunity, giving the team a clearer view of the buying group.

Wave CRM Companies table with eight fictional accounts, lifecycle statuses, revenue, company sizes, and owners.
A populated company list keeps account status and ownership visible. Fictional demo data.

3. Separate lifecycle statuses for contacts and companies

Wave uses different status sets for people and accounts. Contacts can be New, Contacted, Engaged, Unresponsive, Do Not Contact, or Inactive. Company statuses include Lead, Prospect, Active, Churned, and Lost.

This distinction supports a realistic relationship. An active customer can have a newly introduced contact. A prospect account can have one engaged stakeholder and another person who has not responded. A company’s lifecycle does not have to overwrite each person’s situation.

Agree on what each status means for your team. Update it when the relationship changes, and use the status as context for the next action.

4. Owners, labels, and linked relationships

Assign an owner to a company, contact, or deal so responsibility is visible. Labels help describe the relationship, and associated company, contact, and deal fields connect the records that belong together.

In the sample pipeline, Alex Rivera owns the Cedar opportunity and Morgan’s relationship. The deal includes Cedar Labs and both relevant contacts. A teammate can see who should coordinate the next step without searching through a separate spreadsheet.

Ownership is most useful when it means something operational: who updates the record, who responds to the customer, and who makes sure the next agreed action happens.

5. Search, filters, display controls, and favorites

CRM tables include search and filtering controls to narrow a growing record list. Display controls let you choose which groups or statuses to show where supported. Favorites provide quick access to records you return to often.

Use a focused view for a specific job, such as reviewing active prospects or checking the accounts assigned to one owner. Keep the main record as the source of context instead of creating disconnected copies for each review.

The demo favorites Morgan Lee and the New Business pipeline because the team is actively preparing the Cedar proposal review.

Keep the customer’s context with the record

6. Profile overviews and relationship highlights

Contact and company profiles bring related information together. Overview highlights include the associated company where relevant, connection strength, and the last email interaction. Related proposals give the team a direct route to the documents connected to that relationship.

Connection strength is a contextual indicator based on available identity and email activity. It is not a promise that a deal will close. Use it alongside the actual conversations and the customer’s stated decision process.

For Cedar Labs, the overview helps the team move from “Who is Morgan?” to “What have we discussed, and which proposal are we reviewing?”

Wave CRM contact profile for fictional Morgan Lee with identity details, company context, a linked proposal, and conversation logs.
A contact profile brings the person, account context, linked proposal, and conversation history together.

7. Email context from connected Mail accounts

The Emails area surfaces messages associated with the contact or company through the connected Mail experience. The overview can also show recent email interactions, helping the team pick up the conversation with the right context.

This is useful before a meeting or handoff. Check what the customer asked, which document was discussed, and whether the team has already responded. Contact and company identity information helps connect the correct messages.

Email visibility depends on the accounts, access, and message data available in your workspace. Connect the appropriate Mail account and keep the CRM identity fields accurate.

8. Conversation logs, replies, and reactions

Logs record the substance of an interaction: a request, feedback, an idea, a bug or issue, or a complaint. Log entries include their author and time, and support replies, reactions, and supporting resources.

A call can produce a feedback log even when the call itself happened elsewhere. In the demo, Alex records Morgan’s priorities, the phased rollout plan, and the next proposal review. The entry gives another teammate enough detail to continue the work.

A practical log answers three questions: what did we learn, what did we agree, and what happens next? Keep the customer’s actual words or requirements clear when they affect the proposal.

9. Notes and files for durable reference material

Profile Notes and Files keep supporting material close to the relationship. Use notes for a discovery summary, account plan, implementation requirements, or decisions that need to outlast a single conversation.

Files and resources provide a place for the material behind the discussion. A requirements document, rollout brief, or customer reference should be attached where the team will look for it.

Separate the current agreed plan from the history that produced it. Logs preserve individual interactions; a well-maintained note can explain the latest state of the account.

10. Related tasks, tickets, and activity

Contact and company profiles include areas for related tasks, support tickets, and activity. These connections help the team understand the work around a customer, including follow-up actions and support context.

A proposal review may create a task to prepare a rollout plan. An existing customer may have a support ticket that should be understood before an expansion conversation. Reviewing the linked work makes the next interaction more informed.

For a deeper look at planning and delivery, see the Wave Projects guide. CRM provides relationship context, while project and task workflows organize the work that follows.

11. Audience lists and record housekeeping

Contact and company sidebars include audience-list membership controls. These let the team keep a record connected to the relevant audience organization without losing its individual profile.

Record menus and selection controls support management actions such as copying references and deleting selected records where available. Deals also include archive controls. Use the lifecycle and management controls appropriate to the record and your access.

A regular review keeps the workspace useful: confirm owners, correct stale identity information, update statuses, and remove unnecessary duplication through your team’s normal record-management process.

Manage opportunities through the sales pipeline

12. Custom pipelines and stages

Wave CRM supports deal pipelines with configurable stages. Pipelines and stages have names, colors, and ordering, so the board can reflect the way your team sells.

The sample New Business pipeline uses Qualified, Discovery, Proposal, and Won. Those names describe the example team’s process; they are not a required template. Define stages around meaningful progress that someone can verify.

For example, move an opportunity into Proposal when the scope is understood and there is a document to review. That makes the stage a useful signal during a team check-in.

13. Visual pipeline and deal list views

The pipeline view organizes deal cards by stage. Cards show the opportunity title, amount, associated company and contacts, and owner. Stage counts show how many opportunities sit in each part of the process.

Drag-and-drop interactions support moving and ordering deals. A list view provides another way to review the same opportunities, with display controls for visible columns and filters for the stages you need.

The demo includes nine deals across four stages. A quick scan shows which opportunities still need discovery, which proposals are active, and which accounts have reached Won.

14. Deal details with value, ownership, and buying contacts

Open a deal to review its description, pipeline, stage, owner, amount, company, and associated contacts. The detail drawer keeps that information accessible while the pipeline remains behind it.

The Cedar team workspace deal has a sample value of $36,000, Alex as the owner, Cedar Labs as the company, and two associated contacts. The description explains the proposed 30-person rollout and the customer’s priorities.

This is the minimum context for a useful opportunity review: what is being proposed, who is involved, who owns it, and where it stands. All amounts in the showcase are fictional examples.

Wave CRM deal drawer for the fictional Cedar team workspace opportunity with value, company, contacts, ownership, and notes.
The sample opportunity connects its value and buying team with the notes that explain the next step.

15. Deal notes, comments, attachments, and activity

Deals support notes, comments, attachments, and activity alongside their core properties. Keep decision criteria and the agreed next step in the notes, discuss the opportunity in comments, and attach the material needed for review.

In the showcase, the deal notes name the decision criteria and a November 19 proposal review. That makes the record useful even to a teammate who did not attend discovery.

Write the next step as an action with a person and a checkpoint. “Review the rollout proposal with Morgan and Reese on November 19” gives the team more direction than “follow up soon.”

Organize prospecting and follow-up

16. People and company prospect lists

Prospecting includes lists for people and companies, with a table for reviewing and editing records. Choose relevant columns, adjust the table layout, search, filter, and save useful views. Custom columns support additional information needed for your process.

The example Operations leaders list shows names, roles, companies, email addresses, and qualification status. Five entries are qualified and three are waiting for review. The distinction makes the list useful as a working queue.

Use a list to explain why a group belongs together. A specific audience and review criteria are more useful than a large collection of unrelated names.

17. Imports, exports, qualification, and CRM promotion

Prospecting’s import flow supports CSV data, pasted contacts, and a public Google Sheet source. Column mapping, preview, destination selection, and duplicate-skipping options help the team review what will enter the list. Export controls support taking list data back out.

Qualification records whether a prospect is relevant and can include the reason. Selected prospects can be promoted into CRM, connecting prospect research with the contacts and companies used in the relationship workflow.

Review identity and fit before promotion. In the demo, Morgan and Avery already have CRM links while the other entries remain part of the prospecting queue.

18. Enrichment and source context

Prospecting includes enrichment controls and record metadata for supported fields. Available enrichment operations depend on the providers and capabilities configured for the workspace. Records can show source information, observed times, and enrichment progress.

This helps distinguish information entered by the team from information returned by a provider. Missing data should remain visible as missing; an enrichment action does not guarantee a result for every record.

Use the relevant fields to improve an existing prospect record, then review the result before using it in a customer-facing message. The sample data is fictional and was not obtained through a provider search.

19. Campaign sequences and personalized messages

Campaigns organize outreach into a sequence of steps with message content and follow-up delays. The editor supports personalization variables and message variants. Email steps use connected sender accounts; Text steps are available when an eligible Phone sender is configured.

Build a sequence around a clear reason to contact the audience. Personalization should reflect something relevant about the person or account, and each follow-up should add useful context.

Campaign preparation and launch are separate from editing the copy. Review the selected audience, sending account, channel availability, and readiness before starting outreach. The showcase does not send any messages.

20. Sending schedules, limits, and reply handling

Campaign settings include sending days and windows, time zones, start and stop dates, and daily limits. Sender selection and per-sender settings help define how the campaign runs.

Reply-handling controls include stopping a sequence on a reply, with additional settings for company-level replies and automatic replies. Variant optimization settings support reviewing message performance where enabled.

Use these controls to match the campaign to the audience and the team’s capacity to respond. The right schedule is one the team can manage, with clear ownership of the conversations it creates.

21. Unibox and campaign results

Prospecting’s Unibox provides a workspace for campaign conversations. Campaign views bring together the sequence, leads, settings, and analytics so the team can review outreach and the responses it generates.

Results can include sending and reply activity, interested responses, and opportunity outcomes according to the data available. Use the lead-level context to understand what happened before drawing conclusions from a total.

When a useful conversation develops, update the CRM record and define the next step. That closes the gap between an outreach campaign and an owned customer relationship.

Create, share, and track proposals

22. Proposal documents and reusable templates

The Proposals workspace includes documents and templates. The builder supports structured content such as headings, paragraphs, lists, images, video, columns, tables, and signing blocks. PDF import and export workflows support working with document formats outside the editor.

Templates provide a repeatable starting point for the documents your team creates often. Customize the customer context, scope, responsibilities, and proposed outcome for each opportunity.

Link the proposal to the relevant contact, company, or deal so it remains easy to find from the relationship. In the demo, the Cedar proposal is visible both in the proposal list and Morgan’s profile.

23. Pricing catalog and proposal pricing tables

The Pricing Catalog stores reusable items with fields such as name, SKU, list price, default quantity, billing frequency, and description. Catalog items can be used in proposal pricing tables.

Pricing controls include optional items and editable quantities where configured. Reusing catalog information helps the team maintain a consistent starting point while allowing the proposal to reflect the agreed scope.

For the sample rollout, the proposal value is tied to the specific opportunity. Review quantities, inclusions, and any optional items before sharing the document with the buying team.

24. Sharing, recipients, approvals, and signatures

Proposal sharing includes email and link workflows, recipient configuration, and viewer-identification controls. Signing features support assigning signature fields and configuring signing participants, including company-representative workflows.

Approval controls and document statuses help track the review process. A signing deadline can limit when recipients may sign while leaving the document available to view after that date.

Set up the actual people who need to review or act on the proposal. A document with clear scope still needs a clear recipient and decision process.

25. Proposal status and performance reporting

The proposal list shows document title, status, last-edited date, recipients, owner, and value. Statuses include Draft, Sent, Viewed, Awaiting Signature, Awaiting Approval, Approved, Lost, and Won.

Metrics include proposal count, total value, win rate, average time to first view, and average time to close, with filters and performance views. These describe proposal activity and outcomes; they should not be treated as a guaranteed revenue forecast.

The sample list includes draft, sent, viewed, and won documents. Morgan and Reese appear as recipients on the Cedar proposal, making it easy to connect the document status with the people involved.

How to get started with Wave CRM

  1. Add your active accounts and contacts. Start with the relationships your team is already working on. Record the correct company association, role, and contact details.
  2. Assign an owner. Make responsibility clear for each active relationship and opportunity.
  3. Define a simple pipeline. Use stages that describe observable progress in your sales process.
  4. Create the opportunities. Add a clear title, realistic value, description, company, and buying contacts.
  5. Capture the context. Connect the appropriate Mail account, record conversation logs, and keep requirements or decisions in notes.
  6. Make the next step visible. Create the relevant follow-up task and keep the deal notes current.
  7. Prepare and link the proposal. Use a template and catalog items where helpful, then review recipients, scope, and pricing before sharing.
  8. Review the pipeline regularly. Check stalled opportunities, ownership, proposal status, and the next customer action.

For a small founding team, start with a manageable set of real opportunities. The founder sales pipeline guide explains how to organize the work around your first ten customers.

Wave CRM FAQs

What does Wave CRM include?

Wave CRM includes contact and company records, deals and pipelines, prospecting lists and campaigns, and proposals. Profiles connect related context such as emails, notes, logs, files, tasks, tickets, and activity.

Can I customize the sales pipeline?

Yes. Pipelines and stages can be named, colored, and ordered. Deals can be reviewed in a visual pipeline or list view.

Can one deal have multiple contacts?

Yes. A deal can link to a company and multiple associated contacts, which helps represent the buying team around an opportunity.

Does Wave CRM include email outreach?

Prospecting includes campaign sequences, sender settings, schedules, and reply handling. Email outreach requires a connected sender account. Text steps require an eligible configured Phone sender.

Can I import prospects?

Yes. The prospecting import workflow supports CSV data, pasted contacts, and public Google Sheet sources, with mapping, preview, and duplicate-handling options.

Can I create and track proposals in Wave CRM?

Yes. Proposals includes documents, templates, a pricing catalog, sharing and signing workflows, statuses, and metrics. Proposals can be linked to CRM records.

How does Wave CRM relate to Wave Phone and Chat?

CRM organizes the relationship and opportunity. The Wave Phone system supports calling and customer communication, while Wave Chat supports conversations and collaboration inside the team.

Is the video showing real customer data?

No. The video uses Wave’s actual UI components with fictional companies, people, opportunities, and proposals in an isolated demo. The sample values and outcomes are illustrative.

Give every customer relationship a clear next step

Wave CRM helps the team connect the people, accounts, opportunities, conversations, and proposals involved in customer work. Start with accurate records and clear ownership, then keep the context and next action visible as the relationship develops.

Get started with Wave or contact us to discuss your team’s CRM workflow.

Explore