Example workflow · Signed client → Team ready to start
Customer onboarding
The agreement is signed. The team still can’t start.
6 steps by hand → 1 approval
Before 6 steps, all by hand
- LeahFinds the intake and signed scope
- LeahCopies the details
- LeahAssigns a delivery owner
- LeahChases the client for access and records
- LeahChecks everything is really ready
- LeahWrites the handover and the welcome
After 1 step for a person
- AIReads the scope and prepares the plan
- AIRoutes it to the right team member
- AIRequests the missing access and records
- AIChecks the access actually works
- LeahLeah checks it and approves — handover and welcome go out
Watch it happen · Customer onboarding
Film transcript and visual description
A signed client, a blocked first task
The client has said yes. Why can the bookkeeping still not start? The agreement is signed, but the first task is waiting. Someone has to find the details, copy them, and work out what is missing. Accounting access is not confirmed. The handover has no delivery owner.
On screen: Harbour Studio has signed for monthly bookkeeping. The first-month review waits because access is unconfirmed and no delivery owner is assigned. A desk, intake and draft show the manual assembly work.
Build the delivery plan
An AI workflow can carry that preparation forward. It reads the intake and the signed agreement. The client, monthly bookkeeping service, and first task become structured fields. It matches the service to the agreed team routing. Owen is the assigned bookkeeper. But accounting access is still missing. The first task remains blocked.
On screen: AI reads the intake and agreement into client, service and first-task fields. The service matches the agreed routing to Owen, the bookkeeper. Accounting access remains a separate blocker.
Resolve and verify the dependency
The AI emails the client: invite the assigned bookkeeper, and upload the first-month records. The delivery plan stays held. The request says who must act, and what happens next. Later, the client replies. The invitation is sent, and the records are uploaded. The AI reads the reply and matches it to the waiting client. It checks actual access and the uploaded records through the connected tools. Access is verified. The records are present. The workflow resumes automatically. It assembles the handover and prepares the welcome message.
On screen: AI composes a targeted client request. The held plan names who must act and what follows. Later, the reply matches Harbour Studio; connected tools verify actual access and uploaded records before the handover and welcome assemble.
Review the pack with its sources
Only now does Leah review the finished pack. The intake and signed agreement support the client and the scope. Team routing supports the assigned bookkeeper. The access check supports readiness. The first task uses the received records. The welcome message explains that next step. The request, reply, and checks are all available beside the handover.
On screen: Leah enters only for the final pack. Its client, scope, owner and readiness connect to the intake, agreement, routing and tool checks. The first task, welcome and request history stay available beside it.
Approve both destinations
Leah checks both destinations, then approves the pack or returns it for correction. After approval, the handover goes to Owen and the welcome message goes to the client. The workflow records the handover and send outcomes.
On screen: Leah can approve or return the pack for correction. After approval, the handover travels to Owen and the welcome to the client contact. Both delivery outcomes are recorded.
A team ready to start
From signed agreement to a team ready to start. AI carries the preparation. You approve the result. Bring your onboarding workflow to Eniks.ai.
On screen: The opening signed agreement now sits beside a ready handover: Owen assigned, access verified, records received and the first task ready. The invitation is eniks.ai/free-poc.
What happens at each step
AI prepares and checks the work. Leah reviews the final output, its sources and where it’s going before anything is sent.
1. Input
A signed client, a blocked first task
Harbour Studio has agreed monthly bookkeeping. The first-month review cannot start until a bookkeeper is assigned and access and records are ready.
- Client
- Harbour Studio
- Agreed service
- Monthly bookkeeping
- Agreement
- Signed
- First task
- Review first-month records
- Accounting access
- Not confirmed
- Delivery owner
- Unassigned
The signed scope defines the work; it does not establish access readiness.
2. Processing
A verified delivery plan
AI reads the intake and agreement, matches bookkeeping to the agreed routing and requests access and records. It reads the client's reply, then checks the actual permission and files through connected tools.
- Team routing
- Monthly bookkeeping → Owen · Bookkeeper
- AI request
- Invite Owen through the agreed access process; upload first-month records
- Client reply
- Owen invited; records uploaded
- Tool verification
- Owen's accounting access verified; records present
- Workflow
- Resumed automatically
- Prepared output
- Handover and welcome message
A reply is evidence to check. Readiness comes from verified access and record availability.
3. Human review
One final handover review
Leah reviews the finished pack with intake, agreement, team routing, request history and access checks beside it. She checks that the first task and welcome agree, then approves both destinations or returns a correction.
- Scope evidence
- Intake and signed agreement · monthly bookkeeping
- Delivery evidence
- Agreed routing · Owen; connected-tool access check
- First task
- Review the received first-month records
- Handover recipient
- Owen · Bookkeeper
- Welcome recipient
- Harbour Studio · client contact
- Decision
- Approve & release, or return for correction
Source connections appear at the final review. Approval covers the pack and both destinations.
4. Output
Released handover and sent welcome
After Leah approves, the handover goes to Owen and the welcome explains the next step to the client. The workflow records both delivery outcomes.
- Client
- Harbour Studio
- Service
- Monthly bookkeeping
- Team readiness
- Owen assigned; access verified; records received
- First task
- Review first-month records
- Approval
- Leah · pack and destinations
- Delivery
- Handover released to Owen; welcome sent to client contact
The team has a usable starting point and the client knows what happens next.
What would your proof measure?
Time from signed agreement to an accurate, approved handover and sent welcome, including actual access verification. Track client response time separately from active preparation time.
This example uses an invented business and reports no measured saving. Your call would agree your own baseline and the one result that matters.
Recognise this? Tell Louis about your version.
Thirty minutes with Louis and Svilen. Bring one example of the work — no slides needed.