All stories
AI news3 min read

Your next AI tool may build on software you already use

SAP's latest Joule updates point to a useful starting question: could a better connection save more work than adding another separate app?

The useful part

Map the repeated handover before choosing a new tool. Ask what can be improved within your existing setup, what is available now, and what will cost extra.

More ways to connect AI to everyday work

When a team copies the same information between tools, another screen may be the last thing it needs. The useful change might be a clearer handover between the systems already in place.

At TechEd on October 27, SAP announced updates to Joule Studio, Joule Work, and its business AI platform. Joule Studio offers ways to build AI helpers through visual tools as well as programming. SAP also described more controls for seeing what those helpers do and how much they use.

Availability is mixed. SAP says the wider rollout is happening in phases. Some connections are limited to early adopters, while other additions are planned for 2027. Ask about the specific feature you need, rather than assuming every announcement is ready to use.

Read the announcement: SAP: TechEd developer announcements.

Look at the work between the screens

If your organisation already uses SAP, this news is a reason to review a repeated task with the people responsible for that setup. It is not a reason for every business to buy SAP.

The planning lesson travels further. Follow one request from arrival to completion. Where does someone retype a detail, look for an update, or wait for a colleague to move it along? That is a better starting point than a list of AI features.

You may find that an existing tool already handles part of the job. A useful build can connect that work, make the next decision clearer, and keep approval with the right person.

Prepare a brief people can follow

Choose a made-up example that reflects the shape of your work. Keep private records out of an early demonstration.

  1. Name the request and the tools it passes through.
  2. Mark the details someone currently copies by hand.
  3. Write which decisions should stay with a person.
  4. Ask for a demonstration of the improved handover using your example.

Learn or build around the outcome

If you want training, ask to work through one of those handovers rather than a tour of product names. If you want it built for you, the same example gives a builder something useful to investigate.

Before agreeing the work, ask what is included in your current plan, what needs another service, and who will look after the connection. Make sure any preview feature or future release date is clear in the proposal.

The positive opportunity is practical: your knowledge of how the team works can guide the build. Start with the point where work slows down, then choose the simplest way to make it move again.

Go to the source

Read the original reporting.

Our perspective is based on these sources. Product details and availability can change after publication.

  1. SAP: TechEd developer announcementsPublished 27 October 2026
  2. SAP: TechEd 2026 Innovation News GuidePublished 27 October 2026

Last updated .

Explore all stories
Put it into practice

Make your next idea
something people use.

Build your skills in a live AI course, or work with us on a tool that takes repeated work off your plate.