A structured sequence, used on every engagement
Whether the work is a software build or a consultancy review, ELVARIS follows the same nine-stage sequence. It keeps scope visible, gives both sides a clear point of reference, and means nothing starts without a written agreement in place.
The complete engagement sequence
From the first conversation to delivery and optional support, each stage keeps scope, responsibilities and decisions visible.
Seven visible points on the way to delivery
The nine stages below group into seven points a client actually experiences. Each one has a clear output, so it is always obvious where an engagement currently sits.
Conversation
An initial call. Output: a shared understanding of the problem.
Scope
Information request. Output: an agreed boundary for the work.
Discovery
Evidence gathering. Output: findings grounded in your systems.
Design / analysis
Build or draft. Output: a working system or a written recommendation.
Review
Validation against scope. Output: confirmed or corrected work.
Delivery
Handover. Output: source materials and documentation.
Optional support
Arranged separately. Output: a further written agreement.
From first conversation to optional follow-on support
Initial conversation
A call or written exchange to understand what has prompted the enquiry, whether it fits software development, IT consultancy, or both, and what a useful outcome would look like.
Problem and context definition
The situation is described in enough detail to identify which category and service applies, and what existing systems, teams or constraints are already in play.
Scope and information request
ELVARIS sets out what information is needed to write an accurate proposal — process detail, system inventories, stakeholder availability, or reference material, depending on the service.
Written proposal
A written proposal is issued covering scope, assumptions, an indicative starting price, and an indicative timeframe. Nothing is built or analysed before this is agreed.
Discovery or analysis
For development, this covers data structure and interface decisions. For consultancy, this covers evidence gathering — document review and structured conversations with relevant people.
Design or recommendation
Development work moves into build against the agreed design. Consultancy work moves into drafting the written recommendation, findings and any supporting diagrams.
Review and validation
The client reviews the output — a working build or a draft recommendation — against the written scope, and any agreed revision points are addressed.
Delivery
The finished system or the finished written output is delivered, along with the documentation and source materials needed for the client to use it independently.
Optional follow-on support
Ongoing support, further development or a follow-on consultancy review can be arranged separately, in writing, once the initial engagement has closed.
How the sequence applies to a build
Stages 5 and 6 focus on interface and data-structure design, followed by development. Stage 7 becomes client testing against the written scope. Stage 8 includes source materials and administration notes.
View software development →How the sequence applies to a review
Stages 5 and 6 focus on evidence gathering and drafting findings. Stage 7 becomes a walkthrough of the draft recommendation. Stage 8 is the final written output plus any supporting diagrams.
View IT consultancy →Ready for stage one?
Start with a conversation about the situation you are facing. There is no charge for an initial conversation.