One call to connect.
The rest is practice.

Turning Latte on takes a single call. What follows is a few weeks of it learning how your client's team actually works, with our team next to you for every adjustment.

Book the kickoff call What the first weeks look like

Before the callFour thingsNothing to install

One owner on the client sideThe person whose work should get easier firstBring

Someone who can sign in to the CRMAdmin rights, on the call, at a keyboardBring

The two workflows to start withThe jobs the team complains aboutBring

Who approves whatSending, writing back, anything that leaves the buildingDecide together

No data prep, no export, no spreadsheet to fill in firstReady

What deployment actually looks like.

Four stages. Only the first one needs a calendar invite.

Kickoff call Riverbend Food Bank · with Northwind Advisory

Connect your systemsScreen share, no install3 of 3

Raiser's Edge NXTSigned in as the client · read access firstConnected

Google WorkspaceMail and calendar for two staffConnected

SlackOne channel, so requests have somewhere to landConnected

Nothing is written anywhere until someone approves itLatte is live for Riverbend Food Bank · 14 minutes into the callLive

Ask Latte for something, and watch it propose the first one…

1The call · 30 minutes

Connect the systems.

You and your client sign in to the CRM, mail, and wherever the team already talks, live on the call so they see exactly what was granted. Latte reads first and writes nothing. Nothing is migrated, nothing is replaced, and nothing is installed on anybody's machine.

WorkflowsRiverbend Food BankStart with two

Contact reportsFrom email, calls, and meeting notesSelected

Follow-up draftsIn each officer's own voiceSelected

Wealth screeningiWave and DonorSearchLater

Grant cycleFind, draft, submit, trackLater

Add the rest whenever the team is ready for themLive for 2 staff · every result arrives as a proposalOn

2Week one

Pick the jobs the team resents.

Usually contact reports and follow-up drafts. Every result arrives as a proposal with an approve button, so the cost of a wrong first draft is one click and a note, not a mess in the CRM to clean up.

Drafted the spring appeal for the 84 lapsed donors. Here is the opening line.

Draft 1M. Alvarez

"Your support last year allowed us to serve 640 beneficiaries across the county."

Too formal. We say neighbors, not beneficiaries, and we never lead with a number.

Rewritten, and saved to your profile. I will use it on your drafts from now on.

What I learnedM. Alvarez · Riverbend Food Bank

Say "neighbors", never "beneficiaries"Applies to every draft for this organizationSaved

Open on the person, not the figureM. Alvarez onlySaved

Sign off "Warmly, Maria"Learned from 6 approved draftsLearned

3Weeks two to four

It learns the person, not just the shop.

Corrections are the training. When someone rewrites a line, Latte keeps the reason, not just the edit, and applies it to that person's work from then on. Two officers at the same organization end up with drafts that sound like each of them.

See what it drafts

Shared channelNorthwind Advisory + LatteSlack

NARay Okonkwo Northwind Advisory 9:12 AMRiverbend wants acknowledgements coming from the ED, not the officer. Can we change that?

MOMaya Okafor Latte 1:40 PMDone. Acknowledgement drafts now come from Dana's address with the officer copied, and I applied it to the three waiting for approval. Anything else from the first month?

AdjustmentsRiverbend Food BankSince the kickoff

Acknowledgements send from the EDLatte team · todayApplied

Fund code maps from column FLatte team, after the first import · week 3Applied

Program director copied on contact reportsAsked for in the thread, Latte applied it · week 2Applied

Bigger changes go to a person hereLogged

4Ongoing

Our team tunes it with you.

Say the small things in the thread and Latte keeps them itself. Bring the bigger ones to the shared channel, a workflow shaped wrong or a field mapped to the wrong place, and someone here changes it that day. You are not filing tickets into a queue and waiting.

Things we change for you, whenever you ask

Workflow scope
Field mappings
Tone and house language
Approval routing
New systems to connect
Who sees what

Book the kickoff, or ask us first.

Either one reaches the same people. There is no handoff to an onboarding department.

Book the kickoff call

Questions between calls: support@latteconnect.com