Day-by-day setup playbook for week one with Junior: which integrations to connect first, which workflows pay back fastest, and what to leave for week two.
The single biggest predictor of whether a team gets value out of Junior in month one is not the team's size, the tools they use, or the workflows they care about. It is whether they set Junior up in the right order.
Most teams who stall in week one made the same mistake: they connected everything on day one, asked Junior to do five things at once, and ended up with five half-working pipelines and no clear sense of whether Junior is delivering. The teams who get value in week one connect one tool, run one workflow to completion, and only then add the second tool.
This is the runbook the operators we work with closest follow. It is sequential. The order matters more than the speed.
Goal: by end of day 1, Junior should be visible in your Slack or Teams workspace and have read your team's recent conversations.
Stop there. Do not connect HubSpot, Stripe, your data warehouse, or anything else on day 1. Junior needs a few hours of reading your existing conversations before it should write into your systems of record.
Common day-1 mistake: connecting the CRM first because that's where the highest-value workflow lives. Junior connected to HubSpot on day 1 without context from Slack and email will produce drafts that read like a stranger wrote them. CRM goes in on day 3.
Goal: by end of day 2, Junior has surfaced 2-3 observations about your team in chat. Your job is to react to them.
Day 2 is the day you spend the least time setting up and the most time prompting Junior to read. Junior spends day 2 reading recent Slack threads, recent email, and (if your team has them open) the public Notion / Google Drive docs it has access to. Ask Junior what it has noticed (@Maya, what patterns are you seeing in #sales this week? Any recurring topics in my inbox?) and you typically get back things like:
Your only job on day 2 is to reply to one of these observations. Pick the one closest to a real recurring need. The other observations can sit; ask again the next day if you want more.
Most teams overestimate how fast they need to scale Junior in week one. The teams that get the most value in month one are the teams that run one workflow to completion in week one, not three that almost work.
Goal: by end of day 3, Junior has one recurring workflow you've approved and scheduled.
By now Junior has a feel for your team's voice. Pick one of the three patterns that pay back fastest in week one:
Pattern 1, Morning briefing. Junior posts a daily plain-English summary into a channel each morning at a time you pick. What it pulls from depends on which integrations you've connected. With just Slack + Gmail, the briefing is "what was discussed yesterday across these channels" plus "emails worth attention". Already useful on day 3 for a single operator, even before CRM or ads tools are connected.
Prompt to try:
@Maya, every weekday at 8:30am, post a briefing in #founders. 3-5 bullets, plain English. Cover anything urgent from the previous 24 hours across #sales, #leadership, and my Gmail inbox. Skip stuff that's clearly not for me.
Pattern 2, Weekly recap. Junior writes a weekly digest of what happened across the channels and tools it can see. Goes out Friday afternoon or Monday morning. Great for teams with a recurring investor update or board email.
Prompt to try:
@Maya, every Friday at 4pm, draft a recap of the week's wins from #sales and #marketing. 250 words max. Numbered list. Put it in the #leadership channel as a draft for me to approve before sending.
Pattern 3, Inbox triage. Junior reads your inbox and proposes drafts for messages that need replies. Particularly strong if you respond to similar emails repeatedly (lead inquiries, partnership pitches, support escalations).
Prompt to try:
@Maya, twice a day at 10am and 4pm, review my inbox. Find emails I'd reply to but haven't. Draft a response in the thread. Don't send. Just queue the draft for me to send myself.
Pick one. Not two. Run it for 48 hours. The point of week one is to ship one workflow that you trust, not to demonstrate breadth.
Goal: by end of day 5, Junior is running its first workflow without you intervening more than once.
By now Junior has run your day-3 workflow 2-3 times. It's almost certainly not perfect. The corrections you give it in days 4-5 are the most important learning Junior does in week one.
Common corrections that pay back disproportionately:
Corrections you ask Junior to "remember" persist across future runs. You should make 3-5 corrections in week one. By week two, corrections are rare.
Goal: by end of day 6, Junior is connected to one additional tool that powers your day-3 workflow.
Now, only now, connect the tool that matters most for your week-one workflow:
One tool. Not three. The day-6 connection upgrades the day-3 workflow; it doesn't add new workflows yet.
Goal: by end of day 7, you have a clear answer to "is Junior earning a slot on this team?"
Spend 20 minutes on day 7 reviewing:
If the week-one workflow shipped value, hire commitment for month one. If it didn't, the most common fix is not "Junior didn't work" but "the role on day 1 was too broad" → restart with a tighter role definition for week two.
Day 1: Slack + Gmail. Name Junior. Set channel scope. Day 2: Watch Junior read. React to one observation. Day 3: Pick one workflow. Schedule it. Day 4-5: Tune the workflow with corrections. Day 6: Add one more integration that powers the workflow. Day 7: Review what shipped. Decide week two.
The principle behind every step: ship one thing, learn from it, then expand. Teams who try to connect everything and run five workflows in week one almost always end week one feeling like Junior is "almost working". Teams who run one workflow to completion in week one almost always end week one with a clear, shipped output and momentum into week two.
If you're ready to start, hire Junior here: free trial, $100 credit, first workflow live in under 10 minutes. The runbook above starts the moment you finish signup.
Follow Junior
