CRM & Systems of Record
M

Map My Customers

Field execution platform for outside sales, built around a map of the rep's accounts rather than a list. Territory drawing and automatic generation, multi day route optimisation, activity capture and check ins, and an offline mobile application form the base, with two way synchronisation into the four major customer relationship platforms and an enterprise resource system. A field agent takes voice debriefs after a visit, drafts follow ups and briefs the rep before the next stop. The top tier pairs field activity with revenue and order outcomes into weekly executive summaries and per rep coaching pages, staffed by a named strategy engineer. A separate healthcare intelligence line handles claims data, and the platform is built for buyers covered by health information rules.

Last VerifiedAugust 20, 2026
Compare Map My Customers with other vendors
Founded
2015
Headquarters
Cary, NC
Categories
crm, revenue-intelligence, sales-enablement
Assessment

Capability Axes

AI Capability
AI CentralityAI CentralityWhether AI is the product or a feature veneer. The removal test: peel the AI label off, and does anything sellable remain?
CC on AI CentralityAI features on a conventional platform. Peel the AI label off and the product still works roughly as before.
Vendor Published

A model layer sits on top of a mature mapping and routing product and the removal test settles it cleanly. Territory drawing, multi day route optimisation, activity capture, check ins, the offline mobile application, two way synchronisation and the reporting all survive without it, and those are the capabilities the product was built on from 2015.

The model features are real and specific rather than decorative, a field agent taking voice debriefs and drafting follow ups, executive summaries generated from activity data, but they arrive as tier upgrades on an existing platform. This is the established platform pattern the convention describes, applied here to a ten year old vendor rather than an enterprise suite.

Autonomy and Oversight ModelAutonomy and Oversight ModelWhat the system does without a human. Draft for review, auto send, or fully agentic, and what contains a bad run.
BB on Autonomy and Oversight ModelThe human in the loop posture is described substantively (draft versus auto send, approval flows) but the failure containment story is incomplete.
Vendor Published

Administrative oversight is enumerated per tier rather than asserted: role based permissions on every plan, audit logging from the middle tier, single sign on and federated identity, custom data retention policies on enterprise plans, and a service level agreement. The field agent's own design keeps a human in the loop by construction, since it takes a debrief the rep records, drafts a follow up the rep sends, and suggests next steps rather than taking them.

Off the top band because the agent's drafting boundary is described in marketing rather than documented, and nothing states whether a generated executive summary or a coaching page is reviewed before a manager acts on it. That matters more here than on a drafting tool, because these outputs feed rep performance management.

AI Disclosure and Model TransparencyAI Disclosure and Model TransparencyWhat models power the product, whether AI generated outreach discloses itself, and whether scoring and routing logic is explainable.
CC on AI Disclosure and Model TransparencyThe product is described as AI powered with the stack, the disclosure behavior, and the scoring logic all unstated.
Vendor Published

Three distinct model driven surfaces are marketed by name, an email assistant available on every tier, a field agent taking voice debriefs on the upper tiers, and executive summaries generated from activity and check in data at the top. Not one of them carries a model, provider, version, hosting location or boundary anywhere on the pages read.

The voice debrief is where the gap bites hardest, because speech from a rep's day is being processed by an unnamed system at a company that elsewhere documents its compliance posture in unusual detail, and a buyer covered by health information rules would need to know where that audio goes.

Operational and Outcome EvidenceOperational and Outcome EvidenceMeasured outcomes with a stated basis: replies, meetings, pipeline, win rates. Logos are not evidence and prestige is not measurement.
BB on Operational and Outcome EvidenceReal outcome evidence published, with named customers and numbers, but the measurement basis is incomplete: population, period, or definition unstated.
Vendor Published

The evidence surface is deep by the standards of this index: a customer stories section with named accounts, quotes attributed to named individuals with titles and employers including a vice president of operations at a flooring manufacturer and a vice president of sales at a hose distributor, a logo wall of six identifiable companies across diagnostics, engine remanufacture, healthcare, tyres, food distribution and consumer finance, plus webinars named after specific customers, a podcast, a research section and a return calculator.

Scale is quantified twice and inconsistently, at more than 1,000 sales teams on one page and more than 4,000 field reps on another, which are compatible but unreconciled. Off the top band because the one quantified outcome claim, drive time cut by 30 percent and face to face meetings doubled in the first month, is attributed only to an unnamed vice president at an unnamed medical device company, so the sharpest number on the site is the one a buyer cannot check.

Compliance and Risk
Outreach Compliance PostureOutreach Compliance PostureHow the product handles regulated outreach: consent, DNC scrubbing, opt out mechanics, caller ID conduct, and the public enforcement record.
CC on Outreach Compliance PostureCompliance is mentioned as the customer’s responsibility, with little or no product enforcement described. The tool can be run lawfully, and nothing about it helps.
Vendor Published

This product does not run outbound campaigns, so the axis bites lightly and is graded on what is knowable, as the sibling rule requires. Two surfaces do touch it. An email assistant ships on every tier and email history and reporting are captured, so messages are drafted and sent through the platform without any named statute, consent position, unsubscribe mechanism or suppression list appearing anywhere.

And a lead finder supplies prospect records at 125 or 200 searches per user each month, so new contacts enter the system and are then emailed, with no stated position on the basis for that first contact. Neither is a campaign engine and both are real enough to note.

Data Privacy PostureData Privacy PostureGDPR and CCPA posture: lawful basis, data subject rights handling, DPA availability, subprocessor disclosure.
BB on Data Privacy PostureA real privacy program is visible (DPA available, policy substantive) with a gap on the hard question, commonly lawful basis for enriched or tracked individuals.
Vendor Published

The published set is complete and easy to find: a privacy policy, terms, a standalone data processing addendum at its own address, a cookie policy with a working preference manager offering a reject option alongside accept, and an imprint. The compliance position is stated precisely rather than as a badge, with a business associate agreement offered to customers covered by health information rules and readiness for the European regulation asserted with the addendum behind it.

Custom data retention policies are listed as an enterprise entitlement. Off the top band on scope rather than form. The policy documents themselves were not read for this build, no sub processor register was located, and the healthcare claims line and the voice debrief feature both raise questions about categories of personal data that nothing on the pages read addresses. Flagged for re verification.

Data Licensing and ProvenanceData Licensing and ProvenanceWhere the data comes from and on what legal footing: licensed, contributed, public record, or scraped, and who stands behind the answer.
CC on Data Licensing and ProvenanceData is described by its size and coverage with its origin unstated. The provenance question is answerable only by asking the vendor.
Vendor Published

Three data sources feed this product and the buyer's own records are the only one explained. A lead finder supplies prospect records at a published monthly search allowance per user, demographic and territory data is included on every tier, and proprietary data services plus healthcare claims intelligence sit at the top of the range. For all three, the supplier, database, licence, refresh cadence and coverage go unnamed on the pages read.

Claims data is the sharpest instance: it is a regulated category with its own permitted use rules, it is sold here as territory intelligence, and nothing published states where it comes from or on what basis it may be used for targeting.

Platform Terms ExposurePlatform Terms ExposureWhether the product operates inside the terms of the platforms it touches, and the restriction risk a buyer inherits when it does not.
BB on Platform Terms ExposureThe method is described and mostly conformant, with one real ambiguity the vendor does not resolve, or conformance asserted without the partnership evidence that would settle it.
Vendor Published

Exposure is low by construction and the reason is worth stating, since this axis has done heavy work across this alphabetical block. Every integration named is an official, documented connector into a system the customer already licenses, four customer relationship platforms and an enterprise resource system, alongside a public interface, secure file transfer loading and file import.

Nothing scrapes a platform, rents an identity, rotates an address, drives a browser extension against terms that prohibit it, or relays mail through infrastructure the vendor does not control. Under the convention, official connectors plus the vendor's own infrastructure is this band, with the top reserved for a stated conformance position, and none is published.

AI Safety and Data StewardshipAI Safety and Data StewardshipThe cross client boundary: whether customer data trains models that serve competitors, plus retention and deletion posture.
CC on AI Safety and Data StewardshipSecurity language exists but the training question, the one this axis turns on, is unanswered: a buyer cannot tell whether their pipeline data improves a competitor’s instance.
Vendor Published

The stewardship apparatus around conventional data is genuinely strong, with an audited security certification, a business associate agreement for covered customers, custom retention policies and an audit log. The specific question this axis asks goes unanswered anyway. Whether customer data trains or tunes the models behind the email assistant, the field agent or the executive summaries, and whether anything learned in one account can surface in another, is not addressed anywhere read.

The gap is conspicuous precisely because this vendor is careful elsewhere: a company that publishes a processing addendum and offers a covered entity agreement has the legal machinery to answer the training question and has not.

Recipient Disclosure and AuthenticityRecipient Disclosure and AuthenticityHow the product presents itself to the people it targets: whether automated outreach and AI agents disclose themselves, whether sender personas are real, and whether personalization is grounded in verifiable fact. Measured as known compliance with Article 50 of the EU AI Act, in force since August 2, 2026, which requires AI systems that interact with individuals to disclose that fact.
CC on Recipient Disclosure and AuthenticityNothing published on whether recipients are told they are dealing with software. For a product whose AI talks to prospects, silence here is now a regulatory posture, not a style choice.
Vendor Published

Most of what this platform does happens face to face, where the rep is unambiguously themselves and no authenticity question arises. One surface does raise it. An email assistant drafts messages on every tier and a field agent drafts follow ups on the upper ones, both sent under the rep's own name from the rep's own address after a real visit, and no position on disclosing machine authorship appears anywhere. The European obligation is unaddressed. This is a milder version of the question than the manufactured personas graded elsewhere in this block, since the relationship and the visit are real and only the drafting is not.

Integration and Deployment
Ecosystem and Integration DepthEcosystem and Integration DepthDocumented depth of CRM and stack integration: objects, sync direction, API surface, marketplace presence that matches the claims.
AA on Ecosystem and Integration DepthDeep, documented, bidirectional integration with the systems of record: named CRM objects and sync behavior, a public API with real docs, and a marketplace presence that matches the claims.
Vendor Published

This is the deepest integration surface graded in this session and each element is documented at its own address rather than listed as a logo. Two way synchronisation with the four major customer relationship platforms, each with its own integration page, plus an enterprise resource system, a public interface with developer documentation, secure file transfer data loading, file import, calendar synchronisation, external resource syncing and a data merger.

Two way is the default on every tier including the entry plan, which is the distinguishing fact: two vendors graded earlier in this same session gate full two way synchronisation to a custom priced enterprise tier, and this one does not. Mobile applications ship for both platforms with an offline mode, and a public status page covers availability. The interface is gated above the entry tier, which is the only thing worth a buyer's attention here.

Deployment Model and Data ResidencyDeployment Model and Data ResidencyWhere the product runs and where customer data lives, including residency options for EU buyers.
CC on Deployment Model and Data ResidencyCloud hosted is the whole public answer. Region and residency questions require a sales conversation.
Vendor Published

Corporate presence is published properly, with two named offices at street addresses in North Carolina and New York and an imprint page, which is more than most vendors in this session offer. Residency itself is missing. Processing region, storage location, transfer mechanism and any customer choice are all unstated on the pages read, and encryption at rest and in transit is asserted without a location attached.

Readiness for the European regulation is claimed and a processing addendum is published, so the transfer question is presumably answered inside a document that was not read for this build. Flagged for re verification rather than graded lower.

Security Certifications and Trust CenterSecurity Certifications and Trust CenterVerifiable security posture: enumerated current certifications and a trust center an outsider can actually read.
AA on Security Certifications and Trust CenterA live trust center with enumerated, current certifications (SOC 2 Type II and peers), audit recency visible, and security practices documented beyond the badge.
Vendor Published

A live trust centre is hosted on a recognised compliance automation platform and linked from both the pricing page and the site footer, which means a buyer reaches current attestations without a sales conversation or a request form.

Around it sit an audited service organisation control report at the type that covers operating effectiveness over time, a business associate agreement available to customers covered by health information rules, readiness for the European regulation with a published processing addendum, single sign on and federated identity, role based permissions on every tier, audit logging, custom data retention policies, a custom service level agreement, encryption stated at rest and in transit, and a public status page. Self service access to the attestations is the distinction this index draws between the top two bands, and it is met here.

Commercial and Operational
Commercial TransparencyCommercial TransparencyWhether a buyer can budget without a sales call. Published pricing graded on completeness, not on the price itself.
BB on Commercial TransparencyPartial pricing published (entry tiers real, enterprise opaque) or pricing published with load bearing exclusions.
Vendor Published

Three tiers publish a per seat annual price, 99, 139 and 199 dollars per user per month, above a comparison table running to roughly sixty rows that marks every feature by tier and distinguishes what is included from what is an add on. Seat minimums are published for each plan at five, ten and thirty five users, which is the number that actually determines whether a buyer can afford the tier and which most vendors leave to a sales call.

A non profit discount is stated at 25 percent, upgrade and downgrade timing is explained, and multi year and volume discounting are disclosed as available. Two things hold it off the top band. Six capabilities are marked as add ons with no price attached anywhere, including single sign on and advanced reporting at the entry tier, so the real bill is not computable from the page.

And the vendor's own answers contradict the page: the frequently asked questions state that pricing is custom because field teams vary and direct the reader to a demo, while the pricing page is headed with a claim of transparent plans and prints three figures.

Exit and Data PortabilityExit and Data PortabilityWhat happens when a customer leaves: completeness of data export, rights to enriched or licensed data after termination, deletion commitments, and auto renewal mechanics, graded from published terms and documentation.
BB on Exit and Data PortabilityReal export capability documented, with a material exit question unstated in public terms, commonly post termination rights to licensed or enriched records.
Vendor Published

The exit position is stronger than most in this index and the reason is structural rather than a stated policy. Two way synchronisation runs on every tier, so the customer's accounts, activity and contact history are continuously written back into a system of record they already own, which means the most valuable data never lives only here.

Around that sit a public interface above the entry tier, secure file transfer loading, custom data retention policies on enterprise plans and mileage logs described as exportable. Off the top band because no post termination data right, deletion timeline, retrieval window or export function for the platform's own artefacts is stated on the pages read, the terms were not read, and the commercial exit is tight: plans are twelve month commitments, downgrades take effect only at annual renewal, and nothing published describes what happens to territory configuration or field history at the end of a term.

Deliverability and Sending DisciplineDeliverability and Sending DisciplineThe operational craft of sending: warmup, rotation, volume governance, spam rate monitoring, and what happens when reputation degrades.
CC on Deliverability and Sending DisciplineDeliverability is invoked as a benefit with no documented mechanism. For senders this is the axis where marketing most outruns evidence.
Vendor Published

This platform is not built to send at volume and the axis is graded on what is knowable rather than skipped, per the sibling rule for categories that do not send. What exists is real enough to record: an email assistant on every tier, email history and reporting, and a lead finder feeding new contacts into the same system.

What is absent is every mechanism this axis measures, with no sending limit, warmup guidance, throttling control, bounce handling, complaint threshold, authentication guidance or suppression list published anywhere. A buyer should read the absence as structural rather than as a disclosure failure, since the volume here is a rep writing follow ups after visits rather than a campaign engine.

Segment and Market CoverageSegment and Market CoverageWho the product actually serves, evidenced: segments, geographies, languages, and customers that match the claim.
AA on Segment and Market CoverageWho the product serves is stated with evidence: segments, team sizes, geographies, and languages, with named customers that match the claim.
Vendor Published

Coverage is documented to a depth almost nothing in this index matches, and in both dimensions at once. Ten industries are named individually with their own anchored sections, from medical devices and diagnostics through building materials, industrial distribution and machinery to automotive services and virtual care, alongside four buying roles each with a dedicated page.

The tier structure then encodes the segment boundaries numerically rather than describing them, with published seat minimums of five, ten and thirty five reps and a stated threshold above fifty reps where a bespoke quote applies, so a buyer can locate themselves precisely and can also see where they are too small. Named customers span six distinct verticals and corroborate the industry claims rather than merely illustrating them. The regulated segment is served explicitly, with a covered entity agreement and a separate healthcare claims intelligence line, which is a real market commitment rather than a positioning line.

Commercial

Pricing

Vendor-published figures are labeled as such. Figures labeled “Estimated” are derived from third-party sources and have not been confirmed by the vendor.

No pricing data has been verified for this vendor. Pricing information will be published here once confirmed through vendor disclosure or third-party estimation.

Contact us

Found a vendor we missed? Have feedback on the index? We’d love to hear from you.

GTM Tech Index

An independent reference for evaluating the software revenue teams use to find, win, and keep customers. No vendor pays for inclusion, placement, or rating.

Index Status
Last index update
August 20, 2026
The GTM Tech Index is an editorial reference, not a law firm or a regulator. Compliance postures are assessed from published sources and public records, and nothing on the index is legal advice. Figures labeled “Estimated” have not been confirmed by the vendor. See the Methodology page for evaluation standards and limitations.
© 2026 GTM Tech Index
3801 N Capital of Texas Hwy, Ste E240 · Austin, TX 78746