Dashboard – initiatives at a glance
01 · Discover
Discover
Signals from every source are clustered and prioritised against vision, personas and code. You see value vs effort instead of gut feel.
The Product
The shared Product Brain for your software team.
Teklens knows your product decisions, Jira and the actual code, and keeps people and agents aligned from decision to release. It takes coordination work off your product managers so they can focus on customers, strategy and decisions.
Did what we decided survive implementation?
Creating a ticket is only the start. Teklens connects the decision and spec to Jira and the code that implements them. People and agents work from one current product context and can check where the result diverges before release.
Shared product context
Decisions, specs, Jira and code stay connected for people and agents.
Priorities with a reason
Scattered ideas, bugs and feedback become a continuously prioritised roadmap – every position backed by value against effort, risk and complexity, grounded in the real code.
Human decisions
You decide what's canonical. Teklens keeps the state per initiative current and makes decisions traceable.
Use AI without losing control
Pick the model per project (Claude, GPT, Gemini). CH/EU hosting, no training on your data.
One shared memory over everything
Integrated, always in sync.
Every source feeds a single Context Engine. The answer shows up where you work – no tab-hopping.
01 – Context
Code
Every repo, semantically indexed
Jira
Issues & sprints
Confluence
Docs & decisions
Git history
Features & experts
Meetings (beta)
Product-relevant discussions
02 – Context Engine
Context Engine
Every query goes through the Context Engine. It assembles the relevant context from every source.
03 – In your tools
Embedded in Jira
Answer right inside the ticket – PROJ-2481
Teklens web app & meeting bot (beta)
app.teklens.ai – same context, own workspace
Always in sync – same context in Jira and on the web.
From product decision to shipped software.
Decision → Spec → Plan → Build → Review → Ship. The groups below organise work along this journey.
Risk analysis – edge cases surfaced
02 · Define
Define
The Impact & Feasibility Matrix prioritises by value, effort and risk. Code-grounded PRDs, acceptance criteria and risk analyses from real code paths – estimates are backed by the repository.
Live view – progress in real time
03 · Build
Build
A live agent team per initiative – PM, PO, engineering – works in the same context, across live conversations and artefacts.
Support – PRD & evidence
04 · Operate
Operate
Support, incidents and root causes flow back into the graph – and into the next Discover round.
Every tool is good. Nothing holds them together.
Jira, coding agents, repositories and collaboration tools are useful. The work of keeping them aligned still falls to your team.
Jira and GitHub/GitLab
Tickets and code record different parts of delivery. Someone still checks whether they match the decision.
Claude, Codex and other agents
Agents help implement faster. Each needs the current scope, context and a human review.
Teams/Slack, meetings and automations
Decisions, changes and status move between tools. Your team assembles the current picture by hand.
Teklens
One shared product context connects decisions, specs, Jira and the actual code. People and agents stay aligned, and implementation can be checked against the original intent.
Hold every solution against this list.
Eight selection criteria – whether the answer ends up being Teklens or not.
- Does it read our real code and link it to ideas, tickets and incidents?
- Does context persist per initiative and grow – without us maintaining it?
- Does it prioritise value against effort, risk and complexity – with a traceable reason?
- Do acceptance criteria and edge cases come from real code paths, before the build?
- Do we see live where every initiative stands – checked at every status change?
- Do learnings from support and operations flow back into planning?
- Does it connect to Jira, Confluence and GitHub instead of replacing them?
- Data and hosting CH/EU, no training on our data, model choice per project?
The features behind the shared context
Explore the product details and technical mechanisms.
Product Brain
Jira, Confluence, GitHub, GitLab and watched folders, indexed continuously. Plus the decisions and results from your conversations. Every answer and every agent works from the same state.
More →
Beta
Meeting recording & transcripts
Teklens records a refinement, interview or review, produces a searchable transcript and captures decisions and open questions. Later you ask, instead of hunting for notes. In beta.
More →
Multiplayer chats
A conversation belongs to the project, not to one person. Everyone writes in the same thread, and every answer knows your Jira, your docs and your code. Questions get settled before anything is built.
More →
Flexible IDE handover
Hand a Jira ticket with plan and context to a local agent by link, open it in Claude Code or Codex, or let a Teklens agent work in an isolated sandbox. Model per run, usage visible.
More →
AI skills library & playbook
Built-in skills for story drafting, estimation, review and release notes. Build your own in the Skill Studio and enable them per project. Every change to Jira stays a draft until you approve it. Playbook in beta.
More →
From product decision to shipped software.
Explore the design instance or agree a test on one current initiative with a founder.
Two paths: set the direction or test Teklens on real product work.