What Is MarTech? Define Your MA, CRM and Measurement Project
Published:
Last Updated:
Category: MarTech
Authors: Shusaku Yosa
MarTech is technology used in marketing, including customer information systems, communication tools, website measurement and reporting. A larger stack is not the objective. The useful starting point is a specific operational problem: inquiries are not handed over reliably, campaigns require repeated manual work or reporting does not answer a business question.
This guide helps teams distinguish MA/CRM work from data and measurement work, identify internal responsibilities and prepare a practical estimate request. It does not assume that every business needs to adopt the same tools or all categories at once.
Separate three roles
CRM, or customer relationship management, helps organize information about customers and sales opportunities. Marketing automation supports marketing tasks and workflows based on agreed conditions. Measurement and reporting prepare evidence about activity and outcomes for decisions.
One product may cover several roles. A product category alone does not establish the work required. Check the actual functions, plan, permissions and existing connections. Even a suitable tool needs a process for entering information and a person who will maintain it.
Translate an operational problem into work
Problem | Define first | Possible work |
|---|---|---|
Inquiries depend on one person's memory | Ownership, response expectations and customer states | CRM fields, notifications and handover settings |
Campaign preparation repeats manual steps | Audience, entry, stopping and approval conditions | Automation flows and templates |
Forms and CRM contain duplicate information | Authoritative fields and identifiers | Standard connections, mapping and verification |
Website actions are not measured reliably | Outcome definitions, events and production hosts | Measurement design, implementation and testing |
Reports do not lead to decisions | Reader, decision, period and measurement unit | Report design, data preparation and recurring analysis |
For example, “automate our emails” is not yet a configuration brief if nobody has defined the recipients. “Build a dashboard” is incomplete if the decision maker and decision are unknown. Map the current workflow first. Some problems can be resolved with a clearer process or existing functions before another tool is purchased.
What changes the estimate?
A new setup or an established environment
Creating a new configuration differs from reorganizing fields and workflows used by several departments. Review duplicates, naming, permissions and communications that cannot be interrupted. If existing operations will change, include checks before migration and verification afterwards.
The number and type of connections
Check whether a standard connector supports the required work or a custom API is needed. “Integrates with” does not establish that the right fields can move in the required direction and frequency. Confirm the plan, permissions, available fields, volume and handling of failed transfers. Separate software subscriptions from setup and implementation support.
Workflow boundaries and ongoing ownership
Define entry, exclusion, exit and stopping conditions, notifications and repeated processing. Assign testing and approval before release. Also name the owner who checks the workflow afterwards. Creating a template and producing the content sent through it are different tasks and may need separate briefs.
Measurement design and implementation
Google Analytics key events are used for important actions, but the meaning of the count depends on the event definition. Distinguish a form click from an accepted inquiry and a document view from a sales opportunity. Verify repeated events and non-production traffic before treating a number as a business result.
Measurement can require website changes, while CRM reporting can depend on consistent human updates. Define both sides. A dashboard should make its periods, units and limitations clear rather than conceal differences behind a single total.
Keep business decisions inside the company
Your team must define customer and opportunity states, recipient eligibility, communication approval and sales handover. Outside support can help translate requirements into settings, review an existing environment, verify connections and document operating procedures.
Include sales, site administration and information-management owners when their responsibilities are affected. Agree on the purpose and use of the data, access, consent and retention. Do not send account credentials with an initial request; first agree on the necessary permission and sharing method.
If outside support will handle sales activity after an inquiry, separate that work from CRM configuration. The sales outsourcing scope guide helps define the stage to cover and the internal owner. If the project involves personalized product suggestions, the recommendation engine adoption guide explains the data, placement, validation and development questions to resolve first.
Two hypothetical project scopes
Scope A: make inquiry handover reliable. The company defines inquiry categories and owners. It requests a review of existing CRM fields, notifications and the response workflow. New software purchases or major migration can be considered separately if the review establishes a need.
Scope B: understand the path from activity to inquiry. The company defines an accepted inquiry, then reviews website measurement and CRM states. Reporting uses compatible units and periods. Paths that cannot be linked remain unknown. A CRM configuration project alone should not be assumed to provide complete tracking across every channel.
These examples show possible boundaries, not a guarantee that every product or connection can be supported. Confirm the actual environment and feasibility before agreeing on the work.
Prepare a useful project note
- The workflow to improve and the steps people currently follow.
- Current tools, subscription plans and owning departments.
- Customer or opportunity fields, identifiers and approximate volume.
- Required flows, recipients, entry, stopping and exception conditions.
- Connections, synchronization direction and frequency.
- The internal implementation and approval owners.
- Reports, readers and definitions of the outcomes being measured.
- Testing, release approval, ongoing operation and handover.
The note does not need to be a technical specification. A clear example of a real workflow is often more helpful than a long list of desired features. Identify unknown requirements so that discovery and implementation are not mistaken for the same stage.
Frequently asked questions
Should MA and CRM be introduced together?
That depends on the problem and current systems. Check what the existing environment can do. Avoid expanding software adoption and process change beyond what the team can maintain.
Do AI functions remove the need for an operating owner?
No. Inputs, outputs, approvals and incorrect classifications or communications still need attention. Decide which actions can be automated and when a person must review them before configuring the workflow.
Does a setup fee include software subscriptions?
Confirm subscriptions and support as separate items. Additional users, usage, integration functions and migration may change the conditions. Rely on the actual software contract and project quotation rather than a general category description.
Are all integrations standard work?
No. The current MA/CRM estimator distinguishes existing connectors and standard functions from custom APIs, migration and complex branching. Describe those requirements explicitly rather than assuming that adding one connection covers all integration work.
Use the guide and estimate that match the work
For customer information, communication flows and standard connections, start with the MA/CRM cost and scope guide and check an MA/CRM support estimate.
For tracking implementation and reporting, use the data and measurement guide and data and measurement estimator. If the project spans several areas, review the service list and separate the work before comparing costs.
An estimate is not a binding price or a guarantee of business outcomes. Copy the conditions and breakdown into the inquiry form, adding the current environment and unresolved requirements. Final scope, availability and terms are confirmed after reviewing the request.
