Scaling In
Understand scaling into crypto spot positions: staged entries, pre-planned risk, average entry price, confirmation and averaging-down risk.
Reading progress — saved on this device
Scaling in means building a planned position through several entries rather than committing the full size at once. Done well, it can separate initial evidence from later confirmation. Done poorly, it becomes uncontrolled averaging down.
Scaling changes timing, not the need for a risk plan
A scale-in plan divides a desired maximum position into tranches. Tranches can be linked to price levels, confirmation events, time, or liquidity. The important phrase is maximum position: scaling should not create an unlimited sequence of additions.
Common scale-in structures
Confirmation ladder
Small initial entry, more size only after defined evidence improves.
Price-zone ladder
Several limits inside a pre-defined accumulation zone with one shared invalidation.
Liquidity-aware execution
Break a larger order into smaller clips to reduce immediate market impact.
Time-sliced entry
Build exposure at defined intervals when timing precision is intentionally reduced.
Calculate aggregate risk, not tranche risk in isolation
If tranches have different entry prices but share one invalidation level, total planned loss is the sum of each tranche's distance to invalidation multiplied by its quantity.
This prevents a misleading calculation where each addition “looks small” but the combined position exceeds the original risk budget.
| Before entry | Define |
|---|---|
| Maximum notional | Largest total position permitted |
| Tranche conditions | What must happen before each addition |
| Shared/updated invalidation | Where the total thesis fails |
| Aggregate loss cap | Maximum monetary risk including all tranches |
Worked example
You are willing to hold at most 150 tokens. The plan is 50 tokens at £50 after an initial trigger, 50 more at £51.50 only after a higher low forms, and the final 50 at £53 only if price closes above resistance. Shared invalidation is £47.
If all three fill, planned price risk is: (50×£3) + (50×£4.50) + (50×£6) = £675 before costs. The average entry is £51.50, but average entry alone hides the real risk: later confirmation tranches have larger distance to the same invalidation.
If your risk budget were only £400, the original tranche sizes would be inconsistent with the plan even though no individual purchase looked large.
Define conditions that stop further additions
A strong scale-in plan specifies not only when to add, but when the next tranche is cancelled. If the setup deteriorates after tranche one, unused capacity should remain unused rather than becoming an obligation to complete the position.
Examples of stop-adding conditions include a break of the planned structure, abnormal spread/depth, a new event risk, or the aggregate position already reaching its monetary risk cap because volatility widened.
| State | Action on unused tranche | Reason |
|---|---|---|
| Evidence improves | Add only if planned condition fires | Confirmation-based scaling |
| Evidence unchanged | Wait | No reason to increase exposure |
| Evidence worsens | Cancel future additions | Do not average into thesis failure |
| Liquidity deteriorates | Pause/reduce tranche | Execution risk changed |
Common mistakes and misunderstandings
- Adding because price is lower without any pre-defined reason.
- Calculating only the average entry and ignoring aggregate loss to invalidation.
- Leaving the number of tranches open-ended.
- Increasing tranche size after losses to “get back to break-even”.
- Assuming scaling in always reduces execution cost; more orders can also add fees or adverse selection.
Knowledge checkpoint
These questions are specific to Scaling In.
Q1. Why is “buy more if it drops” not a complete scale-in plan?
Q2. How do you calculate aggregate risk when several entries share one invalidation level?
Q3. Why can later confirmation tranches have more risk per unit than the first tranche?
Q4. What should stop further additions even if the maximum number of tranches has not been used?
FAQ
❓ Does scaling in always lower the average entry?
No. Confirmation-based scaling can add at higher prices and raise the average entry.
❓ Is averaging down always wrong?
Not automatically, but it should be pre-planned, capped and supported by a thesis that remains valid rather than used emotionally.
❓ Should each tranche have its own stop?
It can, but the aggregate risk still needs to be calculated across the whole position.
❓ Can scaling reduce market impact?
Yes for larger orders, but the benefit depends on liquidity, timing and how the market moves while execution is split.
Summary
- Scaling in builds a position through pre-defined tranches.
- Model the maximum fully built position and aggregate loss before tranche one.
- Confirmation-based additions differ from uncontrolled averaging down.
- Average entry is not a substitute for total risk calculation.
This building block explains trading process and execution risk. It is not investment advice or a trade recommendation.
Want this in a personalised order?
Take the crypto assessment and get a custom path of 10 modules matched to what you already know. Free, no card required.
Build my path →