CRM automation project brief

Tell me what is happening now—and where the process breaks.

Share the current journey, the point creating friction, and what you want the system to handle better. Plain language is enough; you do not need a technical specification.

Use this brief when

  • A lead or client journey is hard to see from start to finish.
  • Follow-up, booking, onboarding, or reactivation depends on manual tracking.
  • Your CRM has data, but the next action or owner is unclear.

Start with the current process

Give me enough context to understand the handoff.

The form stays focused on seven details: who you are, the system you use, what happens now, and what should become clearer.

Project brief / local preparation

Describe the operating path.

All fields are required. Your answers are used only to prepare the email draft shown at the end of this form.

01About you

Who should I reply to, and what business, team, or project is this brief about?

Use the address where you want to receive a reply.

A working name is fine if the project is still being defined.

02Current process

Choose the closest options, then explain the sequence in ordinary language. Technical terminology is not required.

Include the entry point, messages, staff actions, and tracking you already know about. Up to 2,000 characters.

03Desired outcome

Focus on the operating change you need, not a polished solution or technical specification.

Describe the bottleneck and the clearer result you want. Up to 1,500 characters.

Keep sensitive information out of the brief. Do not include passwords, login codes, payment details, or confidential customer data.

This creates a reviewable email draft. Nothing is sent when you press the button.

Email handoff

Review before sending.

Complete the required fields to prepare a structured draft. You stay in control of whether it is sent.

Email directly: ligayaautomation@gmail.com

What happens next

A simple review, without artificial urgency.

The brief starts a conversation. It does not create a booking, contract, or commitment.

  1. 01

    I review the brief

    I look at the current process, the bottleneck, and the result you want the system to support.

  2. 02

    I reply with a next step

    I respond by email with relevant questions, fit, or a practical recommendation based on the context provided.

  3. 03

    We clarify the scope

    When there is a potential fit, we define the system boundary, responsibilities, and the next useful action.

Prefer regular email?

You can send the same context directly without using the brief generator.

ligayaautomation@gmail.comReview the service scope first