How a CRM and
follow-up project runs.

From diagnostic to handover: agree the sales journey, responsibilities, scope and acceptance tests, then connect the tools around a process your team can operate.

Discuss your projectExplore the workflow

From the first review to a working handover.

A project moves forward when the next step is clear. Here is what each stage is intended to produce.

  1. Review the sales journey

    Understand where the journey slows down.

    Review your offer, enquiry sources and sales process with the person responsible. Identify the gap worth solving first.

    OutcomeA fit decision and an agreed next step.
  2. Agree scope and fee

    Make the work concrete.

    Use a paid diagnostic where investigation is needed. Confirm the workflow, scope, access, responsibilities, baseline and acceptance tests before implementation.

    OutcomeA written scope, fixed fee and delivery plan.
  3. Connect the workflow

    Build the smallest useful system.

    Implement the agreed connections in your supported tools. Keep account ownership clear and involve the people who will operate the process.

    OutcomeA configured journey with documented handoffs.
  4. Test and train

    Test what happens when things go wrong.

    Check normal journeys, duplicate records, invalid input, failed integrations and stop conditions. Train the sales owner and hand over the operating notes.

    OutcomeAcceptance evidence and a practical handover.
  5. Review the results

    Build on what the evidence shows.

    Review performance against the starting point. Prioritise the next experiment or agree the support your team needs.

    OutcomeAn agreed improvement or support plan.
A team around a shared desk giving each other a high five

Follow an enquiry through the sales process.

Follow an enquiry from arrival to follow-up, including the moments that need a person’s attention.

  1. Step 1CaptureIn seconds

    One enquiry. A reliable record.

    A clear form asks only what matters. The visitor sees a confirmation only after the enquiry is safely stored.

    • Validated
    • Recorded
    • Acknowledged
    New enquiry3-bedroom villa viewingSource: Google searchRecorded
  2. Step 2ConnectIn seconds

    The right owner, with the context.

    The enquiry reaches your existing CRM with its source and details, assigned to a named person with a next action.

    • Matched
    • Routed
    • Assigned
    CRM contactOwner: sales leadPipeline: viewingsAssigned
  3. Step 3Follow upSame day

    Follow-up that does not rely on memory.

    Agreed reminders and handoffs keep every enquiry visible. Your team still leads the conversation.

    • Reminded
    • Reviewed
    • Replied
    Next actionCall back today, 12:00Reminder set for the ownerDue today
  4. Step 4LearnEvery week

    See which enquiries become revenue.

    Connect each source to recorded outcomes, so you know which channels and follow-ups lead to sales.

    • Measured
    • Reviewed
    • Improved
    Weekly reviewOutcomes by sourceFirst reply time by ownerReady

Explore the exceptions.

Choose a situation and run it to see how the system responds. It runs in your browser, so nothing is sent.

  1. Upcoming: Enquiry validated and recorded
  2. Upcoming: Contact matched and owner assigned
  3. Upcoming: Next action created for the sales owner
  4. Upcoming: Outcome ready for human review

Safe receipt, CRM delivery and a confirmed booking are separate states.

Read the enquiry-system case study

Who owns each part of the implementation.

Skillphase

The agreed workflow design, implementation, testing, documentation and delivery reporting. Every engagement has a named owner.

Your business

Lawful access, accurate offer information, approvals, subscriptions, sales follow-up and fulfilment. A sales owner participates in testing and training.

Together

Baseline definitions, priorities, acceptance criteria, business measurement and changes to the scope.

Training, operating notes and ongoing support.

You receive operating notes, account ownership details and the agreed support route. Your team should know how to use the system, recognise a problem and find the person responsible.

Continuing optimisation has its own scope. If the system is stable and there is no useful backlog, a lighter support arrangement may be enough.

What the initial system includes

A clearer process starts with a conversation.

Plan your CRM and follow-up project.

Start a conversation