IndustriesClient-based service businesses

CRM setup for client-based service businesses, from enquiry to final invoice

Each step of a client booking is simple: a reply, a proposal, a contract, a deposit, a questionnaire. Doing all of them by hand, for every client at a different stage, is where things slip. We set up Dubsado or HoneyBook so the steps happen on time, and you only step in where a person should.

Photographers, planners, designers, consultantsDubsado or HoneyBookFixed price, agreed up front

One client, enquiry to handoverExample

  1. Enquiry form submittedDay 0
  2. Reply with availability and a call linkDay 0
  3. Discovery callDay 3
  4. Proposal, contract and deposit togetherDay 4
  5. Questionnaire, timed to the project dateWeek 6
  6. Final payment and handoverMonth 4
Illustrative. Your client journey and timings are mapped in discovery.

Common starting situations

Where service businesses usually lose time and clients.

  • Copy-and-paste onboarding

    Every new client means retyping the same details from the enquiry into the proposal, the contract and the invoice.

  • Proposals that sit unsigned

    Nobody notices a proposal has gone quiet until the client mentions they've booked someone else.

  • Reminders after they've paid

    The automation keeps chasing a deposit or a signature that already came in, because nothing tells it to stop.

  • A workflow nobody dares touch

    It was built a few years ago, nobody is sure what half of it does, so the team quietly works around it.

  • Forms that ask the same question twice

    The enquiry form, the questionnaire and the contract each ask for the same address and date.

  • The final balance chased by hand

    Instalment and balance dates live in someone's calendar rather than in the system that sends the invoice.

Most of these don't come from the software. They come from a setup copied from a template, or built once and never revisited as the business changed.

How a client booking works

A client is won in days and served over months.

The enquiry needs speed. The booking needs paperwork that doesn't stall. The project needs the right thing sent at the right point before the date.

“Are you free, and roughly what does it cost?”

Hours

The enquiry

  • Automate: a prompt reply with availability or a pricing guide, a link to book a call, and the enquiry logged with its source
  • Keep human: the call that works out fit and scope
  • Usual failure: the reply goes out days later, after they've booked someone who answered first

“So what do I sign, and what do I pay?”

Weeks

The booking

  • Automate: a proposal, contract and deposit invoice sent together, with reminders that stop once each one is done
  • Keep human: tailoring the proposal, and answering the question that's actually holding them up
  • Usual failure: a proposal sits unsigned and nobody notices, or the reminders keep going after they've paid

“What happens next, and when?”

Months

The project

  • Automate: questionnaires and reminders timed to the project date, instalment and final invoices, and a review request after delivery
  • Keep human: the work itself, the judgement calls and the handover
  • Usual failure: a questionnaire goes out at the wrong time because it was timed from the wrong date

Most of the paperwork sits in the middle clock. Each step is simple on its own. Fifteen of them, across thirty clients at different stages, is where things go missing.

Where automation needs a person

Automate the sequence. Approve the exceptions.

In client-based work, the order of steps is predictable but the clients aren't. Your contract may be the same for everyone. The package, the date and the payment plan often aren't.

That's why fully automatic sending goes wrong: a client gets the wrong proposal, or a deposit reminder after they've paid. Both platforms allow checkpoints. In Dubsado, steps such as sending an email, form, contract or invoice can be set to wait for manual approval. HoneyBook automations can branch on conditions, and wait for a set time or a project event before moving on. So the useful question isn't what can be automated, but which steps should pause for a person.

  1. Automatic: the predictable steps

    Confirmations, reminders, tasks and status changes. They're the same for every client, so nobody needs to check them.

  2. Approved: anything client-specific

    Proposals, custom quotes and contract variations are prepared by the system, then a person checks them before they go out.

  3. Conditional: the chasers

    Reminders for an unsigned contract or an unpaid invoice that stop as soon as the client signs or pays.

  4. Owned: the exceptions

    A postponed date, a changed package, a refund. A named person handles it, and the client's workflow is paused or updated to match.

What we set up

What a service business CRM setup covers.

Your proposal lists which of these your project includes. What is possible depends on the platform and plan, which we confirm in discovery.

Client journey mapping

Your real process from enquiry to handover written down step by step, including the exceptions, before anything is built.

Process mapExceptions

Enquiry capture and first reply

Enquiry forms connected to your website, a prompt first reply, and a way to book a call, with the source of every enquiry recorded.

Lead formsFirst replyCall booking

Proposals, contracts and invoices

Packages and add-ons set up so a proposal, contract and first invoice can go out together, with the client's details filled in once.

PackagesContractsInvoices

Payment schedules and reminders

Deposits, instalments and final balances scheduled in the system, with reminders that stop once a payment arrives.

DepositsInstalmentsReminders

Questionnaires and onboarding

Questionnaires that ask for information once, sent at the right point before the project date, with an onboarding sequence for new clients.

QuestionnairesOnboarding

Workflows and automation

Dubsado flows or HoneyBook automations built around your journey, with approval steps and conditions where a person should check first.

FlowsApprovalsConditions

Templates and branding

Email templates and client-facing documents written in your voice and styled to match your brand.

EmailsDocumentsBranding

Scheduling and client portal

Booking links for calls and a client portal where clients can find their documents and invoices, where your platform supports it.

SchedulerPortal

Migration, training and handover

Clients and active projects moved where your current system allows, your team trained, and the setup documented so you own it.

MigrationTrainingDocs

Being clear about limits

What a better CRM won't fix.

A good setup makes the client journey consistent and visible. Some problems sit outside the software, and we would rather say so up front.

  1. 01A package that changes every time

    If every proposal is built from scratch, the workflow will keep breaking. Settling a small set of packages and add-ons usually helps more than any automation, and we'll say so before building.

  2. 02Pricing decisions

    We can make a proposal clear and easy to accept. Whether the price is right for the work is a business decision, and a better system won't make it for you.

  3. 03Capacity

    A smoother booking process can bring in more projects. It doesn't create more time to deliver them, so it's worth knowing how many you can take on first.

  4. 04Contract wording and terms

    We set up your contracts, payment schedules and policies in the platform. The wording, cancellation and refund terms are for you and your legal adviser to approve.

How it works

How a service business CRM project runs.

  1. 01

    Discovery

    Your packages, how clients find you, and every step from enquiry to handover as it happens today.

  2. 02

    Journey map

    Each step marked as automatic, approved, conditional or owned by a person, agreed before anything is built.

  3. 03

    Build and test

    Forms, documents, payments and workflows, then a sample client taken through every path.

  4. 04

    Handover

    Training, documentation of what was built and why, and optional support once you're live.

Before and after

What we need from you, and what you receive.

What we need

Confirmed during discovery

  • Admin access to Dubsado or HoneyBook, or your platform choice
  • Your packages, prices and payment terms
  • Your current contract, proposal and email templates
  • A walk-through of how you handle a client today
  • Your sign-off on contract wording and policies

At handover

Final scope set in your proposal

  • A documented client journey, from enquiry to handover
  • Proposals, contracts and invoices that fill in the right details
  • Payment schedules and reminders that stop when paid
  • Workflows with approval steps where they matter, tested
  • Templates in your voice, training and documentation

Questions

Service business CRM FAQs

Choosing and fixing a platform

Is Dubsado or HoneyBook better for a service business?

It depends on how you work. Dubsado gives you more building blocks and more control over forms, flows and branding, which suits businesses with a detailed or unusual process. HoneyBook offers a more guided setup with payments built in. If you already use one of them, fixing it is usually better than switching. Our Dubsado vs HoneyBook comparison goes through the differences in detail.

Can you fix our existing Dubsado or HoneyBook setup?

Yes. Common problems are workflows nobody understands any more, reminders that don't stop after a client pays, forms that ask for the same details twice, and old templates still in use. We map how you work today, fix what matters and document how the setup should be used.

Can you move our clients from another system?

Usually. Both platforms can import client and contact lists. We clean the data first and set up active projects so they continue where they left off. What can be moved depends on what your current system can export, which we confirm in discovery.

Proposals and automation

Can a proposal, contract and invoice go out together?

Yes, on both platforms. In Dubsado, a proposal can be bundled with a contract and an invoice. In HoneyBook, clients can choose services, sign the contract and pay from a single link. We set up your packages so the right details carry through to each document.

Will automation send the wrong thing to a client?

Not if it's designed with checkpoints. Dubsado lets steps such as sending a contract or invoice wait for manual approval, and HoneyBook automations can branch on conditions and wait for project events. We decide with you which steps run on their own and which should be checked first, then test every path with a sample client.

Will automated emails feel impersonal?

They shouldn't. Emails are written in your voice and reviewed with you before they go live. Automation handles the timing and reminders. The calls, the tailored proposals and the work itself stay with you.

Projects

How is a service business CRM project priced?

Every project starts with a discovery call. The proposal then sets out the deliverables, exclusions, milestones and a fixed project price. Platform subscriptions are paid directly to the platform and are separate from our fee.

Platform features checked against Dubsado's and HoneyBook's own pages in October 2026: Dubsado Help Center, Flow actions; HoneyBook Help Center, How to create an automation; HoneyBook, Proposal software; Dubsado Help Center, Bulk import a client list; HoneyBook Help Center, Add and import contacts. Platform names are trademarks of their owners. Sage Kite is an independent consultant and is not affiliated with, endorsed by or certified by the platforms listed.

Build a client journey that doesn't depend on you remembering it.

A discovery call looks at your packages, the platform you use, and where clients or payments slip through. We'll tell you plainly where we'd start.