---
title: "Meet Strategy Studio: say the idea, run the strategy"
description: "Describe a rule-based idea and TickMate writes it as real C#. Ask for an indicator the SDK does not ship and it writes that too. Backtest in a sentence, then decide, behind nine acknowledgements, whether it ever runs on an account."
author: "TickHint Dev Team"
date: 2026-10-14
canonical: https://www.tickhint.com/blog/meet-strategy-studio
tags: ["Strategies", "TickMate", "Product"]
---

# Meet Strategy Studio: say the idea, run the strategy

> Describe a rule-based idea and TickMate writes it as real C#. Ask for an indicator the SDK does not ship and it writes that too. Backtest in a sentence, then decide, behind nine acknowledgements, whether it ever runs on an account.

Video: Strategy Studio: one sentence asks TickMate for an aggressive momentum strategy and it writes the C# code; asked for ATR, an indicator the SDK does not ship, it writes the indicator from scratch and uses it; a backtest runs from a sentence and is kept with the version; deploying takes your account, symbol and limits plus nine acknowledgements, and the strategy runs on a demo account.

You have an idea for a rule-based strategy. The usual path from there is a weekend: learn the platform's scripting language, write the rules, debug them, discover the indicator you need is not built in, write that too, and only then find out whether the idea was any good.

**Strategy Studio** turns that weekend into a conversation. The video above is one conversation, start to finish, in four chapters.

## 1. Build it

*"Let's create an aggressive momentum strategy please."*

TickMate writes the strategy as real C#: code you can read, change and apply, not a black box with a name. It compiles against the TickHint SDK before it is saved. The result is **version 1**, and every change from here becomes a version you can go back to.

## 2. Any indicator

The SDK ships five indicators: Bollinger Bands, EMA, MACD, RSI and SMA. Momentum strategies tend to want ATR for sizing, so the next sentence is:

*"I know that ATR is not in the built-in indicators. Can you implement it and use it in our strategy as well?"*

It writes ATR from scratch, wires it into the strategy, and leaves its period and the sizing as parameters you can tune. **Version 2.** The same works for any indicator you can describe, including the one only you use.

## 3. Test it

*"Give the wallet 100K funds and run it against EURUSD 1h bars over the past 6 months."*

That sentence is the whole backtest setup. The run is kept with the version it tested, so when you change the rules you can see what the change did. A backtest is history, not a forecast, and we never publish or promise returns; in the video the result panel is blurred on purpose. What a backtest is good for is the honest question: does the idea do what you think it does, before any money is involved?

## 4. Your call

Deploying is a sheet, not a button. You pick the account, the symbol and the timeframe, and you set the limits the strategy runs inside: position size, daily loss, open positions. Then come **nine acknowledgements**, one by one, before automation touches an account.

This is the one place in TickHint where something trades without a tap. It only happens because you walked it there yourself, and it runs on each closed bar until you press **Stop**. The video deploys to a demo account, which is where we suggest every strategy starts.

## What it does, and what it does not

TickMate writes code, and code can be wrong. Read it, change it, backtest it, and start on a demo account. Its output is analysis and software, not investment advice, and you are responsible for every strategy you take live.

## Plans

Writing, compiling and backtesting strategies is on every plan, including Free. Running a strategy in the cloud is part of Pro. Founding members, the first 200 Pro accounts, get $10 off every month for 12 months with the code FOUNDING at checkout. [See the plans](/#pricing).

[Start free](/), open Strategy Studio, and say the idea.