Upshot Engine
For governmentLet’s talk

ENGAGEMENTS

Custom pricing. Clear scope.

Pricing reflects your workflows, systems, deployment requirements, and team. We agree the scope, investment, and delivery milestones before work begins.

Discuss your project

02 / Help your people adopt AI

AI Training & Enablement

Help employees use approved AI tools confidently in the work they do every day.

Custom program pricing

Shaped around your teams, roles, and learning objectives.

Discuss employee training
What’s included
  • Role-specific workshops and practical exercises
  • Employee onboarding and workflow playbooks
  • Guidance for using your approved tools
  • Adoption support and agreed progress measures

03 / Keep improving

Ongoing Support

Keep your AI systems useful as your data, workflows, and team requirements evolve.

Custom monthly agreement

Coverage, service levels, and improvement capacity agreed upfront.

Discuss ongoing support
What’s included
  • Monitoring and maintenance for agreed systems
  • Source and integration upkeep
  • Quality reviews and scoped improvements
  • Support coverage and escalation process

A sample first engagement

Your first pilot.

Start with a bounded implementation your team can evaluate. For example, help a client-service team prepare a meeting brief from approved account records. The proposal defines the sources, deliverables, responsibilities, and price for your organization.

  1. 01

    A defined task and baseline

    What you receiveWorkflow map, source register, and acceptance criteria.

    How this works

    Choose one team and one recurring workflow. Agree the source set, permission boundaries, current effort, and what counts as an accepted output.

  2. 02

    A working pilot and evaluation

    What you receiveWorking pilot, evaluation findings, and an issue log.

    How this works

    Build with representative, approved information. Run the same tasks through the existing and assisted workflows, including missing data and review steps.

  3. 03

    An enabled team and a decision

    What you receiveTeam playbook, handover, and a go/no-go recommendation.

    How this works

    Onboard the pilot group, document operating responsibilities, and review the evidence together. Decide whether to expand, revise the workflow, or stop.

Your responsibilities & what we agree upfront

What your team contributes

A business owner, representative tasks and approved source access, an IT or security contact, and time from the employees and subject experts who will test the output.

What we agree before starting

Scope, delivery milestones, evaluation criteria, software and operating costs, ownership, and support. Expansion is a separate decision based on the pilot findings.

Discuss your first workflow

A CLEAR STARTING POINT

From conversation to proposal.

Start with one useful outcome. We make the scope and costs clear before you commit to the work.

01 / Start with a conversation

In a free discovery conversation, identify a useful first workflow, the people involved, and the sources it depends on. Discuss whether implementation or training is the right starting point.

02 / Understand the investment

Once we understand the need, we share an initial budget estimate so you can assess the fit.

03 / Resolve the unknowns

If technical questions need deeper investigation, agree a separate paid assessment. Its written outputs can include a workflow map, source and integration findings, and a proposed implementation scope.

04 / Agree the work upfront

Your proposal sets out deliverables, fees, milestones, and acceptance criteria before implementation begins.

BEFORE WE BEGIN

Pricing questions.

Looking for employee training?
Explore AI enablement

Public-sector project?
See government engagement options

What determines the price?

Your workflows, data quality, integrations, deployment requirements, access controls, team size, and support needs shape the scope. We explain those factors and provide an initial budget estimate after understanding the project.

Do we need a paid assessment first?

The first discovery conversation is free. If we need to investigate technical uncertainty before quoting implementation, we propose a separate paid assessment with clear deliverables and a fee for you to approve.

How are fees and payments agreed?

Once the scope is clear, we agree the project or program fee and payment milestones in your proposal. Ongoing support has its own monthly agreement. Changes to scope are reviewed and priced before additional work begins.

Are software and running costs included?

Your proposal identifies implementation fees, third-party licenses, cloud and model usage, and ongoing support separately. We make clear what is included, what is billed separately, and which costs depend on usage.

What happens after delivery?

We agree documentation, handover, ownership, and any post-delivery support in your proposal. Ongoing monitoring, maintenance, improvements, and service levels can be covered by a separate support agreement.

Can we book employee training on its own?

Yes. Training can support an implementation or stand alone around tools your organization already approves. We scope the program around your roles, cohort size, workshops, and adoption needs.