Goals before the board
Maya Okafor, chief of staff at Northwind, asks which company goals are off track before the leadership meeting. Memtro reads the company goals and lists the off-track ones with their owners and measured progress.
Which company goals are off track, and who reports to Priya?
Memtro reads your Lattice directory: people with title, department, manager, work email and start date. It reads departments, goals and OKRs with owners, status and measured progress, and review cycles by name and stage. It never reads reviews, ratings, feedback, check-ins, pay or personal details, and private goals are never returned. When asked, and once an administrator has granted the action by name, it creates a goal or key result with the owners you name, and posts progress updates on goals. Owners may be notified, and neither a goal nor an update can be deleted through the API.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Lattice tool, reads what it needs, and answers with the source cited.
These tools change something in Lattice. 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 Lattice 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 company goals are off track?
Who reports to Priya Sharma?
What are the engineering OKRs this quarter?
Is the mid-year review open?
Post an amber update on the hiring goal: two offers out, one accepted.
Maya Okafor, chief of staff at Northwind, asks which company goals are off track before the leadership meeting. Memtro reads the company goals and lists the off-track ones with their owners and measured progress.
Tom Reilly, engineering manager at BigCo, asks Memtro to update the platform migration goal to 60 percent with an amber status and his note on the delay. Memtro posts the update in the words he approved, and the goal's owners see it in Lattice.
The teams that lean on Lattice most, a question each of them asks, and what they connect beside it.
A record in Lattice 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 Lattice, signed in as a dedicated admin account kept for integrations, open Admin → Settings → Platform → API keys. The key carries that admin's privileges and stops working if the admin leaves.
Generate an API key and copy it, because it is shown once.
In Memtro, open Connections → Lattice, paste it into API key, and set Data residency to emea if your account is hosted there.
Ask: which company 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 Lattice tools are the same everywhere.
Only when you ask, and only what it has been granted: create a goal or key result with named owners; post a progress update on a goal. 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 key and optional data residency. In Lattice, signed in as a dedicated admin account kept for integrations, open Admin → Settings → Platform → API keys. The key carries that admin's privileges and stops working if the admin leaves.
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