Questions we are usually asked first
Practical answers about what ELVARIS SOFTWARE LTD provides, how a project is scoped and proposed, and what happens after delivery. Where an answer genuinely depends on the work involved, that is said plainly rather than guessed at.
What ELVARIS does, and how work is defined
The two registered activities, the difference between them, and how the boundary of a piece of work is agreed.
ELVARIS SOFTWARE LTD is a UK private limited company registered in England and Wales, providing project-based software development and information technology consultancy. It is registered for two activities: 62012 — business and domestic software development and 62020 — information technology consultancy activities.
The work is organised into four categories holding eight named services in total. Each service is scoped and priced individually rather than sold as a bundle, and every engagement is delivered against a written proposal agreed in advance.
Software development (62012) produces a working browser-based system: workforce planning and resource platforms, appointment, membership and client portals, smart property and connected home applications, or cross-device service experience platforms. The output is deployed software plus handover documentation and source materials.
IT consultancy (62020) produces a written, evidence-based recommendation rather than software: cloud migration readiness and platform planning, application portfolio and platform architecture, a digital product delivery operating model, or an automation, integration and data flow strategy.
Some engagements draw on both, where a consultancy review leads into a build. Which applies to your situation is confirmed during the initial conversation.
Scope is defined in a written proposal before any work begins. The proposal sets out what is included, the assumptions it rests on, an indicative starting price and an indicative timeframe. Those assumptions come from the information supplied during scoping, so the more accurate that information is, the more accurate the scope.
Any later change — whether requested by you or identified during delivery — is agreed in writing before it is carried out, and may affect both price and timeframe. The written proposal stays the reference point for both sides throughout the engagement.
Yes — most engagements involve systems that already exist. A new platform is normally expected to sit alongside current tools rather than replace everything, and the services descriptions treat existing systems and required integrations as standard scoping questions.
Integration with a third-party system is possible where that system offers a suitable interface, and is scoped and priced individually rather than assumed. Where no suitable interface exists, that constraint is stated in the review or proposal along with any realistic alternatives.
How an engagement actually runs
From the first conversation through to review, and what is needed from you along the way.
It starts with a call or written exchange to understand what has prompted the enquiry, which registered activity applies, and what a useful outcome would look like. There is no charge for an initial conversation, and submitting an enquiry does not commit either side to proceed.
From there the situation is described in enough detail to identify the relevant category and service, after which ELVARIS sets out what information is needed to write an accurate proposal.
Typically: a description of the current process and where it falls short; details of any existing systems the work needs to sit alongside; who will use the result and in what roles; any branding, content or reference material to be reflected; and a named point of contact for decisions during the engagement.
For a consultancy review, this usually also includes current system inventories and hosting arrangements, any process documentation that exists, usage or volume data where available, and access to the relevant people for structured conversations. Where documentation is incomplete, structured interviews can substitute, though that may extend the evidence-gathering stage.
Each service carries an indicative duration — consultancy reviews range from around two to six weeks, and development projects from around four to ten weeks, depending on the service. These are estimates, not guaranteed delivery dates.
The figure for your engagement is confirmed in the written proposal. What moves a project towards the longer end of its range is usually the number of distinct user roles, integration with existing systems, bespoke reporting requirements, data migration, or additional review cycles beyond those set out in the proposal. Delivery can also be affected by delays in information, approvals, access or third-party dependencies.
Where an engagement requires access to your systems, accounts or premises, that access is granted at your discretion and used only for the purposes of the agreed work. ELVARIS requests only the access reasonably necessary to deliver the scoped engagement.
Both parties agree to keep non-public information disclosed during a project confidential and to use it only for that project, except where disclosure is required by law. Where an engagement involves personal data, both parties comply with applicable data protection law; how ELVARIS handles personal data is set out in the Privacy Policy.
Pricing, proposals and what follows delivery
How figures are arrived at, what sits outside a starting price, and how to begin.
Every service shows an indicative starting price, from £1,200 for the shortest consultancy review up to £1,900 for the largest development service. These are starting points, not fixed final prices.
Final pricing is confirmed in a written proposal after your requirements have been reviewed, and depends on the scope factors relevant to that service. Prices are exclusive of VAT and any other applicable taxes unless a proposal states otherwise. Third-party services are not automatically included — software subscriptions, hosting, domain registration and similar infrastructure costs are identified during scoping and are normally your responsibility to procure or reimburse. Work begins only once a proposal has been accepted in writing.
Yes. Post-launch support is not included in a starting price by default, but it can be arranged as a separate, optional arrangement agreed in writing. The same applies to further development or a follow-on consultancy review.
Handover is designed so that this remains your choice rather than a dependency: on full payment of sums due, you receive the source materials and documentation needed to maintain the outcome, either in-house or with a provider of your choosing.
Use the enquiry form on the Contact page, which lets you describe the current situation, the objective, intended users, existing systems and any required integrations. You can also call +44 7737 137168 or email support@elvarissoftware.tech directly.
If you are unsure which service applies, say so — describing the situation is enough, and the right starting point is confirmed before any proposal is written. Work is delivered remotely where appropriate, with scope and commercial terms agreed in writing beforehand.
Where an answer depends on the specific work involved, the details are confirmed after an initial discussion and in the written proposal. Full commercial terms are set out in the Terms & Conditions.
Still have a question?
Describe the situation and we will confirm the right starting point before any proposal is written. There is no charge for an initial conversation.