References
You won't see any logos here. You'll be able to talk to our customers.
Healthcare, humanitarian aid, industry, public sector: Some of our clients are contractually prohibited from being named, and others would have nothing to gain from it. What we can show you are the projects we’ve undertaken, described in detail but without naming the clients. The best we can do is put you in touch with a client whose situation is similar to yours, with that client’s permission.
Production began in 1995. Still the same company, still the same teams.
What has been confirmed
Three numbers, and where they come from.
A figure without a source is a claim. Each of these refers to something that can be verified: our project registry, our portfolio of active clients, or a project description published on this site.
major implementation projects carried out since the first one in 1995
Internal Project Registry
long-term clients, ranging from international corporations to institutions in French-speaking Switzerland
Active Client Portfolio
Sites managed through a single portal for one of our clients
Project summary published · platform Teams
Who are they?
Three families, with nothing in common except us.
They are not the same size, do not work in the same field, and do not have the same resources. What brings them together can be summed up in one sentence: an IT system that cannot be shut down, and no one in-house to handle the project alone.
01
International Groups
Multiple countries, multiple time zones, multiple entities that have never had the same tools—and often a recent acquisition to integrate. These are the longest and most restrictive projects: nothing can be shut down during anyone’s business hours.
- Merger of tenants Microsoft 365, mergers and acquisitions
- Teams -based Telephony: Multi-Carrier, Multi-Site, Multi-Tenant
- Delivery of equipment to job sites, including those with restricted access
02
Companies and Institutions in French-Speaking Switzerland
From 100 to 2,000 people, an IT team that knows the existing system better than anyone else—and that doesn’t have the capacity to take on yet another project. We’re taking charge of the project; they retain control and on-the-ground expertise.
- Infrastructure Renewal, Backup, and Disaster Recovery
- Microsoft 365, workspace, workplace safety
- Level 2 and 3 support, including for systems we did not build
03
Mission-Driven Organizations
Healthcare, humanitarian aid, public sector. Data governed by law, a service that operates around the clock, including nights and weekends, and an auditor who will request supporting evidence. In these sectors, compliance dictates the architecture before the technical aspects.
- Hosting and storage must be approved before any architectural decisions are made
- Service continuity during the switchover, with no downtime
- Evidence Submitted for the Audit
The common thread
Five traits that are common across all professions.
These aren’t selection criteria: they’re things we notice in hindsight, when looking back at assignments that went well. If you recognize three of them, it’s worth asking the following question.
01
They can't stop.
A 24/7 operation, a production line, and an on-call service. The result is clear: the new infrastructure is being set up alongside the old one, and we’re switching over machine by machine. It takes longer, it’s more expensive, and it’s the only viable approach.
02
They live between two worlds.
Almost no one is entirely on-premises; almost no one is entirely in the cloud. The rare skill is neither one nor the other: it’s coexistence —a synchronized directory, cross-platform messaging, a single identity, and security policies that must be consistent on both sides.
03
They have a need that the market does not meet.
In a specific scenario, there is no off-the-shelf product available. So we develop the tool that meets the need: a web service that exposes your data, an interface between two systems, a business application on Power Apps and Dataverse, an automation tool, or a calculation engine. The specific component exists separately, outside the application that uses it and outside the system that consumes its results.
04
They are accountable.
To a regulator, an auditor, a parent company, or a funder. The mandate therefore does not end with the system going live, but rather with the submission of supporting documentation: the acceptance test case completed, architecture decisions documented, and access authorizations recorded.
05
They're staying.
Not out of loyalty—no one renews a service provider out of sentiment—but because there has never been a break: the project ends, support takes over, the equipment reaches the end of its life, and another project begins. That’s the next section, and it’s probably the real answer to the question you’re asking yourself.
The Real Question
Could you be one of them?
Four questions, no contact information to provide, and an answer that specifies the terms of the contract we would offer you. Sometimes the answer is “no”—that’s written down, too, and that’s what makes the rest credible.
Answer the four questions.
The conclusion is written right here. Nothing is sent, nothing is saved, and there’s no address to provide to read it.
The Form of the Mandate
A project package.
Scope, workload, timeline, and written deliverables are established before we begin, and the price remains fixed as long as the scope does not change. This is how the majority of our projects are structured. The proposal is free of charge; the design study and audit, however, are included in the project scope.
A design and development package.
We won’t try to sell you a product that doesn’t exist. We design the tool, develop it, and then integrate it with what you already have. The specific components exist separately: built outside the application that uses them and outside the system that consumes their results, a service is tested, versioned, and monitored—and it evolves without affecting the rest.
A service contract.
Level 2 and Level 3 support after system deployment, including in environments we did not build. Taking over systems that no one else knows how to manage is part of our routine work—in fact, it’s often what brings us to a client’s site before any project even begins.
A temporary team member.
Our engineers work as part of your teams, under your supervision, at a daily rate. Lambert Consulting has helda federal license for temporary staffing services since 2018: this is the license that allows us to assign our own employees to work at your site, and not everyone has it.
Probably not us.
A company with fewer than 100 employees and no in-house IT team needs someone right on the spot—someone who can be reached within an hour when a system isn’t working. A local IT partner can do that better than we can—and for less. There are two exceptions where it’s still worth reaching out to us: if you need hardware or licenses—which we supply and deliver with or without additional services—or if your project involves business telephony, where we act as both a software vendor and an integrator.
A comparable published mandate
A telephony management platform, Teams, built from the ground up There was no off-the-shelf solution on the market for managing multiple operators, multiple sites, and multiple tenants. With more than 280 sites and a single portal, provisioning time went from hours to minutes. Read the mandate Storage infrastructure replaced without any downtime Operations run 24 hours a day, 365 days a year. The new infrastructure was set up in parallel, and the virtual machines were migrated one by one. Two data centers, synchronous replication, automatic failover. Read the mandate A migration toward Azure where compliance dictated the architecture Patient data subject to Swiss regulations. Each option was evaluated against this standard before being considered, and the on-site environment remained in operation until the client gave its approval. Read the mandate Switch from Skype for Business and an Alcatel, without missing a call 1,600 users migrated gradually, 0800 numbers retained, carrier commitments maintained during the transition, and the SBC existing infrastructure reused. Read the mandateWhat Your Team Is Changing
You have an IT department that takes the lead. In that case, we act as just one vendor among others: interface specifications validated with other service providers, test sets, and the delivery pipeline. You retain control, and we do not seek to take it over.
You have a small team. They know your current setup better than we ever will, and they don’t have time to manage another project on top of that. We’ll manage the project, they’ll stay in control of their day-to-day operations, and we’ll stick to a schedule agreed upon in advance.
You don't have a dedicated in-house team. The scope of work therefore includes what no one else will handle for you: documentation, handoff to your usual service provider (if you have one), and post-launch support.
What You'll Receive
In any case: a proposal for the project —the scope, estimated workload, timeline, and list of deliverables. Not an opinion, not a sales pitch.
This estimate is for informational purposes only: it is calculated based on your four answers, without any information about your circumstances. It does not constitute an offer. We will respond within 24 business hours.
Duration
Why a Customer Stays: Five Steps.
Loyalty cannot be bought or demanded. It stems from the fact that there is never a break between two terms: at every stage, someone who is already familiar with the environment is still there.
Step 01
Going live isn't the end.
The test script is run with you, the documentation is provided, and the previous environment remains in service until you approve it. Until you say yes, nothing is taken down.
Step 02
Support takes over.
Level 3 in our areas of expertise, Level 2 in certain technologies. The engineers who respond are the ones who built— or took over —the environment: taking over systems that no one else knows how to manage is part of our routine assignments.
Step 03
Reinforcements arrive when the peak arrives.
A new project, an audit, a site takeover, or a side project. In these cases, our engineers work on a time-and-materials basis, integrated into your teams and under your direction—this is permitted under the federal license for temporary staffing services, which we have held since 2018.
Step 04
The equipment and licenses are listed below.
A server’s warranty is about to expire, a software license agreement is up for renewal, or a new location is opening abroad. We size, configure, and prepare the workstations before the boxes are even opened, and we deliver them directly to your locations.
Step 05
And the next project begins.
With the same people, and without starting from scratch. That’s the whole point: it’s not fidelity that makes a relationship last—it’s the absence of a breakup.
The best we can do
Talk to one of our customers.
Not ours— his. A useful reference isn’t just a logo in a grid; it’s someone who’s been through the same project that you’re about to undertake and who can tell you how it really went.
Tell us what you're trying to verify
A specific technology, organizational size, industry, or type of assignment. The more specific you are, the more comparable the reference will be—and the faster we’ll know who to reach out to.
We ask the customer in question for their consent
No names are released without prior approval. That is why there is no list on this page, and it also explains the delay: please allow a few business days for the person to respond.
You communicate directly
By phone or videoconference—and without us participating in the conversation, if you prefer. We have no interest in attending a meeting whose purpose is precisely that we not be there.
On the form, select “Get Customer References” and specify the technology: your request will be sent to the sales team at Renens —and nowhere else.
What We Won't Do
Publish a collection of logos to make it look like there are a lot of them.
A logo doesn't prove anything: not the scope of the project, not its success, not even that it took place this past decade. We'd rather have a twenty-minute conversation with someone who was there.
To take a closer look
Let's talk about it
Describe your situation. We'll respond with a scope of work.
Just a few lines will suffice: what you have, what you want to achieve, and what’s standing in your way. We’ll let you know what similar projects we’ve handled before and how we could assist—whether on a fixed-price basis, on a time-and-materials basis, or through post-launch support.
Preparing a quote is free. Design studies and audits are included in the scope of work. We’ll respond within 24 business hours.