7:30 AM

Scan the room.
See the territory.
Build the day.

Capture cards as fast as you meet people. See which relationships are cooling off. Circle a cluster, or hand-pick the stops, and turn it into a drivable field day.

7:35 AM

Nobody loses the relationship during the conversation. They lose it afterward.

A strong lunch, event, tour, or hallway conversation becomes a card in a pocket, a note without context, and a follow-up remembered three days too late.

The cards become a weekend project

Field time creates a backlog. Re-entering it later strips away the details that made the relationship useful.

The context stays in one person’s head

The organization name survives. The conversation, timing, trust, and promised next move do not.

A shared CRM flattens the relationship

A personal network becomes generic rows, while the rep inherits another system to clean and maintain.

7:40 AM

The BD day, in your hand.

Capture — scan without stopping

Open the rear camera, capture the front, flip for the back, and review the structured contact before saving. Event Mode keeps a temporary device inbox moving while earlier cards process.

Territory — see relationship heat, not just pins

Visits stay warm longer than calls, and calls longer than emails. Heat shows Hot, Warm, Cooling, Cold, and No history. Lasso lets you circle the cluster you want.

Route — route it your way

Tap pins, circle a cluster, or let Build my day prioritize follow-ups due, cooling relationships, and first-visit opportunities. Teryli suggests the stop order, then hands it off to Maps.

Territory · THUSynthetic
Hot Warm Cooling Cold No history
→ Maps

4:50 PM · follow-up drafted, held for your review

Captured · THU · Event ModeSynthetic
R.M.Harbor Pines IOPHot
T.C.Cedar Line RecoveryCooling
D.A.Northgate Clinical ServicesNo history
J.P.Sable Creek TransitionsCooling

Reviewed before saving · nothing sent

5:00 PM

Capture it now. Decide what is true. Carry the relationship forward.

From handshake to next move

  1. 01CaptureGet the card while the conversation is fresh — front and back, manual add, or Event Mode while earlier cards process.
  2. 02ConnectSurface a possible organization match; the rep confirms the association. Directory context supports the relationship without becoming the relationship record.
  3. 03PreparePublic professional sources support a role summary, talking points, editable tags, and follow-up timing.
  4. 04ReviewNothing becomes trusted until a person reviews it. Accept, edit, reject, or hold the result — saving is a human decision, not an automated consequence.
Any day

Meet Fred. You review every output.

Fred · Teryli’s executive assistantDescribed, not shown

Fred is Teryli’s executive assistant, included with BD Field + AI, Team, and Office — not Directory Access. Helpful research and drafting; your judgment stays in the loop. Fred can organize context, search the Directory with de-identified criteria, and prepare a brief or follow-up draft. You review every output before you rely on it.

Fred’s boundary

Not autonomous outreach.Fred does not send messages or make changes on his own.
Not placement advice.Directory research is operational support, not a clinical, medical, or placement recommendation.
No client details.Never enter PHI, client, resident, or sensitive care information into Fred prompts or public forms.

Fred prepares research, context, and drafts for review; do not enter PHI or client details.

Any day

A book of business is not a pile of rows.

Importing relationship data is identity work. A shared office phone is not one person. An account name is not the owner of every email beside it. Teryli’s standard is conservative on purpose.

Your book is not the Program Directory.

My Book · owner-scopedPeople and confirmed identity, your notes and last touch, event and route context, the history you built. Linked when useful, not merged by assumption.
Program Directory · sharedProgram identity and location, levels of care, published contacts, last-checked dates. A directory correction can improve a program record without rewriting your relationship history; a follow-up note in My Book never becomes shared directory data just because records are linked.
Account ≠ contactAn organization can exist without borrowing a person’s phone, email, or identity.
Shared channel ≠ duplicateOffice phones, shared inboxes, and common domains do not silently collapse different people.
Uncertain stays heldLow-confidence matches belong in a review queue, not inside a trusted relationship record.

Imports are designed to stay reviewable. Preview, provenance, completion reporting, and rollback requirements are confirmed before a backlog is treated as ready.

Any day

Start with research. Add the field workflow when you need it.

Directory $90 · BD Field + AI $130 · no setup fee on either.

Directory Access Available nowFind and compare programs. $90/monthOrganization workspace · one authorized user · no setup fee Request Directory Access
Program Directory, maps, filters, profiles, contacts, and source contextIncluded
Fred, private Book, card scanning, Event Finder, routes, mileage, or follow-up workspaceNot included
BD Field + AI Organization planRun your territory. $130/monthOrganization workspace · one authorized user · Directory included See current pricing
Private Book, card capture and review, Briefs, Event Finder, relationship heat, routes, and mileageIncluded
Fred call prep, field-day planning, and reviewable follow-up draftsIncluded

Directory Access and BD Field + AI are available through organization onboarding. We confirm the organization, purchaser authority, authorized users, and scope before billing or activation. Shared workspaces for more than one rep are in early access; ask in a workflow review. Full breakdown on the pricing page.

Now

Your BD day deserves better than a backlog.

We’ll walk through a de-identified field workflow, confirm the right plan, and tell you what is available before anything is billed. Do not send PHI or client details.