Build a 30-60-90 onboarding plan with first-week schedule, milestones, owners, and check-ins.
The English summary is being prepared. Showing the original description.
Run score Not tested
See how to installReview the instructions the agent will receive before you install.
Use this once a start date and manager are confirmed.
Ask for the role description, what the person must own by day 90, the manager, a buddy, the teams they will work with, and the tools they need. Turn the day-90 goal into a 30-day and 60-day step. If the goal is vague, ask the manager for one outcome that would show the hire is settled.
Give every item an owner and a date. Keep week one about access and people, not output.
Set check-ins at the end of week one, day 30, day 60, and day 90, with three questions for each: what is going well, what is blocking, and what help is needed.
Never add personal details the manager did not share. Do not send the plan, book meetings, or create accounts yourself; the manager approves and runs it.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Use when a support account wobbles or a quarterly business review looms: read the health signals, run the success plan, and prep the review from evidence.
The English summary is being prepared. Showing the original description.
Reconcile accounts by comparing GL balances to subledgers, bank statements, or third-party data. Use when performing bank reconciliations, GL-to-subledger recs, intercompany reconciliations, or identifying and categorizing reconciling items.
The English summary is being prepared. Showing the original description.
Review open receivables and draft factual, staged payment follow-ups without inventing status or contacting a customer.
The English summary is being prepared. Showing the original description.
Write ad variants that each test one idea, within platform limits and supported claims.
The English summary is being prepared. Showing the original description.
Use on the first conversation with Alex, or whenever their memory has no product preferences yet: learn what the user is building and who for, where specs, roadmap and numbers live, who decides dates and scope, and get them to a first real product deliverable.
The English summary is being prepared. Showing the original description.
Use when a strategic alliance needs joint selling governance: operating model, joint targeting, steering prep, and milestone accountability.
The English summary is being prepared. Showing the original description.