Plan@Job lets an operator hire AI colleagues for specific parts of project administration. Sophie Bennett helps get existing job briefs ready to price. Daniel Reed supports subcontractor coordination. Maya Collins prepares financial actions for review. Each role has a defined remit and an activity record; your business remains responsible for the decisions and delivery.
An operator is the contractor business managing the work. It serves clients, coordinates subcontractors and may also have in-house operatives. The AI team works within that business's account, using the supported workflows and supervision settings.
Hire the colleague that fits the bottleneck
Start with the administrative task that repeatedly interrupts your day. If the job is too vague to price, look at Sophie. If you are chasing outstanding prices and proposed dates, look at Daniel. If deposits and overdue invoices need attention, look at Maya.
- Sophie, AI Enquiries Coordinator: checks existing job information, asks for missing details and hands unresolved questions back after two attempts.
- Daniel, AI Operations Manager: supports eligible sharing within the existing vetted subcontractor network, quote follow-ups, proposed-date follow-ups and a morning brief.
- Maya, AI Finance Coordinator: prepares deposit actions and follow-ups for unpaid deposits or overdue invoices. Financial actions require approval.
These are different jobs, not three names for the same chatbot. Their work depends on the information and prerequisites available in your account.
What supervision looks like
Open the AI staff workspace in your operator account. Choose a colleague, appoint a supervisor and review its settings before putting it on duty. Your account permissions determine who can configure staff.
Enquiries and Operations can use instructions about writing style within their existing permissions. Finance follows fixed financial rules. Changing a text instruction does not give a colleague the right to set prices or move money.
The activity history distinguishes completed, proposed and failed work. An approval request is a decision for the responsible person, not proof that an action has already happened. Quiet hours, job eligibility and operating limits can also prevent or delay an action.
An example across one project
Consider a fictional bathroom refurbishment. Sophie helps gather the missing scope details. The operator organises the work and decides how to approach subcontractors. Daniel can help follow up on eligible outstanding prices or ask an awarded subcontractor for proposed dates. Once the acceptance and agreed-price conditions are met, Maya can prepare the deposit action for review.
The operator still chooses the commercial offer, makes the award and confirms the commitments. The example describes the roles; it is not a customer performance claim or a promise that every project automatically passes through every step.
AI staff, Ask Plan@Job and your own AI
AI staff are configured background roles. Ask Plan@Job is the conversational assistant you use when you want to inspect work or request a supported action. The MCP connection is a separate route for a compatible external AI client. A customer's external AI subscription does not power the hosted staff.
Common questions
What does hiring cost?
Account access follows your operator agreement. Review current access and usage arrangements during onboarding and in your account. The staff workspace shows usage for the month; this guide does not introduce separate prices for the three roles.
Does Auto remove the need for approval?
No. Routine actions and commercial commitments have different controls. Awards, prices and financial commitments remain subject to their approval rules.
Where should I start?
Meet the AI team, pick one recurring bottleneck and configure the colleague that fits it. If you already have a contractor account, that is your operator account; you do not need another one.