Custom ATAS Indicator Development: Process, Cost & Examples

An alert the moment an imbalance builds up in the footprint across several candles. A custom variant of the volume profile with an added delta filter. A setup that checks several conditions at once before firing a signal. Ideas like these are very specific - and rarely find an exact match in the ATAS store. That's where a custom-built indicator makes sense.

When is a custom indicator worth it?

• The idea combines two or more signals that aren't available together in the store
• You need an active alert (Telegram, sound, email) rather than just a visual display
• The logic needs to run consistently across multiple symbols and timeframes
• The logic should stay private instead of sitting publicly in the store

What the process actually looks like

The process is deliberately kept simple - a rough sketch or a reference chart is more than enough as a starting point:

• Describe the idea - as text, a sketch, or a chart example
• Free, non-binding quote within 24-48 hours
• Fixed-price offer instead of hourly billing - no surprises on the invoice
• Development and delivery within 3-5 days after the quote is accepted
• Installation guide included, plus free support afterward for questions and minor adjustments

What determines the cost

Pricing isn't based on hours but on the actual scope of the project. The main factors are:

• Complexity of the logic - how many conditions and signals need to be combined
• Whether the indicator needs to run on multiple chart types (footprint, cluster, classic candles)
• Whether active alerts (Telegram, sound, email) are part of the scope
• Whether it's a pure indicator (visual only) or a strategy (can place orders on its own) - strategies generally require more testing

Typical examples from real projects

Common requests include a breakout indicator that combines volatility (e.g. via ATR) with a volume filter and only fires once both conditions are met; a custom volume profile variant with an added delta-divergence display; or a cluster-based alert that reacts to a recurring order flow pattern across several candles. Each of these is meant as a starting point - the actual rule set is always tailored to the specific request.