Skip to main content

Your first week with Spiich

A five-day plan for a new workspace: connect your tools and ask a real question, record a meeting, work the follow-ups, build a table, then hand repeat work to a background agent.

Do one thing a day for five days and by Friday you will have used every part of Spiich on real work. Nothing here takes more than twenty minutes, and each day builds on the one before.

Day one: connect, then ask something real

Finish the first-run setup wizard if you have not already, and check the three connections that matter most.

  • Your CRM: connect your CRM. One per workspace, and it is what everything else reads from.
  • Your mailbox and calendar: Google or Microsoft 365. Each person connects their own.
  • Check Settings to see what is still missing.

Then open Chat and ask something you would otherwise have gone digging for.

Try this on day one

Which of my open deals have not moved in the last two weeks, and what was the last thing that happened on each?

Type @ while you write to mention a real CRM record so Spiich works on exactly the account you mean.

Day two: record a meeting

Install the Spiich Recorder and pair it before your first external call of the day. No bot joins the meeting; it records from your own machine.

Before the call, read the briefing Spiich prepared. After it, look at the summary and the searchable transcript. See how meetings work for the whole path from calendar to CRM.

Already on Fathom or Fireflies.ai? Import meetings from there instead.

Day three: work the follow-ups

Open My Day. Yesterday's meeting should now carry a summary, CRM updates and a follow-up email draft.

  • Review the CRM updates before they land. See what Spiich does on its own.
  • Edit the follow-up draft, then open it in your mail client and send it. Spiich never sends for you.
  • Dictate what happened on a call you did not record: voice updates.

While you are here, tell Spiich how you actually work so it stops guessing: teach Spiich how you work.

Day four: build a table

A table is a saved view of your CRM: one object type, the columns you care about, a saved filter and sort. It stays live against the CRM rather than being a snapshot.

Build the list you rebuild by hand every week. You can ask for it in chat:

Ask for a table

Build me a table of open deals over 20k closing this quarter, with the owner, the stage and the last activity date.

Then add an AI or prompt column that answers a question per row, and use bulk actions to work the list. Click into any row to see its record page.

Day five: hand off the repeat work

Now automate the thing you did three times this week. Start with background agents overview, then create a background agent.

  • Decide when it fires: agent triggers.
  • Have it stage changes for approval rather than writing straight to the CRM while you build trust.
  • Watch the first few runs: monitor agent runs.

Once the week is over

Stuck on a word along the way? The glossary has all of them.

Frequently asked questions

Connect your CRM and your mailbox, then correct the four company cards in setup. Everything Spiich says afterwards is grounded in those, so five minutes spent on them changes the quality of every answer, briefing and agent run for months.