Website and CRM Package: A Complete Guide for Small Businesses

A website can bring a potential customer to your business, but it does not automatically organise what happens next.

Someone still has to receive the enquiry, check the details, reply, prepare a quote, confirm the work, request a deposit, issue an invoice, track the balance and follow up after the job. When those steps are spread across email, WhatsApp, Facebook messages, handwritten notes and separate payment apps, good leads are easy to lose.

A website and CRM package connects the public-facing website to the system used to manage customers and work behind the scenes. The website explains the service and captures the right information. The CRM stores that information, gives the enquiry a clear status and supports the steps that turn it into booked, paid work.

That distinction matters. A polished website is useful, but a polished website connected to a weak process can still produce slow replies, duplicated admin and forgotten follow-ups.

This guide explains what a proper website and CRM package should include, how the workflow should operate, which businesses benefit most, what to ask a supplier and where the legal, security and data-protection responsibilities sit.

Contents

1. What is a website and CRM package?
2. How the complete enquiry-to-payment workflow works
3. The essential parts of a good package
4. Website only versus website and CRM
5. Which businesses benefit most?
6. What the CRM should record
7. Automation that helps rather than annoys
8. Payments, invoices and deposits
9. Data protection, cookies and security
10. SEO and conversion requirements
11. How implementation should work
12. How to compare suppliers and packages
13. What to measure after launch
14. Common mistakes
15. Frequently asked questions

What is a website and CRM package?

CRM stands for customer relationship management. Microsoft describes a CRM as a connected system used to manage, track and store information about customers and prospective customers in one central place. That definition is useful because it highlights the real purpose: a CRM is not just an address book. It is the working record of the relationship between an enquiry and the business. See Microsoft's explanation of customer relationship management.

A website and CRM package normally combines two layers.

The customer-facing layer

This is the website people visit. It should:

• explain what the business does;
• show who the service is for;
• provide evidence such as reviews, photographs, case studies or qualifications;
• answer common questions;
• make the next step clear;
• capture enough information to handle the enquiry properly;
• work cleanly on mobile devices.

The business-management layer

This is the private system used by the business. It should:

• create a record when an enquiry arrives;
• store customer and job details;
• show the status of each lead;
• record replies, notes and tasks;
• support quotes, bookings, invoices and payments where required;
• prompt the business when follow-up is due;
• retain a clear history of what happened.

The value comes from the connection between those layers. A contact form that merely sends an email is not the same as a form that creates a structured enquiry record, assigns a status, triggers an acknowledgement and makes the next action visible.

A good package therefore joins the full process rather than selling a website and adding an unrelated CRM login afterwards.

How the complete enquiry-to-payment workflow works

The exact workflow will vary by business, but a service-led small business commonly needs the following sequence.

1. A customer finds the right page

The customer might arrive from Google Search, Google Maps, a referral, social media or a direct link. The page should match the reason for the visit. A person looking for a wedding DJ should land on a wedding-focused page, while someone looking for emergency plumbing should see the urgent service, coverage area and fastest contact option immediately.

Google's guidance is to create helpful, reliable content for people and to use the words searchers would naturally use in prominent places such as page titles and headings. That supports clear service pages without turning the copy into repetitive keyword text. See Google Search Essentials and its guidance on people-first content.

2. The website captures the right details

The form or booking route should collect the minimum information needed to take a useful next step.

For a general service business, that could include:

• name;
• email address;
• telephone number;
• service required;
• postcode or area;
• preferred timescale;
• a short description of the work.

For a date-led business, it may also need:

• event or appointment date;
• venue or location;
• approximate times;
• package or service interest;
• guest numbers or job size.

The form should not ask for every detail the business might ever want. The Information Commissioner's Office explains that data minimisation means collecting personal information that is adequate, relevant and limited to what is necessary for the purpose. See the ICO's data minimisation guidance.

The cluster guide on a website with an enquiry form and CRM explains the form design and data flow in more detail.

3. The CRM creates a structured enquiry

When the form is submitted, the CRM should create or update the relevant contact and create a separate enquiry or opportunity record.

That separation is important. One customer may make several enquiries or book more than one job. If the system stores everything in a single contact note, the history becomes difficult to understand. A better structure distinguishes between:

• the person or organisation;
• the individual enquiry;
• the job or booking;
• the quote;
• the invoice;
• the payment;
• the communication history.

The new enquiry should have an owner, timestamp, source and status. It should not depend on someone noticing a message in an overcrowded inbox.

4. The customer receives a useful acknowledgement

An automatic acknowledgement should confirm that the enquiry arrived and explain what happens next. It should not pretend that the enquiry has been reviewed when it has not.

A clear acknowledgement might say:

Thanks for your enquiry. Your details have arrived safely. We will check the information and reply within one working day. If your request is urgent, call us on [number].

This reduces uncertainty while the business prepares a real response.

5. The business qualifies the enquiry

The next step may involve checking:

• whether the service is suitable;
• whether the location is covered;
• whether the date or appointment slot is available;
• whether enough information has been provided;
• whether a site visit or call is needed;
• whether the likely budget and timescale fit.

The CRM should make the result explicit. Useful stages might be:

• new enquiry;
• reply needed;
• waiting for customer;
• qualified;
• quote required;
• quote sent;
• follow-up due;
• booked;
• lost;
• not suitable.

A stage is only useful when it tells the business what should happen next.

6. A quote or proposal is issued

For quote-led work, the CRM should allow the business to create a clear quote without retyping the customer's details and job information from scratch.

The quote should make clear:

• what is included;
• what is excluded;
• the price and applicable tax treatment;
• how long the quote remains valid;
• payment stages;
• expected timings;
• relevant terms;
• how the customer accepts.

Acceptance should be recorded, rather than relying on a vague message buried in a thread.

7. The booking or job is confirmed

A request is not always a confirmed booking. The system should distinguish between:

• requested;
• provisionally held;
• quote accepted;
• deposit due;
• confirmed;
• completed;
• cancelled.

For businesses that sell appointments or fixed time slots, a live scheduler may be appropriate. For DJs, entertainers, tradespeople and other work with travel, setup or bespoke requirements, a request-to-book process is often safer than instant confirmation.

The guide to a website with a booking system compares those models and explains how to prevent double-booking.

8. The invoice and payment request are connected

Once work is agreed, the CRM should create the relevant invoice or payment request and keep the payment status with the booking.

The system may need to track:

• deposit requested;
• deposit paid;
• balance outstanding;
• balance due date;
• payment received;
• refund or adjustment;
• invoice number;
• receipt issued.

The point is not to replace proper accounting software in every business. It is to stop the operational team from guessing whether a booking is financially secure.

9. Reminders and follow-up are scheduled

A good system makes unfinished work visible. That might include:

• enquiries awaiting a first response;
• quotes awaiting a decision;
• deposits not yet paid;
• final balances approaching their due date;
• information still needed before the job;
• completed work ready for a review request.

The CRM should support follow-up, not simply store old messages.

10. The record closes with a clear outcome

Every enquiry should eventually have an outcome such as booked, lost, withdrawn, unavailable or unsuitable. Recording the reason helps the business see whether it is losing work because of price, response time, location, unavailable dates or poor-fit enquiries.

Without those outcomes, the business has a list of contacts but no useful sales information.

The essential parts of a good package

A package should be judged by the operating system it creates, not the length of its feature list.

1. A website built around real customer decisions

The website should contain enough information for a suitable customer to decide whether to enquire.

That usually means:

• a direct homepage message;
• a page for each important service or booking type;
• location or service-area information;
• evidence of real work;
• pricing guidance or a clear explanation of what affects price;
• an understandable process;
• FAQs;
• clear contact routes.

A five-page website can work well when the service is simple. A business with several distinct services, audiences or locations may need a deeper structure. Page count should follow customer needs rather than an arbitrary package limit.

2. Mobile-friendly design

Google uses the mobile version of a website's content for indexing and ranking, which makes mobile usability part of both search visibility and conversion. See Google's mobile-first indexing guidance.

The mobile version should provide:

• readable text;
• obvious calls to action;
• tap-to-call telephone numbers;
• forms that do not require awkward zooming;
• fast-loading media;
• menus that are easy to use;
• no important content hidden from mobile users.

A desktop mock-up is not enough. The forms, payment route and booking process need testing on real phones.

3. Enquiry forms designed for the service

A generic name-email-message form often creates unnecessary back-and-forth. A better form asks the questions needed to qualify that type of work.

Examples include:

• postcode and job type for a trade;
• event date, venue and package interest for a DJ;
• preferred appointment and service for a clinic or consultant;
• organisation, project scope and timescale for a business service.

Conditional fields can keep the form short by showing detailed questions only when relevant.

Forms should also be accessible. The W3C's guidance explains that labels and instructions help users enter information correctly, while errors should be identified in text rather than only by colour or a generic failure message. See the W3C guidance on labels and instructions and error identification.

4. Reliable CRM integration

The CRM connection should be more than forwarding a copy of the form by email.

Check whether it:

• creates the correct contact and enquiry records;
• prevents obvious duplicate records;
• preserves all submitted fields;
• records the source page or campaign where appropriate;
• alerts the right person;
• sends the customer a confirmation;
• records failures for investigation;
• lets the business export its data.

Email notifications are useful, but the CRM record should remain the source of truth.

5. A simple pipeline

A pipeline should reflect the actual business process. It should not force a small business into corporate sales language that nobody uses.

For a booking business:

New enquiry -> Availability checked -> Quote sent -> Deposit due -> Confirmed -> Balance due -> Complete -> Review requested

For a trade:

New enquiry -> Details requested -> Site visit booked -> Quote sent -> Approved -> Work scheduled -> Invoiced -> Paid

For a consultant:

New enquiry -> Discovery call -> Proposal sent -> Follow-up -> Won -> Onboarding -> Complete

The pipeline should answer two questions at a glance: where is this enquiry now, and what must happen next?

6. Quotes and terms

Quote generation should reuse information already held in the system. Re-entering names, addresses and job details wastes time and creates avoidable errors.

Where the customer accepts online, the system should record:

• the version accepted;
• the date and time;
• the person accepting;
• the associated terms;
• any required confirmation or signature.

A web designer should not invent legal terms for the client. The business remains responsible for ensuring its quote, cancellation and service terms are suitable.

7. Invoices and payment status

The package should either create invoices that meet the business's needs or integrate cleanly with the accounting system that does.

UK invoice requirements depend on the business and whether it is VAT registered. GOV.UK lists the information invoices must contain and notes that VAT-registered businesses need the additional information required on VAT invoices. See GOV.UK's invoicing guidance.

A CRM may support the operational invoice workflow while the accounting platform remains responsible for bookkeeping, VAT records and reconciliation. The roles should be agreed before implementation.

8. Hosted online payments

Customers may need to pay a deposit, booking fee, part payment or final balance. A safe implementation normally sends the customer to a reputable hosted payment page rather than collecting raw card information through an ordinary website form.

Stripe, for example, documents that its Payment Links use a Stripe-hosted page and can be shared by email or placed on a website. See Stripe's Payment Links documentation. The PCI Security Standards Council also provides merchant resources for protecting payment data.

The CRM should store the payment reference and status, not the customer's full card details.

9. Email templates and reminders

Templates are useful for repeated messages such as:

• enquiry received;
• more information needed;
• quote ready;
• quote follow-up;
• deposit request;
• booking confirmation;
• balance reminder;
• appointment reminder;
• job-complete message;
• review request.

They should be editable and written in the business's own voice. A template should save typing without making every customer feel as though they are speaking to a robot.

10. Reporting that supports decisions

A small business does not need an enormous dashboard. It does need enough information to answer practical questions:

• How many enquiries arrived?
• Where did they come from?
• How quickly did we reply?
• How many received a quote?
• How many booked?
• How many deposits were paid?
• Why were opportunities lost?
• Which services produce worthwhile work?

A report is useful only when the underlying statuses and records are kept accurately.

Website only versus website and CRM

A connected package is not automatically the right answer for every business.

A website-only package may be enough when:

• enquiry volume is very low;
• most work comes from a small number of known clients;
• there is no quote or booking process;
• the existing CRM already works well;
• the immediate need is simply a credible online presence;
• the business is not ready to change its internal process.

Yorkshire Digital's Starter website package is designed for that simpler requirement.

A website and CRM package is more useful when:

• enquiries arrive from several channels;
• the business forgets to follow up;
• customers need quotes or proposals;
• dates, appointments or job stages must be managed;
• deposits and final balances are important;
• more than one person handles customer communication;
• the owner cannot see what is still outstanding;
• repeated admin is taking time away from paid work.

The decision should be based on operational need, not on whether CRM software sounds impressive.

Which businesses benefit most?

The strongest fit is usually an enquiry-led or booking-led service business.

DJs, entertainers and event suppliers

These businesses need to capture event date, venue, timings, package interest and availability. The CRM then supports the quote, deposit, confirmation, balance and post-event review request.

The dedicated guide to website design for DJs explains the pages and booking workflow in detail.

Tradespeople and home-service businesses

Trades often need to collect postcode, job type, urgency, photographs and access information. The CRM can organise site visits, quote status, scheduled work, invoices and payment follow-up.

Consultants and professional services

A consultant may need a discovery call, proposal, acceptance, invoice and onboarding sequence. The CRM keeps the decision history and next action visible.

Venues, trainers and appointment businesses

These businesses may need live availability, capacity limits, recurring slots, reminders and cancellations. Their booking logic can be more complex, so the website should not be built before those rules are mapped.

Service businesses with repeat customers

Cleaners, maintenance providers, photographers, tutors and other repeat-service businesses benefit from being able to see the customer's previous jobs, preferences and payment history without searching several systems.

Businesses that may not be a good fit

A service-oriented website and CRM package may be the wrong architecture for:

• a large ecommerce catalogue that needs stock, fulfilment and returns management;
• a highly regulated case-management process requiring specialist sector software;
• a business whose existing CRM and accounting integrations are already mature;
• a very simple operation that receives only occasional enquiries and has no follow-up problem.

A responsible supplier should say when the package is unnecessary or when specialist software is the better choice.

What the CRM should record

A weak CRM stores names. A useful CRM stores the information needed to move work forward.

Contact record

This normally includes:

• name;
• organisation where relevant;
• preferred contact details;
• address or service location where needed;
• communication preferences;
• relevant notes;
• linked enquiries, bookings and invoices.

Enquiry record

This should include:

• date and time received;
• service requested;
• source;
• customer message and form answers;
• owner;
• status;
• next action;
• outcome and lost reason.

Booking or job record

This may include:

• agreed service;
• date and times;
• venue or job address;
• access and setup details;
• package or scope;
• internal notes;
• deposit and balance status;
• documents and communications.

Quote record

Useful fields include:

• quote number;
• version;
• issue date;
• expiry date;
• line items;
• tax treatment;
• acceptance status;
• accepted date;
• associated terms.

Invoice and payment record

The system may need:

• invoice number;
• issue and due dates;
• amount;
• VAT details where applicable;
• payment link;
• payment reference;
• paid date;
• outstanding balance;
• refund or credit note status.

Task and communication record

The business should be able to see:

• messages sent;
• replies received;
• telephone notes;
• files shared;
• tasks due;
• reminders completed;
• who took each action.

This does not mean storing unnecessary personal detail. It means maintaining a clear, relevant operational history.

Automation that helps rather than annoys

Automation is valuable when it removes repetitive work and prevents silence. It becomes harmful when it sends inappropriate messages or makes promises the business has not checked.

Good uses of automation

• immediate confirmation that a form was received;
• internal notification of a new enquiry;
• task creation when a reply is due;
• reminder after a quote has been unanswered for a reasonable period;
• deposit and balance reminders;
• appointment or event reminders;
• review requests after completed work;
• alerts for failed integrations or overdue records.

Decisions that often still need a person

• whether a bespoke job is suitable;
• whether an event date is genuinely available;
• final pricing;
• exceptions to normal terms;
• complaint handling;
• sensitive or unusual enquiries;
• changes that affect scope, risk or delivery.

Service emails are not the same as marketing emails

A business can reply to an enquiry and send transactional messages needed to provide the requested service. That does not automatically give permission to add the person to a promotional email list.

The ICO explains that unsolicited marketing emails to individual subscribers generally require consent unless all conditions for a permitted soft opt-in are met. A separate, optional and unticked marketing choice is safer than hiding marketing permission inside a general enquiry form. See the ICO's electronic mail marketing guidance.

Automation rules should therefore distinguish between:

• replying to the requested enquiry;
• sending information necessary for an agreed booking;
• asking for a genuine post-service review;
• sending future promotional marketing.

Payments, invoices and deposits

A connected payment process should make the commercial status of the job obvious.

Define what confirms the booking

The business should decide whether confirmation occurs when:

• the quote is accepted;
• terms are accepted;
• the deposit is paid;
• the full amount is paid;
• a member of staff manually approves the request.

That rule should be reflected consistently in the website wording, email templates and CRM stages.

Keep payment status with the job

A booking card should show whether the deposit and final balance are:

• not requested;
• requested;
• due;
• overdue;
• paid;
• refunded;
• disputed.

The staff member handling the booking should not need access to a separate payment dashboard simply to know whether work is financially confirmed.

Do not use a normal enquiry form for card details

Card data should be handled through an appropriate payment provider. A hosted checkout reduces the amount of sensitive payment handling performed by the business's own website, although the business still has responsibilities for its overall payment setup and security.

Make terms visible before the customer commits

Online and distance-selling requirements can apply when consumers book services online. GOV.UK explains that businesses must provide specified information and, depending on the service and circumstances, cancellation rights may apply. See GOV.UK's online and distance selling guidance.

Deposit and cancellation terms also need to be fair. The Competition and Markets Authority's consumer guidance states that a business cannot keep any amount it chooses merely because a cancellation clause appears in the contract; charges need to be reasonable and linked to actual loss. See the CMA guidance on cancelling goods or services.

The correct position depends on the contract and type of service, so businesses should obtain legal advice rather than copying another company's terms.

Data protection, cookies and security

A website and CRM package processes personal information. The fact that software makes collection easy does not remove the business's responsibilities.

Identify the roles

The business using the CRM is usually the organisation deciding why and how customer information is used. The website or CRM provider may process that information on the business's behalf. The contract should explain:

• where data is hosted;
• which subprocessors are used;
• how data can be exported or deleted;
• how incidents are handled;
• what happens when the service ends;
• what security controls are available.

Provide a clear privacy notice

The ICO says a privacy notice should explain why personal data is processed, how long it is kept and who it is shared with, using clear and accessible language. See the ICO's guidance on privacy notices and cookies for small organisations.

A form should link to the privacy notice near the submit button. A vague footer link is better than nothing, but a short just-in-time explanation is clearer.

Collect only what is needed

Do not collect dates of birth, full home addresses, sensitive health information or identification documents unless the service genuinely requires them and the business has considered the legal basis, access controls and retention period.

Set retention rules

The ICO explains that personal data should not be kept longer than needed for the stated purpose. See its storage limitation guidance.

The business should decide how long it keeps:

• unsuccessful enquiries;
• customer records;
• booking documents;
• invoices and accounting records;
• marketing consent records;
• support messages.

Different categories may need different retention periods.

Handle cookies properly

Non-essential analytics, advertising and tracking technologies may require valid consent. The ICO says consent must be informed and involve an unambiguous positive action; simply mentioning cookies in a difficult-to-find privacy policy is not enough. See the ICO's cookies and similar technologies guidance.

The cookie banner should reflect the technologies actually used, not a generic list copied from another website.

Use practical security controls

At minimum, ask whether the package provides:

• HTTPS;
• secure account access;
• multi-factor authentication where available;
• role-based permissions;
• software updates;
• backups;
• activity logs;
• secure password-reset processes;
• incident support;
• data export.

The UK's National Cyber Security Centre provides a practical small organisations guide to cyber security covering account protection, backups, devices and scams.

The business should also remove access promptly when a staff member or contractor no longer needs it.

SEO and conversion requirements

A CRM cannot compensate for a website that attracts the wrong visitors or fails to persuade suitable customers to enquire.

Build a clear page structure

Important services should normally have their own useful pages. This helps customers understand the offer and gives search engines clearer information than a single page containing a short list of everything.

The page should answer:

• what the service is;
• who it is for;
• the problem it solves;
• what is included;
• how the process works;
• the area covered;
• what affects the price;
• why the business is credible;
• how to take the next step.

Use internal links deliberately

Google recommends crawlable links with descriptive anchor text that helps people and search engines understand the destination. See Google's link best practices.

Useful internal links from this topic cluster include:

• how to get more enquiries from your website;
• why small businesses miss leads;
• why fast replies help win more bookings;
• how to turn website visitors into paying customers.

Make the call to action match the decision

"Contact us" is acceptable but often weak. More specific actions include:

• Check availability;
• Request a quote;
• Book a consultation;
• Ask about your project;
• Send job details;
• See whether your date is free.

The form that follows must match the promise on the button.

Put proof near the decision point

Reviews, case studies, guarantees, qualifications and real photographs are most useful near the point where the customer is deciding whether to enquire. A separate testimonials page is less effective when no proof appears on the service page itself.

Keep performance under control

A CRM widget, scheduler, video gallery or chat tool can slow a page down. Google's Core Web Vitals measure aspects of loading, responsiveness and visual stability. See the overview of Core Web Vitals.

Use third-party scripts only when they earn their place. Test the public website independently from the CRM dashboard.

Add structured data accurately

Where relevant, LocalBusiness and Organisation structured data can help Google understand business details. Google explains that structured data must represent visible page content accurately and does not guarantee a rich result. See its guidance on LocalBusiness structured data and general structured data policies.

Do not mark up fake reviews, hidden content or services that the page does not actually describe.

How implementation should work

A reliable implementation starts with the business process, not the visual design.

Stage 1: Map the current process

Document:

• where enquiries arrive now;
• who responds;
• what information is normally missing;
• how prices are prepared;
• what confirms the booking;
• when invoices are issued;
• how deposits and balances are tracked;
• what gets forgotten;
• what the customer repeatedly asks.

This exposes the operational problem the package needs to solve.

Stage 2: Define the future workflow

Agree the exact stages, responsibilities and exceptions.

For every stage, define:

• entry condition;
• owner;
• required information;
• next action;
• automated message if any;
• exit condition.

For example, "Quote sent" should mean a dated quote was actually issued, not that someone intends to prepare one.

Stage 3: Plan website pages and forms

Map each important customer search or decision to a page. Then decide which form belongs on that page and which fields are required.

Do not build one enormous form to cover every service. Use service-specific fields or conditional sections where necessary.

Stage 4: Configure CRM records and pipeline

Set up:

• contact fields;
• enquiry fields;
• booking or job fields;
• pipeline stages;
• ownership rules;
• task rules;
• document templates;
• permissions;
• retention settings.

Use plain field names the business will understand.

Stage 5: Connect quotes, invoices and payments

Agree which system creates each document and where the authoritative financial record lives. Test tax, numbering, due dates, partial payments and refunds with the business's accountant or bookkeeper where relevant.

Stage 6: Write and approve messages

Prepare acknowledgements, reminders and booking emails. Check every message for:

• accurate promises;
• correct contact details;
• suitable tone;
• clear next step;
• correct legal or privacy wording;
• a fallback route when the customer needs help.

Stage 7: Test complete journeys

Testing should cover more than whether a button works.

Run realistic scenarios such as:

• a valid enquiry;
• missing required information;
• duplicate customer;
• spam submission;
• unavailable date;
• accepted quote;
• failed payment;
• part payment;
• cancellation;
• refund;
• mobile form submission;
• notification email failure;
• staff member with restricted permissions.

Test what the customer sees and what the business sees.

Stage 8: Train the users

The system will fail if nobody updates the pipeline. Training should cover:

• how to find new enquiries;
• how to reply and record notes;
• how to move a stage;
• how to issue a quote;
• how to confirm a booking;
• how to check payment status;
• how to close lost enquiries;
• what not to store.

Stage 9: Review after real use

The first month will expose fields that are unnecessary, messages that need clarification and stages that do not reflect reality. Schedule a post-launch review instead of treating launch as the end of the project.

How to compare suppliers and packages

A low headline price is not useful when the package excludes the work needed to make the system function.

Ask every supplier the following questions.

Website ownership

• Who owns the domain?
• Who owns the written content, design assets and photographs?
• Can the website be moved elsewhere?
• What happens if the monthly service ends?
• Are premium plugins, fonts or image licences transferable?

The domain should normally be registered in the client's name or under an arrangement that gives the client clear control.

CRM ownership and portability

• Can contacts, enquiries, bookings and invoices be exported?
• In what format?
• Are files and communication histories included?
• Is there an exit fee?
• How long is data retained after cancellation?

A CRM becomes operationally important. The business needs a credible exit route.

Scope

• How many services and pages are included?
• Is content planning included or is the client expected to provide finished copy?
• Are forms customised for the business?
• Are quotes, invoices and payment links included?
• Are automated emails included?
• Is calendar or accounting integration included?
• Is ongoing SEO included or only launch basics?

Yorkshire Digital separates a simpler website package from the full Professional website and CRM package, while the Growth package adds ongoing SEO work. That makes the operating scope clearer than calling every level "web design".

Support and maintenance

• Who handles hosting and software updates?
• What support channel is available?
• What response times apply?
• Are small content changes included?
• How are faults prioritised?
• Who monitors failed form submissions or integrations?

Security and resilience

• Is multi-factor authentication supported?
• Are backups taken and tested?
• How are staff permissions managed?
• How are vulnerabilities and software updates handled?
• What happens during a security incident?
• Where is data hosted?

Payment fees and third-party costs

• Are payment-processing fees separate?
• Are email, SMS, calendar or accounting integrations charged separately?
• Does the price rise when contact or email volume increases?
• Are domain renewal and premium-domain costs included?
• Are there setup, migration or cancellation fees?

SEO claims

No honest supplier can guarantee a number-one Google ranking. Google itself states that there is no way to request or pay for a better local ranking. Local results are mainly based on relevance, distance and prominence. See Google's local ranking guidance.

A credible supplier should explain the work it will perform, the pages it will improve and the measurements it will use rather than promise a fixed ranking.

Fit rather than feature count

Ask the supplier to demonstrate the exact journey for your business:

1. Submit a real test enquiry.
2. Show where it appears.
3. Show how it is assigned and replied to.
4. Create a quote.
5. Accept the quote.
6. Request a deposit.
7. Record the payment.
8. Show the outstanding balance.
9. Send a review request.
10. Export the record.

A working demonstration exposes gaps that a feature list can hide.

What to measure after launch

The goal is not merely more website traffic. It is a better path from suitable visitor to profitable customer.

Enquiry volume

Track total enquiries and break them down by:

• service;
• location;
• source;
• landing page;
• device where possible;
• new versus returning customer.

Enquiry quality

Record whether the enquiry was suitable. A page that generates many irrelevant enquiries may need clearer scope, location or pricing guidance.

Response time

Measure the time between submission and the first useful human response. An automatic acknowledgement is not the same as a real response.

The existing guide on why fast replies help win more bookings explains how to reduce delays without requiring someone to monitor a phone continuously.

Enquiry-to-quote rate

This shows whether the business is attracting appropriate customers and whether staff are progressing them.

Quote-to-booking rate

Review the rate by service, source and price band. Do not assume every lost quote is caused by price; delayed replies, unclear scope and missing proof also matter.

Deposit completion

Track how many accepted jobs reach the required payment stage and how long it takes.

Outstanding balances

Measure overdue value and average payment delay. The CRM should make financial follow-up visible before it becomes urgent.

Lost reasons

Use a short, consistent list such as:

• unavailable;
• outside area;
• budget mismatch;
• no response;
• chose competitor;
• unsuitable work;
• timescale mismatch;
• duplicate or spam.

Add notes where useful, but keep categories consistent enough to analyse.

Customer experience

Monitor common support questions, complaints, reschedules and reviews. A connected system should reduce confusion for the customer, not merely create a more detailed dashboard for the business.

Common mistakes

Buying software before mapping the process

The result is usually a generic CRM full of unused fields and unclear stages. Map the business first.

Treating the CRM as an email archive

A record of old messages is not a workflow. Every active enquiry needs a status, owner and next action.

Asking for too much information on the first form

Long forms can create friction and unnecessary data collection. Ask only what is needed to provide the next useful response.

Hiding the price and process completely

Not every business can publish an exact price, but customers need guidance. Explain starting points, packages or the factors that affect cost.

Automating promises that require human checks

Do not automatically tell a customer that a date is available, a job is accepted or a price is final unless the system has reliable rules and data to support that claim.

Using separate systems with no ownership rule

If the CRM, accounting tool, calendar and payment provider all contain different statuses, staff will not know which one is correct. Define the source of truth for each type of information.

Ignoring failed submissions

Forms and integrations can fail. Use logging, test submissions and a secondary alert route. A contact page that silently loses messages is worse than having no form at all.

Collecting marketing consent carelessly

An enquiry does not equal permission for unrelated promotional email. Keep service communication and marketing choices separate.

Forgetting the exit plan

Before launch, confirm how the business can export its website content, customer data and documents if it changes supplier.

The practical conclusion

A website and CRM package should create one understandable route from first visit to completed work:

Useful page -> relevant enquiry -> organised record -> timely reply -> clear quote -> confirmed booking -> invoice and payment -> follow-up -> review

The website attracts and reassures the customer. The CRM keeps the business from dropping the opportunity once the customer makes contact.

The strongest package is not the one with the most features. It is the one that reflects how the business really sells, delivers and gets paid, while remaining simple enough that staff will use it every day.