Two-week builder plan

The workspace currently records that Collins was released on July 18 and that his remaining tasks should be cancelled. Akash now wants Collins to execute the builder vision. This plan treats Collins as the preferred candidate, not as an active employee.

• Akash explicitly decides whether Collins is being rehired.
• If yes, Akash communicates the role, trial length, pay, expected hours, and success measures directly.
• Only after that decision should Collins receive live assignments or restored access.

★ Akash should not write the task list, debug the implementation, or design another dashboard. His brief should explain the destination, the user experience, the guardrails, and the proof required.

1. Establish the Builder operating system and daily huddle.
   • Verify the existing GitHub, Cloud Coworker, workspace, and communication access. Restore only what the confirmed role requires.
   • Use one branch or isolated work area per assignment.
   • Use one written vision brief, one owner, one completion test, and one rollback plan per project.
   • Run a fifteen-minute daily huddle and a short end-of-day handoff.
   Done when: the Builder can receive one brief, find the correct system, ship a tested change, and hand back proof without Akash directing every step.
2. Build the SDR recruiting and onboarding system.
   • Create the role scorecard, job post, application questions, candidate tracker, interview guide, and live audition.
   • Turn Akash’s pitch practice into reusable training: offer lesson, script walkthrough, objection examples, quizzes, role-play prompts, and certification tests.
   • Create a first-day checklist and a supervised ten-account pilot.
   • Use the Sales Command Center for daily outcomes. Do not create another sales dashboard.
   Done when: Akash can send a candidate one onboarding link and receive a clear pass, retrain, or reject result.
3. Automate the approved sales communication before and after calls.
   • Before the call, send the approved preparation message, day-before confirmation, and respectful no-show sequence.
   • After the call, use the recorded outcome to schedule the correct approved follow-up.
   • Attach the recording, transcript, summary, commitments, and next date to the correct person.
   • Automatic messages must use approved wording. New or unusual replies receive a draft for human review.
   Done when: one safe test booking receives the correct preparation, recording, outcome, and follow-up without manual copying between systems.
4. Create a daily creative-production pilot.
   • Use the existing proven visual rules, research library, and performance data to prepare one reviewable creative package each workday.
   • Each package includes the idea, audience, words, image or video, destination, and reason it deserves a test.
   • The Meta dashboard is the source for performance. Do not create a separate creative-results dashboard.
   • The pilot prepares work in a paused or draft state. It does not publish ads or spend money automatically.
   Done when: the system creates five consecutive daily packages that pass the visual check and are ready for one-click human approval.
5. Turn the Dallas launch into repeatable client onboarding.
   • Complete the Level King Pro Facebook page, local ad, account ownership, lead routing, customer list, advertising measurement, and launch checks.
   • Use one concrete-leveling ad as the first proof. Do not build a large client creative factory yet.
   • Send every live test only to Akash’s owned test phone ending 5477.
   • Convert the finished work into a reusable checklist for the next contractor.
   Done when: one Dallas ad can produce a test lead, route it correctly, start approved follow-up, and show the result in the existing dashboards.

Day 1: confirm the role and prove access

• Akash confirms whether Collins is the Builder.
• The Builder verifies GitHub, Cloud Coworker, the workspace, Slack, and the existing dashboards.
• The Builder ships one harmless test change through the full branch, review, proof, and handoff process.

Days 2–3: ship the SDR recruiting and onboarding package

• Build the job post, applicant screen, interview, audition, training, quizzes, certification, and first-day checklist.
• Use Akash’s sales war room, discovery script, objection practice, and pitch quizzes as the source material.
• Give Akash one link and one candidate decision sheet.

Days 4–5: prove pre-call and post-call automation

• Map the approved messages to the fifteen-step sales process.
• Test booking preparation, confirmation, no-show handling, call recording, transcript, outcome, and follow-up.
• Use only Akash-controlled test information.

Days 6–8: run the creative-production pilot

• Prepare one paused creative package per workday.
• Check that each image or video includes the required visual elements, not only the correct words.
• Compare the work with the highest-spend ads first, because that is where the platform chose to deliver.
• Submit one compact daily approval card instead of a folder of unexplained files.

Days 9–10: run Dallas through the onboarding checklist

• Complete the page, one ad, routing, measurement, follow-up, and controlled test.
• Capture every missing input that required Akash and convert it into the next client’s intake form.
• Hand back a reusable checklist and a short “how to launch the next client” guide.

The huddle is not a tour of files, a coding lesson, or a brainstorming session. Unblocked implementation belongs to the Builder.

1. Who is this for? Name the salesperson, prospect, client, or operator.
2. What is frustrating today? Describe the real moment that fails.
3. What should the future feel like? Tell the story from the user’s point of view.
4. What must already exist? Link the current dashboard, script, page, or workflow.
5. What must never happen? State safety, spending, sending, and data boundaries.
6. What proves completion? Give one visible pass-or-fail test.
7. What is the deadline? Name the date and the cost of missing it.

• Do not create another command center, Meta dashboard, sales dashboard, or task board.
• Do not begin all four engines at once. Finish the working slice before opening the next one.
• Do not publish ads, spend money, contact humans as Akash, or change account permissions without the required human decision.
• Do not automate newly generated sales messages directly to prospects. Approved scripted messages may run; unusual replies stay human-reviewed.
• Do not build a large client creative factory around one concrete-leveling ad. Prove the single-ad onboarding path first.
• Do not reopen retired Collins tasks. Create fresh assignments against the new role if the rehire is confirmed.