# Programmes Source: https://tpiros.dev/programmes Two ways to work with me, and nothing else. One closes the distance between the people in an organisation who got these tools to work and the people who did not. The other puts an engineering team through the parts of agent building that break in production. Both are half a day, both run on your own work, and both are scoped in a conversation rather than priced on a page. ## At a glance - **Format**: a live half-day, on your own tasks and systems - **Cohort**: up to fifteen people for The Power User Gap, up to twelve engineers for the Agent Workshop - **Delivery**: remote or on-site - **Preparation**: none for attendees, and no confidential material changes hands ## The two sessions ### The Power User Gap - **For**: One organisation's learning, talent or transformation lead, with their most effective AI users in the room; up to fifteen people - **Format**: Three or four half-hour conversations with the organisation's own power users, then a half-day, then a written playbook within a week. Remote or on-site, no pre-work for attendees Most organisations that rolled AI out did not fail at it; they split. A minority worked out how to hand real work to these tools, and everybody else settled for a faster way to look things up. The session surfaces what that minority actually does, on the organisation's own tasks, and turns it into a document the rest of the organisation can follow. What the team leaves with: - Tell the difference between querying a model and delegating work to one - Supply the context a task needs, which is what separates the effective users from the rest - Check output that arrives faster than anyone can read it, at a cost proportionate to the risk - A written playbook of the organisation's own patterns, owned by whoever runs enablement and reusable without me ### The Agent Workshop - **For**: One engineering team, typically up to twelve people - **Format**: A hands-on half-day as standard, remote or on-site; extends to multi-day The part of agent building that most often goes wrong: harness design, tool contracts, context strategy, and a working evaluation. Half a day as standard, or multi-day where the team wants to apply it to their own systems rather than a prepared example. What the team leaves with: - An agent with real tools and contracts that hold under misuse - A context strategy that survives a long-running task - A small evaluation that fails when the agent does ## What is deliberately not here There is no multi-week programme, no business-team course and no advisory product on this site. Those existed and were retired in Aug 2026 because five offers built from two bodies of material could not be told apart by anybody reading the page. Longer engagements and ongoing work happen, and they start as a conversation after a first session rather than as a thing to choose from a list. ## Next step Email hello@tamaspiros.com with what your organisation needs to be able to do, or book a call at https://calendly.com/tamas-piros/30min.