Contact us

Let's Meet

Markentive audits and challenges Expensya's Technical Stack

case study expensya tool stack

Doc

to centralize data models and synchronization mappings

Plan

of the interconnections to be made for the implementation of the new ToolStack

Proposal

of an organization to define the future data architecture

Expensya supports companies in automating their expense report management processes, with a 0 entry, 0 paper, 100% mobile and 100% integrated approach.

Industry

SAAS, Expense management

Founded in

2015

Number of employees

+100

Markentive Services

CRM & Sales Enablement
audit technical stack

Goals and challenges

Following the CRM strategy redesign, Markentive supported Expensya in the audit of its Technical Stack and the definition of a new data architecture.

The challenges of this project were multiple:

  • Challenge and optimize Expensya's tool stack (around twenty tools used across all teams : customer service, sales, delivery, marketing and finance)
  • The tools used : Dropcontact, Linkedin Sales Navigator, Aircall, Docusign, Quickbooks, Livestorm, Lemlist, Intercom, Zendesk...
  • Suggest a new version of their ToolStack to positively change business practices
  • Have a unified 360° vision of the customer journey for all teams
  • Simplify and streamline business processes and reduce double entries, by changing tools or adding new connections between tools.

Solutions

expensya technical stack
  • Audit the business practices of Expensya’s teams and the current use of the various tools
  • Benchmark of customer service tools
  • Analysis of existing API flows and mapping of the ToolStack
  • Analysis of the overall cost of the ToolStack and search for optimizations (duplicate and/or abandoned tools)
  • Identification of new integration needs and search for tools that are well integrated with HubSpot following their migration from Pipedrive to HubSpot
  • Documentation of the bi-directional / uni-directional flows of each connection & mapping of the properties of each object to be connected
  • Suggestion of a new optimized ToolStack while taking into account the aspects of governance and change management on each tool
  • Building of data architecture diagrams with and without Data Lake, using a market solution or an open source software customization
data architecture

Results

  • A plan of all the interconnections to be made for the implementation of the new ToolStack (list of flows between different tools to be synchronized);
  • Delivery of a document to centralize data models, define mappings and synchronization rules to be implemented;
  • Proposal of an organization and a schedule to define the future data architecture (with feasibility studies to be carried out, native connections & custom APIs to be implemented).

You too can benefit from the advice of our experts

and may become one of our future customer stories!

Contact us