Jalli Academy
From business context to a focused plan.
Build a small, reviewable growth brief before multiplying activity. Practice the method with a focused objective and a useful review question.
Leave with a brief you can review.
Move from source facts to a buyer hypothesis, a focused objective, and a review question. Use the worked example to shape your own brief.
Build your first growth brief
Have your website, a description of your offer and a blank document ready. Each step produces something you can inspect.
- 01
Separate facts from assumptions
Write three statements supported directly by business material, with their sources. Put audience beliefs and market guesses in a separate column.
- 02
Describe a recognizable buyer
Specify company type, relevant business situation and responsible role. Add exclusions: an attractive company is not automatically a good fit.
- 03
State the offer plainly
Complete: We help [audience] address [problem] through [deliverable]. Remove unsupported return-on-investment claims and define what you do not deliver.
- 04
Choose one workstream
Pick a hypothesis to explore through research, outreach or useful content. Name its inputs, review owner and permissions before external action.
- 05
Set a review question
Decide what observation would lead you to continue, change the audience, revise the offer or stop. Set a review point and resource limit.
A filled fact-and-assumption worksheet
A worked example for a logistics software studio.
| Topic | Source-backed input | Hypothesis to test |
|---|---|---|
| Offer | The sample service description lists systems integration. | Dispatch handoffs may be a useful problem to discuss. |
| Audience | The studio’s delivery scope covers business software projects. | Operations leaders at logistics providers may own the problem. |
| First commitment | The studio can provide a process review. | A diagnostic conversation may be a suitable starting point. |
A completed first brief
Use this completed brief as a starting point for your own decisions.
- Offer: review one dispatch handoff, then assess whether a scoped systems-integration project is appropriate.
- Audience hypothesis: operations leads at US logistics providers; whether the handoff problem matters remains to be checked.
- Objective: learn how the relevant role describes exception handling before proposing software.
- First workstream: research suitable account context and prepare one opening for review. Do not launch a sequence at this stage.
- Review owner: the studio owner checks source observations, fit reasons, claim accuracy and the proposed next action.
- Scope: one audience hypothesis and one reviewed shortlist. Agree the resource limit before research; external contact requires a separate permission and channel check.
- Review decision: if account fit is unclear, refine the criteria. If a later, appropriately obtained reply challenges the problem or role, record that evidence and revise the hypothesis rather than assuming validation.
Keep the review honest
Record completed activity, replies, relevant replies and agreed next steps separately. Keep the denominator and time window beside each count. A reply is not automatically a qualified opportunity.
A small experiment can reveal questions without proving a cause. Record stale sources, inconsistent execution and uncertainty before judging the message.
Your final brief should contain one audience, one offer, one workstream, a review owner and a question the next round of activity can answer.
Check your understanding
Is a plausible buyer problem a fact?
No. It remains a hypothesis until relevant evidence supports it. Keep its uncertainty visible rather than hiding it in a polished profile.
Why start with one workstream?
It makes the decision and its review easier to understand. Adding channels early can obscure which assumption needs attention.
When is the brief ready to share?
When another teammate can distinguish facts from assumptions, recognize the audience and explain what action is permitted next.