Jackson second brain call script
A practical script for the install call. Read the blue boxes out loud. Send the green boxes to Jackson. Keep this simple: Telegram first, capture first, behavior first.
Goal of this call
This is not a pitch. It is a setup call. The win is that Jackson knows what to text the agent, sends a few real messages, and leaves with simple nudges that make starting easier when motivation is low.
Read this first
Jackson, the goal is not to build you another app to manage. The goal is to give you a place to text messy stuff before you lose it. School notes, project ideas, links, reminders, tasks, random thoughts. You send it here first. Later you can ask for it back.
The second part is motivation. We are not going to rely on you feeling motivated. We are going to make useful things easier to start. That means tiny first steps, reminders at the right time, and small setup actions that reduce friction tomorrow.
The second part is motivation. We are not going to rely on you feeling motivated. We are going to make useful things easier to start. That means tiny first steps, reminders at the right time, and small setup actions that reduce friction tomorrow.
Do not over-explain
- No dashboard today.
- No NotebookLM today.
- No Notion sync today.
- No calendar integration today.
- Prove he texts it first.
Text block 1: first message for Jackson to send Hermes
Send this to Jackson and have him paste it into Telegram.
I want you to be my second brain for school, engineering projects, ideas, links, reminders, and small tasks. Motivation is one of my main issues, so do not rely on hype, guilt, or long pep talks. Use behavioral ideas instead: reduce friction, make the next action tiny, use timely nudges, help me set up my environment, and create tomorrow hooks so starting is easier. Help me capture things quickly, file them into simple buckets, remind me at useful times, and help me take tiny next actions. If I say something vague, ask one short follow-up question.
Text block 2: setup messages for Jackson to send Hermes
Send these after the first message. One block is fine.
Remember that I am using you as my second brain. My main buckets are School, Mechanical Engineering, Projects, Game Design, Watch Ideas, Links, Tasks, Reminders, and Parking Lot. Create a simple notes folder for me with those buckets. Keep it lightweight. Tell me where you saved it. Set up a morning nudge for 8:30 AM: ask me for one tiny win today and the first 5-minute action. If I sound unmotivated, make the task smaller instead of trying to motivate me. Set up an evening nudge for 9:30 PM: ask what I want to make easier tomorrow and suggest one friction-reducing setup action, like opening the right file, laying something out, charging a device, or blocking a distraction. Set up a Sunday 6 PM review: summarize my captures, tasks, reminders, open loops, and one friction fix for next week. Point out where motivation failed and suggest an easier environment or smaller starting step.
Read this after he sends the setup block
Don't treat this like Google. Treat it like a notebook that can text you back and do chores. Send messy thoughts. Ask for them later. If something matters, ask it to remind you. If something feels hard to start, ask it to make the first step smaller.
The point is not to become more motivated. The point is to make the useful thing easier to start when motivation is not there.
The point is not to become more motivated. The point is to make the useful thing easier to start when motivation is not there.
Have Jackson test these live
- Save one school thought.
- Save one engineering or project idea.
- Save one link or research item.
- Create one reminder.
- Ask it to make one avoided task easier to start.
Text block 3: examples Jackson can copy later
Save this idea: [rough idea here] What did I say about [topic]? Remind me tomorrow at 4 PM to open the CAD file. Turn these notes into a 10-question quiz: [paste notes] Break this into the next 3 tiny actions: [task] I keep avoiding this: [task]. Make it easier to start. Make a tomorrow hook for this: [thing I want to do].
If he says motivation is the problem
That is exactly why we are setting it up this way. If motivation is unreliable, we do not build a system that depends on motivation. We build one that lowers the effort. Smaller first step. Better timing. Less searching. Fewer decisions. More reminders when action is realistic.
If he asks why not build the full stack now
Because the first question is not whether we can build a powerful second brain. We can. The first question is whether you will actually use it. If you text it for a few days and it helps, then we add the heavier stuff: source packs, NotebookLM, calendar, dashboards, and deeper research workflows.
48-hour success check
- Jackson sends at least 10 captures.
- He asks for one old note and gets it back.
- He uses one reminder.
- He tries one tiny-start prompt.
- He uses one friction fix.
- He can explain what the agent is for in one sentence.
Close the call
For the next two days, do not use this perfectly. Just text it. Ideas, links, reminders, school stuff, random tasks, anything you might want later. If it makes capture and recall easier, we build on it. If it feels like another thing to manage, we cut it down.
Why this is designed around nudges and friction
- Thaler and Sunstein, Nudge: small changes in choice architecture can change behavior without forcing people.
- Behavioural Insights Team, EAST: people are more likely to act when the behavior is easy, attractive, social, and timely.
- Fogg Behavior Model: behavior happens when motivation, ability, and a prompt meet. When motivation is low, make the action easier.
- Gollwitzer, 1999: implementation intentions connect a situation to a specific action. That is the idea behind if-then plans and tomorrow hooks.
- Michie, van Stralen, and West, 2011: the COM-B model says behavior depends on capability, opportunity, and motivation.