Get it delivered
Client-side advisory: turning your needs into requirements, and choosing the right solution
Comparable offers, a reasoned decision
Client-side advisory (known in French as AMOA) means turning a company’s needs into requirements the market can understand, consulting the right players, comparing their responses and helping leadership decide. Lunova, a consulting firm based in Nyon, holds this role for SMEs in Western Switzerland: we represent your interests towards vendors, without selling or installing the solution chosen.
Situations
What client-side advisory resolves
What makes an IT decision expensive has less to do with the product chosen than with what came before the choice: a poorly stated need, offers that cannot be compared, commitments whose reach nobody measured.
A company calls on client-side advisory when it is about to commit money to an IT solution and wants to decide on comparable evidence rather than on a proposal it received. Several situations lead there.
The assessment is done, the trajectory is set: now you need to know what the market offers, at what service level and at what cost, before committing to anything.
Renewing a major building block of the IS
A core network, a collaboration platform, a key application: several vendors are in play, scopes overlap and offers arrive built on different bases.
A new building or site to equip
The IT side is decided at the same time as the rest of the project, with deadlines that cannot be recovered and choices that are hard to reverse once works have started.
A capable internal team without the time
Business units and IT know what they need; nobody has the weeks required to write it down, consult the market and analyse the responses on top of the day-to-day.
A vendor proposal nobody can challenge
The incumbent provider proposes a solution. It may be the right one, but the company has no means of checking, or of knowing what it would have obtained elsewhere.
Results
What client-side advisory changes for your company
Five concrete effects of formalising the need before going to the market.
Needs written by the company, not by the vendor
Requirements are built from what your teams do and what they need to achieve, then validated by them. The market then responds to your needs, in your terms, and not to a vendor’s reading of them.
Offers that can really be compared
A mandatory response framework requires bidders to price the same scope, address the same assumptions and present their recurring costs the same way. Without it, the gap between two proposals tells you more about their sales writing than their content.
Risks addressed before signature
Dependencies, reversibility, service commitments, liability in case of failure, infrastructure prerequisites, internal workload to plan for: these points are dealt with during the consultation, while they can still be negotiated.
Project workload absorbed externally
Your teams stay on what nobody can do for them: expressing the need, arbitrating, approving. Writing, bidder relations, response analysis and running meetings are taken care of.
Support at the right level
Some teams need continuous support; others need expertise on a specific point at a specific time. The level of involvement is defined with you at scoping and need not be the same from start to finish.
Method
How a client-side advisory engagement works
Client-side advisory follows the same logic whatever the subject: formalise, consult, compare, decide, then support design, verify and support the teams. The depth of each step adjusts to the scope and deadlines, and not every step is used in every engagement.
1 · Scoping
The context, what the company wants to achieve, the time and budget constraints, the stakeholders to involve and how the decision will be taken.
2 · Expressing the need
Interviews with business units and IT, then translation into prioritised requirements: functional, technical, service and contractual. This is where the quality of everything that follows is decided: needs written in the company’s language, not the vendor’s.
3 · Consulting the market
An RFI when the field is still open, to identify what exists and narrow the scope. An RFP when the need is settled, to put bidders in competition on an identical basis with a mandatory response framework.
4 · Comparing responses
A comparison grid built on the requirements, clarification questions to bidders, highlighting gaps against the need, risks and what the offers leave unsaid.
5 · Supporting the decision
A reasoned recommendation, with the strengths and limits of each response. The decision belongs to the company: our role is to make sure it decides with full knowledge, not to decide in its place.
6 · Supporting design
Between the decision and delivery, taking part in the workshops held with the selected provider: steering design choices so they serve the intended use, and supporting business users, for whom this is when the concrete consequences of the decision become visible.
7 · User acceptance testing
Once the solution is delivered, checking that it does what the specifications required: defining test cases from the requirements, organising tests with users, logging deviations and tracking their correction before go-live.
8 · Change support
Preparing teams to work differently: identifying what concretely changes in their daily work, informing at the right time, organising skills development and raising difficulties while they can still be addressed.
Lunova does not develop, configure or integrate: specialists do the work. Its role is that of a conductor: analysing, selecting, challenging, coordinating, arbitrating with you and following delivery through to the result. When we know technologies or partners that work, we propose them because we consider that they meet the need.
Examples
Examples of client-side advisory engagements
These examples illustrate the role of client-side advisory before the decision: formalising the need and preparing a choice on comparable grounds. Depending on the project, it then continues through design, user acceptance testing and change support.
A market consultation as part of an IT master plan (RFI).
The field is open: the goal is to identify the players and solutions available, understand the models and orders of magnitude, and narrow the field before writing a tender.
A network tender (RFP).
The need is settled: technical and service requirements, mandatory response framework, comparison of offers, input to the decision.
Choosing a collaboration platform.
Formalising expected uses, document management requirements and existing constraints, then consulting on that basis.
The IT side of a new building.
Translating operational needs into requirements, consulting the vendors concerned and making decisions at the right point in the construction schedule.
Deliverables
What you receive
What client-side advisory produces is not an end-of-engagement report. It is the working documents that make it possible to consult the market, compare responses and decide, then to check during acceptance testing that the solution meets the requirements set.
The exact scope is set at scoping. Depending on the engagement, it produces:
- a statement of needs or specifications, with prioritised requirements validated by the business units;
- the consultation pack sent to vendors (RFI or RFP), including the response framework that makes offers comparable;
- a comparison grid of the responses received, built on those requirements;
- a decision summary: gaps against the need, risks identified, points to clarify or negotiate before signing;
- when the engagement runs through to delivery, the test cases derived from the requirements and the log of deviations found during acceptance testing.
These documents belong to the company. Steering delivery (schedule, provider coordination, steering committees) is a different service, project leadership, which can be carried out in parallel or entrusted to someone else.
Comparison
Client side or delivery side: who does what?
What the role represents
Client side
Represents the company that buys.
Delivery side
Builds what the company has bought.
What it does
Client side
Turns the need into requirements, consults the market, compares responses, informs the decision, then checks during acceptance testing that what is delivered matches what was asked for, and supports the teams.
Delivery side
Designs, develops, configures, installs and puts the solution into service.
How its success is measured
Client side
The quality of the decision and the fit with the need.
Delivery side
The conformity of what is built and the fulfilment of commitments.
Who holds it
Client side
Lunova.
Delivery side
The integrator, software vendor or provider selected.
Both roles are necessary and complementary. Confusing them means asking the same party to propose a solution and judge whether it was the right one. Lunova does not develop, configure or integrate: that is what allows it to represent your point of view towards the market rather than that of a solution.
Before you decide
Your questions about client-side advisory
How much does a client-side advisory engagement cost?
Scope and budget are tailored to the size and complexity of the company. Formalising the need for a single building block and running a multi-lot tender are not the same amount of work. A thirty-minute conversation, with no commitment, helps frame the need and size the engagement before any pricing.
What is the difference between client-side advisory and project leadership?
Client-side advisory represents the client: it formalises the need, writes the requirements, consults the market, compares responses and informs the decision, then supports design, checks what is delivered through acceptance testing and supports the change. Project leadership steers delivery: scope, schedule, budget, risks, coordination of teams and providers, governance and go-live. The two roles are distinct and can be held in parallel on the same project, including by the same person.
Our provider already supplies a project manager. Does client-side advisory still make sense?
The vendor’s project manager steers delivery within the scope of its contract, and that is their role. Client-side advisory sits on the other side of the table: it represents the company, checks that what is delivered matches what was asked for and raises the points that do not suit the vendor. The two roles coexist without replacing each other.
How do you choose a solution without starting from a vendor’s proposal?
By writing the need before looking at the market, and by imposing the same response framework on every bidder. An unsolicited proposal may be excellent; the problem is that without a reference point, nothing allows you to check it or know what you would have obtained elsewhere.
Should we change the tool or review the processes first?
The question comes up with ERP and business applications. Replacing a tool without addressing processes and data quality means reproducing the problem in a newer, more expensive environment. Formalising the need forces this point to be settled before going to the market, not during roll-out.
Who writes the specifications, you or our teams?
The need belongs to the company; the writing is joint work. We conduct the interviews, structure the requirements and draft the document; your business teams review and approve it. Specifications they have not approved do not bind them, and the project pays for it later.