Capability in your team
Practical AI workshops
Practice AI use on examples that fit your team’s work. Leave with completed exercises, reusable templates, and a shared way to check results, so colleagues can work more independently.
Plan a workshopWhat works? Good question.
Make AI work.
In your world.
Less manual work, smoother handoffs, and useful AI in your team. Together, we find where a change is worth making, build the solution, and bring it into everyday use.
Engineering is our home ground. The opportunity goes beyond it.
From separate pieces to a working system
Find the people, systems, and friction behind the task.
Drag to explore · choose a stage From understanding the work to putting it into use
Where does the work get stuck?
Sound familiar?
Choose a familiar situation. See how the work could change, where AI could help, and which decisions stay with your team.
Every request is missing something. Less back-and-forth, a clearer task.
Illustrative example
Where it gets stuck today
“The monthly report is wrong.” Before fixing it, a developer has to find out which report, what is missing, and what their colleague expected to see.
How it could move forward
The colleague provides the report and an example. AI organizes the information, flags missing details, and drafts a task: what is wrong, what needs to change, and how to check it.
Your team decides
The owner clarifies and accepts the task. The fix goes into use after testing and review.
Using a recent bug report, we find where handoffs, tools, or the team’s working methods need to improve.
Let’s discuss your handoffsWe copy the same thing into three systems. Less copying, traceable approval.
Illustrative example
Where it gets stuck today
An order arrives by email. Someone copies the customer details into a register, checks the prices, and sends a separate message for approval.
How it could move forward
Automation takes the order details, checks them against the register, and prepares the entry. AI highlights missing or conflicting details for the person approving it.
Your team decides
A person resolves discrepancies. The order enters the target system only after the agreed approval, and the requester gets an update.
We choose the steps worth connecting. Your useful systems stay in place; Berek can provide a shared foundation for subsequent workflows.
Let’s look at your workflowWe can’t see where the AI budget goes. Put the work next to the bill.
Illustrative example
Where it gets stuck today
There is a subscription bill, a developer tool, and a remote AI run. They contributed to the same fix, but the costs appear in three separate places.
How it could move forward
With Legroom, we’re building a shared view that connects local and remote usage to the task. Measured charges, subscriptions, and estimates stay separate; missing data is marked too.
Your team decides
The budget owner can consider spending, completed work, and review effort when deciding what to continue. A more expensive run is not automatically a worse choice.
Legroom is at an early stage. We can start the discussion with one team and the data sources from tools you already use.
Explore LegroomThese are possible workflows. We design the implementation around your systems and rules.
Discover, build, and adopt together · FDE
We get into the work.
We work alongside your team, in the systems you already use. Around a shared goal, we build the changes, test them together, and help put them into use. That can mean improving several connected workflows.
-
Understand what matters.
Map the real work with the people doing it. Choose a valuable improvement, name its owner, and establish what better looks like.
A shared goal and a starting baseline. -
Build. Try. Improve.
Simplify the process and build what it needs: integrations, conventional automation, AI, or a focused application. Test it on real examples together.
Working changes, introduced as we go. -
Make it everyday.
Help the team adopt the change. Agree who operates it, hand over the knowledge, and evaluate the result in actual use.
A usable solution with clear ownership.
Your part in the work
Someone who can approve changes, colleagues who know the daily work, and a technical contact. We ask your team for real examples, joint testing, and feedback. Agree the time and access needed before starting.
The right tools for the work.
Choose the solution around the task. If you know what you need, we can discuss a workshop or product implementation directly. If the starting point is still unclear, we find it together.
A shared foundation
Berek
Give the next automation or internal application a foundation to build on. Berek connects people, AI, and existing systems in an environment your company controls. We plan the implementation, updates, and operation together.
Explore BerekAI spend & control · Early stage
Legroom
See which work accounts for AI spending across colleagues’ computers and remote runs. We’re building that shared picture and the controls for spending limits. Legroom can work without Berek; we agree the first use case and development needed separately.
Explore LegroomUseful is something you can check.
We compare against the starting point: accepted results, quality, turnaround time, human effort, and total cost. The review work and failed attempts count, too.
The measure of our work
- A clear outcome, owned by a person.
- Evidence from actual use.
- An agreed home for ongoing operation.
A person behind the work
Led by Nagy Gergő. Engineering experience and two four-week practical AI programs in Hungarian telecommunications inform the work. Your results are established in your environment.