The decks
Tessaro_SteerCo_v7_final_TM.pptx. Which version did the client see?
For consulting firms
What your teams learn, stays with the firm.
Interviews, models and steerco decks stay with the engagement, not on a laptop that rolls off. AI coworkers do the research grind and cite the interview, the call note and the past deck. Nothing reaches the client until the partner signs off.
Client walls built in Partner sign-off Sources on every insight Files stay on your Mac
The problem
An engagement lives in a shared drive and the team's heads.
Interview notes, models and deck versions spread across drives and inboxes. When the team rolls off, what it learned goes with it, and the next team starts again.
The research
38 interview notes across 22 email threads. Nobody has read all of them twice.
The lessons
The team that ran the Halden price test is on three other engagements. What it learned is in their heads.
What you get
Built for how a firm runs its engagements.
One channel per engagement. The research, the questions, the answers and the sign-offs stay together, and the firm's method grows from them.
Research at engagement speed
Ask in the engagement channel. The agent codes every interview by theme, joins the survey data and reports what it found, with counts.
Every insight cites its source
Each finding names the interview, the call note and the past deck it came from, so a partner can check it before a client sees it.
Client walls built in
An agent reads as the person who asked. An engagement you cannot open stays out of its context and out of its answers.
A partner signs off
Anything sent to the client waits for the partner. Approve in the workspace or in Slack. Routine research runs without approval.
Status that drafts itself
Every Monday a pipeline gathers updates from each engagement channel and drafts one page per client. Your review is a stage.
Method that compounds
Scribe turns what each team learned into firm method, such as how you run price tests. Every line points to its source.
Plan your team in plain words
Describe your practice. Review the team it proposes.
Chief of Staff asks up to three questions, then proposes AI coworkers and channels. You edit or untick each role before anything is created, and every new agent starts restricted.
An example team for a strategy practice. Your proposal follows the work you describe.
- Research AnalystCodes interviews and desk research by theme, with a source for every finding.
- Data AnalystJoins survey and client data and checks the numbers behind each claim.
- Engagement WriterDrafts status pages and steerco summaries for the partner to review.
The record
Everything lands on one record.
Every message, run, file change and approval is one event on an append-only record. It shows who did it, person or agent, what was approved and by whom.
- 09:15 · #eng-tessaro-pricinghuman
Lena asks Research Analyst for the pricing insights from 38 store interviews
- 09:18 · run · Lena's MacBook Proagent
Research Analyst codes 38 interviews into 6 themes and joins 1,240 survey answers
- 09:24 · threadhuman
Lena answers: lead with shoppers, managers as support
- 09:38 · gate · deck to clientgate
Deck parked. Sending to Tessaro waits for the partner
- 09:40 · approvalhuman
Tom approves. The record keeps who approved, and the deck as sent
The next engagement starts from this one
Findings, decks and decisions stay with the engagement. The next team starts from what the firm already learned.
Know what each engagement costs
See agent spend per accepted deliverable, against the fee, across every agent and model.
Private beta
Run one engagement through Mobtasks.
Bring one live engagement and its research. We'll set up the team with you during the private beta.