What a CRM setup fee should include

A setup fee is not a delivery charge. It buys decisions: your stages, your fields, your automations, your numbers. Here is what should be in writing before you pay it.

The BittaFlow team

3 min read

On this page
  1. What you are actually buying
  2. The deliverables that should be listed
  3. Questions worth asking before you pay
  4. Red flags
  5. When to skip the setup fee
  6. The middle path that usually works
  7. How to judge the number
  8. What our onboarding actually covers

A setup fee is the most argued-about line on a software invoice, mostly because nobody defines what it buys.

If it buys “onboarding”, it is a delivery charge and it should be small. If it buys decisions about how your business runs, it is consulting and it is worth real money — but only if you can see what you are getting.

What you are actually buying

Three things, in order of value:

1. Decisions. Your stages, your required fields, your response windows, your definition of a lead. Someone has to make these, and a good setup makes them with you rather than for you.

2. Configuration. Those decisions turned into the system: pipelines, templates, automations, permissions, reports.

3. Transfer. Your existing contacts, notes and history, imported and de-duplicated, with a clear answer for what happens to the messy records.

If a proposal only promises the second and third, you are paying for data entry with a nicer name.

The deliverables that should be listed

Ask for these in writing. If a provider cannot list them, the fee is a guess.

  • A written record of your stages, with the entry and exit rule for each
  • The fields marked required, and why
  • The automations switched on at launch, named individually
  • The message templates, written and approved before launch
  • The import scope: how many records, which fields, how duplicates are handled
  • Who does what, with dates
  • Training: how many sessions, for whom, recorded or not
  • A defined end date and what “done” means
  • What happens after launch: support window, response time, cost of changes

Questions worth asking before you pay

“Which of my decisions will you make for me?” A good answer separates the parts that are standard from the parts that need your input.

“What do you need from me, and by when?” Setup projects fail on customer-side delays far more often than on the provider’s side. If they cannot tell you what they need, the timeline is fiction.

“What is not included?” The honest answer to this question tells you more than the whole proposal.

“What does a change cost after launch?” Small changes should be self-service. If every tweak is a ticket, the fee is really a retainer.

“Can I see the configuration before it goes live?” You should review it in a test state, not discover it on a Monday morning.

Red flags

  • A fee quoted before anyone has asked how your business works.
  • “Best practice configuration” with no questions about your stages.
  • Import described as “we will migrate your data” with no mention of duplicates.
  • Training counted in “sessions” without saying who attends.
  • No end date.
  • A setup fee that is large but a support contract that is larger, with no defined scope for either.

When to skip the setup fee

Sometimes the honest answer is: do it yourself.

  • Your team is small and the workflow is simple.
  • You have someone who enjoys configuration.
  • You are still deciding how the business should run — a setup would freeze a decision you have not made.

Most modern platforms let a competent office manager configure a basic pipeline in an afternoon. What you cannot easily do alone is the part that requires an outside view: questioning why a stage exists, or why a field is required.

The middle path that usually works

Pay for the decisions, not the clicking.

A short, fixed-scope engagement — two workshops, a written configuration plan, then your team implements with support — is often better value than a large done-for-you package. You keep the knowledge, and the system reflects how you actually work.

How to judge the number

Compare the fee against what the first month of a bad configuration costs: leads that fall through, reports nobody trusts, a team that quietly goes back to the spreadsheet.

If the fee is smaller than that, it is cheap. If it is larger, ask what specifically you are buying that you could not do yourself.

What our onboarding actually covers

Ours is scoped around the decisions, not the clicking: stages, response windows, templates, and the first automations, with your existing contacts imported and de-duplicated. Setup pricing lives on the pricing page because it depends on scope, and we would rather quote it after seeing the scope than before.

Whatever you buy, ask for the deliverables list above first. It is the quickest way to tell a real setup from a delivery charge.

Useful? Send it to someone who runs the phones.