DAY 1 · 16 SEPTEMBER 2026
How to be an Octopus
Day 1 at Casablanca AI Lab, 16 September 2026. An Octopus is a creative technologist, builder, and client-facing problem solver. The mission is simple: find meaningful client pain, turn it into an innovative prototype, validate it with the client within two weeks, and prepare it for the Wolf to deliver.
The role
An Octopus is not a conventional job title. It is a role for people who can move between technology, clients, industries, and ideas without losing sight of the problem that matters. They connect ideas across different contexts, turn unclear pain into a concrete opportunity, and build something the client can react to quickly.
Five strengths
Speed
Move quickly from conversation to prototype. Speed creates momentum, gives the client something concrete to respond to, and exposes wrong assumptions early.
Two-week field guide
From first conversation to a delivery-ready handoff. Nine steps. Two weeks.
01
Prepare for the client
Learn the business, tools, and likely pressures before the meeting. Find relevant DaiL work and configure the harness so it can take notes, retrieve similar projects, and surface questions. The aim is not to know everything. The aim is to recognize the important thing when it appears.
02
Find the pain in the first meeting
Establish credibility, then watch where the client responds. As soon as they describe use cases, stop presenting and listen: the problem, who feels it, how the process works today, which systems are involved, and what a convincing result looks like.
03
Help the client see the difference
Many clients still think of AI as a chatbot that waits for a prompt. Show the difference between a pull-based assistant and a push-based agent. Explain local-first as data control, privacy, and compliance from the start, not as an afterthought.
04
Use the harness during the meeting
With consent and approved tooling, the harness captures decisions, retrieves similar work, explains unfamiliar systems, and can produce an initial view the client can react to. It expands attention. It does not replace it.
05
Capture what the transcript missed
Write four or five observations that require human instinct: what made their eyes widen, which bottleneck they kept returning to, who cared about control versus speed. Those notes often become the feature that makes the prototype feel exceptional.
06
Build the first version immediately
Spend up to two focused hours after the meeting making the idea visible. Track the problem, users, core workflow, systems, and assumptions. Do not wait for a perfect specification. The prototype is part of discovery.
07
Work in three-to-four-hour loops
For the next few days, improve the prototype in focused cycles. Set a concrete outcome, review what the harness produced, test it, and define the next outcome. Keep it functional. A strong demo proves the central workflow can work.
08
Validate with the client
Show progress every few days. Each session should answer three questions: are we solving the right problem, does this workflow fit how they operate, and what must change before this becomes a real project. Track feedback as decisions.
09
Prepare the Wolf handoff
At the end of two weeks, package transcripts, the prototype, confirmed requirements, open questions, systems, scope, and risks. A strong handoff lets the Wolf take over without repeating discovery. Then review it yourself.
Definition of done
An Octopus has succeeded when the client’s real pain is clear, the solution is specific to their context, the core workflow has been demonstrated in a functional prototype, the client has validated the direction, the most important assumptions and risks are visible, the Wolf can take over without repeating discovery, and scope, pricing inputs, and the path to delivery are clear. The Octopus does not hand over an idea. The Octopus hands over a validated opportunity with momentum.
Listen for pain, make the opportunity visible, build fast, validate continuously, and hand the Wolf a project that is ready to run.