Skip to main content
GullySystem
Real estate and construction

Lead Management for Industrial park developers

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.

Each broker call or lessee visit is logged against the space asked for, and the follow-up date keeps the enquiry from going cold.

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.
Industrial park developers

How the business operates.

Enquiries, lease terms, rent, shared charges and meter readings for plot allotments and shed lettings in an industrial park all run in one system that GullySystem configures. Every plot and shed carries its area, its lease and its dues. Service requests, fit-out approvals and renewals sit on the same unit record.

Park layout, plots and sheds

List each plot, shed and racked bay with its phase, plinth area, clear height, floor loading and asking rate. Leasing sees at once what is vacant, held, let or near expiry.

Enquiries and site visits

Record each broker or lessee enquiry with the space asked for, the visit made and the follow-up due. Nothing depends on a card in someone’s pocket, and a lost enquiry keeps its reason.

See the full industry workflow, reports and implementation plan →

The records that hold the operation together.

  • Park layout, plots and sheds. List each plot, shed and racked bay with its phase, plinth area, clear height, floor loading and asking rate. Leasing sees at once what is vacant, held, let or near expiry.
  • Enquiries and site visits. Record each broker or lessee enquiry with the space asked for, the visit made and the follow-up due. Nothing depends on a card in someone’s pocket, and a lost enquiry keeps its reason.
  • Quotations and offer letters. Build an offer from the unit’s area and rate, with lock-in, escalation and deposit written in. Every revision stays beside the first, and an accepted offer starts the lease for that allottee.
  • Lease register. Hold start date, lock-in, escalation step, rent-free period, deposit, sublease clause and renewal option for each lessee. A monthly list shows the dates falling due, in the clauses your own leases use.

Operational bottlenecks to check

Vacant space is known by walking the roads

Which sheds stand empty, which are held for a quotation and which sit under notice lives in the manager’s head. Two brokers are then promised the same bay, and one of them goes elsewhere.

Lease clauses sit in scanned files

Lock-in, rent-free fit-out and escalation step are typed into a sheet by whoever read the leasehold agreement last. A date buried in a scan reaches the leasing head late, after the notice window closed.

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. Enquiry

    A broker, a site visit or a call from a cold-chain, auto-component or fulfilment firm is logged with the area, dock count and floor loading it needs. The enquiry also records who answered the call.

  2. 2. Offer and site visit

    The leasing team shows a layout, then sends a quotation with area, rate, lock-in and deposit. The unit is marked held, and each revised offer is kept next to the first one.

  3. 3. Lease and handover

    The agreed terms become a lease record with its escalation steps, deposit and rent-free period. Possession is noted against the unit once keys and meter readings are handed over to the new allottee.

  4. 4. Monthly billing

    The park office enters sub-meter readings on a phone. Rent, shared charges, power and water are drawn up from the lease and the readings, then sent to the lessee with the kVAh figure shown.

  5. 5. Running the park

    Complaints, fit-out requests and rounds on pump rooms, generator sets and boom barriers are logged against a location. A named person follows each one to closure, and the streetlight faults too.

  6. 6. Renewal or exit

    Expiries are listed ahead of time. A renewal repeats the offer step. An exit closes the unit, settles the deposit against dues and puts the shed back on the vacant list for the next enquiry.

Industry reports to connect with

  • Occupancy by phase, with vacant, held, let and under-notice units
  • Rent roll by lessee, unit and escalation step
  • Lease expiries and renewal options falling due, month by month
  • Shared charges billed per square metre, with area used for each unit

Questions before implementation.

When should industrial park developers 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.

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