I thought I was designing a strategy builder.
I thought I was designing a strategy builder.
I wasn't.
I wasn't.
I was designing a language.
I was designing a language.
When I joined Optionlogy, the goal was to build a no code strategy builder for retail traders.
When I joined Optionlogy, the goal was to build a no code strategy builder for retail traders.
At first, I assumed the challenge was making algorithmic trading easier.
At first, I assumed the challenge was making algorithmic trading easier.
The more I explored the problem, the more I realized traders weren't struggling because of code.
The more I explored the problem, the more I realized traders weren't struggling because of code.
They were struggling because existing builders couldn't express the strategies they actually wanted to create.
They were struggling because existing builders couldn't express the strategies they actually wanted to create.
Every competitor failed differently.
Every competitor failed differently.
None solved flexibility.
None solved flexibility.
I recreated strategies across platforms like Tradetron, Streak, StockMock, Option Alpha, Algotest, and Capitalise.ai.
I recreated strategies across platforms like Tradetron, Streak, StockMock, Option Alpha, Algotest, and Capitalise.ai.
Some couldn't support nested logic.
Some couldn't support nested logic.
Some struggled with trade management.
Some struggled with trade management.
Others became impossible to use as strategies grew larger.
Others became impossible to use as strategies grew larger.
The interface wasn't the problem.
The interface wasn't the problem.
The architecture was.
The architecture was.
So I stopped studying products.
So I stopped studying products.
I started studying strategies.
I started studying strategies.
I analyzed 30 complex trading strategies looking for a common structure.
I analyzed 30 complex trading strategies looking for a common structure.
Regardless of complexity, they all followed the same execution pattern.
Regardless of complexity, they all followed the same execution pattern.
Entry → Adjustment → Exit
Entry → Adjustment → Exit
Every block answered two simple questions.
Every block answered two simple questions.
When should something happen?
When should something happen?
What should happen?
What should happen?
A strategy shouldn't feel like programming.
A strategy shouldn't feel like programming.
It should feel like describing an idea.
It should feel like describing an idea.
Instead of asking traders to think in rules or scripts, the product asked four simple questions.
Instead of asking traders to think in rules or scripts, the product asked four simple questions.
What are you trading?
What are you trading?
When do you enter?
When do you enter?
How do you manage the trade?
How do you manage the trade?
When do you exit?
When do you exit?
STRATEGY BUILDER
Every strategy needs context.
Every strategy needs context.
Before defining trading rules, traders first define the strategy itself.
Before defining trading rules, traders first define the strategy itself.
The asset, symbol, timeframe, capital, and broker establish the context that every rule references.
The asset, symbol, timeframe, capital, and broker establish the context that every rule references.
This information is configured once and reused throughout the builder.
This information is configured once and reused throughout the builder.
TRADE SETUP
Traders don't think in code.
Traders don't think in code.
They think in decisions.
They think in decisions.
The Entry section combines three related decisions into a single workflow.
The Entry section combines three related decisions into a single workflow.
When should the trade open?
When should the trade open?
What order should be placed?
What order should be placed?
How should the position be protected?
How should the position be protected?
Rather than exposing complex trading logic, the builder guides users through these decisions one step at a time.
Rather than exposing complex trading logic, the builder guides users through these decisions one step at a time.
TRADE ENTRY
Complexity wasn't the problem.
Complexity wasn't the problem.
Showing everything at once was.
Showing everything at once was.
Some strategies require trailing stops, scaling, or time based rules.
Some strategies require trailing stops, scaling, or time based rules.
Others don't.
Others don't.
Instead of forcing every user through advanced configuration, trade management remains optional.
Instead of forcing every user through advanced configuration, trade management remains optional.
Simple strategies stay simple.
Simple strategies stay simple.
Complex strategies grow naturally.
Complex strategies grow naturally.
TRADE MANAGEMENT
Exiting should be just as simple as entering.
Exiting should be just as simple as entering.
The Exit section automatically reuses protection rules defined during Entry while allowing traders to add additional exit conditions.
The Exit section automatically reuses protection rules defined during Entry while allowing traders to add additional exit conditions.
This keeps strategies easier to understand and prevents duplicate configuration.
This keeps strategies easier to understand and prevents duplicate configuration.
TRADE EXIT
The strategy explained itself.
The strategy explained itself.
Every change updated a live summary written in plain English.
Every change updated a live summary written in plain English.
Instead of checking technical rules, traders could simply read the strategy back and confirm it matched their intent.
Instead of checking technical rules, traders could simply read the strategy back and confirm it matched their intent.
This became one of the strongest trust building features in the product.
This became one of the strongest trust building features in the product.
STRATEGY SUMMARY
Before building it, we tested the idea.
Before building it, we tested the idea.
Together with the Product Manager, I created a high fidelity prototype and walked five experienced options traders through the complete strategy building workflow.
Together with the Product Manager, I created a high fidelity prototype and walked five experienced options traders through the complete strategy building workflow.
Every participant understood the interaction model and agreed that it addressed limitations they had experienced with existing no code platforms.
Every participant understood the interaction model and agreed that it addressed limitations they had experienced with existing no code platforms.
The sessions validated the product direction rather than the final implementation.
The sessions validated the product direction rather than the final implementation.
We didn't build everything.
We didn't build everything.
We built the right foundation.
We built the right foundation.
The original vision included strategy building, historical backtesting, paper trading, and live deployment.
The original vision included strategy building, historical backtesting, paper trading, and live deployment.
Rather than building every feature at once, we intentionally focused the MVP on validating the strategy builder first.
Rather than building every feature at once, we intentionally focused the MVP on validating the strategy builder first.
Backtesting, deployment, AI assisted strategy generation, and a visual strategy editor were planned for future iterations.
Backtesting, deployment, AI assisted strategy generation, and a visual strategy editor were planned for future iterations.
What happened next.
What happened next.
The strategy builder entered development and became the foundation for the backend architecture.
The strategy builder entered development and became the foundation for the backend architecture.
I left Optionlogy to move to the US for my higher studies.
I left Optionlogy to move to the US for my higher studies.
Unfortunately, Optionlogy shut down before the MVP could be completed and launched.
Unfortunately, Optionlogy shut down before the MVP could be completed and launched.
Although the product never reached production, the interaction model was validated with experienced traders and established a scalable foundation for building complex trading strategies.
Although the product never reached production, the interaction model was validated with experienced traders and established a scalable foundation for building complex trading strategies.
Looking back
Looking back
When I joined the project, I thought I was simplifying algorithmic trading.
When I joined the project, I thought I was simplifying algorithmic trading.
Instead, I learned that the real challenge was understanding how traders think before deciding how software should work.
Instead, I learned that the real challenge was understanding how traders think before deciding how software should work.
The best interfaces don't remove complexity.
The best interfaces don't remove complexity.
They organize it around the user's mental model.
They organize it around the user's mental model.
That lesson continues to shape how I approach every product I design today.
That lesson continues to shape how I approach every product I design today.
Optionlogy
No-Code Algorithmic Trading
Designing a no-code strategy builder for algorithmic trading
Designed the MVP for a no code strategy builder that helped retail traders create complex trading strategies without writing code.
Designed the MVP for a no code strategy builder that helped retail traders create complex trading strategies without writing code.
Role
Role
Product Designer
Product Designer
Ownership
Ownership
Drove the product from discovery to MVP, leading research, product strategy, UX design, validation, and collaboration with engineering.
Drove the product from discovery to MVP, leading research, product strategy, UX design, validation, and collaboration with engineering.
Team
Team
CEO, CTO, 2 Developers, Me
CEO, CTO, 2 Developers, Me
1 PM, 2 Devs, Me
Timeline
Timeline
3 Months
3 Months