From sample request to completed order.

A designer can return with several projects over time. Treating every conversation as a new relationship loses context. Treating every project as one continuous opportunity makes it difficult to see which purchase is progressing.

Distinguish the person, their company where relevant, and the specific sales opportunity. Keep an order or project reference available where your team needs it.

For example, a designer asking about lighting for two homes may have different decision-makers, specifications, and deadlines for each opportunity. Follow-up should reflect those differences.

The exact record structure depends on your platform. It does not automatically require custom objects or another software subscription.

Stages are useful when everyone agrees what moves an opportunity forward. “Interested” is harder to apply consistently than “consultation completed” or “quote sent.”

1. Inquiry received and assigned
2. Requirements or consultation completed
3. Sample or specification review, when needed
4. Quote sent
5. Decision or approval pending
6. Order confirmed and handed to operations

This is an illustrative workflow. Not every purchase needs every step. A sample request can be an activity associated with an opportunity rather than a mandatory sales stage.

A record full of notes can still leave a team uncertain. For each active opportunity, make three answers easy to find: who owns it, what happens next, and when it should happen.

A sample sent without a follow-up plan can remain unresolved even when the contact details are complete. A quote awaiting approval needs a different next action from a quote waiting on an internal correction.

Use a small number of fields the team can maintain reliably. Add detail when it supports a decision or a handoff, rather than making every possible field mandatory.

When a quote becomes an order, the next team needs more than a notification. Agree on the minimum information required: the approved scope or specification reference, the customer contact, the internal owner, and any unresolved decisions.

If an order-management tool controls production dates, the CRM should not invite salespeople to maintain a second, conflicting version. Decide how your team accesses current information before deciding whether to integrate systems.

Internal reminders, task assignment, and acknowledgments can help a team follow an agreed process. An unusual specification, a delay, or a frustrated customer may need a personal response.

Start with one workflow and test realistic examples, including missing information and changed plans. Check who receives a message, what happens if the owner is unavailable, and how the team stops an inappropriate follow-up.

Record a baseline before changing the workflow:

• Time from inquiry to first meaningful response.
• Open opportunities without an owner or next action.
• Quotes with overdue follow-up.
• Time spent in consistently defined sales stages.
• Handoffs returned because essential information was missing.

Review the numbers alongside team and customer conversations. A delay may reflect a normal design decision rather than a broken process.

Tight Ship CX helps businesses map customer journeys and put practical CRM workflows in place. See how we approach the work.