How we work

Agree what working means.

A useful implementation begins with the actual problem and a shared definition of acceptance. Calvoryn works from that definition through the build, the tests and the handover.

An explicit path to acceptance

Understand → Define → Build → Verify

  1. 01

    Understand the system

    Start with the work that needs to happen, the tools already in place and the point where the path breaks down. Identify constraints, dependencies and the people affected.

    Output a shared account of the problem and the current system.

  2. 02

    Define a bounded scope

    Agree the intended behaviour, what is out of scope and what must never happen. Name the person who can accept the result. Prefer the smallest useful change that addresses the need.

    Output an agreed scope and acceptance criteria.

  3. 03

    Build and test the path

    Reuse existing tools where they fit. Build the missing connections and test the operating path, including the failures and exceptions that matter to this engagement.

    Output an implementation with evidence of what was tested and any known limitations.

  4. 04

    Verify and hand over

    Have the accepting person work through the agreed criteria. Explain how to operate the system, recognise a failure and stop or recover the workflow. Discuss further improvements after acceptance.

    Output a clear acceptance decision and an operational handover.

Questions to agree before delivery

  • What result should the system produce?
  • Which inputs and exceptions are in scope?
  • Which actions require a person's approval?
  • How does an operator see that something has failed?
  • How can the workflow be stopped or recovered?
  • Who is authorised to accept the result?

These questions form a starting point. The final criteria depend on the work.

Scope, price and ongoing support

Scope, timing and price are discussed after the current situation is understood. Changes to the work need an explicit decision. Ongoing monitoring, maintenance and support are defined for the engagement rather than assumed.

Explore the services · Read about production acceptance

Start a conversation

Start with the work in front of you.

Describe the current system, the problem and the constraints. A short note is enough to start.

Discuss a project