Back to Hub
Workshop • 6 Weeks
AI-Assisted Development Workshop
Treat AI as a collaborator, not a stateless tool.
Most teams treat AI like automation, hit context decay when token budgets and context windows get saturated, and generate specs before understanding the problem. This workshop installs a practical collaboration model: maintain context over long projects, design directly in code, and iterate without losing coherence. It is for teams building complex systems over weeks or months, not teams that need certainty before they move.
Where this is most useful
- Product teams hitting context decay in long AI-assisted projects
- Engineering/design teams that ship in iterative loops, not static specs
- Organizations that need durable AI collaboration practices, not one-off prompt tricks
Weekly Schedule
Week 1
Discovery: workflow mapping, pain points, and baseline behavior
Week 2
Research: industry pattern study and model selection
Week 3-6
Workshop implementation: your team builds, I guide the thinking
Week 6
Handover: codified collaboration model and next-phase execution plan
Investment Range
Scoped based on complexity
From 36,700 AED
~$10,000+ per engagement
• Single team baseline: One product squad, 6 weeks, from $10,000
• Multi-stream implementation: Cross-functional team, extended coaching, custom scope
• Enterprise adaptation: Multiple squads, governance layer, custom proposal
How it works:
Book a 15-minute scoping call. I'll ask about your product complexity and timeline, then send a fixed-price proposal.
Limited to 6-12 companies annually. You do the work; I install the mental model that keeps long-running AI collaboration coherent.
Common Questions
Do we need to know how to code?
No, but someone on your team should be able to implement what we design. I teach the mindset and guide the approach - your team does the actual building. If you're a purely non-technical team, this isn't a fit.
What if we're already using AI tools like Copilot or ChatGPT?
Good. This is not about which tools you use. It is about changing how you work with them - from stateless task execution to persistent collaboration. The methodology works regardless of your current tooling.
How is this different from prompt engineering courses?
I do not teach prompt engineering. I teach you to stop needing it. Most prompt engineering is theater. What matters is context persistence and treating AI as a collaborator, not optimizing how you phrase requests.
What happens after the 6 weeks?
You continue independently. The goal is to make you self-sufficient, not dependent on ongoing consulting. Some teams want continued support - that is available separately. Most do not need it.
Why only 6-12 engagements per year?
Each workshop is custom-researched for your specific industry and workflow. I cannot do that at scale and maintain quality. This is not a productized course - it is tailored consulting delivered as guided learning.
How do we know if we're ready for this?
You are ready if: (1) You are building systems that take weeks/months, not days. (2) You have hit context decay or spec-generation problems with AI. (3) Your team is comfortable with iteration over certainty. If you need a guaranteed outcome before starting, this is not the right approach.
Do you work remotely or on-site?
Remote by default (based in Dubai, serving UAE and GCC). On-site available for UAE-based teams.
What if it doesn't work for us?
Week 1 is discovery. If after that week we both agree this is not a fit, I will refund 50% and you keep the discovery report. I'd rather part ways early than force a mismatched engagement.
Do you sign NDAs?
Yes, standard for all client work.
Deliverables
- Discovery report: current workflow bottlenecks, context-loss patterns, and decision friction
- Industry benchmark brief: how comparable teams are using AI in long-running build cycles
- 4-week guided implementation plan with weekly checkpoints and artifacts
- Workflow model for sustained AI collaboration without context loss
Limited availability for Q2 2026.
Based in Dubai, serving UAE & GCC.