VELORIQ

Software Ltd

VELORIQSOFTWARE LTD Routing toVeloriq
VELORIQSOFTWARE LTD
+44 7848 457256 Start a Project
A project team working through plans and reference material around a large table

Process

Seven stages. No stage where you are left guessing.

Every project runs through the same sequence, sized to the work. Each stage states what we need from you, what we provide, and what exists at the end of it — so progress is something you can see rather than something you are told about.

Why it is written down

Most project failures are communication failures wearing a technical disguise.

Software projects rarely fail because a technical problem proved unsolvable. They fail because two parties held different assumptions about what was being built, discovered it late, and had no agreed mechanism for resolving the difference.

The process below exists to make those assumptions visible early, while they are still cheap to correct. It is why we write an exclusion list as well as a scope, why quotations are fixed against a defined scope, and why every stage produces something you can review rather than a percentage complete.

It scales down as well as up. A three-week automation project runs through the same seven stages as a six-month platform build — some of them in a single afternoon.

Written scopeIncluding what is explicitly excluded.
Fixed quotationAgainst that scope. It moves only if scope moves.
Working softwareReviewable at every stage, not a status report.
Named contactDirect access to the people doing the work.

The sequence

Seven stages, seven defined outputs

Nothing is marked complete because a date has passed. A stage ends when the thing it was supposed to produce exists and you have seen it.

Drawn in SVG for this page. The same sequence runs whether the project is three weeks or six months — only the depth of each stage changes.

The seven stages

01 of 07

  1. 01Discovery
  2. 02Scope & Planning
  3. 03UX & Technical Architecture
  4. 04Development / Advisory
  5. 05Testing & Review
  6. 06Deployment / Delivery
  7. 07Support & Improvement
Start at stage one
01

Discovery

Understanding the problem before proposing anything

A working conversation about the process, the people who use it, what currently goes wrong and what a good outcome looks like in practical terms. For larger engagements this extends into observation and stakeholder interviews.

What you provide

  • A description of the problem, not a specification
  • Access to the people who do the work
  • Any existing documentation, however incomplete
  • An honest view of previous attempts

What Veloriq provides

  • Structured discussion and question set
  • Review of existing systems and data
  • Process observation where useful
  • Early view of feasibility and rough cost

Output at this stage

  • Written summary of the requirement
  • Initial risks and constraints
  • Indication of which services apply
  • A go or no-go recommendation
02

Scope & Planning

Turning a requirement into a fixed, written commitment

We write down exactly what is included, what is explicitly excluded, what it will cost and how long it will take. The exclusion list is the part most suppliers omit and the part that prevents most disputes.

What you provide

  • Review and challenge of the draft scope
  • Confirmation of priorities and constraints
  • Named decision maker and point of contact
  • Purchase approval where required

What Veloriq provides

  • Detailed scope document
  • Fixed quotation against that scope
  • Schedule with stages and review points
  • Assumptions and dependencies stated

Output at this stage

  • Signed scope and quotation
  • Agreed schedule
  • Change control process
  • Payment stages confirmed
03

UX & Technical Architecture

Designing the structure before building on it

Data model, screen flows, interface design across breakpoints, integration points and technical approach. For consultancy engagements this stage is the analysis framework and the evidence to be gathered.

What you provide

  • Review of designs and data model
  • Confirmation of terminology and rules
  • Access to systems to be integrated
  • Feedback within agreed review windows

What Veloriq provides

  • Data model and schema design
  • Interface design for desktop and mobile
  • Architecture and technology decisions
  • Non-functional targets written down

Output at this stage

  • Approved designs
  • Documented architecture
  • Integration specifications
  • Test approach
04

Development / Advisory

The work itself, in reviewable increments

Development proceeds in vertical slices, each one complete and usable, with a working environment available to you throughout. Consultancy proceeds through evidence gathering, analysis and option development.

What you provide

  • Regular review of working software
  • Prompt answers to open questions
  • Early flagging of anything that has changed
  • Attendance at agreed review points

What Veloriq provides

  • Development in short cycles
  • Working environment kept available
  • Written progress notes at each review
  • Immediate flagging of scope questions

Output at this stage

  • Working software at every review
  • Updated documentation
  • Open decisions log
  • Revised estimates if scope changes
05

Testing & Review

Proving it works, including the awkward cases

Automated tests on core logic, manual testing of journeys, cross-browser and responsive checks, security and accessibility review, then structured user acceptance testing by your team against the agreed scope.

What you provide

  • User acceptance testing against the scope
  • Realistic test data where possible
  • Consolidated feedback, prioritised
  • Sign-off or a clear list of defects

What Veloriq provides

  • Automated and manual test execution
  • Security and accessibility checks
  • Performance verification
  • Defect correction and retest

Output at this stage

  • Test results and coverage summary
  • Defect log with resolution status
  • Accessibility and performance notes
  • Acceptance sign-off
06

Deployment / Delivery

Going live without drama

Production setup, data migration with verification, cutover plan, rollback route and support through the first period of live running. For consultancy, this is the delivery of the written report and the working session.

What you provide

  • Confirmation of the cutover window
  • Availability of key staff at go-live
  • Communication to end users
  • Final data verification

What Veloriq provides

  • Production environment and monitoring
  • Data migration and reconciliation
  • Cutover execution and rollback plan
  • Documentation and handover session

Output at this stage

  • Live system, or delivered report
  • Source code and documentation
  • Credentials in your own accounts
  • Trained staff and support route
07

Support & Improvement

What happens after the invoice is paid

A defined post-delivery period during which defects in the delivered scope are corrected at no charge, followed by an optional arrangement for ongoing support, maintenance or continued development. There is no compulsory retainer.

What you provide

  • Reporting of any defects found
  • A decision on ongoing arrangements
  • Feedback once the system is in real use
  • Notice of upcoming changes to the business

What Veloriq provides

  • Defect correction within the agreed period
  • Monitoring and error review
  • Recommendations for improvement
  • Costed options for the next stage

Output at this stage

  • Stable system in live use
  • Improvement backlog if wanted
  • Clear ongoing cost, or none
  • Full ability to leave and self-maintain

Change control

What happens when something changes

Requirements change during projects. That is normal and usually a sign something useful has been learned. What matters is that it never changes the price without your agreement.

  • 01
    Raise it at any time

    Through your named point of contact. Small refinements that do not affect scope are absorbed as part of normal iteration.

  • 02
    We assess it in writing

    What the change involves, what it affects, the effect on price and the effect on the schedule — stated before any work begins.

  • 03
    You approve or decline

    Work on the change starts only once you have approved it. Declining a change costs nothing and does not affect the agreed scope.

  • 04
    The plan is reissued

    Scope, schedule and quotation are updated so there is always one current version rather than a trail of amendments.

Ready to start at stage one?

Discovery begins with a conversation. Send an enquiry or call us directly, and we will tell you quickly whether this is work we should be doing.

Start a Project Call +44 7848 457256