aitsa integration
Menu

How we work

A clear scope. A practical way forward.

Choose the service, agree the outputs and work through a scope that fits your business. Training, roadmaps and implementation each have their own delivery path.

Start a conversation

Start with the result you need.

The initial conversation is free. We explore a workflow, a learning need or an AI decision and agree a sensible next step. Any deeper investigation is agreed before it begins.

Leadership AI training, employee workshops and corporate roadmaps are paid services that can each be bought on their own. Implementation is optional and separately scoped.

Corporate AI training and roadmaps

Prepare, deliver and check the agreed result.

Your corporate proposal sets out the paid scope, fee, payment terms, client inputs, participants, delivery format, outputs and acceptance check. The session length or roadmap schedule is agreed for the work you need.

Workflow implementation

From an agreed scope to a usable system.

  1. Define the implementation

    Understand the workflow, who it affects and what needs to improve. Any further investigation needed before an implementation quote is agreed before it begins.

  2. Agree the work

    Your implementation proposal defines the scope, fixed fee, responsibilities, schedule and completion checks. Implementation begins after acceptance and the agreed 50% deposit.

  3. Build and test together

    Within the accepted scope, we confirm the process, configure or build the system and test representative normal and exception cases with your input.

  4. Complete and hand over

    Check the implementation deliverables and provide the agreed instructions, training and initial support. The remaining 50% of the implementation fee is payable at its defined completion point, followed by the agreed follow-up.

Put the important details in the proposal.

A useful scope makes the work reviewable before it begins. It identifies the service, organisational boundary, client inputs, preparation, deliverables and acceptance checks. System implementation also needs its users, integrations and information work defined.

  • Responsibilities

    Who supplies information, provides access, makes decisions and takes part in the agreed sessions, validation or testing.

  • Practical arrangements

    The participants, delivery format, tool access, materials and handover needed. For systems, include hosting, accounts and running costs.

  • Follow-up and changes

    Any agreed follow-up, revision or support, its limits and how additional work is quoted.

After system implementation

Give the system time to become part of the work.

The implementation follow-up is a chance to review how the system is being used and what needs attention. We normally discuss optional ongoing system support after 30–60 days of use.

For an Aitsa implementation, you retain use of the delivered system without taking a retainer. Third-party subscriptions remain payable, and new features or processes are agreed as additional work.

Understand pricing and support

Good questions

A little clarity
before we begin.

Ask your own question
How is the delivery schedule agreed?

For corporate training and roadmaps, preparation, participants, format, written outputs and any validation or revisions determine the schedule. Implementation timing also depends on integrations, information quality and testing. Your proposal sets the schedule for the service you choose.

What if the requirements change?

Changes to the agreed scope are discussed before the additional work is undertaken. New features, integrations or processes may need a separate quote.

What does initial implementation support include?

The implementation proposal specifies handover and training, fixes where the system does not perform as agreed, and follow-up. Its duration, contact arrangements and limits are set for that project. Any follow-up for a corporate training or roadmap engagement is agreed in that service’s own scope.

Will we receive a quote after the first conversation?

A quote needs a clear enough scope to define the work and acceptance checks. The first conversation may establish that outline or identify further investigation to agree before a proposal can be prepared.

A useful place to start

More room for the work that moves you forward.

Bring a workflow to improve, a team that needs practical AI skills, or a decision about where to begin. Let’s find a useful next step.

Start a conversationA free first conversation. No commitment to a project.