# Workshops: Focused discovery, technical reviews and planning for the next decision.

URL: https://extra.dev/engagement/workshops
Typical length: 1–2 weeks
Format: On-site or remote
Pricing: Fixed, agreed up front
Deliverable: A written report and recommendation

**Focused assessment for product and technical decisions**

Focused engagements to clarify scope, assess an existing system or evaluate a product direction. Each concludes with a written report setting out the analysis and recommended next steps.

A workshop combines the client’s knowledge of the product or problem with our analysis of the available options. We review the relevant information, clarify the constraints and assess the work against business priorities and technical requirements.
The report sets out the analysis, options, trade-offs and recommendations, with the assumptions made clear. Depending on the scope, it may also include a proposed plan, estimates, a roadmap or a technical assessment. It is yours to use with whichever team takes the work forward.

Includes:
- **Scoping workshop**: Clarifying the problem, users, requirements and constraints, then defining priorities, an initial scope and an estimate range.
- **Technical audit**: Assessing an existing codebase and supporting systems for maintainability, security, performance and delivery risk, with recommendations prioritised by impact and cost.
- **Architecture review**: Reviewing the structure, integrations and technology choices of a proposed or existing system, with options and trade-offs documented.
- **AI opportunity assessment**: Assessing where AI could improve a product or workflow, the data and controls required, and the expected value against implementation and operating costs.
- **Delivery health check**: Reviewing plans, dependencies and delivery practices to identify risks and improve progress.
- **Product strategy session**: Evaluating user needs, business priorities and development options to set direction for the next stage of a product.

A good fit when:
- You know the problem, but not yet the shape of the solution
- You want an independent review of a proposed scope or estimate
- You need to assess an existing system before extending or replacing it
- You want to assess whether AI could add practical value to a product or workflow
- You want to evaluate an approach through a defined piece of work before committing to delivery

Not the right shape when:
- Your requirements are defined and you need delivery capacity rather than an assessment: use Specialists, Teams or Projects according to the responsibility required
- You are looking for a free proposal; a workshop is paid work with a deliverable
- You need a decision within days; a workshop runs one to two weeks

How it runs:
1. **Scope and preparation**: We agree the objectives, scope, participants and expected output, then review the available material before the working sessions.
2. **Working sessions**: Sessions bring together the people who understand the goals, constraints and current situation. We test assumptions, examine options and identify points that need further analysis.
3. **Analysis and recommendations**: We document the analysis, options considered, key risks and a recommended course. If scope and cost are part of the brief, the report includes estimates and the assumptions behind them.
4. **Review and handover**: We walk through the report, answer questions and clarify any decisions that remain open. The written output is yours to take forward with your own team, another partner or us.

- **What does a workshop cost?** We agree a fixed fee for the defined workshop before work begins. Its scope, duration and deliverables are set out in the proposal; any additional work is agreed separately.
- **Is the workshop fee credited toward a project that follows?** No. A workshop is a separate, paid engagement with its own deliverable. Any work that follows is scoped and priced separately.
- **What if the conclusion is that we should not build it?** Then we document that recommendation and the evidence behind it, along with alternatives where relevant. The purpose of the workshop is to support a sound decision, including a decision not to proceed.
- **Who needs to be involved on our side?** The people who own the decision and understand the product, process or system being assessed. We agree who needs to participate during scoping; most workshops involve two to four client representatives in the working sessions.
- **Is a workshop useful without a technical team on our side?** Yes. We can start with a business or product question and provide the technical assessment ourselves. We identify the information needed and explain the recommendations in terms that support the decision.

---

Published by Extra.dev (https://extra.dev), a software engineering team in Ljubljana, Slovenia.
Canonical page: https://extra.dev/engagement/workshops
Contact: hello@extra.dev · Replies within one working day
Site index for agents: https://extra.dev/llms.txt · Full text: https://extra.dev/llms-full.txt