At a glance
A sign-shop CRM earns its place when it makes the next action and the job context easier to find. It should preserve source, uncertainty, contacts and consent while connecting an enquiry to the work being evaluated—without pretending every conversation is qualified or won.
01 / Trigger and problem
Capture an enquiry when there is a useful next question to own.
The trigger is a new request or a material customer conversation. The problem is that contact details alone do not tell sales, estimating or operations which site, sign type, decision-maker, timing or uncertainty belongs to the opportunity.
Do not inflate a sparse message into a qualified job. Preserve what was supplied, what was inferred and what remains unanswered so follow-up has a clear purpose.
02 / Inputs, owners and output
Carry the conversation into a reviewable job context.
The enquiry owner records source, contact, site, requested outcome and permission state. Sales or estimating owns clarification and qualification. A stage owner accepts the next action. The output is a bounded enquiry record with questions, decision role and an owned follow-up—not a conversion claim.
| Input | Responsible owner | Concrete output |
|---|---|---|
| Contact, organisation and source | Enquiry owner | Source-labelled contact record |
| Site, work type and requested timing | Sales / estimator | Initial job context |
| Authority, questions and next action | Qualification owner | Qualified, returned or closed state |
| Marketing permission | Data / marketing owner | Separate consent state |
03 / Fictional process artefact
A useful record keeps uncertainty visible.
This is a fictional sign-shop enquiry example. A contact asks about vehicle graphics for three vans and supplies only an email address and preferred month. The enquiry owner records the request, asks for vehicle variants, panel scope, depot location and decision authority, and assigns estimating review. No quote, booking or win is implied.
04 / Current state
The website stores its own enquiries; a live product CRM is not claimed.
The public form uses a website-only database and may return a receipt after durable storage. That receipt does not prove notification, human review, resource fulfilment, booking or CRM hand-off. Live lead scoring, email sequences, contact sync and marketing automation are not claimed.
| State | Inspectable now | Boundary |
|---|---|---|
| Implemented on this website | Bounded enquiry form and durable website receipt | No automatic notification, booking or fulfilment |
| Demonstrated | Fictional connected job context | No customer account or live sales operation |
| Planned / not claimed | Product CRM, contact sync and sequences | Requires application and provider evidence |
05 / Prerequisites and limitations
Define ownership, consent and retention before importing contacts.
Agree qualification fields, response ownership, deduplication, role access, retention, deletion and a lawful communication basis. Separate service responses from optional marketing permission, and do not place customer files, artwork, credentials or sensitive job data in a general website form.
- Named owner for unqualified, active, dormant and closed enquiries
- Source, freshness and correction route for contact information
- Separate consent evidence for any optional marketing use
- Permission and export rules for a future protected application
06 / Fit and next action
Test the enquiry-to-estimate hand-off, not a generic contact database.
This may fit a sign team that loses customer context between inbox, quote and operations. It is not evidence of a live CRM, sales automation, mailbox integration, outcome improvement or a service-level response commitment.
Inspect the form expectations and sample workflow, then use synthetic information to map the minimum record your team would need. A demo request should describe the difficult hand-off only; do not submit real customer documents or credentials.