Everything a small team needs. Nothing it has to work around.
Stretto is one product: records, pipelines, tasks, email and an assistant, all on the same customer timeline. Below is what each part does, and what it deliberately does not.
One record, one history
Contacts and companies carry every interaction in a day-grouped timeline: notes with @mentions, emails with open tracking, calls, tickets, deals and stage changes. An AI summary at the top says where things stand.
- Header highlights, About and sidebar cards you arrange per object
- Associations with cardinality: one company, many contacts
- Duplicate detection on email at create and import
Not a data warehouse: there is no BI layer, exports are CSV and API.
Deals and tickets, the same way
Any object with stages gets a kanban and a calendar on the same saved filters. Drag to change stage, drop on a day to set a date. Won and lost stages ask for a reason so reports mean something.
- Multiple pipelines per object, stages with probability
- Optimistic drag with rollback on failure
- Column count and value update as you move cards
No forecasting models or quota plans: a board, a calendar and honest totals.
Follow-ups that create themselves
A reply, a missed call or a stage change can create the next task on the right person's list, due on the right day. Tasks live on the record and in a personal list, with overdue first.
- Automatic tasks from sequence steps and stage changes
- Assign, reschedule and complete inline
- Daily digest of what is due, by email or in-app
Not a project tool: tasks are about customers, not sprints.
Templates, broadcasts and sequences from your own domain
Verify a sending domain once. Then send one-to-one from a record, one-to-many to a list with a pre-flight checklist, or enroll contacts in a multi-step sequence that stops the moment they reply.
- Templates with record variables and a live preview
- Broadcast report: delivered, opened, clicked, bounced, unsubscribed
- Sequences with send windows, timezone and exit criteria
Not a marketing suite: no landing pages, no ad tracking, no lead scoring.
Filters you can name and share
Build a filter once and save it as a view or an active list that updates itself. Views drive the table, the board and the calendar. Lists drive broadcasts and sequence enrollment.
- Static lists for one-off imports, active lists for rules
- Bulk actions from any view: assign, enroll, tag, export
- Column picker and inline editing in the table
Lists are per account, not per person: everyone sees the same truth.
Shape it in a dialog, not a project
Add a property with one of 13 types, create a custom object with its own pipeline, define how objects associate, and drag the record layout into place. Every change applies immediately and shows up in the API.
- Text, number, money, dates, select, multiselect, user, formula and more
- Custom objects like subscriptions, shipments or properties
- Hide objects the team does not use: data and API stay intact
Fixed roles, not a permission matrix: owner, admin, member, read-only.
Reads freely. Writes only when you say so
Ask in plain language, for example deals in negotiation with no activity for two weeks, and the assistant searches, summarizes and drafts. Anything that would change data arrives as a proposal card you confirm or reject. Nothing writes on its own.
- Record summaries and reply drafts with tone controls
- Proposal cards show what changes and how many records
- Confirmed actions come with undo
The confirm step is a product rule, not a setting you can switch off.
Know what changed, not everything that happened
Mentions, assignments, due tasks, replies and bounces group by day in one popover. Choose in-app, email or a digest per event type, including AI proposals waiting for you.
- Grouped items: three tasks due today, not three separate pings
- Per-event delivery preferences
- Quiet hours
No Slack-style channels: notifications point to a record, always.
Everything in the UI is in the API
Scoped API keys, REST endpoints for every object including custom ones, and webhooks for record, email and sequence events. Add the tracking snippet and page views land on the contact.
- Scopes per key: objects, schema, email, sequences, lists, tracking, webhooks, AI
- Webhook deliveries with retries and a log
- Website tracking with a live event feed
Rate-limited per account. The docs list the limits honestly.