Industries · Software companies
AI for software companies where product, engineering, sales and CS no longer share a room
Between 30 and 250 people, every team has its own rituals and channels. Tessa captures what each one decides, turns it into owned tasks and follows through.
"We decided it in planning, but who owns it?"
At 30, 80 or 200 people, product, engineering, sales and customer success don't sit together any more. Each team has its own meetings (planning, retro, roadmap review, account review) and its own Slack channels. What one decides rarely reaches the others intact: sales promises a date engineering has never heard of, and CS doesn't know a key customer's bug slipped to next sprint.
Meeting notes, when they exist, end up in a doc nobody opens again. Retro action items get written down with good intentions and vanish. And every new joiner, engineer or account manager, spends weeks asking in Slack about things that were settled months ago.
The temptation is to measure more: activity dashboards, hours in meetings, commits per person. In an engineering team that breaks trust and fixes nothing, because the problem isn't effort. It's losing the thread.
How it works with Tessa
- 1
Everyone connects Google and Slack
One click per person, nothing to install. Tessa reads each person's email and messages privately, plus the team's Slack channels.
- 2
Tessa joins your meetings
In Google Meet (Zoom and Teams in beta) she joins as "Tessa (taking notes)". Notes from a planning or retro capture decisions, blockers and tasks with an owner and date, and the recap goes to attendees in Slack and by email.
- 3
Tasks land where each team works
Sales and CS see their tasks in Tessa's inbox, next to email. Connect Jira, Linear or GitHub (beta) and engineering tasks can go to your tracker.
- 4
Follow-through and a pulse per department
Tessa reminds each owner of their commitments and tells whoever asked if something stalls. Every week, leadership gets a pulse per department: blockers, overdue work and risks.
What you get
- What gets decided gets doneEvery meeting commitment has an owner, a date and a reminder. Fewer "wait, who was doing this?" moments.
- Product, sales and CS on the same pageAsk "what did we tell the customer about SSO?" and Tessa answers with sources: the notes, the Slack thread or the email you have access to.
- New engineers start with contextEach new joiner gets who's who, how things work here, the technical decisions the wiki has picked up from meetings and channels, and the tools to connect.
- Visibility without surveillanceThe pulse is per department, with a minimum of 5 people. Nobody sees another person's hours, activity or email.
- Fewer catch-up meetingsMissed it? The notes tell you what was decided and what's on you, without asking anyone for a recap.
Example routines for a software company
These are examples you write in your own words, and Tessa runs them. If you are a small SaaS startup, the "SaaS" template also sets priorities for customer incidents and renewals.
- "After every retro, create the agreed tasks and remind each owner on Monday."
- "Every Friday, post this week's decisions in #product with their sources."
- "If a customer emails about something on the roadmap, tell their account manager and link the latest decision."
- "When someone joins engineering, draft their onboarding plan with recent technical decisions."
The software company stack
The core (Gmail, Calendar, Drive, Meet and Slack) is proven with real accounts. In beta: Jira, Linear, GitHub, Notion, Asana and ClickUp for tasks; Zoom and Teams for calls with customers who use them; HubSpot and Pipedrive for sales; and Microsoft 365 if part of the team is on Outlook.
Privacy an engineering team can review
Engineers are usually the first to ask what the AI reads. The short answer: what Tessa reads in each person's email and messages is visible only to them; DMs between colleagues never go into company memory; the wiki and search respect who can see what; and managers get no individual metrics.
Data is stored encrypted in the EU, anything leaving the company needs approval and everything is logged. The DPA, the subprocessor list and the security policy are published, and you can ask for analysis to run on a European AI model.
What Tessa reads for each person stays private, your data is stored in the EU and nothing goes out without your approval.
Frequently asked questions
Does Tessa replace Jira or Linear?
No. Tessa captures tasks born in meetings, email and Slack and follows them up. If you connect Jira or Linear (beta), engineering tasks can land there, and your tracker stays the source of truth for development.
Can a manager see what each engineer does?
No. Tessa gives managers no metrics on individuals: no hours, no activity, no meetings. The weekly pulse is per department and only shows with at least 5 people.
Does it work with a company-wide Slack?
Yes. Slack is one of her main sources: requests in messages land in your inbox, and in any channel you can type "@Tessa summarise this thread" or "@Tessa create a task for Ana".
How do we trial it at a 100-person company?
We recommend a guided pilot with one team, for example product and engineering, for a few weeks. You can book a demo from the companies page.
Does it work if the team works in English?
Yes. Tessa works in Spanish and English and replies in the language you use with her. Plenty of software teams mix both, and you don't have to pick one for the whole company.
Keep reading
- FeaturesTessa takes the notes, assigns the work and sends the recapTessa takes notes in your meetings, writes the minutes, assigns each action item to its owner and sends the recap to attendees. Try 14 days free.
- FeaturesYour company's pulse, in one message a weekEvery week, what needs your attention: blocked or overdue work, unpaid invoices, cash position and what to tackle first. No employee tracking.
- FeaturesYour company wiki, written while you workDecisions, processes and “how we do things here” pulled from meetings and channels, with sources and the right permissions. Try it free today.
- FeaturesEvery new hire starts with a plan, not a “just ask if you need anything”Every new hire gets a message from Tessa with who's who, key clients, processes and their welcome checklist, plus someone to ask. Try it free.
- IntegrationsBetaJira with AI: project issues and inbox tasks on one listConnect a Jira project and Tessa mirrors it in Tasks, next to what she picks up from email, Slack and meetings. One view of what’s pending, no Jira login.
- GuidesHow to coordinate across teams without adding more meetingsHow to coordinate departments without filling the calendar: visible dependencies, one owner per task, one place for blockers and a weekly pulse.
What does your team look like?
Same AI for both. Where you start is what changes.
- Best fit for this page
Companies
30 to 250 people
What gets decided gets done
Minutes and tasks from every meeting, commitments that get followed up and a pulse per team, without watching anyone.
Startups
5 to 30 people
Grow without losing the thread
Tasks from email and Slack, follow-ups, sales and investors, without everything landing on the founders.
Start with one team, connect Google and Slack, and see at your next planning whether decisions turn into done work.
Start freeFree plan for teams of up to 3 people. Anything that leaves the company waits for your approval.