The 20-minute weekly brief BD teams run on Compass

Crypto market timing in 20 minutes a week: read the Compass brief Monday, re-check Wednesday, send by Thursday, end with 2 or 3 timed decisions.

How do you use a weekly brief for crypto market timing?

Crypto market timing improves the day you swap the daily feed for 1 weekly brief. The brief is a 20-minute read that ends in 2 or 3 outreach decisions. The feed is a habit that ends in open tabs.

Treat the read as a filter with an exit. Go in with market context. Come out with named accounts, named people, and a tag on each. That is the read Compass Briefs is built for.

The pass runs Monday to Thursday: one catalyst, one account, one owner, one outreach decision. Every step below lands on a live Compass page.

FlowFrom Monday brief to Thursday sendOne week, one pass, 2 or 3 decisions. Every step is a live page.
  1. 01
    Read the brief

    About 20 minutes on Monday. Shortlist 2 or 3 candidates.

  2. 02
    Pick 1 catalyst

    Keep the single dated event that best fits your pipeline.

  3. 03
    Open the account

    Read the project page, for example TON.

  4. 04
    Find the owner

    Name the 1 person who owns that event.

  5. 05
    Decide by Thursday

    Send it, prep it for next week, or park it with a reason.

What weekly rhythm works best for crypto market timing?

3 touchpoints beat daily checking: read Monday, re-check Wednesday, send by Thursday. The whole rhythm costs about 40 minutes a week. A feed habit costs more than that before lunch.

Monday chooses. The 20-minute read ends with 2 or 3 candidates and nothing else carried forward. Wednesday confirms each candidate still has a dated event: a 5-to-10-minute check on the Catalysts feed.

Thursday decides. Ready notes go out. The rest get parked with a written reason. Friday belongs to replies, not new research.

Table3 touchpoints, about 40 minutes a weekBlock the 3 slots in your calendar. Monday chooses, Wednesday confirms, Thursday sends; nothing rolls into Friday.
TouchpointWhenWhat you do
Read the briefMonday20 minutes. Shortlist 2 or 3 candidates with a person attached.
Re-check catalystsWednesday5 to 10 minutes. Confirm each dated event still holds.
Send or parkThursday10 minutes. Send the ready notes; park the rest with a reason.

What should happen after you read the brief?

A brief read should end in a short list: about 5 accounts, each with a person attached. Not a campaign, not a spreadsheet. Five lines you can verify by Wednesday.

Each line carries 4 fields: the account, the person hypothesis, the timing reason, and the warmest route. A line missing 2 of the 4 gets cut. Short lists get verified. Long lists get skimmed.

Ownership closes the loop. Every line needs a teammate's name on it. Unowned lines roll over once, then die.

  • Accounts: about 5, each tied to a line in the brief.
  • People: 1 named owner hypothesis per account, pulled from the people directory.
  • Timing: the dated event that makes this week different.
  • Route: the warmest path in, checked before Thursday.
  • Question: the 1 unknown to verify before sending.

How do teams turn a brief into decisions?

Treat every line in the brief as a candidate, not a command. The team tags each one: send now, prep for next week, or park with a reason. 3 tags, no maybes.

Send means the note ships this week with an owner named. Prep means the account is real but 1 field is missing. Park means it stops costing attention until something changes.

For crypto BD teams the measure is throughput. A brief that produces 2 shipped notes beats one that produces 10 open questions. Tag fast, log the reason, move on.

TableBrief decision tableRead each brief line against its question, then tag the account send, prep, or park. One tag per line.
Brief lineQuestion to answerWhere you check
Sector momentumDoes the momentum name an account worth 20 minutes?Pulse
Specific catalystDoes the event change timing or the right person?Catalysts
Investor movementDoes the fund activity open a warmer route?Investors
Company activityDoes the account fit a current priority?Companies
People changeIs there a new owner to contact?People

What should a brief not do?

A brief should not send your outreach for you. It supplies timing context. The evidence lives on the project page and the person profile. No note should cite the brief as its only source.

It should not manufacture urgency either. A line with no dated event behind it gets tagged park, not prep. A brief that makes everything feel urgent is a feed with nicer type.

And it should not rank the whole market. The crypto BD question is narrower: which 2 or 3 moves create account work this week. Hand everything else back to the feed.

What should you save after the weekly review?

Save 5 fields per account: the tag, the person, the timing reason, the route, and the open question. One line each, written for the teammate who missed the meeting. That file is next Monday's head start.

Here is the person-first version. Say Monday's brief flags a raise involving Flying Tulip. The fast move is opening the founder's profile, Andre Cronje, not running a company search.

The profile gives you the role, the history, and the contact channels available on it. A Nexus line works the same way: open Daniel Marin, its CEO, first. People answer notes. Sectors do not.

Save the line even when the tag is park. A parked account with a written reason costs 30 seconds next week. An unlogged one costs the whole conversation again.

Frequently asked questions

Is a brief alone enough for crypto market timing?

No, the brief supplies context and the account page supplies evidence. Timing turns real when a brief line matches a dated event and a named person. Those 2 checks take about 10 minutes.

How many accounts should one weekly brief produce?

About 5 to shortlist, and 2 or 3 to decide on. More than that means the read replaced judgment with collecting. Cut lines until each has a person attached.

What should you save after reading a brief?

5 fields per account: tag, person, timing reason, route, and open question. One line each is enough. Write it for the teammate who missed the meeting.

How do you avoid brief overload?

Tag every line send, prep, or park in the same sitting. Parked lines stop costing attention, which is the point. If everything stays a topic, you have rebuilt the feed.

Which Compass pages does a brief point to?

5 pages: Briefs at /brief, Pulse at /home, Catalysts at /news, companies at /projects, and people at /people. A single weekly pass touches 3 or 4 of them. It should end on a person profile.

Sources and methodology

This article pattern uses Compass data objects: people, companies, investors, catalysts, sectors, and relationship paths. The goal is to keep outreach decisions tied to visible evidence instead of generic market commentary.

Compass BriefsCompass PulseCompass Catalysts feedCompass company directoryCompass people directoryTON on CompassAndre Cronje, Founder of Flying TulipDaniel Marin, CEO of Nexus