Lead intake automation service: one source, one owned record.

The handoff to check

If your team copies requests by hand, start by agreeing the record that must exist after intake. A missing field should remain visible, rather than being invented to make the record look complete.

Try the fictional workflow demo →

Decide what counts as a new enquiry

Agree the difference between a new request, an update to an existing job and an unrelated message. Define an identifier and a duplicate-handling rule before connecting the source. One person submitting twice need not mean two sales opportunities.

Keep the intake boundary small

Select one source that already receives commercially relevant requests. Map contact and company details, request type, supplied scope and timing. The first pilot creates or updates the agreed destination record; it does not rebuild the CRM or combine all acquisition channels.

Test the failure path as well as the happy path

Use supplied examples with complete fields, missing scope, repeat submissions and an unavailable destination. Acceptance checks that a record or visible exception exists and that a human can recover it. Sales results are outside the acceptance promise.

The bounded deliverable

• One enquiry source: one web form or one shared inbox
• One destination: HubSpot or Google Sheets
• Extraction of available contact or company details, enquiry type, work scope, postcode or service area, domestic or commercial context, requested timing, drawings, urgency and preferred contact method
• An owner, status and dated next action on every created record
• A visible human review queue for uncertain or incomplete records
• A basic team notification
• Acceptance testing against up to 30 historical examples supplied by your team
• Short operating and handover documentation
• Customer-owned accounts and operational data

The 14-day delivery window starts once the agreed access, sample enquiries and acceptance rules are available.

£475 at the agreed start; £475 after documented acceptance. Third-party software fees are excluded. The pilot does not include autonomous pricing, quoting, revenue guarantees or CRM replacement.

Read the full scope, exclusions and acceptance criteria →

Check the fit

Fits: A stable form or shared inbox, HubSpot or Google Sheets, and a team willing to agree ownership rules.

Outside this pilot: Lead list building, outbound campaigns, many sources in one pilot, or a new CRM rollout.

Do you need AI for lead intake?

Not necessarily. Structured form fields and agreed routing rules can be handled deterministically. Any uncertain interpretation must remain visible for human review; the offer is an operational handoff, not an AI-agent subscription.