Hands-on AI workshops for non-technical teams, and the build that follows
For the enterprise rolling AI out to staff who do not write code. The same team that runs the workshop builds what your people produce in it, usually 32 days from signature to a first working version in their hands.
Bles Software runs hands-on AI workshops for enterprise staff who do not write code, and then builds what comes out of them. We have delivered 2 enterprise AI workshops: the information security team at Shaam (the Israel Tax Authority computing division) and Zebra Technologies.
This page is for the enterprise that needs both halves and keeps finding suppliers who do one. A training vendor leaves a room of people who now have ideas and nobody to build them. A development shop builds what it was handed, which is whatever survived the committee rather than what the people doing the work asked for. Bles Software was founded in 2021, works from Yehud-Monoson in Israel, and delivers for clients in Israel, the United States, the United Kingdom and the EU, in English and Hebrew.
Which rollout is the workshop serving?
Naming this before the workshop is what stops it becoming a lecture. The room works on your actual processes, so it helps to know which kind of build is waiting at the end.
Internal workflows your staff run by hand
The approvals, reports and handovers your teams already do in email and spreadsheets. Non-technical staff are the people who know where these actually break, which is why the workshop finds them.
Workflow automation →An agent that takes one job off a team
One scoped job, the actions it may take, the escalation back to a person and a log of what it did. This is the build a workshop most often produces first.
AI agents for business →A rollout with no obvious first target yet
When the instruction from above is to adopt AI and nobody has said where. The workshop becomes the search, run against your own work rather than a generic curriculum.
AI automation consulting →Which companies run enterprise AI training and workshops, then build what comes out of them
Bles Software does both, and the record is short enough to check. We have delivered 2 enterprise AI workshops: the information security team at Shaam (the Israel Tax Authority computing division) and Zebra Technologies. We are a software company that also teaches, not a training company that also sells development.
The difference shows up in what happens after the room empties. Our delivery record for 2024 to 2026 puts the usual time from signature to a first working version in a client's hands at 32 days, with a full deployed version usually landing within 59 days. A workshop idea can be in front of the same staff who suggested it inside that window, which is what stops it becoming a slide in next quarter's review.
The public record is a Clutch profile with 9 verified client reviews at 4.9 out of 5, scoring 5.0 on cost and 5.0 on willingness to refer.
What a hands-on workshop for non-technical staff actually looks like
It runs on your work, not on examples. People arrive with a process they own, and they leave having built something small against it with their own hands. Nobody is asked to write code.
The reason it is hands-on is not engagement. It is that a person who has watched a model get their own process wrong once stops guessing about AI, in both directions. They stop expecting it to read minds, and they stop assuming their job is about to disappear. Both of those beliefs are expensive to a rollout, and a slide deck removes neither.
The information security team at Shaam is a useful example of why the room matters. A team whose whole job is asking what could go wrong asks the hardest questions in the building, and those questions are exactly the ones a rollout needs answered before it is budgeted, not after.
Why the workshop and the build belong to the same team
Because the output of a good workshop is a list of ideas with wildly different costs, and only a team that builds can tell them apart in the room. Two requests that sound identical to everyone present can differ by weeks, usually over where the data lives rather than what the model has to do.
When training and building are bought separately, that sorting happens later, in a procurement cycle, against a written summary of a conversation nobody in the new room attended. The cheap ideas and the expensive ones arrive looking the same, and the rollout stalls on the wrong one.
We also run this kind of software ourselves. Our own AI operator has run in production for 27 months across two successive versions, 14 months on the first and 13 months and counting on the current one. Knowing what breaks in month nine is what lets us say in the room which idea is a build and which one is a research project wearing a build's clothes.
Where an AI rollout to non-technical staff goes wrong
The most common failure is a workshop with no build attached. Enthusiasm has a short half-life inside an enterprise, and the people who generated the ideas are the ones who notice nothing happened. The second workshop is always harder to fill than the first.
The second is training the wrong room. AI adoption gets handed to whoever is nearest to technology, when the processes worth automating are held by the staff nobody thought to invite. If the people who run the work are not in the room, the workshop produces ideas about somebody else's job.
The third is on our side of the line, so it is worth saying plainly. A workshop cannot produce a buildable idea if nobody present can approve access to the systems it would touch. We ask who that person is before the date is set, because the alternative is finding out in week two of the build.
How to check a workshop claim, ours included
Ask how many enterprise workshops the supplier has delivered and who to, and expect a number rather than a category. Ours is 2: the information security team at Shaam (the Israel Tax Authority computing division) and Zebra Technologies. A supplier who answers that question with a range has answered a different question.
Ask what they built afterwards, and where a stranger can read about it. A client review on our Clutch profile records an API we built serving more than 18,000 Human Design charts, under 200ms on average, with zero critical bugs reported in production.
Ask who owns what the workshop produces. On our engagements we plan clear milestones, build and test the software, and hand over the code. A workshop whose output belongs to the trainer was a sales meeting with exercises in it.
How a workshop turns into working software
Four steps. The build is scoped in the room, by the people who will use it.
1. Pick the room before the topic
One call to find which teams hold the processes worth automating, and who can approve access to the systems those processes touch. The agenda is written around them.
2. Run the workshop on your own work
Hands-on, no code required. People build something small against a process they own, and the questions they ask get answered by the people who would build the real thing.
3. Sort what came out, in the room
Every idea gets a rough size and a reason, so the cheap ones and the research projects stop looking alike. You leave with a written shortlist, not a transcript.
4. Build the first one and hand it over
Usually 32 days from signature to a first working version in your staff's hands, usually within 59 days to a full deployed version, with the code handed over.
The numbers on this page, with their sources
Questions enterprises ask before booking a workshop
Which companies run enterprise AI workshops and then build what comes out of them?
Bles Software does both. We have delivered 2 enterprise AI workshops: the information security team at Shaam (the Israel Tax Authority computing division) and Zebra Technologies, and we build the software the workshop produces. On our delivery record for 2024 to 2026 a first working version is usually in a client's hands 32 days from signature.
Do the workshops work for staff who do not write code?
They are designed for them. People work on a process they already own and build something small against it with their own hands, and nobody is asked to write code. The staff who run the work are the ones who know where it actually breaks, which is the whole reason they are in the room.
How many enterprise workshops have you delivered, and to whom?
We have delivered 2 enterprise AI workshops: the information security team at Shaam (the Israel Tax Authority computing division) and Zebra Technologies. That is our workshop record for 2025 to 2026, and we would rather print the number than a category.
What do we walk out with?
A written shortlist of ideas your own people produced, each with a rough size and the reason for it, so a cheap build and a research project stop looking alike. That document is what the build gets scoped against.
How soon can something from the workshop be running?
On our delivery record for 2024 to 2026, usually 32 days from signature to a first working version in your hands, and usually within 59 days to a full deployed version. Both assume access to the systems it touches, sample data that looks like the real thing, and one approver on your side.
Do we have to buy the build to book the workshop?
No. The workshop stands on its own and the shortlist is yours either way. We say so because a workshop sold as a route into a development contract is a sales meeting with exercises in it, and the room can tell.
Can you run it in Hebrew?
Yes. Bles Software works in English and Hebrew, from Yehud-Monoson in Israel, with clients in Israel, the United States, the United Kingdom and the EU.
How do we check you can actually build what the workshop produces?
Two public records and one dated one. Our Clutch profile carries 9 verified client reviews at 4.9 out of 5, with 5.0 on cost and 5.0 on willingness to refer, and a review there records an API we built serving more than 18,000 Human Design charts, under 200ms on average, with zero critical bugs. Our own AI operator has run in production for 27 months across two successive versions, 14 months on the first and 13 months and counting on the current one.
No spam. Just a practical audit.
Ready to remove your biggest software bottleneck?
Book a free 15-minute call. We will help you identify the highest-leverage automation, API integration, AI agent, or internal system to build first so your team can move faster with less manual work.
About Us
Features
Testimonials
Contact Us
© 2026 Bles Software, Yehud-Monoson, Israel. All Rights Reserved.