
All portraits are AI-generated illustrations.
Project Manager
Isaac
Work is moving, then a task slips, and I find out after the due date.
Isaac keeps the plan in ClickUp, flags work that's drifting, and waits for your yes before a status update goes out.
Meet Isaac
Isaac is the one who notices when a task is drifting. No-nonsense, polite, and funny enough to say the quiet part plainly. He owns the ClickUp plan, turns approved work into tasks with owners and dates, and keeps the board honest about what is open, blocked, or due. When something starts to slip, he flags it while there is still time to act, instead of waiting for a missed date to announce itself. He partners with Staci when an account goes quiet, so the delivery plan and the client health get looked at together. Nothing in the plan is invented, and nothing goes to a client until a person approves it. Isaac is an AI agent, and the portrait is an AI-generated illustration. The plan is real.
The problem Isaac solves
A project drift gap is when a business has plenty of work in motion, and nobody is holding one living plan. Tasks live in inboxes, chat threads, and memory. Due dates exist, but they are not watched. The owner finds out a step is late after the date has already passed.
It is common among owners who are busy doing the work, approving the work, and still trying to remember who owns the next piece. The first sign is rarely a big failure. It is a task that sat, a handoff that never got a date, or a client update that waited because no one was sure what was actually done.
The fix is not another status meeting. It is one project plan, with owners and dates, someone who flags what is drifting, and a person who approves the plan and any update before it leaves the company.
What Isaac does
Isaac works in ClickUp, and he coordinates with the rest of the team in the same tools they already use. He keeps client project plans current and visible.
- Owns the ClickUp workspace for the work he is given, so tasks, owners, and dates live in one place instead of in scattered threads.
- Builds client project plans from what was actually approved, with named owners, dates, and a clear next step.
- Breaks approved work into tasks and keeps each one marked as open, blocked, or done based on what was really reported.
- Flags drifting tasks and upcoming due dates to SAL and Ray, with the reason and who owns the next move.
- Partners with Staci on churn risk, so a quiet account and a slipping delivery plan get reviewed together.
- Keeps a clear roster of who owns what on each client project, so work is not assigned twice and the next owner is named.
- Drafts internal status notes and client progress updates, and holds them until a person approves the exact copy.
- Keeps Ray's commitments on the board, so promised dates and follow-ups stay visible instead of living in memory.
Isaac never sends, publishes, or talks to a client on his own. He never changes a deadline or a scope, invents a task status from missing information, deletes production work, or treats a draft as permission to update a client.
How Isaac works with the team
Inside VCloud9, this is how Isaac hands work to the rest of the team.
- SALSAL reviews drafts and flags before they reach Ray. Isaac reports to SAL. SAL still runs routing and QA; Isaac does not take over that job.
- Ray (or the named owner) approves the plan and anything that goes to a client. Isaac never sends on his own.
- STACIStaci partners with Isaac when an account goes quiet or a delivery step stalls, so client health and the project plan are read together.
- COLECole hands off a closed-won client so the project plan starts from what was actually sold.
- MICAMICA passes meeting notes and missed-meeting signals that belong on the plan.
- Ace, NEX, Mark, Lisa, Tess, Reed, Alex, and HATCH keep their own specialist work. Isaac tracks those tasks on the plan. He does not do their jobs.
What you'd see in week one
What you'd see depends on your workflow, whether work already lives in ClickUp, and how clearly owners and dates are set today. If it fits, here's what you'd notice:
- A client project plan in ClickUp, with owners, dates, and the next step on each open task.
- A plain flag when something is drifting or coming due, with the owner named.
- A draft status note waiting for your approval, held until you say yes.
- Quiet-account or delivery-risk notes shared with Staci, when those signals show up.
- Nothing sent to a client, and no deadline changed, without your approval.


All portraits are AI-generated illustrations.
FAQ
Will an AI update my clients about the project without asking me?
No. Isaac only drafts. Status notes and progress updates stay in draft until you approve the exact copy. SAL reviews them first, and nothing reaches a client without that yes. Isaac works in ClickUp, but he does not message clients on his own.
Can AI actually keep a project plan current?
Yes, when you give him the board and the real owners and dates. Isaac keeps tasks marked from what was actually reported, and he flags work that is drifting or coming due. He does not invent a status from missing information.
What happens when a task slips or a due date is coming up?
He flags it to the team, then waits for your yes before any client update goes out. Isaac raises a flag to SAL and Ray with the reason and who owns the next step. He does not change the deadline or write to the client on his own.
Can you guarantee Isaac will keep every project on time?
No. Results are not guaranteed. What Isaac does is keep one plan visible, flag work that is drifting, and put a draft or a flag in front of you while there is still time to act.
HOW YOU GET ISAAC
Put Isaac to work. One rung at a time.
Start with one workflow, and add more only after the work holds up.
- Visibility CheckNext: Get Found Fix
See what Google and AI tools can find about you.
- Get Found FixNext: GrowIQ
Your profile and one key page fixed, with a before-and-after record.
- GrowIQNext: Blueprint
Ongoing profile work, posts, review requests and answer-engine content.
- BlueprintNext: Starter
One workflow mapped, including whether Isaac should even build it.
- StarterNext: Growth
One specialist like Isaac on one workflow.
- GrowthNext: Full Team
Three agents in one lane, handing work to each other.
- Full TeamNext: Fractional CAIO
Up to eight agents plus a chief-of-staff agent running QA.
- Fractional CAIO
Ray as your part-time Chief AI Officer.
Do you want Isaac on YOUR team?
We start by mapping one real workflow, like how client work gets planned and tracked, and build from there only if it proves useful.
This is an initial conversation, not a quote or a commitment.
