How we work

Scope first. Then a stage you can judge.

Operations Software starts by mapping the work and agreeing the scope. Vantaris by Tecblitz starts with a conversation, then Replay on your own history. AVENOR starts with a website or store preview. Each path is its own engagement.

Operations Software

Map the work, then agree the scope.

This path is for custom software around how a company works, from one workflow to a complete operational system. It is not a Vantaris engagement, and it is not an AVENOR preview.

  1. Map the work

    Walk through the workflow with the people who do it. Name the request, the records, the decisions and who needs to act.

  2. Agree the scope

    Write the first workflow, what is included, and how the team will judge it, before the build starts.

  3. Test with the team

    The people who will use it try the workflow and compare it with the agreed scope.

  4. Expand where useful

    A later workflow, team or record is a separate decision, taken when the first one is useful.

Vantaris

One workflow, evaluated, then a decision.

This track is for Vantaris by Tecblitz. Replay on your own history is the first paid stage. Custom operations software has its own track.

Container ship, gantry crane, truck and warehouse at a harbour.
Illustrative · Sample data
  1. Initial conversation

    The supply chain question, in your words.

  2. Replay on your history (first paid stage)

    We run the agreed rules on your own history and show which past problems they would have caught, and which they missed.

  3. Configure to your locations, suppliers and stock records

    The build matches Vantaris to those records.

  4. Staged rollout

    Further sites or workflows are a separate decision.

  5. Subscription: hosting, updates and support

    Hosting, updates and support continue under the subscription.

The enquiry stays on the stock or supplier decision. It does not ask you to choose a technical layer. Operations Software and an AVENOR preview are separate offers.

Three short answers do not produce one fixed price for a complex build.

AVENOR

A preview before you pay for the build.

This path is a website or store preview. It is not Operations Software and it is not Vantaris.

  1. What the business needs to show

    For a website, the pages and the enquiries. For a store, the products, the delivery and who will work the orders.

  2. A preview

    A working website preview, or a clickable store preview. You can stop before you pay.

    Before you pay
  3. A written scope

    The pages, the rules and the payment schedule are named before the production build starts.

    The scope
  4. Build, changes, support

    Two rounds of changes are included, and support continues after launch. Work outside the plan is quoted first. There is no universal delivery date.

    Agreed in writing

On every engagement

The agreement is the offer.

This page describes how we work. The signed agreement governs the job.

  • Confidentiality can be arranged during scoping. It is not a list of unnamed clients.
  • Your data, the export and the handover are written into the engagement.
  • A change outside the agreed scope is quoted before it is built.
  • Work is tested away from the live system and moves across when you accept it.

Describe the problem first.

Operations Software, Vantaris, or an AVENOR preview. We reply by email or by phone.