Everything you need to know,
organized around your work.

LeadBin is a customer relationship workspace for keeping people, companies, opportunities, tasks, and service work connected. Today highlights recorded work that needs attention; Revenue Rescue helps you investigate particular follow-up and deal signals.

It is designed for solo operators and growing teams that want a practical CRM without a complicated setup. Teams can begin with core records and add forms, reporting, workflows, and permissions as their needs grow.

Teachers can explore CRM activities for a simulated business, a school store, or sponsor relationships on our Educational Resources page. A restricted student classroom mode is planned for a controlled, school-approved pilot; it is not available for general sign-up. Do not enter student education records into a general workspace for a classroom test.

Yes. Free includes one workspace, up to three seats and 500 contacts in that workspace, plus people and companies, a basic pipeline, tasks, and notes. You do not need a credit card.

Create an account, set up a workspace, then add a person, company, or opportunity. You can start with a small set of records and configure your pipeline before importing a larger list.

No. You can enter records manually and use tasks and opportunities immediately. Import is useful when you already have a clean contact or company list, but it is not a prerequisite.

Yes. Core CRM records, tasks, notes, and opportunities do not depend on a mail or calendar connection. Connected activity is optional and its availability can depend on your plan and the current provider pilot.

The Pricing page lists Free, Starter, Growth, and Scale with monthly and annual billing, headline limits, and current availability notes. Annual paid plans show a 20% lower monthly equivalent and are billed upfront for the year. Features remain subject to plan entitlements and separate provider gates; a listed allowance does not itself switch on sending.

A workspace is the boundary for a team’s CRM records, settings, and membership. Use the workspace switcher to move between workspaces you can access; records from one workspace should not appear in another.

Yes, when you have been granted membership in each one. Select the active workspace before adding or editing records so your work lands in the intended place.

Free includes one workspace owned by your account. One Starter subscription covers up to three owned workspaces; Growth covers up to five; Scale has no workspace cap. Seats and contact limits apply separately to each workspace. Joining a workspace owned by someone else does not use one of your slots. Existing separate subscriptions are not consolidated automatically.

Yes. Settings → Workspaces lists the active owner or owners. An owner or admin can change the workspace display name there. The workspace ID, membership, and customer records stay with the same workspace; the change is recorded in its audit history.

Open Settings → Workspaces and choose New workspace. When your account has reached its allowance, choose a higher plan before creating another. The new workspace has its own records and members, but can use your account’s active paid plan. An owner or admin can start checkout for a workspace; contact billing support to change or consolidate an existing subscription.

An authorized workspace owner or admin can use the team area in Settings to invite a member. Seat capacity depends on the plan: Free includes up to three seats, Starter ten, Growth twenty, and Scale has no seat cap. Pending invitations reserve a seat.

Yes. Workspace roles govern who can view or manage particular resources; additional permission controls are associated with higher plans. An action shown in a screen is still checked by the server when you submit it.

Written Teamwork is available in every workspace for active members. It includes Team updates, direct messages, record-linked conversations, replies, mentions, search, and tasks made from shared messages. Free supports collaboration among up to three workspace members.

Yes. Work → Calendar is included in every workspace. It has month, week, and day views for dated tasks and LeadBin meetings. Tasks start with those assigned to you, with an option to see the whole workspace. You can schedule a meeting for yourself or make it visible to workspace members. Connected Google or Microsoft events are separate read-only approved pilots, not a standard-plan promise.

No. A LeadBin meeting saves its time, title, visibility, and optional supported HTTPS meeting link in the workspace. It does not create an external calendar event, email attendees, send an RSVP, or change a provider meeting. Undated Teamwork links appear beside Calendar until you create a dated LeadBin meeting.

Yes. Eligible signed-in members can start an in-app call from Teamwork or a workspace-visible Calendar meeting in any workspace. Calls support up to eight participants for 60 minutes and have an in-call chat. External guests, recording, and transcription are disabled. Members can also share an existing Google Meet, Microsoft Teams, or Zoom link.

No. The call chat is available during a newly started LeadBin video room, including to participants who join later, but LeadBin does not archive it or copy it into Teamwork. Post any decision or follow-up in the related Teamwork conversation if it needs to remain available.

Yes. In Teamwork, choose New conversation and select multiple active members of the current workspace for a private group chat. Only its participants can read it; the same workspace and membership checks apply to its call link.

Yes. Open a conversation and choose Pop out to keep a compact Teamwork window beside your other work. Unread counts appear on Teamwork when messages need your attention, and opening a conversation clears its unread state for you.

Use the top-bar search to look for supported records in the active workspace, or open the relevant People, Companies, Opportunities, Tasks, or Tickets section and use its search and filters. Results remain scoped to the workspace you selected.

No. Collapsing the navigation changes the layout only; it does not archive records or alter your permissions. Expand it again to see the full labels.

A person is an individual contact; a company is an account or organization. Link them when that relationship is known so tasks, opportunities, and context are easier to understand.

Yes. Records can be linked so a teammate can move from the contact to its open deal or follow-up work. Check the links when importing or creating records to avoid attaching activity to the wrong customer.

Yes. People Import Center accepts CSV and .xlsx files up to 1,000 rows or 5 MB, subject to your workspace contact allowance, with reviewed exact-email updates and row-level results. On Companies, use the separate CSV importer for up to 250 rows or 256 KB. Preview new, existing, and repeated companies before importing. Existing companies are skipped; company imports do not create contacts or marketing consent.

Yes. In People, explicitly select records, review an owner, lead status, or category change, and apply it. The result reports per-record failures. Common fields such as phone and job title can also be edited inline; identity fields remain in the contact record.

A static list stores selected contact IDs; a dynamic list uses saved People filters. Lists are scoped to one workspace and show current counts. Active members can use them, while owners and admins manage them. Selecting a list never starts a sequence or sends a message.

Form intake and import paths include duplicate-aware handling, but no matching rule is perfect. Review names, email addresses, and links before changing a record; ambiguous matches should be resolved by a person.

Custom fields are available with the appropriate plan and workspace permissions. Use a field for data the team will maintain consistently, and consider whether a standard field or note is simpler first.

Scale workspaces can define additional record types for processes that do not fit people, companies, opportunities, or tickets. Custom-object reporting and task-oriented automation are available in supported flows; broader actions remain subject to release gates.

Data export is included in the plans described on the Pricing page. Use the relevant record area or workspace tools available to your role, and review the exported file before sharing it outside your organization.

Open Opportunities and choose New opportunity. Give it a clear name, select the appropriate pipeline and stage, and link the people or company involved when known.

Yes, if your role permits it. Move it in the board or edit its stage in the record; stage reporting is based on recorded changes, so it should not be read as a complete history of activity that happened before tracking began.

Workspace pipeline configuration can represent different sales processes, subject to your plan and permissions. Pick the pipeline whose stages match the work rather than forcing unrelated deals through one sequence.

Open deal value totals amounts recorded on active opportunities, grouped by currency where applicable. Forecast views may weight saved amounts using explicit deal or stage probabilities; they are estimates from entered data, not promises or predictions that a deal will close.

Check its status, pipeline, close date, amount, currency, and probability inputs. A view can exclude incomplete or past-due inputs and show them in a review list instead of silently inventing values.

Supported proposal tools let authorized users work with drafts, versions, and PDFs. Delivery and view evidence have separate release and recipient safeguards; a proposal marked sent is not proof that a recipient opened it.

Its daily priorities now live in Today, so there is one clear starting place for the selected workspace. Open Sales > Dashboards for the separate pipeline, activity, conversion, and reporting views. Both use recorded data; missing outside activity is not inferred.

Today brings together recorded tasks, meetings, pipeline items, tickets, and a ranked list of next actions for the active workspace. Counts describe saved and matched data; missing synchronization or unlogged work can affect what you see.

The priority list uses recorded due dates and other available record signals to surface timely work. It is an ordering aid, not a guarantee of business impact. Open the source record before contacting someone or changing a deal.

It looks for supported patterns such as overdue follow-ups, quiet open opportunities, unanswered form leads, reactivation candidates, renewals, and proposal follow-up. Each finding should explain the recorded evidence and provide a route back to the source.

No. It is based on recorded open-deal, contract, or proposal amounts associated with findings, with overlapping values counted carefully. It is not money recovered, a predicted win, or a substitute for an accounting system.

Urgency is a way to order findings from the evidence available to that scan. It is not a win probability or a published predictive risk model; limited-data and unverified-activity messages matter when deciding what to do.

Supported findings can be snoozed so they leave the active list for a period. Snoozing does not complete the underlying task or change the source opportunity; review the record when the finding returns.

The scan depends on workspace records, source revisions, a healthy worker, and available activity coverage. Refresh the view, inspect any “checked” timestamp or coverage note, and verify the linked record; an absent finding is not proof that all outreach happened.

Open Tasks or use Create task from a related record, enter a specific title and due date, and select an assignee. Link the relevant person, company, or opportunity so the next teammate has context.

Its saved status changes and the completed work can appear in relevant activity or reporting. Completing a task does not send an email, log a call, or close a deal automatically unless a separate, enabled rule explicitly does so.

Supported lists let authorized users save useful filter or sort combinations. People also supports workspace-shared static and dynamic prospect lists. A view or list organizes records; it does not send outreach or change the contacts by itself.

Playbooks provide repeatable questions or prompts that a teammate can use during a customer conversation. They support consistent notes and handoffs, but they do not talk to a customer on their own.

Sequences organize timed tasks and editable follow-up drafts. Enrollment and any later send require the applicable permissions, suppression checks, provider readiness, and human review; adding someone to a sequence is not blanket consent to message them.

Supported rules can create tasks or in-app notifications when specific CRM events occur, with conditions tied to the record and rule. Rules begin as drafts and should be tested against a disposable record before you rely on them; external messaging is separately gated.

No. Task and notification workflows do not silently send email. Campaign delivery is a separate selected-workspace pilot that requires a connected provider, verified sender and feedback, consent and suppression checks, and an explicit reviewed launch.

Yes, on a plan that includes Forms. Create the form, review its fields and consent copy, and verify any site where it will be embedded before activation. A submission creates or matches a lead; it does not automatically send a marketing email.

The Forms area includes landing-page drafts that can be paired with an existing lead form. Review the public content and publish intentionally; creating a draft alone does not make it live.

LeadBin records the submission and attempts a workspace-scoped contact match using the available data. Review the new contact, source, and follow-up task before assuming the person is qualified or already contacted.

No. A checked box is a recorded consent claim that still needs clear wording, the appropriate permission basis, and the platform’s verification and suppression safeguards. The existence of a checkbox or an email allowance does not enable sending.

An owner or admin can enable CampaignBin in Settings → Extensions on a supported plan. Drafts and previews remain separate from outbound delivery. Sending requires sender verification, consent, and workspace release controls; enabling CampaignBin alone never sends mail.

In an approved workspace, an owner or admin can connect that workspace’s own Brevo account or a dedicated campaign SMTP mailbox. SMTP requires authenticated bounce, complaint, and unsubscribe feedback. A personal one-to-one mailbox does not activate campaigns. Your provider’s sending allowance and charges remain yours.

Use New ticket in Tickets, provide a meaningful subject and description, set priority, and select one or more active teammates to own the work. The ticket then has a status and history your team can review.

Supported service settings let an authorized workspace define deadline clocks and target hours by priority. New tickets use saved policy; changing targets does not silently rewrite the deadlines of older tickets.

Only when service targets, alert settings, and the server-side checker are enabled for that workspace. An on-screen target configuration without an active checker is not a promise that alerts are being generated.

No. Logging a first response records that your teammate actually replied through the chosen channel; it does not send the reply. Use it only after the customer communication happened.

Support forms provide a structured intake path for issues, while knowledge-base articles give the team reusable answers. Review publication and access settings before treating either as customer-facing.

Portal workflows are release-gated and may not be available to your workspace. Do not rely on a customer portal or live chat as a generally available support channel until your workspace has been explicitly enabled and verified.

Dashboards groups pipeline, activity, lead-conversion, customer-revenue, and custom-report views into tabs. A tab can show a limited-data state when a source is not connected or enough recorded history does not exist.

Zero can mean the scoped query found no matching recorded event; a dash often means a rate cannot be calculated from the available denominator. Neither should be taken as proof that an off-platform interaction did not happen.

Conversion views follow a defined cohort of form-created contacts and recorded qualification or opportunity outcomes. Time windows must mature before a fair percentage is shown; older history is not invented from a contact’s current stage.

Authorized users on eligible plans can preview and save supported grouped views of CRM records. A saved report preserves a definition; it is not an automatically emailed report or an independent source of truth for missing data.

Scale reporting can group active records of a configured custom-object type by supported fields. The report counts saved object records; it does not automatically turn them into revenue forecasts.

No. LeadBin’s own subscription billing must stay separate from a customer workspace’s purchases and lifetime value. Customer-owned revenue reporting requires its own verified integration; the current customer Stripe path is synthetic-only, not live customer purchase evidence.

Recorded amounts should be shown by currency unless an explicit conversion source and rate are configured. LeadBin does not silently treat different currencies as interchangeable in a deal or Rescue total.

QuoteBin is an optional workspace extension for a service catalog, versioned quotes, separate contract approval, and Stripe invoices. An owner or admin enables it in Settings → Extensions and connects that workspace’s own Stripe merchant before payable documents can be issued.

No. Quote approval prepares a separate contract. The buyer reviews and approves that agreement with an emailed code before QuoteBin creates its invoice. An issued invoice is not an automatic payment; the buyer chooses whether to pay through Stripe.

Yes. In an enabled workspace, open QuoteBin → Invoices → New invoice. Link an existing contact or company if appropriate, or enter a one-time recipient email. Save a private draft, review the amount and recipient, then explicitly issue it. You can copy the hosted link or ask Stripe to email the invoice.

The creator or a workspace owner/admin can delete an unissued direct-invoice draft. An owner/admin can void an Open, unpaid invoice from a direct invoice or approved contract; Stripe confirms the void, and the invoice stays visible for the financial record. Paid invoices cannot be deleted or voided. QuoteBin does not automatically email the buyer when an invoice is voided.

No. LeadBin plan payments and QuoteBin customer invoices are separate. Each QuoteBin workspace connects its own Stripe merchant; that merchant’s public business name is shown to the buyer. Stripe fees and merchant eligibility are governed by that connection.

No public v1 QuoteBin API is documented. Quotes, contracts, invoices, and Stripe connection steps use the signed-in app and workspace permissions.

A workspace owner or admin enables the optional TimeBin extension in Settings → Extensions. Active members can then start a timer from supported CRM records or add a reviewed manual entry; viewers cannot log time.

TimeBin shows tracked hours and, when rates are configured, labor cost. It uses paid, linked QuoteBin invoices as verified revenue and calls revenue less tracked labor cost labor contribution. It does not include every external cost or claim to calculate net profit.

No. TimeBin works on its own for timers, entries, projects, and hour reports. Without a linked paid QuoteBin invoice, revenue is shown as not linked rather than inferred from an opportunity amount or unpaid quote.

Optional per-user connections exist in controlled provider pilots and depend on plan, account approval, and workspace configuration. Check Settings for current connection health; a provider badge alone does not prove that recent mail or meetings have synchronized.

Personal email lets an active, non-viewer member connect an SMTP mailbox in one workspace to send reviewed, one-to-one messages. The general connection does not sync Inbox or Sent mail. Google and Microsoft activity connections are separate read-only pilots, and neither connection enables bulk campaign sending.

No. Connected activity is used to provide recorded context where the pilot allows it. Draft creation, approval, and an actual send are separate actions, and campaign delivery has its own gates.

No connected content should be sent to Scout without separate consent. Review the particular assistant action and the data it offers before using it, especially when working with sensitive customer information.

Scout can prepare a draft for you to review. Sending one-to-one from inside LeadBin requires an eligible personal mailbox connection and a separately enabled pilot; it does not turn on campaign sending. Check the recipient, message, and mailbox before confirming any send.

API access and outbound webhook drafts are available in supported higher-plan workflows with role and workspace checks. Before using either with live data, verify the endpoint, token scope, delivery configuration, and any release gate in your workspace.

The app may show provider errors or stale-sync status so you can reconnect or investigate. Until the connection is healthy, missing activity is a coverage gap—not evidence that no customer contact took place.

The app has responsive screens and installable PWA support, with selected offline record and draft flows. Offline behavior is not yet a blanket guarantee for every feature or device; confirm synchronization after reconnecting before relying on a change.

Current monthly subscription prices are Starter $29, Growth $79, and Scale $199. One subscription covers the included owned workspaces: up to three on Starter, five on Growth, and unlimited on Scale. Seat and contact limits apply to each workspace. Annual options and current availability are on Pricing; check checkout for the exact term and total before confirming payment.

No. The allowance is an upper bound for a billing cycle if campaign email is enabled. Sender verification, consent, suppression, provider feedback, and a workspace-specific release are separate requirements. Campaign sending is currently a selected-workspace pilot.

The documented plans do not automatically charge overages. If you reach a plan limit, review your options in the workspace rather than assuming more members, contacts, or messages will be added or billed automatically.

Plan changes depend on the available billing flow and your workspace’s eligibility. Review the checkout or billing screen before confirming, and contact support if a pilot restriction or entitlement does not match what you expect.

Some screens explain a higher-plan entitlement, a required role, or a release-gated pilot. Check the message in the app and your workspace plan first; a visible control does not override server-side access or provider-readiness checks.

Use the Help area or the support route available to your workspace, and include the affected page, approximate time, and what you expected to happen. Avoid including passwords, API tokens, or sensitive customer data in a support request.