The situation

A conversation dies between the handshake and the CRM

The room went well. The follow-up never reached the system.

• A card goes in a pocket.
• A name goes in a phone.
• By Monday neither is a contact.

The complication

The note is a memory The system is somewhere else

Sometimes that system is Salesforce. Sometimes it predates the word CRM.

• The rep remembers a person.
• The system holds rows.
• Nothing carries one to the other.

The answer

The capture is the iPad in the room

Three steps on one screen.

1. The picture A card, or a LinkedIn screen.
2. The note Typed, or spoken.
3. The read A person checks it before it is saved.

Try it now

A blank stays blank

Photograph a card. Watch what it fills and what it leaves alone.

• The name comes off the picture.
• A field it cannot read stays empty.
• Nothing saves until you have read it.

Open the scanner

For your team

Each rep's iPad holds the night

In the morning, each rep exports. The file is the handoff.

• No shared server. The night stays on the device.
• No shared password. The iPads do not share a login.
• Rows, not devices. A manager collects the export.

Over the system you already run

The file goes where your system already looks

This page never logs into your org.

Why it holds

The same rule as a department file

Ronald builds for the PA State Department. A machine may draft. A person decides.

• Generated code is a draft.
• A person reviews it.
• Nothing merges itself.

Roadmap

Four horizons Start with tonight

Each horizon stands on the one before it. Dates come after the team is named.

1. Tonight This scanner.
2. One team Your event. Your export.
3. Your system The file it already eats.
4. The pattern A photo in. Strict fields. A person confirms. The record you trust.