Interview with Helen Bally, Head of QA&T, and Paul Barnabé, Head of Itecor Suisse Romande · April 20, 2026
For more than ten years, Itecor has been supporting its customers in hybrid mode from Switzerland and North Macedonia. This organisation, combining proximity, flexibility and operational excellence, enables the delivery of high value-added managed services in areas such as testing, development and application management.
In this discussion with Helen Bally, Head of the Quality Assurance & Testing service line, and Paul Barnabé, Head of Itecor Suisse Romande, we look at the main advantages of this delivery model combined with nearshore, the business drivers that make it particularly relevant today, and the practical steps a company can take to start a Managed Service with Itecor.
The primary objective is often very concrete: to do better with less. Our clients seek to maintain the same level of service, or even improve it, while optimising their costs. The Managed Service model responds precisely to this need: it allows them to maintain operational quality equivalent to or superior to that of an internal team, while introducing flexibility and budgetary visibility.
But beyond cost reduction, there is also a desire for peace of mind. Many IT organisations struggle to recruit and retain talent, whether in testing or development. By entrusting us with all or part of the service, they delegate the burden of recruitment, retention and management.
We become, in a way, their operational life insurance: they no longer have to manage turnover, profile availability or onboarding, as this is integrated into our model. Itecor manages the entire HR lifecycle of the service, from recruitment to training and retention, ensuring continuity without any additional burden on the client. The client also benefits from integrated technology monitoring and, if desired, management of their software factory tools or licences.
Several major players in Switzerland and France, in insurance, industry and public services, have already chosen this model with Itecor.
The first driver is, of course, budgetary. But other issues quickly follow: scalability and organisational complexity.
Let’s take a concrete example: a large digital transformation programme often involves several service providers, each with their own contacts and working methods. The client has to coordinate all of this, which generates a lot of internal workload. With a Managed Service, you can have a single supplier, clear governance and precise contractual commitments: delivery times, service continuity, compliance with SLAs, operational KPIs, etc.
This is what we call model scalability: the ability to quickly adapt resources to needs—with very short ramp-up times, often around one month—while maintaining a high level of efficiency, in other words, operational and budgetary performance.
Finally, in areas such as testing, Managed Services make it possible to guarantee functional coverage and monitor quality indicators such as the automation rate or the number of defects detected in production.
We are moving from a resource-based approach to a results–based approach.
A management structure – a dedicated delivery manager on the Itecor side and a point of contact on the client side – ensures transparency, strategic alignment and long-term value through regular committees and performance reviews.
Our approach is collaborative and iterative.
It all starts with an analysis phase: we identify stakeholders, gather documentation and assess the existing environment. Next, we define governance, processes, tools and a common service catalogue that clearly describes the services available, such as management, design and execution of functional and performance tests, and automation of regression or integration tests.
This phase is followed by an analysis of the application portfolio and ongoing projects, carried out jointly with the client. The aim is to determine the optimal capacity to be put in place (in terms of resources, skills and tools) for each functional area or product.
This fine-tuning process allows us to tailor the service to actual needs, avoid under- or over-capacity, and ensure efficient team allocation from the outset.
Once this framework is in place, we carry out a due diligence phase to test, adjust and validate the operating assumptions. Only after this stage do our formal SLA and KPI commitments take effect. Our commitments are structured around two families of indicators:
This dual approach enables objective and transparent service management, promoting continuous improvement and making Itecor accountable for results.
The client thus maintains a clear view of the value created, beyond simple resource monitoring.
The service is deployed in stages: takeover of a functional or application scope (ERP, CRM, finance, etc.), gradual ramp-up, then extension to other areas. It is a controlled, structured transition – one without any disruption to service.
Provision of staff; the client remains in charge of day-to-day operations.
Commitment to a specific deliverable, in line with deadlines, costs and budget.
Long-term commitment to performance, quality and continuity of service.
It’s our signature. We offer a European nearshoring model, but with a typically Swiss culture of quality and rigour. This translates into robust processes, transparency in relationships and a constant focus on customer satisfaction.
To be successful, a Managed Service must be supported by strong management sponsorship, clear governance and a long-term relationship of trust. This is what allows value to be anchored over time and makes the service a real performance lever.
Our Managed Services are built on Swiss standards of reliability and compliance: data confidentiality and security, compliance with personal data protection regulations (LPD, GDPR), and service continuity.
This is a strong commitment that is recognised by our customers.
Unlike simple resource outsourcing, we offer our customers a model based on efficiency, governance and lasting trust. A controlled, scalable and, above all, deeply human service. Swiss style.
| Cookie | Duration | Description |
|---|---|---|
| __hssrc | Session | This cookie is set by Hubspot whenever it changes the session cookie. The __hssrc cookie set to 1 indicates that the user has restarted the browser, and if the cookie does not exist, it is assumed to be a new session. |
| _GRECAPTCHA | 5 months 27 days | This cookie is set by the Google recaptcha service to identify bots to protect the website against malicious spam attacks. |
| cookielawinfo-checkbox-advertisement | 1 year | Set by the GDPR Cookie Consent plugin, this cookie is used to record the user consent for the cookies in the "Advertisement" category . |
| cookielawinfo-checkbox-analytics | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics". |
| cookielawinfo-checkbox-functional | 11 months | The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional". |
| cookielawinfo-checkbox-necessary | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary". |
| cookielawinfo-checkbox-others | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other. |
| cookielawinfo-checkbox-performance | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance". |
| CookieLawInfoConsent | 1 year | CookieYes sets this cookie to record the default button state of the corresponding category and the status of CCPA. It works only in coordination with the primary cookie. |
| JSESSIONID | session | New Relic uses this cookie to store a session identifier so that New Relic can monitor session counts for an application. |
| viewed_cookie_policy | 11 months | The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data. |
| Cookie | Duration | Description |
|---|---|---|
| __cf_bm | 30 minutes | This cookie, set by Cloudflare, is used to support Cloudflare Bot Management. |
| __hssc | 30 minutes | HubSpot sets this cookie to keep track of sessions and to determine if HubSpot should increment the session number and timestamps in the __hstc cookie. |
| Cookie | Duration | Description |
|---|---|---|
| __hstc | 1 year 24 days | This is the main cookie set by Hubspot, for tracking visitors. It contains the domain, initial timestamp (first visit), last timestamp (last visit), current timestamp (this visit), and session number (increments for each subsequent session). |
| _ga | 2 years | The _ga cookie, installed by Google Analytics, calculates visitor, session and campaign data and also keeps track of site usage for the site's analytics report. The cookie stores information anonymously and assigns a randomly generated number to recognize unique visitors. |
| _ga_* | 1 year 1 month 4 days | Google Analytics sets this cookie to store and count page views. |
| _ga_JYCPSB48B8 | 2 years | This cookie is installed by Google Analytics. |
| _gat_gtag_UA_* | 1 minute | Google Analytics sets this cookie to store a unique user ID. |
| _gid | 1 day | Google Analytics sets this cookie to store information on how visitors use a website while also creating an analytics report of the website's performance. Some of the collected data includes the number of visitors, their source, and the pages they visit anonymously. |
| CONSENT | 16 years 2 months 25 days 10 hours | YouTube sets this cookie via embedded youtube-videos and registers anonymous statistical data. |
| hubspotutk | 1 year 24 days | This cookie is used by HubSpot to keep track of the visitors to the website. This cookie is passed to Hubspot on form submission and used when deduplicating contacts. |
| Cookie | Duration | Description |
|---|---|---|
| IDE | 1 year 24 days | Google DoubleClick IDE cookies are used to store information about how the user uses the website to present them with relevant ads and according to the user profile. |
| test_cookie | 15 minutes | The test_cookie is set by doubleclick.net and is used to determine if the user's browser supports cookies. |
| VISITOR_INFO1_LIVE | 5 months 27 days | A cookie set by YouTube to measure bandwidth that determines whether the user gets the new or old player interface. |
| YSC | Session | YSC cookie is set by Youtube and is used to track the views of embedded videos on Youtube pages. |
| yt-remote-connected-devices | never | YouTube sets this cookie to store the user's video preferences using embedded YouTube videos. |
| yt-remote-device-id | never | YouTube sets this cookie to store the user's video preferences using embedded YouTube videos. |
| Cookie | Duration | Description |
|---|---|---|
| VISITOR_PRIVACY_METADATA | 5 months 27 days | Description is currently not available. |