Your analytics preferences

With your permission, we use optional analytics to understand website visits and improve our services. You can change your choice in the footer at any time.

Solutions

Fixed-scope AI solutions

Packaged ways to put AI to work, each with a defined outcome, timeline and price. Pick the one that matches your problem and agree the scope before the build.

02Solutions or services?

When a package beats a custom engagement

If your problem matches one of these solutions, it's the fastest way to start. The scope, deliverables and price are known up front, so approval takes a meeting instead of a quarter.

If it doesn't match, that's fine too. Our services cover the same ground with a scope built around your situation, and we'll tell you which route makes more sense on the first call.

03Engagement

How a solution engagement runs

  1. 01Day 1

    Scope call

    A 45-minute call to confirm the solution fits your problem and constraints.

  2. 02Within a week

    Proposal

    Fixed scope, timeline, price and the people who'll deliver it.

  3. 03Week 1

    Kickoff

    Access, success metrics and the delivery plan agreed with your team.

  4. 04Per solution

    Delivery

    Fortnightly demos and a shared progress board from start to finish.

  5. 05Final week

    Handover

    Documentation, training and an agreed plan for what comes next.

04Plan the work

Buy a defined outcome, not an open-ended team

A fixed-scope AI solution is a buying decision with a boundary. The page should tell you who the package fits, what it includes, how delivery is organized and what your team needs to contribute. A scope call checks those assumptions against your situation. It is not a reason to stretch a package until it becomes a different project. If the work does not fit, we point you toward a custom service instead.

The starting points solve different problems. AI Discovery helps choose a use case worth pursuing. An agent package implements a defined operational job. Workflow automation handles a repeatable process. Governance and finance packages have their own stakeholders and acceptance needs. Pilot-to-production work begins with something that already exists and needs assessment and hardening. Choosing the right entry point matters more than buying the largest package.

05Plan the work

What must be agreed before the package starts

Access to systems, data samples, reviewers and operational owners can determine whether an engagement is ready to run. We confirm those dependencies alongside the deliverables and timeline. Where the scope needs validation first, that step should answer a specific uncertainty. A demonstration is useful evidence only when it exercises the task, data and constraints that the production system will face.

The proposal records acceptance criteria and the handling of changes. Working reviews show what has been built, while testing and documentation explain how it behaves and how your team can operate it. The handover includes code and the agreed operational information. Published pricing ranges help with planning, but the written scope determines the commitment. If a package is not a fit, the related service lets you define a custom boundary without pretending the two offers are interchangeable.

07FAQ

Frequently asked questions

View pricing guide
What's the difference between a solution and a service?

Services are the capabilities we bring to any project. Solutions package those capabilities into a defined outcome with a fixed timeline and price.

Can a solution be adapted to our situation?

Yes, within limits. We adjust integrations and scope details during the scope call. If the changes are large, we'll recommend a service engagement instead.

Do solutions include support afterwards?

Each one ends with a handover. Ongoing support or a follow-on cycle can be added as a separate agreement.

Can we change the package scope?

We review the requested change and its effect on deliverables, dependencies, price and timeline. A package is useful because the boundary is explicit. If the changes make it a different engagement, we scope a custom service rather than hiding extra work inside the original offer.

What should our team prepare?

The package determines the requirements, usually including the workflow owner, relevant system access, representative data and people who can review the output. These dependencies are confirmed in the proposal. We do not assume production access or approval authority simply because a scope call has taken place.

Which offer fits an existing AI pilot?

Use the pilot-to-production package when a working pilot already exists and needs assessment, integration and operational hardening. AI Discovery is the route for choosing a use case before building. A custom AI agent service is appropriate when the requirement is a new agent build with its own scope.

Where are the package prices?

Each proposal confirms the fixed scope and price. The pricing guide lists the approved planning ranges for the engagement types it covers, including discovery and pilot rescue. A range helps budget the decision but does not replace checking the package's deliverables and dependencies against your situation.

Solutions

Find the right starting point in one call

Tell us the workflow or decision you want AI to help with. We'll recommend a solution, or tell you if a custom scope fits better.