Docs
Creating Your First Blueprint
Learn how to structure a first strategy blueprint in Setup.Cash using inputs, indicators, logic, execution, and risk management blocks.
A blueprint is the operating definition of your strategy. It is where you convert a trading idea into repeatable conditions, execution rules, and risk controls.
This guide shows how to build a first blueprint that is simple enough to test but structured enough to improve over time.
Blueprint Mindset: Define the Process, Not the Prediction
A blueprint should answer:
- When your strategy is allowed to trade
- What conditions must be true before entry
- How an entry is triggered
- Where risk is defined and capped
- Why the trade exits (target, stop, invalidation, or time)
It should not rely on vague judgments like “looks strong” or “market feels weak.” If a condition matters, write it into the blueprint.
Related resources:
Blueprint Structure (Inputs → Indicators → Logic → Execution → Risk)
Most successful first blueprints follow this flow:
Inputs (market context)
Inputs define where the strategy is valid.
Examples:
- Session or trading hours
- Market symbol or watchlist
- Volatility floor/ceiling
- Spread or liquidity conditions
Without inputs, you may backtest a strategy in market conditions it was never designed for.
Indicators (transforms, not decisions by themselves)
Indicators should support the logic, not replace it.
Examples:
- RSI as a momentum/mean-reversion context tool
- EMA as a trend filter
- ATR as a volatility and stop-distance tool
Indicator values are data points. The blueprint defines what those values mean in context.
Logic (confirmation rules)
Logic combines inputs and indicator states into a trade decision.
Examples:
- Trend filter must be bullish
- Pullback must meet depth condition
- Trigger candle must close above confirmation level
This is the part of the blueprint where ambiguity causes most failures. Be explicit.
Execution (entry + exit behavior)
Execution defines how the trade is opened and how it is managed.
Examples:
- Market or limit entry conditions
- Stop-loss placement rule
- Take-profit ladder or single target
- Move-to-break-even conditions
- Time-based exit
A strategy with good signals but weak execution rules is incomplete.
Risk management (always part of the blueprint)
Risk is not a post-processing step. Include it in the same blueprint version as the entry logic.
Examples:
- Max risk per trade
- Max daily loss
- Max concurrent exposure
- Stop trading after consecutive losses
- Session shutdown conditions
Building a First Blueprint: Step-by-Step
1) Choose one setup pattern
Start with a single idea, such as:
- Trend continuation pullback
- Breakout retest
- Mean reversion to moving average
Do not combine multiple setups in your first blueprint.
2) Write the rules in plain language first
Before building blocks, write a plain-language version:
Trade only during defined session.
Only long when trend filter is bullish.
Enter on pullback confirmation.
Risk 1% max per trade.
Exit at stop, target, or invalidation.
If you cannot explain it in plain language, the visual version will likely be too complex.
3) Build the visual sequence
In Setup.Cash, create the flow in the same order as the strategy logic. Keep the first version linear.
Tips:
- Name blocks clearly (e.g., “London session filter,” “EMA trend filter”)
- Add notes for assumptions that are not obvious
- Avoid hidden conditions in multiple branches on version 1
4) Add risk blocks before saving version 1
Set stop and risk logic before you run the first test. This prevents misleading performance output.
5) Save a baseline version
Save a clean baseline before experimentation. Every later improvement should be compared against it.
Blueprint Example (No-Code Pseudo Flow)
Session Filter (London/NY overlap)
-> Spread Check
-> EMA Trend Filter
-> Pullback Condition
-> Confirmation Candle Rule
-> Position Size Rule
-> Entry
-> Stop / Target
-> Max Daily Loss Gate
This flow is intentionally simple. Its value is that it can be tested, reviewed, and explained.
Common Blueprint Mistakes
1) Using indicators as a substitute for rules
“RSI below 30” alone is not a complete setup. You still need context, confirmation, and risk definitions.
2) Combining too many confirmations
More rules do not automatically improve a strategy. They can overfit the backtest and reduce real-world robustness.
3) No invalidation logic
A blueprint without invalidation often becomes a “hope and hold” system.
4) Testing before documenting assumptions
Write assumptions down first. When results differ, you need a reference point for debugging.
5) Changing multiple variables at once
When you change trend filter, entry logic, and stop logic at the same time, you cannot tell what caused the result.
Blueprint Review Checklist (Before Backtesting)
- Is there exactly one H1 strategy idea in the blueprint version?
- Are entries and exits explicitly defined?
- Is risk per trade capped?
- Is there an invalidation condition?
- Can another person explain the logic after reading your blueprint?
- Have you saved a baseline version?
FAQ
How detailed should my first blueprint be?
Detailed enough to test and explain. Start simple, then add complexity only if data justifies it.
Should I include news filters or session filters immediately?
If your strategy depends on market conditions, yes. Context filters are often core logic, not optional extras.
Can I build multiple versions of the same strategy?
Yes. In fact, you should version your blueprint and compare changes with backtesting and paper trading instead of overwriting the original.
Next Steps
- Run a baseline test with Backtesting docs
- Read Backtesting Explained
- Review Risk Management for Trading Bots and confirm your stop, sizing, and exposure rules before iterating further
- Explore Risk Management for Trading Bots
External references:
Not financial advice. Trading involves risk.
Start here
Build your trading bot workflow with structure
Use Setup.Cash to create, backtest, and paper trade rule-based strategies without relying on guesswork. Not financial advice. Trading involves risk.