AI Product Playbook
Find the bottleneck. Simplify product work.
We find the bottleneck in your backlog, code and handovers. After month one, you have an adapted AI Product Playbook, one prioritised pilot and a clear implementation plan.
For Heads of Product, Heads of Engineering and VPs of Engineering · with your core team
30 minutes · no obligation · no preparation needed
Run by Simon Scheurer and Marc Gasser – in person, start to finish.
Before you invest more in AI.
Coding got fast. Coordination didn’t. Requirements stay unclear, context gets lost in handovers and reviews create rework. More AI tools help once you know which part of product work is holding your team back.
Start focused. Make a clear decision.
One month. A clear outcome.
The timeline starts with the agreed kick-off and required material. We define the exact scope together.
- Week 1
Show us how you work today
Simon Scheurer examines a real workflow with your core team. We reconstruct product logic and dependencies from approved code, Jira or GitHub Issues and existing documentation. AI Monitor questions add a maturity perspective.
- Week 2
Choose one bottleneck
We examine waiting time, clarification loops and rework. Together, we select the opportunity with the strongest expected contribution to your goal. A baseline and success criterion make a later comparison possible.
- Week 3
Redesign the workflow together
We remove unnecessary work, simplify handovers and adapt agentic engineering practices to your context. The playbook records what people and agents do and where human review remains essential.
- Week 4
Make the pilot ready to start
You receive a bounded use case, an adapted playbook and an implementation plan. We walk through a real example and document remaining dependencies. You decide on implementation against this scope.
The Teklens method
Understand. Remove. Then automate.
The AI Monitor assessment puts your starting point in context. Your actual workflows and approved data show where work gets stuck. Reconstructing the codebase reveals product logic and technical constraints. Together, we select one bottleneck and redesign that workflow.
Explore the AI MonitorWhat a playbook decision looks like
Illustrative example · not a customer result
- Bottleneck
- Engineering clarifies the same requirements repeatedly.
- New workflow
- Shared context, a reviewed specification, a clear approval.
- Ownership & evaluation
- Product owns the specification; engineering owns the review. Compare clarification loops and rework before and after the pilot.
Start with one month. Go deeper where needed.
Recommended starting point
Your first advisory month
Analysis, a collaborative workshop, your individual playbook and a 90-day plan. One defined area and one priority opportunity.
Fixed fee based on agreed scope
You know the price, your team's commitment and the deliverables before commissioning.
Optional from month 2
Monthly advisory support
Each further month has its own focus and agreed outcome. We update the analysis and decide together what offers the strongest next opportunity.
- Implement and evaluate the selected pilot with hands-on support from Simon
- Compare lead time, quality and rework; improve the playbook
- Automate proven steps or address the next bottleneck
After month one, you decide whether and how to continue.
What we need from you
Nominate a product or engineering owner and a small core team. Provide a real workflow, relevant issues and approved technical documentation. We handle the analysis and playbook development. Workshop and review commitments are agreed before starting.
Work with operators on your real case
Simon Scheurer brings the perspective of a former CTO and serial founder. Marc Gasser connects product strategy, go-to-market and AI. We agree who leads your scope and how we work together before starting.
Meet Simon and MarcBefore the first conversation
Do we need a mandate from the CEO?
You can start within a defined product or engineering area. You need an accountable owner, access to agreed material and the ability to change the selected workflow.
Do you work with Jira or GitHub Issues?
Either can underpin the engagement. We review your existing issues and ways of working. Any technical connection is agreed in the scope. Azure DevOps is currently outside this offer.
Will software be shipped in the first month?
Month one delivers the baseline, playbook and a clearly defined pilot. Production implementation is agreed separately based on scope, data access and technical dependencies. Monthly support can continue for that work.
What does the engagement cost?
After the discovery call, you receive a defined scope and a fixed fee for month one. Effort, deliverables and your team's contribution are agreed before starting. You commission further months and deep dives separately.
Do we have to use Teklens software?
No. The engagement starts with your workflow and bottleneck. Where shared knowledge across decisions, issues and code helps, the Teklens Product Brain can support it as your team's shared memory. Software usage and setup are agreed separately.
How do we handle confidential data?
We agree sources, access rights and data handling before analysis. You provide only approved material or scoped access. If code access is unavailable, we use available extracts and document the limits of the assessment.
The next step takes 30 minutes
Bring the question holding you back.
Describe your starting point. Together, we define a useful first step. You leave knowing whether we can help and what scope fits. Choose your time directly in the calendar.
No obligation. You are booking a conversation, not an advisory contract.
Looking for a shared AI direction for executive leadership? AI Strategy Workshop