Business development, built for the field
Turn the phone already in your hand into the BD field system: scan the card, see relationship heat, circle or hand-pick the stops, and carry the next move without turning your network into a shared company CRM.
The BD day, in your hand
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.
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.
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.
Relationship temperature, not population density.
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.
Actual product preview · demo workspace · no customer records. Map data © OpenStreetMap contributors.
The real problem
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.
Field time creates a backlog. Re-entering it later strips away the details that made the relationship useful.
The organization name survives. The conversation, timing, trust, and promised next move do not.
A personal network becomes generic rows, while the rep inherits another system to clean and maintain.
From handshake to next move
Teryli keeps the fast field action and the careful identity decision in the same flow.
Capture
Scan the front and back, add someone manually, or keep moving through Event Mode while earlier cards process.
Connect
Program Directory context can support the relationship without becoming the relationship record itself.
Prepare
Public professional sources can support a role summary, talking points, editable tags, and follow-up timing.
Review
Accept, edit, reject, or hold the result. Saving is a human decision, not an automated consequence.
The product boundary
They can work together without becoming the same database.
Owner-scoped relationship layer
Shared program context
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 the records are linked.
Data integrity
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.
An organization can exist without borrowing a person’s phone, email, or identity.
Office phones, shared inboxes, and common domains do not silently collapse different people.
Low-confidence matches belong in a review queue, not inside a trusted relationship record.
Preview, provenance, completion reporting, and rollback come before a backlog is treated as ready.
$90/month · flat subscription
We’ll walk through your actual field day, confirm the workspace fits, and set up private-preview access at $90/month.
Flat subscription, independent of referral activity. Rankings cannot be purchased. Programs cannot buy recommendations.