Automated strategies
Design, coding and go-live of quantitative strategies: explicit rules, risk management written down before the first order, and validation against market data rather than fitted curves.
Valencia · building software since 2008
Built in days.
Running for years.
What used to take months of development now ships in days: AI changed our speed, not our standards. Behind every delivery there are twenty-five years of engineering, and systems still running when nobody is watching.
What we do
Three things, and all three properly.
We don't sell hours: we deliver systems that run on their own and that somebody has to be able to maintain afterwards.
Custom development
Business applications end to end, with Java and Spring on the back end and React on the front. Architecture that outlives its first year, and code you can read without a manual.
Software and AI consulting
Where a model genuinely fits your process, and where it only adds cost. Architecture reviews, task automation, and teams that learn to work with agents without depending on them.
Products
What we publish under our own name.
Two product lines of our own, born out of problems we had in front of us.
Trading
Tradegun
The umbrella for our market tools: roboadvisors, indicators and automated strategies for people who trade with a method and want to stop relying on their nerve.
- C# strategies for ATAS, on CME micro futures
- Order block, breakout and retest indicators
- Daily portfolio and market sentiment reports
- Daily loss limit and position sizing designed in, not bolted on
Business management
Turnera
Diary, client record, session packs and payment for businesses that work by appointment: clinics, beauty salons, physiotherapists and personal trainers. It finds the gap and puts the appointment in it.
- Appointments, services, products and till on a single screen
- Session packs and outstanding balance per client
- A portal where clients book their own slot
- One installation per business, with its data in its own house
Contact
Tell me what you're working on.
Describe the problem in two lines. I read it myself, not a shared inbox: if it fits I'll tell you how I'd approach it, and if it doesn't fit I'll tell you that too.