---
title: "Futures Position Sizing: Ticks, Points and Planned Risk"
slug: futures-position-sizing-ticks-points-and-planned-risk
date: 2026-10-21
modified: 2026-10-21
author: Bhavishya Goyal
excerpt: ""
meta_description: "Learn futures position sizing with MNQ, NQ, MES and ES examples. Convert ticks to points, and check planned risk before automating."
focus_keyword: futures position sizing
canonical_url: "https://blog.pickmytrade.io/futures-position-sizing-ticks-points-and-planned-risk/"
og_title: "Futures Position Sizing: Ticks, Points and Planned Risk"
og_description: "Learn futures position sizing with MNQ, NQ, MES and ES examples. Convert ticks to points, and check planned risk before automating."
og_image: "https://blog.pickmytrade.io/wp-content/uploads/2026/10/Futures-Position-Sizing-1024x537.avif"
schema_type: FAQPage
categories:
  - Algo trading
  - Trading
tags: []
reading_time: 14
word_count: 3397
robots: "index, follow"
lang: en-US
---

# Futures Position Sizing: Ticks, Points and Planned Risk

**Futures position sizing starts with the cash you plan to risk, the distance to your stop, and the contract’s dollar value per point.** Divide the budget by the planned risk per contract, then round down. Check costs, margin, existing exposure, and account limits before treating that number as an order quantity.

Table of Contents

1. [Key takeaways](https://blog.pickmytrade.io/#key-takeaways)
2. [What do quantity, ticks, points, and dollar risk mean?](https://blog.pickmytrade.io/#what-do-quantity-ticks-points-and-dollar-risk-mean)
3. [What are the tick and point values for MNQ, NQ, MES, and ES?](https://blog.pickmytrade.io/#what-are-the-tick-and-point-values-for-mnq-nq-mes-and-es)
4. [How do you calculate futures position sizing step by step?](https://blog.pickmytrade.io/#how-do-you-calculate-futures-position-sizing-step-by-step)
5. [Which inputs must be valid before you calculate quantity?](https://blog.pickmytrade.io/#which-inputs-must-be-valid-before-you-calculate-quantity)
6. [Worked example: size an MNQ trade with a 0 budget](https://blog.pickmytrade.io/#worked-example-size-an-mnq-trade-with-a-100-budget)
7. [Does entry slippage change an absolute stop and a distance stop equally?](https://blog.pickmytrade.io/#does-entry-slippage-change-an-absolute-stop-and-a-distance-stop-equally)
8. [How does a wider stop change the quantity?](https://blog.pickmytrade.io/#how-does-a-wider-stop-change-the-quantity)
9. [Which balance should you use for percentage sizing?](https://blog.pickmytrade.io/#which-balance-should-you-use-for-percentage-sizing)
10. [How should you apply futures position sizing in PickMyTrade?](https://blog.pickmytrade.io/#how-should-you-apply-futures-position-sizing-in-pickmytrade)
11. [Why is margin separate from the risk budget?](https://blog.pickmytrade.io/#why-is-margin-separate-from-the-risk-budget)
12. [Why can actual loss exceed planned stop risk?](https://blog.pickmytrade.io/#why-can-actual-loss-exceed-planned-stop-risk)
13. [What changes when you stack entries or copy trades?](https://blog.pickmytrade.io/#what-changes-when-you-stack-entries-or-copy-trades)
14. [Pre-automation checklist: verify the calculation and execution](https://blog.pickmytrade.io/#pre-automation-checklist-verify-the-calculation-and-execution)
15. [Frequently asked questions](https://blog.pickmytrade.io/#frequently-asked-questions)
16. [Turn the risk budget into a verified contract count](https://blog.pickmytrade.io/#turn-the-risk-budget-into-a-verified-contract-count)

The units matter. A 10-point MNQ stop is 40 ticks and $20 per contract before costs. A 10-tick MNQ stop is only 2.5 points and $5 per contract. Confusing those inputs changes the planned price risk fourfold. CME lists MNQ at $2 per index point with a 0.25-point minimum tick. [Source: CME MNQ specifications](https://www.cmegroup.com/markets/equities/nasdaq/micro-e-mini-nasdaq-100.html).

This guide turns those definitions into a sizing process you can check before sending an alert through PickMyTrade. Examples are hypothetical calculations, not reported trades or recommended risk levels. Product-specific notes cover the documented Tradovate indicator workflow; other brokers and strategy routes need their own field definitions.

## Key takeaways {#key-takeaways}

- Quantity means contracts; ticks and points measure price distance.
- CME specifies a 0.25-point MNQ tick, worth $0.50 per contract.
- Calculate cash risk per contract, include cost assumptions, and round quantity down.
- Margin and prop-account loss allowances require separate checks.
- Verify generated quantities and working stops in demo; planned risk is not a guaranteed loss ceiling.

## What do quantity, ticks, points, and dollar risk mean? {#what-do-quantity-ticks-points-and-dollar-risk-mean}

Quantity counts contracts. A point measures a price change, a tick is the contract’s minimum price increment, and tick value converts that increment into money. For the outright MNQ, NQ, MES, and ES contracts below, four ticks equal one index point. Their dollar exposures differ because their multipliers differ.

| Term | Meaning | MNQ example |
| --- | --- | --- |
| Quantity | Number of contracts in the order or position | 3 contracts |
| Tick size | Minimum quoted price increment | 0.25 index points |
| Tick value | Money gained or lost per tick, per contract | $0.50 |
| Point value | Money gained or lost per full point, per contract | $2 |
| Stop distance | Difference between entry and intended stop | 10 points = 40 ticks |
| Planned price risk | Stop distance × point value × quantity | 10 × $2 × 3 = $60 |

Keep price levels separate from distances. An illustrative long entry at 20,000 with a stop at 19,990 has a 10-point distance. A short entry at 20,000 with a stop at 20,010 also has a 10-point distance. Use the absolute difference for sizing, while separately validating that the stop is on the intended side.

```
Stop distance in points = abs(entry price - stop price)
Stop distance in ticks = stop distance in points / tick size
Tick value = tick size × dollars per point
Planned price risk = stop points × dollars per point × contracts
```

## What are the tick and point values for MNQ, NQ, MES, and ES? {#what-are-the-tick-and-point-values-for-mnq-nq-mes-and-es}

MNQ and MES provide smaller dollar increments than their E-mini counterparts. A 10-point move is $20 per MNQ contract but $200 per NQ contract. For the S&P 500 pair, the same distance is $50 per MES and $500 per ES. These comparisons exclude costs and assume equal entry-to-exit distances.

| Contract | Dollars per point | Tick size | Dollars per tick | 10-point price risk, 1 contract |
| --- | --- | --- | --- | --- |
| MNQ | $2 | 0.25 points | $0.50 | $20 |
| NQ | $20 | 0.25 points | $5 | $200 |
| MES | $5 | 0.25 points | $1.25 | $50 |
| ES | $50 | 0.25 points | $12.50 | $500 |

Sources: CME’s [MNQ](https://www.cmegroup.com/markets/equities/nasdaq/micro-e-mini-nasdaq-100.html) and [MES](https://www.cmegroup.com/markets/equities/sp/micro-e-mini-sandp-500.html) product pages, [NQ specifications](https://www.cmegroup.com/markets/equities/nasdaq/e-mini-nasdaq-100.contractSpecs.html?videoId=6366629509112), and [E-mini equity index FAQ](https://www.cmegroup.com/trading/equity-index/eminifaq.html). Values describe the outright futures contracts, not options or calendar spreads. Verify the instrument and contract month you actually route.

Ten MNQ contracts have the same dollar-per-point exposure as one NQ contract. That does not make their total trading costs or execution identical. Micros let you adjust exposure in smaller increments, but commissions, liquidity, and broker permissions still affect the decision. Changing the symbol requires a fresh sizing check.

## How do you calculate futures position sizing step by step? {#how-do-you-calculate-futures-position-sizing-step-by-step}

First choose a cash budget, then calculate the planned loss per contract at the stop. Divide and round down to a whole-contract quantity. CME’s [position-sizing lesson](https://www.cmegroup.com/education/courses/trade-and-risk-management/proper-position-size) connects the stop location with the amount the trader is willing to risk. A stop chosen for the setup should come before the resulting quantity.

1. Identify the exact contract and verify its point value and tick size.
2. Choose a planned cash budget using a clearly defined account basis.
3. Determine the entry reference and valid stop price for the setup.
4. Calculate the stop distance and price risk per contract.
5. Allow for estimated round-trip fees and adverse execution.
6. Round down, then apply margin, position, and remaining-risk constraints.
7. Verify the submitted size and accepted protective orders.

```
Cash budget = chosen balance basis × (risk percentage / 100)
Price risk per contract = stop points × dollars per point
Planning amount per contract = price risk + estimated fees + slippage allowance
Calculated quantity = floor(cash budget / planning amount per contract)
```

The cost-adjusted formula is a planning model, not a promise about the integration’s internal sizing algorithm. It assumes the listed costs scale per contract. If your broker has fixed order charges or tiered fees, calculate the total expected cost for each candidate whole quantity instead. Never add the same cost allowance twice.

## Which inputs must be valid before you calculate quantity? {#which-inputs-must-be-valid-before-you-calculate-quantity}

Reject an incomplete setup before dividing the risk budget. A missing or zero stop distance makes the formula unusable. For a new long, an initial protective stop normally belongs below the entry reference; for a new short, above it. Taking an absolute difference alone will not catch a stop placed on the wrong side.

| Input problem | Planning response |
| --- | --- |
| Missing, nonnumeric, or nonfinite price | Do not calculate or submit a size from that value. |
| Zero or negative risk budget | No new risk allocation. |
| Zero stop distance | Do not divide by zero or substitute an arbitrary tiny distance. |
| Stop on the wrong side for the intended new entry | Correct the setup before using the distance. |
| Price off the contract’s tick grid | Determine the supported valid price, then recompute risk from that price. |
| Unknown point value or contract mapping | Verify the destination contract before calculating. |
| Result below one contract | Do not round up to force a trade. |

These are validation rules for your planning process, not claims about PickMyTrade’s rejection behavior. For MNQ, a proposed stop at 19,990.10 is not on a 0.25-point grid. If the supported route uses 19,990.00 instead, size from that actual price. Do not assume which rounding direction the platform will choose.

## Worked example: size an MNQ trade with a $100 budget {#worked-example-size-an-mnq-trade-with-a-100-budget}

Suppose your chosen sizing basis is $10,000 and your illustrative budget is 1%, or $100. With a 10-point MNQ stop, price risk is $20 per contract. Before costs, five contracts use the entire budget. Adding even a modest cost allowance changes the number that fits.

| Input | Hypothetical value |
| --- | --- |
| Chosen sizing basis | $10,000 |
| Budget percentage | 1% |
| Cash budget | $100 |
| Entry / long stop | 20,000 / 19,990 |
| Stop distance | 10 points / 40 ticks |
| MNQ point value | $2 |
| Price risk per contract | $20 |
| Assumed round-trip fees per contract | $1.50 |
| Assumed total adverse-execution allowance | 2 ticks × $0.50 = $1 per contract |
| Planning amount per contract | $22.50 |
| Calculated whole quantity | floor($100 ÷ $22.50) = 4 |
| Planned total using those assumptions | 4 × $22.50 = $90 |

The fee and slippage figures are hypothetical inputs for the example, not current broker prices or measured execution. Replace them with your own fee schedule and a justified execution assumption. Five contracts would total $112.50 under these inputs, exceeding the $100 budget. Four leave a $10 planning buffer, not guaranteed protection.

Now change only the instrument to NQ. A 10-point stop carries $200 of price risk for one contract before costs, already exceeding the example’s $100 budget. The whole-contract result is zero. Do not round up or move the stop solely to make one NQ fit. Reassess the instrument or skip the setup.

## Does entry slippage change an absolute stop and a distance stop equally? {#does-entry-slippage-change-an-absolute-stop-and-a-distance-stop-equally}

No. With an absolute stop, a worse entry increases the distance to that unchanged price. A stop placed a fixed distance from the actual fill can preserve the distance while moving the exit price. The following examples assume a long MNQ order, a reference entry of 20,000, and an actual fill of 20,002.

| Stop design | Stop price after fill | Distance from actual fill | Price risk per contract |
| --- | --- | --- | --- |
| Absolute stop remains 19,990 | 19,990 | 12 points | $24 |
| 10-point stop measured from actual fill | 19,992 | 10 points | $20 |

These are hypothetical order designs, not a statement that every PickMyTrade mode anchors to the fill. Confirm whether the route calculates from the alert price, another reference, or the actual fill. In the cost example, identify what the $1 execution allowance covers; do not count entry slippage again if it is already included.

MNQ: price distance becomes dollar riskEntry 20,000, stop 19,990. Ten points equal forty ticks and twenty dollars per contract. Four contracts carry eighty dollars of price risk before costs.MNQ: convert distance before choosing quantityEntry: 20,000Stop: 19,99010 points = 40 ticks$20 per contract4 contracts = $80 price riskHypothetical illustration • Before fees and slippage • MNQ: $2 per pointIllustrative calculation using CME’s MNQ contract multiplier. This is not a trade result or a platform screenshot.
*Illustrative calculation using CME’s MNQ contract multiplier. This is not a trade result or a platform screenshot.*

## How does a wider stop change the quantity? {#how-does-a-wider-stop-change-the-quantity}

With the same dollar budget, a wider stop generally permits fewer contracts. The following MNQ examples hold the $100 budget constant and exclude fees and slippage to isolate the relationship. They show why a fixed quantity cannot also deliver a fixed cash risk when stop distance changes.

| MNQ stop distance | Ticks | Price risk per contract | Whole quantity under $100 | Total planned price risk |
| --- | --- | --- | --- | --- |
| 5 points | 20 | $10 | 10 | $100 |
| 10 points | 40 | $20 | 5 | $100 |
| 15 points | 60 | $30 | 3 | $90 |
| 25 points | 100 | $50 | 2 | $100 |
| 60 points | 240 | $120 | 0 | $0: no trade |

Rounding creates unused budget. At 15 points, three MNQ contracts risk $90 before costs; four would risk $120. That gap is a consequence of whole contracts. Treat the budget as a ceiling for the model, rather than a target you must spend. Recalculate if volatility changes the stop before entry.

## Which balance should you use for percentage sizing? {#which-balance-should-you-use-for-percentage-sizing}

Name the balance basis explicitly before applying a percentage. A cash balance, net liquidation value, available margin, and prop firm’s advertised account size are different inputs. A hypothetical 1% of $50,000 is $500; it does not mean a trader has $500 of acceptable room under every account rule.

For a prop account, examine the current liquidation threshold, remaining loss allowance, daily restrictions, and maximum contracts. If the headline account is $50,000 but remaining loss room is $1,000, a $500 planned trade consumes half that room before additional losses or costs. Those figures illustrate the distinction; actual firm calculations vary.

Keep the trade budget separate from the account’s hard limits. Existing unrealized losses, open-order exposure, and trailing-threshold rules can reduce usable room. A calculation based on balance alone cannot establish compliance. Verify the current rules and leave room for execution uncertainty rather than sizing exactly to a liquidation threshold.

## How should you apply futures position sizing in PickMyTrade? {#how-should-you-apply-futures-position-sizing-in-pickmytrade}

Use the sizing mode documented for your selected connector and alert type. PickMyTrade’s [Tradovate indicator guide](https://docs.pickmytrade.trade/docs/automated-trading-tradingview-indicators/) describes Fixed Quantity and Risk Percentage, with a stop required for percentage sizing. Review the generated message and confirm its balance basis and unit definitions before relying on the calculated quantity.

Fixed quantity specifies the contract count. The [JSON parameter reference](https://docs.pickmytrade.trade/docs/tradingview-json-alert-configuration/) documents automatic sizing when `risk_percentage` is set and `quantity` is omitted. The [multi-account guide](https://docs.pickmytrade.trade/docs/place-trades-in-multiple-accounts/) also shows a percentage example with `quantity: 0`. Those examples do not establish a universal precedence rule when both inputs are positive. Preserve the configuration generated for your route.

**Documentation-based check, not a tested account result:** suppose the route’s verified sizing basis is $10,000, risk is 1%, and the supported stop mode resolves to 10 MNQ points. The stop-only formula gives five contracts. Our illustrative cost-adjusted plan permits four. This difference is why a hand calculation must not be presented as proof of the quantity the software will submit.

The documentation uses both “account balance” and “available account balance”; it does not establish the precise broker field or cost treatment for this example. Confirm those details for your account. Strategy alerts need their own [supported strategy setup](https://docs.pickmytrade.trade/docs/automate-tradingview-strategies/). Do not remove generated fields based only on a different page’s example.

Keep two numbers separate: the quantity produced by the supported configuration and the quantity allowed by your own cost-adjusted plan. If the automated result exceeds your limit, resolve the sizing setup before enabling it. Do not assume the platform includes the fees and slippage allowance used in this article.

| Input to verify | Question to answer before automation |
| --- | --- |
| Contract mapping | Does the destination trade the intended micro or E-mini contract and expiry? |
| Sizing mode | Is contract count fixed or calculated from a percentage? |
| Balance basis | Which account value supplies the percentage calculation? |
| Stop mode | Is the input an absolute price, points, ticks, money, or another supported mode? |
| Money scope | Does any cash amount apply per contract or to the whole position? |
| Costs and limits | Does the automated calculation include your planning allowances and constraints? |

Do not infer units from a field name alone or copy settings from another broker’s example. A price-level field needs a price, not a distance. The abstract 10-point MNQ example could correspond to a 19,990 stop for a 20,000 long entry; it is not a complete alert payload. Use the route’s generated configuration.

## Why is margin separate from the risk budget? {#why-is-margin-separate-from-the-risk-budget}

[CME explains futures margin](https://www.cmegroup.com/education/courses/introduction-to-futures/margin-know-what-is-needed) as funds deposited and maintained with the broker for the position. It is not the loss calculated from a stop. A contract must fit both your planned-risk budget and the current margin rules; meeting one requirement does not establish that it meets the other.

Check the broker’s current intraday and overnight requirements, plus any account-specific restrictions. Margin can change, and a broker can require additional funds. Do not treat low advertised day margin as the amount a trade can lose. The $20 MNQ price-risk example remains a stop-distance calculation, not a margin quote.

## Why can actual loss exceed planned stop risk? {#why-can-actual-loss-exceed-planned-stop-risk}

Planned stop risk assumes an entry reference, an exit price, and a quantity. Actual fills can differ, while costs add to the result. CME’s [order-types guide](https://www.cmegroup.com/education/courses/futures-trading-mechanics-and-regulation/futures-order-types) distinguishes stop-limit and stop-with-protection orders. Triggering does not guarantee a complete exit at the trigger price. Confirm which broker order your selected stop mode creates.

A stop-limit becomes eligible at its limit price or better and may remain unfilled. A stop with protection executes only within its protection range; unfilled quantity can remain working. Order rejection, cancellation, or a disconnected workflow also requires attention. Inspect the broker order state rather than treating a populated stop field as proof of protection.

For example, four MNQ contracts exiting three points worse than the planned stop add $24 of price loss: 4 × 3 × $2. This is an execution scenario, not an expected slippage estimate. The original $80 price-risk calculation would become $104 before fees, showing why planned loss is not a hard ceiling.

Check both sides of the trade in the broker records. Confirm entry fills, remaining quantity, accepted stop orders, and subsequent exit fills. A received webhook does not prove that protection is working. Use [PickMyTrade’s monitoring guide](https://docs.pickmytrade.trade/docs/monitoring-and-managing-trades/) to trace alerts alongside the broker’s actual order states.

## What changes when you stack entries or copy trades? {#what-changes-when-you-stack-entries-or-copy-trades}

Recalculate the entire destination position whenever another entry can be accepted. If one MNQ contract has $20 of planned price risk, three identical entries can create $60 before costs. A per-alert size is not an account-wide risk cap. Different fills and stops require a combined calculation rather than simple multiplication.

For entries sharing a stop, define what “risk” measures before summing. Loss from the original fills differs from additional downside measured from current marked-to-market equity. Use signed profit/loss for the first measure; do not label every absolute entry-to-stop distance a loss when a stop has moved beyond an entry.

| Hypothetical MNQ position | Result at shared 19,990 stop, before costs |
| --- | --- |
| Long 1 at 20,000 | -$20 from entry |
| Long 1 at 20,005 | -$30 from entry |
| Combined result from original entries | -$50 |
| Current price 20,010: unrealized P/L | +$30 |
| Additional downside from current mark to stop | 2 × (20,010 − 19,990) × $2 = $80 |

The $80 downside includes giving back $30 of unrealized profit and then losing $50 from the entries. Do not add $50 to $80 again. If the shared stop moves to 20,002, the first entry shows +$4 and the second -$6, a combined -$2 before costs. Execution uncertainty still applies.

Include working entries that could fill and inspect protection after partial fills. For an account limit based on current equity, the change from today’s mark may matter more than loss from original entries. Keep each firm’s actual threshold calculation separate. An alert name alone does not establish strategy-level position isolation.

Copying creates another sizing check at each destination. A multiplier, different contract mapping, rounding, or account restriction can change exposure. Review the documented [multi-account settings](https://docs.pickmytrade.trade/docs/place-trades-in-multiple-accounts/) and test each account’s actual result. Contract counts alone cannot compare risk across different instruments or different stop distances.

## Pre-automation checklist: verify the calculation and execution {#pre-automation-checklist-verify-the-calculation-and-execution}

A sizing test succeeds when the expected quantity, actual position, and accepted protection agree. Record the inputs so the result can be reproduced after a settings change. Start with a demo route and include cases where the formula produces zero contracts, a different stop distance, or an instrument change.

1. Record account, contract, entry reference, stop mode, stop distance, and point value.
2. Calculate the expected whole-contract quantity independently.
3. Confirm the generated message uses the intended sizing method.
4. Test an initial entry, a repeat entry, and an exit after the position is already flat.
5. Check every destination account if using multipliers or copying.
6. Compare broker fills and working protection with the planned values.
7. Resolve rejected orders, unexpected rounding, or quantity mismatches before using the configuration live.

Keep a short record: “MNQ; $100 budget; 10-point stop; $22.50 assumed amount per contract; expected 4 contracts.” After execution, add actual entry, stop, fees, and order IDs. If the result differs, investigate the first mismatch rather than compensating with a larger quantity on the next alert.

## Frequently asked questions {#frequently-asked-questions}

**What is the formula for futures position sizing?** 

Divide the planned cash budget by the planned amount per contract and round down. Price risk per contract equals stop points multiplied by dollars per point. Include appropriate cost assumptions before division. Then apply account, margin, and position limits; the resulting number is a planning quantity, not a guaranteed loss limit.

 
 
**How many ticks are in one MNQ point?** 

One MNQ point contains four ticks because the minimum tick is 0.25 points. Each tick is worth $0.50 per contract, so one full point is worth $2. A 10-point stop is 40 ticks, carrying $20 of planned price risk for one contract before fees and execution differences.

 
 
**Can I trade a fraction of an MNQ or NQ contract?** 

These futures orders use whole contracts. If your calculation returns 0.6 contracts, rounding up to one exceeds that model’s budget. Consider whether a different supported contract fits the setup or decline the trade. Do not change instrument metadata or tighten the stop arbitrarily just to force a nonzero quantity.

 
 
**Is futures margin the same as the amount I risk?** 

No. Margin is the collateral requirement for holding the position; planned stop risk estimates loss over a chosen price distance. One MNQ contract with a 10-point stop has $20 of planned price risk before costs regardless of its margin requirement. Both checks matter, and losses can exceed the planned amount.

 
 
**Does fixed quantity keep my dollar risk constant?** 

No. Three MNQ contracts with a 10-point stop carry $60 of planned price risk; with a 20-point stop, that becomes $120 before costs. Fixed contracts keep the count constant. Holding a cash budget constant requires recalculating quantity when distance changes, subject to whole-contract rounding and account restrictions.

 
 

## Turn the risk budget into a verified contract count {#turn-the-risk-budget-into-a-verified-contract-count}

Calculate in the same order each time: define the budget, confirm the contract, measure the stop, allow for costs, and round down. Keep margin and account rules as separate constraints. Before automating, follow the [PickMyTrade indicator setup](https://docs.pickmytrade.trade/docs/automated-trading-tradingview-indicators/) for your route and verify the resulting quantity and working protection in demo.

_**Disclaimer:**  
This content is for informational purposes only and does not constitute financial, investment, or trading advice. Trading and investing in financial markets involve risk, and it is possible to lose some or all of your capital. Always perform your own research and consult with a licensed financial advisor before making any trading decisions. The mention of any proprietary trading firms, brokers, does not constitute an endorsement or partnership. Ensure you understand all terms, conditions, and compliance requirements of the firms and platforms you use._

Also Checkout: [Multiple Strategies One Account: TradingView Setup Guide](https://blog.pickmytrade.io/multiple-strategies-one-account-tradingview-setup-guide/)

**Automate Your TradingView Strategies**  
Connect your alerts with [PickMyTrade](https://pickmytrade.io "PickMyTrade") — automated trade execution, no coding required. [Start free →](https://pickmytrade.io/pricing)

For AI tools &amp; developers:[View Markdown →](https://blog.pickmytrade.io/futures-position-sizing-ticks-points-and-planned-risk.md)<!--pmtA1-clean-->