Goals before the board
Priya Sharma, chief of staff at Acme Ltd, asked which Q4 goals were off track. Memtro listed them with owners, progress and deadlines. She took the list into her one-to-ones with each owner.
Which Q4 goals are off track, and who owns them?
Leapsome connects Memtro to your people platform. It reads goals and OKRs with progress, key results, owners and comments, and review cycles with who has completed which step. It also reads the employee directory, absences, public praise, who gave feedback to whom, and work locations. When asked and granted, it can give praise or instant feedback from a named person, write a private note, update a key result's progress, or clock an employee in or out. Absences and time tracking need admin roles on the key, and review ratings, private feedback and pay are never returned.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Leapsome tool, reads what it needs, and answers with the source cited.
These tools change something in Leapsome. The model is told to use them only when you ask for exactly that, and an administrator grants each one by name to the teams that may use it; a personal connection acts only after its owner allows it.
Once Leapsome is connected, these are the kinds of things people ask. Plain questions, no syntax. If the answer lives partly in another system you have connected, Memtro looks there too.
Which Q4 goals are off track?
How far has the autumn review cycle got?
Which absences start next week?
Who joined the sales team this quarter?
Update the churn key result to 4 percent.
Priya Sharma, chief of staff at Acme Ltd, asked which Q4 goals were off track. Memtro listed them with owners, progress and deadlines. She took the list into her one-to-ones with each owner.
Dan Fletcher, engineering manager at Northwind, asked Memtro to praise Maya Okafor publicly for the migration work. With the action granted, Memtro posted the praise from Dan. The whole company saw it in Leapsome.
The teams that lean on Leapsome most, a question each of them asks, and what they connect beside it.
A record in Leapsome is rarely the whole story. Connect the systems that hold the rest and Memtro checks them together, then remembers what it learned so the next question starts further along.
Using something else for the same job, or both? Each connector has its own tools; connect as many as you like.
In Leapsome, open Admin settings → API and create an API secret. An admin can, and assigns the access roles Memtro should read with.
In Memtro, open Connections → Leapsome and paste the API secret.
An administrator grants the actions by name, such as Give praise from a named person to colleagues, to the teams that may use them. Absences and time tracking need admin roles on the key.
Ask "Which Q4 goals are off track?"
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Leapsome tools are the same everywhere.
Only when you ask, and only what it has been granted: give praise from a named person to colleagues; give instant feedback from a named person; write a private note about a colleague (visible only to its sender); update a key result's name, weight or progress; clock an employee in or out. Every other tool reads, searches or lists. The Connections page labels the tools that act, an administrator grants each one by name to the teams that may use it, and a personal connection acts only after its owner allows it.
A personal connection serves only your own requests. A shared connection serves the organisation: everyone, or only the teams an admin chooses. Admins can always add shared connections; other members need the permission.
Credentials are encrypted at rest. Tool results are cached briefly so agent loops do not repeat identical calls, and the facts the model extracts are saved to your organisation's memory with provenance (system, record and link) so they can be checked and superseded.
API secret. In Leapsome, open Admin settings → API and create an API secret. An admin can, and assigns the access roles Memtro should read with.
Seven-day free trial, then one monthly price per organisation. Connectors, jobs and memory are never metered.
Sign in, add a provider key, create an API key and point your tools at Memtro. It takes about five minutes.
7-day free trial · card on file, nothing charged until it ends · cancel any time