HPN Deep-Tech · TRL 5 → TRL 6
01 / 13

2Signals

From idea to a tested strategy — without writing code

Build and backtest in your browser. Run it anywhere with Freqtrade.

CUSTOMER PROBLEM
02 / 13

A trader has a strategy, but can’t automate it.

They know indicators and have their own rules, but testing and automation require code and multiple tools.

01

Too many separate tools

The idea moves between a chart, code, a backtester and bot configuration.

02

Every change creates more work

Changing a rule or parameter means coding and testing it again.

03

A tested strategy is not a bot

It still has to be deployed, configured and started.

idea on a chart

coding

separate backtester

bot configuration

Takeaway

The customer pays for a faster, safer path from an idea to a tested strategy ready to run.

SOLUTION
03 / 13

2Signals turns an idea into a tested strategy ready to run.

ONE WORKFLOW

From idea to a strategy ready to run.

Build rules visually, backtest locally and export without rewriting the strategy.

01

Idea

Entry, exit and strategy assumptions

02

Build

Visual strategy creation without code

03

Backtest

Signals, trades, results and risk

04

Iterate

Change parameters and test again

05

Export

Move to Freqtrade without rewriting the logic

Takeaway

2Signals connects strategy creation, backtesting and export in one workflow.

WORKING PRODUCT
04 / 13

The MVP enables visual strategy building, backtesting and analysis.

Working 2Signals Builder with backtest results
01

Visual strategy rules

Entry and exit logic built without code

02

Local backtesting

Signals, trades and results calculated in the browser

03

Interactive analysis

Rules, triggers and results visible on the chart

Takeaway

The core product workflow already works — from visual rules to backtest results. Controlled tests confirmed agreement with Freqtrade for selected scenarios.

CUSTOMER & PILOT
05 / 13

The initial customer segment is active traders who want to automate strategies without code.

INITIAL SEGMENT

A TradingView user ready to automate

They have their own rules and understand indicators. The barriers are code, multiple tools and no simple path from testing to deployment.

Validation status

The public demo and Lesson 1 are live. The pilot will validate willingness to pay, repeat usage and retention.

01

Defines rules

Builds entry and exit logic without Python

02

Tests the idea

Reviews signals, trades, results and risk

03

Refines the strategy

Changes parameters without rewriting the logic

04

Exports

Moves the strategy to Freqtrade within the supported scope

Takeaway

The product works; the pilot will validate willingness to pay and repeat usage.

COMPETITION & POSITIONING
06 / 13

Existing tools cover parts of the workflow.2Signals connects them into one process.

TradingView

Chart analysis, indicators and strategy ideas.

WORKFLOW LIMITATION

Automation and execution require an additional workflow.

Freqtrade

Backtesting and execution of strategies expressed in code.

WORKFLOW LIMITATION

Building and modifying strategies requires working with code.

Automation platforms

Bot and rule creation inside a managed environment.

WORKFLOW LIMITATION

Export and control over strategy logic and execution environment may be limited.

2Signals

Visual strategy building, local backtesting, analysis and Freqtrade export.

DIFFERENTIATOR

One workflow with the option to run the strategy in an open execution environment.

Takeaway

2Signals does not replace the execution environment — it shortens the path from an idea to a tested strategy ready to run.

INNOVATION & ARCHITECTURE
07 / 13

The R&D project formalises the strategy logic already used by the working product.

WORKS TODAY

visual rules

local backtesting

results and iteration

R&D SCOPE

versioned strategy representation

dependency graph

selective computation

SUPPORTED SCOPE

Freqtrade export

Further development

AI and integrations

experiment result data

Takeaway

The working product is the starting point. R&D formalises the strategy representation and extends where it can be used safely.

STRATEGY LOGIC FLOW
08 / 13

One strategy logic — from a visual rule to Freqtrade export.

WORKS TODAY

Visual rule

The user builds strategy logic without writing code.

Visual rule fragment in the 2Signals Builder
R&D SCOPE

Versioned strategy representation

A readable form of the same logic for the Builder, testing, AI and export.

(EMA[high](20) + (ATR(14) * 0.5))
/\ BBANDS[high](2, 2, 0, 20).upperBand
WORKS WITHIN THE SUPPORTED SCOPE

Freqtrade export

Supported rules are translated into code without manually rewriting the logic.

dataframe.loc[
  qtpylib.crossed_above(
    dataframe['EMA[high](20)'] +
      (dataframe['ATR(14)'] * 0.5),
    dataframe['BBANDS[high](2, 2, 0, 20).upperBand']
  ),
  'enter_short'
] = 1

Takeaway

One logic connects strategy creation, testing and export.

TRL 5 & TECHNOLOGY RISKS
09 / 13

TRL 5 confirms feasibility; it does not remove technology risk.

What works today

visual rules

local backtesting

results and trades

export within the supported scope

Risk → mitigation

Risk

Lower-end devices

Mitigation plan

profiling and a low-load mode

Risk

Growing memory use

Mitigation plan

limits, data removal and selective computation

Risk

Builder, testing and export consistency

Mitigation plan

shared representation and automated equivalence tests

Risk

Multi-asset / multi-timeframe

Mitigation plan

gradual expansion of supported scenarios

Takeaway

The project focuses on open problems that cannot be solved by merely scaling the current MVP.

R&D PLAN & PATH TO TRL 6
10 / 13

Four R&D packages advance 2Signals from TRL 5 to TRL 6 in 6–9 months.

WP1M1–2

Strategy language

How can the same logic be preserved across building, testing and export?

Outcome

Versioned strategy representation

WP2M2–4

Selective computation and memory

How can only the elements affected by a change be recomputed?

Outcome

Measurement of computation time and scope

WP3M4–6

Validation and equivalence

How can results be verified across device classes and scenarios?

Outcome

Testing across device classes

WP4M6–9

AI and experiment data

How can AI propose variants while validation and execution remain deterministic?

Outcome

Validated variant-proposal workflow and structured experiment data

TRL 5
TRL 6

Takeaway

Each package addresses a defined question and ends with a measurable result leading to TRL 6.

ECOSYSTEM & BUSINESS MODEL
11 / 13

TradeEngine is the core of 2Signals.The other modules extend education, community and AI.

2Signals'

ECOSYSTEM

TradeEngine by 2Signals

TradeEngine

Strategy building, backtesting, optimisation and export.

Working core · R&D

TradeLearn by 2Signals

TradeLearn

Interactive education.

First lesson works

TradeHub by 2Signals

TradeHub

Publishing and developing strategies.

Planned development

TradeAI by 2Signals

TradeAI

Support for strategy building and analysis.

Planned R&D layer

Model and revenue

01

Free

Entry point

02

Pro — from USD 9.99

Complete strategy workflow

03

AI, higher limits and advanced optimisation

Service expansion

04

API and partner licensing

Offer for organisations

Takeaway

Pricing and plan scope will be validated during the pilot. Local computation is intended to reduce per-user infrastructure cost — not eliminate it.

TEAM, BUDGET & IP
12 / 13

The founder built the MVP independently.The grant funds the team, R&D and IP protection.

Ability to execute

Aleksander Froncz

Aleksander Froncz

Founder | Lead Software Engineer

13+ years of experience

Built a working 2Signals MVP independently

Experience in scalable web and mobile systems.

Team + IP

Code and documentation belong to the project.

A formal IP protection strategy is planned.

Licences and dependencies will be documented.

PLN 300k budget

Engine and languagePLN 85k
Dependencies and performancePLN 55k
AI/MLPLN 40k
Research infrastructurePLN 35k
ExpertsPLN 35k
HardwarePLN 15k
PilotPLN 20k
IP and legalPLN 15k

Hardware cost eligibility requires confirmation in the programme documentation.

Takeaway

Commercialisation is one project result; most of the budget directly funds measurable technology work.

FUNDING & OUTCOMES
13 / 13

We are raising PLN 300k for 6–9 months to reach TRL 6 and launch a pilot.

Funding requested

PLN 300k

Project target

6–9 months → TRL 6

01

versioned strategy representation connecting visual creation, testing, AI and export

02

validated selective computation across device classes

03

documented correctness and performance boundaries

04

user pilot and validated commercial model

Takeaway

After the programme: a TRL 6 engine, documented validation boundaries, a completed user pilot and a commercialisation decision.