Home > Managed Services
MANAGED SERVICES
Three models to ensure the evolution and maintenance of your CRM
TMA - run
Controlled agility
A flexible budget of days, available according to your priorities for identified requests or emerging needs. Actual usage per half-day, continuous monitoring, and possible adjustments based on priorities.
Envelope - flexibility
Controlled agility
A flexible budget of days, available according to your priorities for identified requests or emerging needs. Actual usage per half-day, continuous monitoring, and possible adjustments based on priorities.
Project framework
Targeted acceleration
A short and delimited project to deliver an identified development: a few days to a few weeks, a defined deliverable, close monitoring and, if necessary, occasional expert support.
The three models
A CRM that supports critical processes is not managed in the same way throughout its lifecycle. Some needs are recurring and require daily platform availability, others are one-off or emerging, and still others are part of a specific project with a deadline. Three models address these situations: Application Maintenance (TMA), Budget-Based Approach, and Project-Based Approach, combining performance, continuous improvement, and cost control over time. They can be combined and adjusted over time, all within a single management framework.
Advice before technology
Our role is not to execute requests, but to challenge them: each change is judged on its business value, and the Salesforce standard takes precedence to avoid accumulating technical debt.
For us, a service center isn't a commodity. It's an extension of consulting: keeping the platform aligned with your business needs, making informed decisions about changes to deliver value, and prioritizing vendor standards to avoid accumulating technical debt over time. As
an independent firm exclusively dedicated to Salesforce, we operate with the same high standards throughout the entire lifecycle, from auditing to ongoing operations, and within complex IT ecosystems where Salesforce coexists with core systems.
Our consultants are all certified, salaried employees, and based in France (Lyon and Paris). Knowledge of your platform is shared within the team to ensure you are not dependent on a single individual.
A team and clear roles
A structured system built around identified key contacts, guaranteeing quality of service and continuity of commitment over time. The same contacts support your platform, regardless of the model activated.
Maïté Solbreux
Delivery Director
Ken Milandou
Director of Engagement
Raphaël Medoc-Elma
Operational Account Manager
What makes the difference between a service provider and a partner
Knowledge sharing
Knowledge sharing
Knowledge of your platform is documented and shared within the team: no dependence on a single person, even in the event of temporary reinforcement.
Steering and committees
Steering and committees
Steering committees and regular follow-up points: consumption, workload plan, risks, progress plan and satisfaction, regardless of the model activated.
Challenge of the need
Challenge of the need
Each request is questioned before being priced, in order to maximize the business value delivered and discard what does not bring it.
Expertise and quality
Expertise and quality
Certified consultants and employees, shared practices between consultants, "standard above all" arbitration to contain technical debt.
Which models for which needs ?
The choice depends on the nature of the need and the expected level of commitment, not on the urgency.
- Over time
TMA
- Recurring and ongoing need
- Continuous flow of requests
- Annual commitment
- Contracted SLAs
- Regular monitoring of the Service Center
- Securing and developing the existing system
- Flexible
Envelope
- Occasional or emerging needs
- Request according to your priorities
- One to several days
- Demand prioritization
- Continuous reporting and monitoring
- Quickly absorb your priorities
- Delimited
Project
- Identified developments
- Short and clearly defined construction site
- A few days to a few weeks
- Deliverable and delivery date defined
- Launch, progress update and closure
- Link a specific development
Unsure which model is right for you? A brief consultation is usually all it takes to decide. We'll tell you whether your needs fall under the service center's purview or not.
Insights
Do you have a question ?
Contact us if you would like more information.
What is a Salesforce service center?
It is a system that supports the management and continuous evolution of a Salesforce platform over time: maintenance, support, upgrades and structuring projects, under a single management framework.
What is the difference between TMA, envelope and project?
TMA is a long-term service commitment with guaranteed service levels. The budget is a flexible capacity of days, available according to priorities, without a fixed deadline. The project is a short, defined undertaking, lasting from a few days to a few weeks, to deliver a specific development.
Can several models be combined?
Yes, and that's the most common configuration. A TMA (Third-Party Application Maintenance) service secures the existing system while a project delivers the expected development, with coordination between the two and a planned takeover for maintenance.
How to choose the right model?
Based on the nature of the need: Recurring and requiring platform availability: Application Maintenance (TMA). One-off or emerging, without a formalized deliverable: Budget. A specific development to be delivered by a date: Project. A scoping discussion allows for a quick decision.
Does a transformation project fall under the purview of the service center?
No. The Service Center Project model focuses on short, well-defined projects. A transformation—that is, a process redesign, a multi-entity deployment, or large-scale change management—requires upstream strategic planning followed by a complete project framework.
Does Texeï intervene on platforms that it did not build?
Yes. The incoming reversibility phase is designed for this: understanding the scope, operational documentation and calibration of the system before committing to service levels.
They trust