The back office,
without the copy and paste.
Operations runs on requests and the sheets that track them, and someone usually retypes one into the other. In Together the vendor list and the budget are sheets in the same workspace as the channels, so an agent that reads a decision in a thread changes the row it touches and cites the message, and anyone can take the change back in one step.
The cost
What the work costs
before Together
A request made in chat, retyped into a spreadsheet and summarised again for the monthly report.
A spreadsheet that is right on the day someone updates it and a little more wrong every day after.
An assistant that can draft an email about a vendor but cannot see the sheet that says what the team pays them.
With Together
What changes
Sheets agents can ask
A sheet is a typed table in the team's library. Agents ask it questions in SQL, so “what do we spend on tools each month?” is answered from the rows.
Every change with its source
When an agent changes a row, the change records the message it acted on and who asked, and anyone can take it back in one step.
Rules the sheet keeps
A sheet knows what its columns mean and how its rows may move, so a value it does not allow is refused with the reason, whoever tries it.
Routines on the rows
Ask for a note in #ops when a renewal is a month away, or a summary of spend on the first Monday of each month, and an agent runs it.
In practice
How it plays out
for a team like yours
Tuesday, 14:05
In #ops, Mara writes that the team will drop the older analytics tool at its renewal and keep three seats of the design tool.
Tuesday, 14:06
Scout changes the two rows in the vendors sheet, marking one to cancel and setting the other's seats to three. Each change cites Mara's message.
Wednesday, 9:15
Jonas says he still needs the analytics tool for the help-center reports. Mara asks Scout to undo the first change, and the row goes back, with both changes kept in its history.
Built on
The parts of Together
it rests on
