Software engineering. Applied AI.

Workshops / For your team

AI that can
work here.

A facilitated working session to turn a broad AI question into a decision your team can act on. Explore a workflow with practitioners who build these systems, then leave with a written opportunity brief.

Three separate sculptural forms in an open arrangement, ready to take shape together.

During the session

Move from examples to your own operation.

We start with practical scenarios and questions. Where could AI help? What would an existing product cover? What would need integration or custom engineering?

Then we work through an opportunity with your team: the task, the information it uses, who depends on the result and what would need to change. There is room to challenge the idea as well as develop it.

A task worth exploring

Identify the benefit you want: less handling, better access to information, a more reliable process or a new product feature.

Requirements you can act on

Record data, permissions, integration and approval requirements, including questions for your technical and governance owners.

A plan for the first test

Define what needs to be learned, the evidence that would support a decision and who should take it forward. A technical assessment may be the right next step before a trial.

Explore the possibilities

What could that look like?

Open an example to see what the system could do and how we would assess it.

01 / Commercial / Tender responsesCan we reuse our best tender answers without exposing another client’s terms?

The task

The bid team has relevant material spread across previous submissions, project records and capability statements.

What could improve

Spend less effort finding material and more on a proposal that fits the opportunity.

How it could work

Bring approved evidence into a source-linked first draft and flag questions the available material cannot answer.

What needs to be controlled

Respect project access and exclude client-specific commercial terms. The bid owner checks claims and approves submission.

What we would test

Can the reviewer trace each claim? Does restricted material stay out of the response?

02 / Operations / Supplier onboardingCan the system move a supplier through onboarding and flag what needs attention?

The task

Procurement reconciles forms, insurance records and internal approvals before setting up a supplier.

What could improve

Reduce manual coordination while keeping ownership of supplier approval.

How it could work

Check the pack, request missing information through an agreed workflow and route a complete record for approval. Update the supplier system only once authorised.

What needs to be controlled

Define which steps can run automatically. Keep supplier approval with an authorised person and record the evidence behind each update.

What we would test

Do missing approvals or expired documents stop activation? Can the team follow the record of each action?

03 / Product / AI in an existing applicationCan customers complete a task in our product by describing what they need?

The task

Users know the result they want but have to navigate several screens and repeat steps to get there.

What could improve

Make an existing product easier to use, with control over the actions AI can take.

How it could work

Connect natural-language requests to supported product actions. Check the result in the application and show the user what changed.

What needs to be controlled

Apply the user’s existing permissions. Require confirmation for consequential changes and make failed or incomplete actions visible.

What we would test

Does the requested change actually happen? Can the system recover or escalate when it cannot complete the task?

Governance is part of the discussion

Ask the questions that matter before a trial.

What changes the choice of model or product?

Discuss task quality, integration, response time and operating cost. Consider whether an existing product, a managed model or an open-weight deployment could fit. The session frames the evaluation; model performance needs to be tested against representative work.

Where will our information go?

Consider hosting, model providers, retention and provider use of data. Identify the requirements your organisation must establish before sharing records.

Who can see it, and who can act on it?

Work through staff and client access, automated actions and approvals. Name the decisions that need a responsible person.

How would we know it is ready to use?

Identify representative tasks, failure cases and the security, privacy or compliance reviews a trial would need. The workshop surfaces these requirements; implementation and testing follow.

Arranging a session

Make it relevant to the people attending.

Who should join?

A business sponsor, people familiar with the task and someone who understands the relevant systems. Include security, privacy or compliance colleagues where their requirements shape the opportunity.

What should we bring?

A high-level description of the task and the friction it creates. Use fictional or redacted examples; you do not need to share confidential records in the session.

How long is it?

We agree the duration, format and preparation around your team’s needs.

Do we need technical knowledge?

No. We explain the systems through familiar tasks. Technical colleagues can help with questions about integration and existing software.

Does it commit us to a project?

No. You leave with a written opportunity brief you can use internally, explore with another provider or develop with Form From.

Let’s make it work

What does your team need to understand?

Tell us about the audience and the questions you want the session to address.

Discuss a workshop