The repetitive half runs itself.
Client onboarding software and a client portal, built around how you deliver.
What you can do in Delivery
- Build the journey once: Stages, tasks and rules live on the service. Every take-on gets its own plan from it.
- Rules do the routine: Send a notice, move the stage or raise a draft invoice. Every run is logged, none runs twice.
- A hub your client can use: Tasks, files, sign-off, messages and invoices on a branded link. Reveal stages by date.
- Cohorts, if you teach: Rosters, gradebook, schedule, verifiable certificates and application tracking.
Pacten AI in Delivery
- Work: Keeps tasks moving and prepares changes for you, from grading to attendance.
- Never without your yes: Reassign or close a task.
How Delivery connects
- CRM: Take them on from the client’s record.
- Booking: The service holds the journey, and a booking opens the work.
- Contracts & Docs: A signed contract can start the work.
- Finance: Rules raise a draft invoice, always for review.
Frequently asked questions
- Planner or Delivery?
- Planner runs your team’s projects and time. Delivery runs the same process for every client, and they can see it.
- Can it start something when a client pays?
- Not yet. A paid invoice isn’t a rule trigger.
- Can a rule send an invoice by itself?
- No. It’s always a draft for you to check.
- Can steps depend on answers?
- Rules can check conditions, and all of them must match. There are no branching paths.
- Do clients need a login?
- They use a private link, with a code.