FICILCOM Inc. LogoFICILCOM Inc.
  • Company
  • Company Overview
  • Mission · Vision · Values
  • Guidelines
  • Services
  • NeX-Ray
  • Xtrategy
  • Trial Job Change
  • Tsurugi
  • Recruit
  • Culture
  • Benefits
  • Process
  • FAQ
  • Open Positions
Contact
  1. Home
  2. Blog
  3. CRM, LTV & Customer Management
  4. What Is CRM? CRM vs. SFA and Marketing Automation, Plus a Selection Checklist

What Is CRM? CRM vs. SFA and Marketing Automation, Plus a Selection Checklist

CRMとは?意味・MAとの違い・選び方を初心者向けに簡単に解説

Published: 05/18/2026

Last Updated: 10/08/2026

Category: CRM, LTV & Customer Management, Marketing Glossary

Authors: Shusaku Yosa

Ready to put this into practice?

Start Xtrategy for free→

1-minute signup, free, cancel anytime

CRM means Customer Relationship Management: the approach and supporting systems used to manage relationships with prospects and existing customers. Company, contact, deal, and interaction records help the next owner understand the relationship and decide what to do. CRM is not limited to people who have already purchased.

Start with the decisions and work you need to improve, then evaluate software. Clarifying the overlap with sales automation and marketing automation, total costs, migration, permissions, and contact restrictions helps avoid introducing a system that produces more input without better handoffs.

CRM, SFA, and marketing automation overlap

Salesforce’s CRM explanation includes both customers and prospects. That does not establish that every CRM product has the same capabilities. Compare the purpose, records, and actual plan conditions.

Category

Typical purpose

Check in the proposed product

CRM

Share prospect and customer relationships and information

Company/contact/deal links, history, permissions, and export

Sales force automation, or SFA

Manage opportunities, activities, and next steps

Stages, ownership, handoffs, and forecasting conditions

Marketing automation

Support marketing operations using contacts and responses

Consent, sending, branching, and feature availability

Combined setup

Move information between responsible teams

Shared identifiers, update direction, limits, and failure handling

Features overlap and vary by subscription and add-on. A CRM subscription does not automatically include email sending, scoring, or advertising connections. See the marketing automation guide, SFA guide, and related tool comparison for deeper decisions, then validate the actual requirements against each product.

Define records and ownership before collecting more data

A company is not the same as a contact or deal. One company can have several people and opportunities; a person’s job change, a lost deal, and a stop request are different updates. Do not create extra companies for spelling variations or lose contact restrictions when ownership changes.

  1. Choose the first workflow: sales handoff, existing-customer service, or deal visibility.
  2. Define identifiers and necessary fields for companies, contacts, deals, owners, next actions, dates, and sources.
  3. Assign responsibility for creating, updating, deduplicating, exporting, and deleting records.
  4. Specify collection purposes, permitted uses, contact conditions, retention, and stop requests.
  5. Decide how to check unowned work, overdue actions, and incomplete handoffs rather than input volume alone.

A job title without a source or confirmation date can silently become outdated. Before making a field mandatory, identify the decision and owner that need it. Align opportunity acceptance with BDR handoffs and consent or withdrawal records with opt-in operations. Avoid collecting personal information simply because a field is available.

Worked example: compare three-year total cost

This fictional example is in Japanese yen, not a market price or product quotation. Ten users pay JPY 3,000 per month for 36 months. Tax, internal labor, renewal changes, and future add-ons are excluded and would need separate consideration in an actual assessment.

Item

Fictional calculation

Scope to confirm

Subscription

10 × JPY 3,000 × 36 = JPY 1,080,000

Extra users, minimum terms, and renewal pricing

Initial setup

JPY 300,000

Configuration, cleanup, and training inclusions

Additional support

JPY 120,000

Hours, supported work, and expiry

Connection implementation

JPY 240,000

Data scope, direction, maintenance, and rebuilding

Included three-year total

JPY 1,740,000

Keep excluded costs visible

The total is JPY 1,080,000 + 300,000 + 120,000 + 240,000 = 1,740,000. Monthly fees alone can miss cleanup, migration, training, and exit work. Do not count external setup labor again if the setup quotation already includes it. A value assigned to internal time should also remain distinct from cash expenditure.

For a connection, check additional contracts, usage limits, update delays, failure handling, and how deletion propagates. A manageable manual workflow can be a valid option. More features do not substitute for the ability to maintain the records.

Test relationships, access, and restrictions before full migration

A fictional trial dataset contains five companies, eight contacts, and six deals. The following are validation requirements, not a claim that every product implements them in the same way.

Test

Expected result

If it fails

Record relationships

Eight contacts and six deals link to the correct five companies

Fix identifiers and matching, then repeat

Duplicates and updates

Spelling variations and job changes have a defined treatment

Establish review rather than assuming automatic merging

Access and export

People cannot view, change, or export unnecessary information

Revise permissions and ownership

Stop requests and purposes

Restrictions, sources, and dates survive migration

Repair missing fields and pre-contact checks

Recovery and portability

Rollback and necessary exports can be demonstrated

Hold full migration and reconsider scope

For Japanese personal-information handling, the Personal Information Protection Commission’s general guidelines address purposes and security measures, including access controls. Possessing a customer list does not make unrestricted export or reuse appropriate. Check contracts, permissions, and the actual operating environment.

Have the responsible users reproduce a real handoff after testing. Fields existing in a screen is not enough: confirm that a stop request is visible, the next action is understandable, and records cannot silently move to the wrong company.

Review decision quality after launch

Check unowned deals, stale records, duplicates, and missing restrictions. If entries rise but sales still repeats questions, simplify the required fields and repair the handoff. The sales and marketing alignment guide helps define acceptance and return conditions.

Do not attribute a revenue increase solely to CRM implementation. Offers, staffing, demand, and campaigns can also change. When moving from records to customer analysis, keep periods, populations, and revenue-versus-profit definitions consistent.

Connect the next decisions

For related decisions, see BDR handoff design, opt-in workflows, customer analysis.

Xtrategy provides company, contact, and deal records alongside project planning and monthly budget-versus-actual management. Review the Xtrategy feature list to decide whether those management functions fit your team’s workflow.

 

 

 

 

Table of Contents

  1. CRM, SFA, and marketing automation overlap
  2. Define records and ownership before collecting more data
  3. Worked example: compare three-year total cost
  4. Test relationships, access, and restrictions before full migration
  5. Review decision quality after launch
  6. Connect the next decisions

 

Company

  • Company
  • Company overview
  • Mission · Vision · Values
  • Guidelines

Services

  • Services

Blog

  • Blog
  • Categories
  • Authors

Estimate

  • Estimate simulator

Careers

  • Careers
  • Culture & Work Style
  • Benefits & Systems
  • Hiring Process
  • FAQ
  • Open Positions

Policies

  • Privacy Policy
  • Anti-Social Policy
  • Information Security Policy

Contact

  • Contact

Social

  • X
  • LinkedIn
  • Facebook
  • Pinterest
© 2026 Ficilcom Inc.

Related Articles

パイプライン管理とは?案件の進捗を可視化して予測精度を上げる
CRM, LTV & Customer Management08/20/2026

What Is Pipeline Management? Stage Definitions, Stalled Deals, and Forecast Examples

Define pipeline stages using customer evidence, investigate stalled deals, calculate a hypothetical in-period bookings f...

Shusaku YosaRead more
中小企業のCRMの選び方|判断軸5つと導入時につまずく点
CRM, LTV & Customer Management08/19/2026

Choosing a CRM for a Smaller Company | Five Criteria and Where Adoption Stalls

How smaller companies should choose a CRM when nobody can be assigned to it full time. Covers five criteria — setup time...

Shusaku YosaRead more
アドボケイト(推奨者)の育て方|事例と施策
CRM, LTV & Customer Management06/30/2026

How to Build Customer Advocacy: Identify, Invite, Support, and Measure

Build a voluntary customer advocacy workflow: identify candidates, offer useful participation options, manage permission...

Shusaku YosaRead more