THE TEAM BEHIND TRADETURE

One Engineer.
Two AI Collaborators.
Zero Guesswork.

Tradeture isn't a ten-person startup, and it isn't someone “vibing” an app into existence with no idea how it works. It's engineered — the same way I've spent more than a decade engineering mission-critical systems for the world's engineering teams — now pointed at trading automation, with Claude and Gemini doing a lot of the typing.

Ric, flanked by Claude and Gemini Ric — with Claude (left) and Gemini (right), his AI engineering collaborators

FOUNDER

Ric M.

Founder & Systems Engineer

For more than a decade, my job has been standing up and administering the engineering systems that large design and construction teams run on every day — the platforms that plant designers, structural engineers, and process engineers build their deliverables in. I've worked on onshore and offshore oil & gas, pharmaceutical, biotech, and mining & minerals processing projects, for teams spread across the globe.

That work was never just "install the software." It was designing the workflows, building the third-party tools that closed the gaps out-of-the-box software leaves open, and putting rules and gate metrics in place so a hundred engineers producing thousands of deliverables still ship consistent, correct work — because in this industry, a mistake that slips through isn't a bug report, it's a multi-million-dollar problem.

Tradeture is that same discipline, pointed at a new problem: trading failure. I'm not a stranger to complex systems or to holding a high bar for quality — I've just spent my career enforcing that bar for other people's engineering. Now I'm building it for traders, with myself as the sole engineer and Claude and Gemini as my AI collaborators.

MORE THAN A DECADE OF EXPERIENCE
GLOBAL PROJECTS
OIL & GAS · ONSHORE & OFFSHORE
PHARMACEUTICAL & BIOTECH
MINING & MINERALS PROCESSING
WORKFLOW & QUALITY-GATE DESIGN

HOW THIS GETS BUILT

Engineered. Not “Vibed.”

If you've spent any time online, you've seen the phrase “vibe coding” — someone with no technical background prompting an AI until something looks like it works, with no real idea why it works or when it'll quietly break. That's not what's happening here.

For over a decade, my actual job has been close to the opposite of that: setting up the systems, defining the workflows, and enforcing the quality gates that keep engineering teams from shipping mistakes on projects worth real money, all over the world. I know what a real gated review process looks like because building them has been my profession.

Claude and Gemini are the tools I use to move fast — architecture, code, debugging, content, a second opinion when I need one. But every decision, every review gate, and every line that ships to production is mine to own. I'm not vibing Tradeture into existence. I'm engineering it, the same way I've engineered every system I've ever been trusted with — just with the best AI copilots available doing more of the typing.

BUILT WITH

AI Collaborators

Claude — by Anthropic

My primary engineering partner. Architecture decisions, the 3D platform tour you just walked through, production code, debugging deep cross-platform issues, and keeping a thousands-of-lines codebase consistent as Tradeture keeps growing.

Gemini — by Google

My second opinion. Research, alternate approaches, and a sanity check on decisions before anything ships — two independent AI perspectives instead of relying on just one.

Tradeture is independently built and operated by its founder. Anthropic and Google are not affiliated with, and do not endorse, Tradeture.

One engineer. Two AI copilots. A platform built to last.