NewCost control: a token allowance a month for each model choice — when one runs out, the cheaper one answers.See how it works
memtro

AI for consultancies, from the proposal to the invoice

A consultancy sells memory and keeps very little of its own: the proposal in a document, the meetings in a calendar and a notes tool, the decisions in Slack, the invoice in Xero. Memtro connects to the tools a firm already runs on and answers a question about a client from all of them, with each fact cited, so a partner is briefed before a call and a promise made in a meeting is checked for whether it was kept.

7-day free trial · card on file, nothing charged until it ends · cancel any time

Every client's engagements, documents, conversations and invoices answered from one memory, with sources.

The systems these questions draw on, connected to one memory. Every connector reads by default; the tools that change something are granted by name, per team.

The problem

What it looks like today

  • 01What was agreed with a client in the last meeting is in a notes app, if anywhere.
  • 02Pre-call preparation means reading the CRM, the inbox and the last deck separately.
  • 03Unbilled work and unpaid invoices are reviewed at month end.
  • 04A consultant rolls off and the client context rolls off with them.
  • 05Every proposal is written from scratch, because nobody can find the last one that worked.
  • 06Utilisation and what has actually been promised to clients are two separate conversations with the same people.
How it works

What Memtro does about it

One memory in front of the systems you already pay for, reading by default and acting only where an administrator has granted the tool by name.

  • Connect HubSpot, Google Calendar or Outlook, Granola, Notion, Slack, SharePoint, Asana, DocuSign and Xero, reading by default and acting where you grant it.
  • Ask for a brief before a call and the answer joins the deal, the last meeting's notes, open tasks and the billing position, each fact cited.
  • Decisions and promises stated in meetings and chat are kept as shared memory and checked for whether they were done.
  • Proposals and statements of work in Notion and SharePoint are searchable from one place, with what was decided about them remembered.
  • Schedule jobs: a Monday brief per client, proposals out for signature past a week, invoices unpaid at 30 days.
The stack

System by system

What Memtro reads in each part of the stack, and what it may change there once the tool has been granted.

Meetings and notes

Granola, Fireflies.ai, Gong, Zoom and Google Meet: the summary, the attendees and the transcript of what was actually said, rather than what somebody remembered to write up.

Diary and mail

Google Calendar or Outlook with Gmail or Outlook mail: who is seeing whom this week, and the thread that arranged it.

The firm's own writing

Notion, Confluence, Coda, Guru, SharePoint, Drive or Dropbox: proposals, statements of work, frameworks and decks, searched by what they say.

The pipeline

HubSpot, Salesforce, Pipedrive, Attio or Close: deals, owners and the history of the relationship, with records changed only through a granted action.

The work

Asana, monday.com, ClickUp, Jira or Linear: what was committed to, who holds it and what has actually moved since the kick-off.

Signature and billing

DocuSign for proposals and statements of work out for signature, Xero or QuickBooks Online for what has been billed and what is unpaid.

There are 144 connectors in all, each with its own tools, its own permissions and a page of its own. Browse every connector →

Who it is for

Who asks what

Partner

Walks into a call briefed from the deal, the last meeting, the open work and the billing position, with each fact cited to its source.

Engagement manager

Checks what was promised against what exists: commitments from meetings beside the tasks that were supposed to follow them.

Consultant

Finds what the firm has written before on a subject, and who wrote it, instead of starting the deck again.

Operations

Sees proposals unsigned, invoices unpaid and engagements ending, without chasing four people for a status.

The work that comes round

The engagement

  1. 01

    The pitch

    What the firm has written before on the subject is one question away, with the author named, so the proposal starts from the best version rather than a blank page.

  2. 02

    Kick-off

    What is agreed in the room is captured from the notes and the thread as commitments, with dates and owners, and checked later against the work that was actually tracked.

  3. 03

    Delivery

    A weekly brief per client joins the deal, the last meeting, the open tasks and the billing position, so nothing is prepared twice.

  4. 04

    Billing and what comes next

    Proposals unsigned after a week and invoices unpaid at 30 days arrive as lists, and engagements ending in 60 days are flagged while a conversation is still possible.

In practice

Ask it like this

Plain English, from chat, your editor, a scheduled job or your own agent. In agent mode each question also checks the other systems that know about the same people, companies and references, and the answer ends with a line per system consulted.

Memtro · agent mode
Brief me on BigCo before Thursday: the engagement, what we agreed last time, open tasks and what they owe
Reading 5 systems…
  • HubSpot
  • Google Calendar
  • Outlook Mail
  • Granola
  • Notion

Every figure in the answer cites the record it came from, and the run ends with a line per system consulted.

  • ›What did we promise Acme in the kick-off, and which of it is done?
  • ›Which proposals have been out for more than a week without a signature?
  • ›Which clients have invoices over £10k unpaid at 30 days?
  • ›What have we written before that is close to this brief, and who wrote it?
  • ›Which engagements end in the next 60 days, and has anybody discussed what comes next?
  • ›What has been agreed with Acme that is not in the statement of work?
  • ›Who at the firm has met anybody at BigCo in the last year, and about what?
On a schedule

Work that runs itself

A job is a prompt the agent runs on a cron schedule as its owner, with their tools and connections. Say any of these in chat and the job exists; every run's report is kept in a chat you can question.

  • schedule:Every Monday 07:30: one brief per active client with meetings this week, from the CRM, notes and billing
  • schedule:Every Friday 16:00: proposals and statements of work sent for signature and unsigned after seven days
  • schedule:First of the month: unpaid invoices by client, oldest first, with the last chaser sent
  • schedule:Every Monday 08:00: engagements ending in 60 days with no follow-on conversation recorded
  • schedule:Every Friday 17:00: commitments made in this week's meetings, with whether a task exists for each
How jobs work
Questions

Questions people ask

Does it write notes for us?+

It reads the notes Granola, Notion and the calendar already hold, and remembers what was decided. Slack can post a summary, HubSpot can write a note onto the record and Xero can raise the invoice when asked, each granted by name per team.

Can each team see only its clients?+

Yes. Connections are granted to named teams, so a client's mailbox and documents are visible only to the people on the engagement, and personal memory stays personal.

Which model answers?+

Whichever you hold keys for, including a Claude Code or ChatGPT subscription. The auto model picks a cheap model for a lookup and a strong one for a brief, and every answer says which.

Does it need our notes to be tidy?+

No. It reads what the tools already hold — the meeting summary, the thread, the document — and extracts the durable facts afterwards with provenance. Nothing has to be filed in a particular place first.

Can it write the proposal?+

It drafts from what the firm has written before and what the client has said, with each source named, and a person edits it. It sends nothing: the mail action is granted separately and used only when you ask.

What happens when a consultant leaves?+

What they learned stays, because the shared facts were extracted as they went: the client's decisions, the commitments and the history, each with its source. Their personal memory and personal connections leave with them.

Next

The same work, by team

The same connectors and the same memory, described through the job somebody does rather than the business they do it in.

Memtro for consultancies

Ask it about your own business

Connect the first two systems, ask the question you opened this page with, and see where the answer comes from. About five minutes.

7-day free trial · card on file, nothing charged until it ends · cancel any time