What Teklens can do today.
The Company Brain has three features: Meeting Companion, Context Manager and Playbooks. Below, every function in detail, with its status. We agree together what comes first in your setup.
Three features. One memory.
The Meeting Companion captures what was decided. The Context Manager shows where work drifts from it. Playbooks make recurring tasks the same for people and AI agents.
Meeting Companion
LiveCaptures what was decided.
- Joins meetings in Zoom, Microsoft Teams, Google Meet and Webex, automatically from the calendar if you like.
- Recording and live transcript with speaker names, searchable in the Company Brain.
- Capture decisions, open questions and next steps with an owner.
Context Manager
LiveGoals, knowledge and decisions in one place. With sources.
- Connect sources to a project or the whole company: Jira, Confluence, SharePoint, Notion, GitHub or GitLab and local folders.
- See contradictions between a decision, documents and tickets, with sources.
- Approve proposals as a diff. Teklens writes them back to the source.
Playbooks
LiveRecurring routines for people and AI agents.
- Use 43 proven routines from the Playbook library.
- Build your own skills in the Skill Studio and enable them per project.
- Every change stays a draft until a person approves it.
- 01DiscoverFind what matters
- 02DefineDecide what to build
- 03BuildShip with context
- 04OperateLearn what’s next
The detailed workflows below currently focus on product and engineering. They do not represent a complete workflow catalogue for every department.
Gather what you know before you decide.
Interviews, notes, support cases and ideas sit in different places. Teklens brings them together, makes them searchable and gives every initiative a frame.
- Initiative planning & phase gates
A charter with goal, value, scope and risks per initiative. Artefacts attach to the initiative and only move to the next phase once you approve.
- Watched folders
A local folder of notes, PDFs or Office files is synced continuously and becomes searchable. The watcher runs on macOS, Linux and Windows.
- UI sketches
Sketch screens for an idea before a story exists, and iterate in the conversation until the team shares the same picture.
Settle the decisions before anything is built.
Questions that only surface in the sprint cost the most. Teklens pulls them forward: product, engineering and agents settle them in the same conversation, and you approve the spec.
- Jira story & epic drafting
An idea becomes a story or an epic with acceptance criteria and code context. You review the draft, then Teklens writes it to Jira.
- Decision history & traceability
Decisions and findings are saved as memories on the conversation, artefact, initiative or project. Every result shows which conversation it came from.
- Code owners & effort estimates
Teklens finds who knows an area from git history and estimates effort, complexity and risk of a change against the real code.
- Structured outputs
Estimates, code owners, backlog findings, release notes and review verdicts appear as structured views instead of prose. For dashboards and timelines Teklens generates a view of its own.
- Backlog hygiene
Finds duplicate, stale or contradictory tickets in your Jira and shows what should be merged or closed.
Effort estimate against the real code, with risks and code owner. 
Code owners from git history. 
Backlog findings with a proposal: merge, close, refresh.
Hand over context instead of explaining it again.
The approved requirements can be handed to engineering or a coding agent with context. Coding handover is beta; confirm the supported path. The team still reviews and delivers the result.
- Coding agent & sandbox
Every agent run works in its own isolated environment. You see progress, model and usage, stop the run or start it again.
- Brain access & external tools
Outward MCP and supported plugins expose scoped Brain knowledge to compatible agents. Separately, attach external MCP servers to Teklens to add tools.
- Test planning
Derives a test plan with edge cases for a story from the code it touches, before implementation starts.
- Implementation review
Checks per acceptance criterion whether a branch or pull request implements the story, with references to the files and symbols involved.
Implementation review per acceptance criterion, with the files involved.
Ship, review and learn from it.
What goes live is documented and checked regularly. Skills and the playbook capture how your team works, so the next round starts better.
- Release notes
Writes release notes or a changelog from what actually shipped in Jira and git since the last release.
- Recurring routines
Ask in a conversation for a recurring task, such as a summary every morning. Each run starts a new conversation with the result.
- Governance & privacy
EU hosting, data separated per tenant, roles for owner, admin and member. Anonymisation per conversation, your own provider keys, human review of Jira changes according to your configured approval rules.
Release notes from what shipped in Jira and git.
Connected to your tools. Controlled by you.
- Jira
- Confluence
- SharePoint
- Notion
- GitLab
- GitHub
Secure access for AI agents to more than 1,500 apps. What is not connected, Teklens does not know.
- Secured Cloud in a dedicated environment for your company only, or self-hosted on your own servers.
- Owner, admin and member roles per workspace.
- Anonymisation per conversation: personal data is replaced before it reaches the model.
Bring one important decision.
In 30 minutes with Marc or Simon we clarify your use case, the sources involved and a sensible first step.
With a founder. No obligation.