Skip to content
PROOF48
All answers
automation

What actually happens automatically in the first week of a new client

In the first week of a new client, automation can send the confirmation, collect their details through one form, offer a time to start, remind them if they go quiet and tell you to check in on day seven. The welcome call stays human. PROOF48 would build the flow as a custom automation, on AUTOMATE or priced on request.

Founder, PROOF48Updated 2026-10-295 min read

01One event starts the week

Onboarding a client starts the moment they say yes: they pay, sign, book the first appointment or accept a quote. That one event is the trigger, and everything else hangs off it. Within minutes the client gets a confirmation that says what happens next in plain steps, a record is created for them in your CRM, and you or whoever owns the client gets a task. Without a trigger, the first week depends on someone remembering, and the weeks when you are busiest are the weeks the new client hears nothing. Put the trigger where the yes happens, because a trigger that someone has to press by hand is a to-do item, not automation.

  • Trigger: payment, signature, first booking or an accepted quote
  • Within minutes: a confirmation with the next steps in plain words
  • A client record is created, with the source and the service bought
  • A named owner for the client, who gets a task

02Day by day: what runs and what stays with you

A first week for a service client can look like this. Day 0: the confirmation, a short form for the details you need (one form, not three emails of questions) and a link to book the first call or appointment. Day 1 or 2: if the form is still empty, one reminder. Day 3: a short message saying what to expect and who to contact. Day 7: one question by email, such as what is still unclear, and a note to you if the answer is a problem or there is no answer. That is four messages. The welcome call, the first delivery, any answer to a worry and any change to price or scope stay with a person. We would cap the week at about four messages. That is our habit, not a measured limit.

  • Day 0: the confirmation, one details form, a link to book the first call
  • Day 1 or 2: one reminder if the form is empty
  • Day 3: what to expect and who to contact
  • Day 7: one question by email, and a flag to you if the answer is a problem or silence
  • Stays human: the welcome call, the first delivery, worries, price and scope

03Rules that keep it from feeling cold

Stop the sequence the moment a person replies. If the client answers a reminder, the next automatic message should never arrive as if nobody had read it. Ask one thing per message. Name something true about this client, such as the service bought or the date of the first appointment, instead of 'thanks for choosing us'. Write the messages yourself and read them the way the client will. Our post on follow-up messages that do not feel robotic goes through the same rules for the messages after an order. A client forms a view of how you work in the first week, so the messages should sound like you.

  • Stop the sequence when a person replies
  • One question per message
  • Name something true about this client
  • Write the messages in your own voice

04What PROOF48 does here, and where it is the wrong choice

This post is about customers, not staff; for new hires see our post on HR onboarding automation. No PROOF48 plan lists customer onboarding as a feature. The AUTOMATE plan, 2,997 EUR a month, lists an AI website chatbot that qualifies and books, AI DM and email auto-responders, booking automation with a CRM and two custom automations a month. A flow with a trigger, a form, reminders and a check-in would be a custom automation, scoped from how you take on clients today, and a single flow takes one to two weeks from mapping to production, per our automation page. Without the plan, a single build is scoped and priced on request through the start page. AUTOMATE does not cover WhatsApp or phone, so a welcome sequence that runs there is not what the plan sells. If you take on a few clients a month, a form and a scheduled email sequence in tools you already use may do the whole job, and a custom build would cost more to keep running than the sequence saves.

  • No plan lists customer onboarding; the flow is a custom automation, scoped from your current process
  • AUTOMATE: 2,997 EUR a month, DM and email auto-responders, booking automation with CRM, no WhatsApp, no phone
  • A single flow: one to two weeks from mapping to production
  • A few new clients a month: a form and a scheduled email sequence may be enough
From a build we shipped

No PROOF48 build is a client onboarding flow

None of our eight written-up builds is a client onboarding sequence, and we will not stretch one to fit. The closest piece is small: Rotiseria Baba Novac sends an order confirmation email on every order, through Resend, and gives the customer order tracking. That is one confirmation, not a week, and this build does not cover client onboarding. We have not measured how much time an onboarding sequence saves a small business and we quote no figure.

See the build: Rotiseria Baba Novac

Questions, answered

What can be automated in a new client's first week?

The confirmation, a details form, a link to book the first call, reminders if the form stays empty, a check-in question on day seven and the client record. The welcome call and any answer to a worry stay with a person.

Is this the same as HR onboarding?

No. This is about customers who have just said yes. Onboarding new staff has its own steps, covered in our post on HR onboarding automation for a small team.

Does the AUTOMATE plan include customer onboarding?

No plan lists it. AUTOMATE, 2,997 EUR a month, lists DM and email auto-responders, booking automation with a CRM and two custom automations a month. An onboarding flow would be a custom automation, and whether it fits inside those two is a scoping question.

How long does it take to build?

Per our automation page, a single flow takes one to two weeks from mapping to production. The mapping of how you take on clients today is the most important part.

Where PROOF48 fits

Automate the trigger, the confirmation, the details form, the reminders and the day-seven check-in. Keep the welcome, the first delivery and every worry with a person, and stop the sequence the moment someone replies. PROOF48 would build the flow as a custom automation, no plan lists it, and AUTOMATE does not cover WhatsApp or phone.

· Founder, PROOF48

Cosmin has worked in online marketing and software development since 2018, and has built with AI every day since January 2023. He still writes code from scratch daily, in Python, React, Rust and C#. PROOF48 ships business websites in 48 hours and invoices afterwards, so every opinion on this blog was paid for in real builds, not in theory.

Related articles

automation

What HR onboarding automation actually looks like for a five-person business

HR onboarding automation for a five-person business means one trigger, one checklist and a few timed messages: when someone accepts the job, the document request, the welcome email, the account setup tasks and the first-week check-ins start on their own. A shared checklist often does most of it.

Read it
ai

How to automate follow-up messages without sounding like a robot

A follow-up message avoids sounding robotic when it names something specific and true about that exact customer's action, a pickup time, an order number, a batch that just landed, rather than a generic "thanks for your order" that could apply to anyone. The trigger can be fully automated; the content still has to reference the real, specific event.

Read it
automation

How booking automation actually removes back-and-forth messages

Booking automation replaces the message chain of 'are you free Tuesday, what about 3pm, actually Wednesday works better' with a calendar the customer books directly, that then confirms itself, blocks the slot and reminds both sides before the appointment. The business sees a filled calendar instead of a phone that will not stop buzzing, and the customer books in under a minute instead of waiting for a reply.

Read it
automation

How to actually map a process before you try to automate it

To map a process, follow one real case from the trigger to the finished result and write down each step, who does it, which tool it touches and what happens when it goes wrong. If the map fits on one page and a newcomer can follow it, the process is ready.

Read it