Sellify AI / Research WorkbenchBlueprintHow it worksResearchInbox, all blocks: 3 Sign out
Blueprint / Insights and platform

Integrations and API

Not shown in the Loom recording.

Why this block matters
  • Not shown in the Loom recording.
Areas in this block:
Not shown in the Loom recording.
Shown by: FieldRoutes, PestPac, Briostack, GorillaDesk, Research and sources for this block
1Our CRM and vendors2How it connects3Inbox

How Well We Know This Block

A person sets it on a 5-step scale. Click a step to set it as Ivan (mock sign-in, top right).

1
Not Explored
Nobody looked into this block yet.
2
First Look
Someone read the vendors’ public pages for it once.
3
Vendors Compared
We know how each of the 4 vendors does it.
4
Plan Drafted
Our CRM plan for the block is written. Open points remain.
5
Full Clarity
We agree how we build it. No open points remain.
Now: Not Explored. Set by Ivan, 2026-10-28 07:08 UTC (mock).
Now: Not Explored. Set by Ivan, 2026-10-28 07:08 UTC (mock).
Now: First Look. Set by Ivan (mock).
Now: Vendors Compared. Set by Ivan (mock).
Now: Plan Drafted. Set by Ivan (mock).
Now: Full Clarity. Set by Ivan, 2026-10-28 07:12 UTC (mock).
Earlier settings (1)Earlier settings (1)Earlier settingsEarlier settingsEarlier settingsEarlier settings (4)
Not shown in the Loom recording.
1
Step 1

Our CRM and the 4 Vendors

One tab each, same layout. The number counts the lines, terms and notes in a tab.
Our CRMFieldRoutes124 terms and notes, 21 screensPestPacBriostackGorillaDeskFull screen
Our CRM in Integrations and API

Our CRM: How We Build Integrations and API

The same layout as a vendor tab. Each line carries one mark: agreed by a person, or waiting. Our CRM across all 20 blocks

Agreed by a person, with the dateWaiting: said or asked in Slack, or agent researchExample. No decision yet.

Screens

No screens of our own CRM for this block yet.

What the block does for us

Nothing yet. A line arrives here when a person accepts an item from the inbox.

The data it holds

Nothing yet. A line arrives here when a person accepts an item from the inbox.

Our picks: which vendor idea we take, and why

Nothing yet. A line arrives here when a person accepts an item from the inbox.

Open points

Nothing yet. A line arrives here when a person accepts an item from the inbox.
2
Step 2

How This Block Connects

Click a block for its vendor terms.

Not in the flow: no links are drawn for this block.

Solid arrow: a source shows this linkDashed arrow: our hypothesis, no source yetThe word on an arrow says what one block does to the next.
3
Step 3

Inbox: New Items for This Block

Items from Slack, uploads and agent research wait here. Accept moves an item to its place.

Add from here

Planned: post in Slack and mention the agent, and it files the post here. Today the copy of Slack keeps the text and file names only.

Upload a screen or note

Ask the agent to research

For example: how does PestPac bill a customer with 12 sites?Ask

Mock: no agent runs in this static page.

Nothing waits in this inbox.

Where this block is stored: How it works, part 2.