Home

Industries · IT consulting

AI for IT consulting firms running several clients and projects at once

Status calls, scope changes, tickets and releases: Tessa captures what you agree with each client, splits it across the team and makes sure it gets done.

"The client says they asked for it two weeks ago"

At an IT consultancy or services firm, every project has its client, its project lead, its weekly calls and often the client's own Jira or Teams on top of yours. What gets asked on a call ("can you add this report?", "let's move the release to Thursday") changes the scope, but it rarely gets written down and sent.

With five or ten projects running in parallel, commitments are scattered across emails, Slack channels and meetings. When the client asks about something, someone has to piece together who said what, and hours mentioned in passing turn up as a surprise on the invoice.

How it works with Tessa

  1. 1

    Connect the team's Google and Slack

    Everyone connects their account. With the "Consulting" template, client requests with a deadline, proposals and billing are high priority.

  2. 2

    Tessa takes notes with the client

    She joins Meet (Zoom and Teams in beta) as "Tessa (taking notes)". The notes capture decisions, scope changes, hours or budget mentioned and next steps with an owner.

  3. 3

    A recap ready for the client

    Internally the recap goes out automatically. The one for the client waits for your approval so you can review and send it.

  4. 4

    Commitments followed up

    Tessa reminds each owner of their part and, if the client owes you something (access, data, a sign-off), leaves the reminder drafted.

What you get

  • Scope changes in writingWhat gets asked on a call lands in the notes with a date and a source. Fewer arguments about what was in scope.
  • Every project up to dateAsk "what's pending with the portal client?" and Tessa answers with the tasks and their sources: notes, email or thread.
  • Client-side blockers in viewIf a project is waiting on access or a client sign-off, it shows up in the weekly pulse before it eats the deadline.
  • A profile for every clientHistory, open items and upcoming meetings for each account, built from the team's email and meetings.
  • Handovers without losing contextWhen someone switches project or leaves, client decisions are in the wiki with their source, not in their head.

Example routines for IT services

The "Consulting" template brings routines for proposal follow-ups and a recap after each meeting. Others you could write:

  • "Every Monday, list this week's commitments by client and who owns them."
  • "If a client asks for a change that wasn't in scope, tell me and draft a confirmation email."
  • "If we've been waiting 3 days for client access, draft the reminder."

Hours and tools

Tessa isn't a timesheet tool and doesn't measure anyone's time: she captures hours or budget mentioned in meetings and emails so they don't get lost. The core runs on Google Workspace and Slack. In beta: Teams and Zoom for calls with clients who use them, Microsoft 365, and Jira, Linear, GitHub or Asana to push tasks to a tracker.

Confidentiality between clients

What Tessa reads in each person's email is visible only to them, and the wiki and search respect who can see what: a private client channel stays visible to its members only. Data is stored encrypted in the EU, with a published DPA and subprocessor list.

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

Can she send the notes straight to the client?

To attendees from your company, yes. For external attendees the recap waits for your approval, and you can edit it first.

Does it work if the client uses Teams?

Yes. Tessa joins Google Meet, Zoom and Teams; Zoom and Teams are in beta, so it's worth trying an internal meeting first.

Does she track hours per project?

No. She captures hours mentioned in meetings and emails, but doesn't log or measure anyone's time. Keep your timesheet tool for that.

Can she create tasks in the client's Jira?

If you connect Jira (beta) with an account that has access, tasks from the notes can go to the project you choose. Check with the client that they're happy with it first.

Does Tessa tell people she is taking notes?

Yes. She joins under the name "Tessa (taking notes)", visible to everyone. We also recommend mentioning it at the start, especially with clients.

What does your team look like?

Same AI for both. Where you start is what changes.

  • Companies

    30 to 250 people

    Best fit for this page

    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.

Try her on one project's meetings this week and compare what ends up in writing.

Start free

Free plan for teams of up to 3 people. Anything that leaves the company waits for your approval.