Skip to main content
GullySystem
Technology

Lead Management for SaaS and software companies

Give each enquiry an owner, status and next action.

CRM

Does this function belong in your operation?

Use when enquiries arrive through several channels or follow-ups are missed.

A prospective buyer makes contact.

Trial sign-ups, demo requests and webinar attendees enter one list with the plan they looked at and the number of seats they asked about. A salesperson picks up product-qualified accounts first. Won deals become subscription records.

Bring the records the workflow depends on.

  • Lead sources
  • Assignment rules
  • Follow-up stages

Outputs to check

  • Assigned enquiry register
  • Due follow-up list
  • Qualification and closure record

Follow the lead management workflow.

Use this sequence to compare your current process with the proposed module. Agree the owner, permission and exception at each step.

  1. 1. Capture the enquiry

    Record the prospect's requirement and source.

  2. 2. Check duplicates

    Review matching contacts while preserving distinct needs.

  3. 3. Assign ownership

    Set the responsible person and next action.

  4. 4. Qualify the requirement

    Record discussions and the reason to progress, pause or close.

  5. 5. Handover to sales

    Create the relevant opportunity or order reference without losing enquiry history.

Who uses the module, and who approves?

Keep responsibilities distinct even when one person holds more than one role.

Sales executive

Opens today’s call list, rings, writes one line and sets the next date.

Sales head or branch manager

Reviews unassigned or overdue leads and transfers actions when a salesperson is unavailable.

Owner

Reviews enquiry sources and the orders linked to them, using the recorded outcome of each lead.

Decide how exceptions are handled.

These business rules belong in configuration and testing. A normal transaction alone does not demonstrate that the workflow is ready.

Repeated enquiry

Review matching contact details and preserve distinct requirements before merging.

Owner unavailable

Reassign the next action with the interaction history intact.

Prospect requests no contact

Record the restriction and stop the relevant follow-up activity under your communication policy.

Can this work independently?

Lead tracking can start with manual entries or file imports. Website forms and messaging channels are optional supported connections. Qualified leads hand over to opportunities or orders using a retained reference; qualification itself does not create revenue or a confirmed customer commitment.

Systems and records it connects with

  • Opportunity management: Deal requirements, values, stages and decision history.
  • Quote and proposal management: Commercial proposal versions and acceptance details.
  • Trade portals and business directories: Permitted enquiry imports retaining their original source references.
  • WhatsApp: Permitted message content and channel delivery responses.

Configure, test and introduce the workflow.

  • Name every channel enquiries use. A note comes back with the sources and the fields each can fill.
  • Name your hot, warm and later stages and your reasons for dropping. They appear on a screen. Try them. Share the sheets executives keep. The trial import flags duplicates for the sales head to resolve.
  • Executives practise logging a call and setting a next date. Each gets a note for the phone. The review meeting opens with the untouched list. After a cycle, source figures are read together.

Check the result before rollout.

Apply these checks to a sample from the agreed workflow, then repeat with an exception. Keep the expected result beside the test record.

  • Active leads have owners.
  • Duplicates can be reviewed together.
  • Closed leads retain reasons.
SaaS and software companies

How the business operates.

Your product ships code, and the business runs on accounts. Each customer is on a plan, has a renewal date, pays through a gateway and writes to support, and those facts live in different tools.

Customer and subscription register

Hold each account with its plan, seat count, add-ons, billing cycle and renewal date, so the list the team works from is the list finance bills from.

Trial and onboarding tracker

Show who started a trial, what they have used and who has been contacted, with a follow-up due before the trial ends.

See the full industry workflow, reports and implementation plan →

The records that hold the operation together.

  • Account and subscription register. Hold every subscriber with its owner, workspace, plan, seat count, add-ons, billing cycle, start date and renewal date. Billing and success work from the same list.
  • Plans, add-ons and pricing rules. Define plans, seat tiers, usage allowances, annual discounts and add-ons once. Proration and the way annual plans count toward monthly revenue are agreed during set-up.
  • Trial and onboarding tracker. List trial signups with seats invited, features used and the sales or success person assigned. A follow-up falls due before the trial ends, not after.
  • Invoices and recurring billing. Raise an invoice for each cycle from the subscription record, with tax settings per country. Upgrades and seat changes mid-cycle produce the adjusted line on the next invoice.

Operational bottlenecks to check

Revenue numbers do not match

The gateway, the invoice list and the sheet each show a different monthly total. Nobody trusts the report.

Failed payments go unchased

A card expires, the retry fails, and the account is live for weeks without paying. Collections stay manual.

How work flows across this business

This module sits within a wider operating process. Use the sequence to identify the other teams and records affected by a change.

  1. 1. Signup and trial

    A visitor registers, and an account is created with the trial plan and its end date. Sales sees which signups used the product and who has been contacted.

  2. 2. Conversion

    A trial turns into a paid subscription with a plan, seat count, add-ons and billing cycle. Enterprise buyers get a contract with a negotiated price on the same record.

  3. 3. Billing and collection

    Invoices are raised for each cycle. Payments arrive from the gateway, failures are retried on a schedule, and unpaid accounts are listed for a person to follow up.

  4. 4. Support and success

    Requests are logged against the account and tagged as a question, a defect or a feature ask. Customer success reads usage and open tickets before every review call.

  5. 5. Renewal or change

    Upcoming renewals are listed ahead of the date. Upgrades, downgrades and pauses change the plan and the invoice together, with the effective date recorded.

  6. 6. Cancellation and learning

    A cancellation records its reason, the last day of access and any refund. Reasons are totalled by plan and by period for the product team.

Industry reports to connect with

  • Monthly recurring revenue by plan: new, expansion, contraction, cancelled
  • Logo churn and seat churn, with cancellation reasons totalled
  • Trials started, converted and lapsed, by source and by owner
  • Failed payments open, by retry stage and age

Questions before implementation.

When should saas and software companies consider lead management?

Use when enquiries arrive through several channels or follow-ups are missed. A prospective buyer makes contact.

What should we bring to the requirements discussion?

Bring anonymised examples of Lead sources; Assignment rules; Follow-up stages. Show who creates, checks and changes each record. Use only records from an activity that meets the suitability conditions above.

Does this replace our existing business software?

The starting point is your current system and the gap you need to close. Give each enquiry an owner, status and next action. Configuration, a connected module or a custom build are evaluated against that gap before a replacement is proposed.

What is outside this module?

Lead tracking organises enquiries already received. Demand generation and the buyer’s sales decision remain separate activities.

How are scope, price and rollout decided?

The proposal follows a review of your records, user roles, branches and existing software. Data migration, connections, training and support are scoped separately where needed. Active leads have owners. Use this check when reviewing the first working version.

Related functions for saas and software companies.

    Talk to us

    Discuss lead management for your business.

    Tell us which workflow needs attention and which systems your team uses. The next step is a requirements discussion and a written scope.

    What happens after you share your requirements

    1. We review your brief and the systems you already use.
    2. We clarify the workflow, missing information and the work to consider first.
    3. The proposed scope sets out the deliverables, responsibilities and dependencies.
    4. Review the scope and commercial terms before deciding whether to proceed.

    Start with your requirements

    Describe your current process, the people involved and the change you need. Start with the details you know; we can clarify the rest together.

    Share your requirements