Boston, 2110, MA,
United States
DirectoryM Technographics
DirectoryM Technographics, Software Purchases, AI and Digital Transformation Initiatives
Discover the latest software purchases and digital transformation initiatives being undertaken by DirectoryM and its business and technology executives. Each quarter our research team identifies on-prem and cloud applications that are being used by the 50 DirectoryM employees from the public (Press Releases, Customer References, Testimonials, Case Studies and Success Stories) and proprietary sources.
During our research, we have identified that DirectoryM has purchased the following applications: Google Workspace (Formerly Google G-Suite) for Collaboration in 2012, Oracle NetSuite Commerce for eCommerce in 2008, Zendesk Service for Customer Support in 2014 and the related IT decision-makers and key stakeholders.
Our database provides customer insight and contextual information on which enterprise applications and software systems DirectoryM is running and its propensity to invest more and deepen its relationship with Google , Microsoft , Oracle or identify new suppliers as part of their overall Digital and IT transformation projects to stay competitive, fend off threats from disruptive forces, or comply with internal mandates to improve overall enterprise efficiency.
We have been analyzing DirectoryM revenues, which have grown to $5.0 million in 2024, plus its IT budget and roadmap, cloud software purchases, aggregating massive amounts of data points that form the basis of our forecast assumptions for DirectoryM intention to invest in emerging technologies such as AI, Machine Learning, IoT, Blockchain, Autonomous Database or in cloud-based ERP, HCM, CRM, EPM, Procurement or Treasury applications.
DirectoryM Tech Stack and Enterprise Applications
DirectoryM Collaboration
Vendor |
Previous System |
Application |
Category |
Market |
VAR/SI |
When |
Live |
Insight |
|---|---|---|---|---|---|---|---|---|
| Legacy | Google Workspace (Formerly Google G-Suite) | Collaboration | Collaboration | n/a | 2012 | 2012 |
In 2012, DirectoryM implemented Google Workspace (Formerly Google G-Suite) as its Collaboration platform. The deployment covers the company’s 50 employees within its United States professional services operations and is publicly observable from the corporate website.
The Google Workspace (Formerly Google G-Suite) implementation centers on core collaboration capabilities including enterprise email, cloud file storage and sharing, real-time document collaboration, calendaring, and video conferencing. Configuration details include domain management and user provisioning through the Google Workspace Admin console, centralized access controls, and device management to support client-facing project work and internal knowledge sharing.
Operational governance emphasizes structured team collaboration, with shared drives for project teams and Google Groups used for distribution and role-based access. Administrative controls and policy settings are used to align collaboration workflows across sales, delivery, and back office functions, enabling consistent document control and communication practices within the small professional services firm.
|
|
|
|
|
|
Collaboration | Collaboration |
|
2015 | 2015 |
|
DirectoryM eCommerce
Vendor |
Previous System |
Application |
Category |
Market |
VAR/SI |
When |
Live |
Insight |
|---|---|---|---|---|---|---|---|---|
| Oracle | Legacy | Oracle NetSuite Commerce | eCommerce | eCommerce | n/a | 2008 | 2008 |
In 2008, DirectoryM implemented Oracle NetSuite Commerce. The eCommerce deployment was scoped for a 50-employee professional services firm based in the United States, and focused on establishing a hosted commerce storefront and a centralized product and service catalog to support online client transactions and self-service ordering. The implementation emphasized catalog management, storefront configuration, and customer account workflows aligned to professional services sales and marketing.
Deployment architecture followed the Oracle NetSuite Commerce SaaS model, with configuration work on storefront templates, shopping cart and checkout orchestration, order management workflows, pricing and promotions configuration, and customer account management. Operational coverage included sales, marketing, and client services teams, with governance centered on catalog ownership, content publishing workflows, and order processing role assignments to preserve separation of duties between catalog curation and transactional operations. DirectoryM configured administrative controls and role-based access to support repeatable processes for catalog updates and online client engagement.
|
DirectoryM CRM
Vendor |
Previous System |
Application |
Category |
Market |
VAR/SI |
When |
Live |
Insight |
|---|---|---|---|---|---|---|---|---|
| Zendesk | Legacy | Zendesk Service | Customer Support | CRM | n/a | 2014 | 2014 |
In 2014, DirectoryM deployed Zendesk Service to provide a consolidated Customer Support channel embedded on its public website. The deployment centers on the cloud hosted Zendesk Service application, delivering web widget based ticket intake and agent-facing ticket management for a 50 person professional services firm.
The implementation configures core Customer Support capabilities consistent with the Zendesk Service model, including ticket creation from the website, email ticket capture, an agent interface for case triage and resolution, and a knowledge base driven help center. Configuration work focused on ticket forms, priority and SLA policies, macros and automated routing rules to standardize first response and handoffs across client service and account management staff.
Operational coverage is scoped to DirectoryM customer service and client-facing teams, with Zendesk Service embedded on the company website to capture inbound client inquiries and support requests. Multi-channel intake is centered on the web channel and email, with internal workflows for assignment, escalation, and status tracking implemented within the Zendesk Service platform.
Governance for the rollout emphasized defined agent roles, ticket lifecycle policies, and a phased adoption plan across support staff and account managers. Ongoing operational controls include configuration governance for ticket forms and automation rules, and role based access to the Zendesk Service admin console to preserve service quality and consistent case handling.
|
DirectoryM IaaS
Vendor |
Previous System |
Application |
Category |
Market |
VAR/SI |
When |
Live |
Insight |
|---|---|---|---|---|---|---|---|---|
|
|
|
|
Application Hosting and Computing Services | IaaS |
|
2013 | 2013 |
|
|
|
|
|
Application Hosting and Computing Services | IaaS |
|
2014 | 2014 |
|
|
|
|
|
Cloud Storage | IaaS |
|
2019 | 2019 |
|
|
|
|
|
Content Delivery Network | IaaS |
|
2019 | 2019 |
|
IT Decision Makers and Key Stakeholders at DirectoryM
| First Name | Last Name | Title | Function | Department | Phone | |
|---|---|---|---|---|---|---|
| CEO | CXO | Finance | ||||
| VP Businesss Development | VP | Sales | ||||
| Vice President of Data | VP | IT |
Apps Being Evaluated by DirectoryM Executives
| Date | Company | Status | Vendor | Product | Category | Market |
|---|---|---|---|---|---|---|
| No data found | ||||||