Case Studies

Case studies, not a project gallery

Each case starts with the problem: what was unclear, which constraints mattered, what decisions were made and what operational impact was created.

Open Source

Quant Research Platform

Quant Systems / Data Pipeline / Research Infrastructure
01
Quant ResearchData PipelineBacktestingMLOpen Source
The Problem

Most quant systems have a gap between trading idea and execution: insufficient data, backtests without real costs, strategies without market regime awareness and non-reproducible results.

Constraints

Data quality in 6 layers, execution costs (fee + slippage + 1-bar delay), no look-ahead bias, full reproducibility and modular architecture.

Systems Thinking

The pipeline was designed from hypothesis to report: data → validation → strategy → backtest → walk-forward → Monte Carlo → dashboard.

Architecture

Three-layer architecture: Browser Dashboard / FastAPI / Research Library on Parquet Data Store. 8 strategy families in frozen dataclasses, vectorized numpy/pandas backtesting.

Operational Impact

Trading decisions are grounded in quantitative evidence. Walk-forward and Monte Carlo reveal the difference between a real strategy and a curve-fitted one.

Metrics

CAGR, Sharpe, Sortino, Calmar, Max Drawdown, Win Rate, Profit Factor — all computed with real execution costs.

Key Lesson

A good quant system starts with a hypothesis, not code. When the architecture from data to report is clear, trading decisions have genuine quality.

  • Incremental download from 111+ exchanges with Binance monthly archives and CCXT fallback
  • Vectorized backtesting with real fees, slippage and 1-bar execution delay
  • Walk-forward validation and Monte Carlo for mandatory robustness testing
  • 4 market regime detection with strategy recommendation per regime
  • ML baseline with chronological split and Feature Library with 40+ indicators
  • Open source under MIT license on GitHub
Decision Engines

Trading Bot

Quant / Decision Systems
02
RL / MLRisk ArchitectureContinuous Optimization
The Problem

Trading logic without test architecture, risk control and a live optimization loop.

Constraints

Data quality, drawdown, 24/7 execution, error monitoring, liquidation guardrails and backtest/live mismatch.

Systems Thinking

The strategy was decomposed into hypothesis, risk metrics, execution rules and review cadence.

Architecture

Backtest module, risk layer, execution logic and monitoring dashboard.

Operational Impact

Decisions about continuing, stopping or improving the strategy became clearer.

Metrics

Focus on drawdown, win/loss distribution, exposure and execution errors.

Key Lesson

In quant, decision quality matters more than code quality; code must serve decisions, risk and live monitoring.

  • Decision ensembles with fuzzy control and reinforcement learning
  • Drawdown controls, profit locks and liquidation guardrails
  • Batch optimization and retraining loops in real operations
Health SaaS Platform

Cliniclick

Product Systems / Healthcare Workflow
03
Multi-Tenant SaaSRealtime OperationsHealthcare Workflow
The Problem

Practice operations and patient experience from booking to intake, messaging, settlement and daily reporting needed one connected flow.

Constraints

Patient trust, simple experience, OTP, doctor/secretary/patient roles, precise follow-up and usable data flow.

Systems Thinking

The product was designed as a coordination system between patient, clinic and operational decisions.

Architecture

Workflow, admin panel, data capture and follow-up paths.

Operational Impact

Follow-up and status visibility improved, reducing abandoned opportunities.

Metrics

Response time, follow-up rate, process completion and data quality.

Key Lesson

In healthcare, a good system must be both human and precise; each role should see only what it needs for the next action.

  • Public OTP booking, in-person/online scheduling and appointment lifecycle control
  • Role-specific doctor/secretary/patient panels with real-time internal messaging
  • Integrated financial and admin operations: payments, debtors, expenses and inventory
Medical Ops Platform

Dr. Sadeghizadeh Platform

Smart Clinic Platform + Finance + Inventory + BI
04
Smart PlatformMedical OpsFinanceInventoryLoyalty ClubAI Analytics
The Problem

The clinic needed a multi-role system for scheduling, records, finance, inventory, loyalty and intelligent analytics.

Constraints

Small team, limited time, simple capture, fast reporting, reducing no-show and connecting finance/care operations.

Systems Thinking

The platform needed to simplify team behavior, not create new administrative load.

Architecture

Pipeline, lead status, reminders, reporting and follow-up ownership.

Operational Impact

Sales opportunities became more visible and follow-ups more controllable.

Metrics

No-show under 5%, intake-to-visit cycle under 8 minutes, patient return rate above 35%, lead aging and pipeline status.

Key Lesson

An intelligent platform works when it understands the team's real language and connects to finance, inventory, loyalty and BI.

  • Unified appointment, intake, records and team communication workflow
  • Finance and accounting layer with profit/cost reports and general ledger
  • Clinic inventory with per-service consumption templates
  • Loyalty program with points, referrals and credit redemption
  • Advanced analytics: RFM, churn, no-show and clinic flow
  • SMS automation and follow-up engine to reduce visit drop-off
FinTech Platform

Soodo

FinTech / Product Ops
05
Multi-EngineDelivery ArchitectureProduct Ops
The Problem

A multi-engine signal platform needed to support fast delivery, decision quality and scalable product operations at the same time.

Constraints

Product simplicity, simultaneous web/Telegram/alert delivery, subscription model, admin operations, behavioral data and fast delivery.

Systems Thinking

The design had to make the product usable while enabling learning from users.

Architecture

Product flow, data points, control panel and staged improvement.

Operational Impact

Product decisions were supported by better data and observation.

Metrics

Activation, retention, completion and friction points.

Key Lesson

A good product is not only an interface; it is a learning, delivery and revenue-operations system.

  • Clear separation between generation and delivery layers
  • Simultaneous support for web, Telegram and alert channels
  • Alignment between technical architecture, subscription model and admin ops
AI Business EdTech

mentorima

Custom AI Agents / Product Systems / Business EdTech
06
Personal AI MentorDeep PersonalizationMultilingual (13 locales)Full RTLWCAG 2.2 AA
The Problem

Business owners don't need another course library — they need to understand the exact thing in front of them and act on it without feeling behind. Generic e-learning is cold and one-size-fits-all; generic AI chat is a blank prompt with no memory of their business.

Constraints

Multilingual is the audience, not a feature: Persian by default, 8+ languages and full RTL from day one. A trustworthy core where the user's path, assessment and progress are never guesswork and nothing is faked. And the moment of waiting must feel like care, not an empty spinner — waiting is a designed experience.

Systems Thinking

Rather than a generic chatbot, a coordinated set of specialized AI minds work together around a deep understanding of the user and their business — from getting to know them to guiding their growth path step by step; but the decision-making core always stays solid and trustworthy, and the AI only brings language and warmth, never guesswork.

Architecture

A warm, questionnaire-free onboarding builds a deep understanding of the user that drives a structured session-by-session learning path; what the system learns is narrated in human terms and correctable in one tap, and the user's business is remembered over time so it always picks up right where it should.

Operational Impact

An operator learns exactly what their business needs in their own language, without feeling behind; the product proves itself with a real applied win instead of a certificate, and growth compounds through activation, shared wins and organic SEO.

Metrics

A fully personal path built around the user's own business · 13 locales / 8+ languages with full RTL by default · WCAG 2.2 AA accessibility bar in both themes.

Key Lesson

Personalization is trust: narrated inference feels like care, silent inference feels like surveillance — the moat is emotional, not technical.

  • Remembers the user's business over time and always picks up right where it should
  • Every recommendation is rooted in the user's real context, never a generic script
  • The path re-tunes to the user's real-time understanding — they never fall behind or get bored
  • Narrates what it learns about the user in human terms, correctable in one tap
  • Persian and 8+ languages with full RTL from the first pixel — beautiful and accessible in both themes
Venture Studio Console

Synora Ventures

Venture Studio / AI-Native Products / Operating Model
07
Venture StudioAI-NativeGovernedShared IntelligenceData-Driven
The Problem

Most studios split a pretty marketing site from a mess of spreadsheets that actually run the business, so the story outside never matches the numbers inside. The problem was to make one source of truth serve both.

Constraints

One source of truth feeds both the public and the internal numbers with no divergence. A real governance model — hard rules and decision gates, all traceable. And a no-excuses principle: take the intelligence away, and if the product still stands it was never the studio's to build.

Systems Thinking

Synora builds itself like one of its products: a single source of truth tells both the public studio story and the internal control room — where no number is fabricated. Few studios run themselves this way.

Architecture

Each product follows a clear build → launch → scale path and is weighed at periodic decision gates (continue, adjust or stop); every decision leaves a trace, and what one product learns reaches the rest.

Operational Impact

The pitch and the control room run off one truth that can't be faked; the business is governed by rules and gates instead of vibes, and it becomes a repeatable operating template for every product the studio launches.

Metrics

One source of truth for the public pitch and the internal numbers · AI-native products that don't stand without the intelligence · run by periodic decision gates, not vibes.

Key Lesson

If the marketing numbers and the operating numbers come from the same source, the story is structurally honest — the site can't drift from the business.

  • The pitch and the control room run off one source of truth — proof you can't fake
  • Governed by rules and decision gates, not by vibes
  • Every product has to be genuinely AI-native, or it doesn't get built
  • Shared intelligence across products; every win benefits the rest
MarTech SaaS

Vistaria

AI Agents / Content & Growth Systems / MarTech SaaS
08
SEO & AI VisibilityContent StudioBrand-NativeGrowth AutomationPersian/RTL
The Problem

Small brands can't afford a real marketing team, and generic AI tools produce off-brand, one-off posts with no strategy behind them. The gap isn't 'make an image' — it's the whole chain from understanding a business to shipping a coherent month of content.

Constraints

Persian-first and full RTL, with content that renders Persian script flawlessly — never broken or mangled. A consistent presence across web and Telegram. And transparent AI: everything produced is measurable and controllable, not a black box.

Systems Thinking

Rather than a post generator, a coordinated set of specialized AI minds — each a master of one part, from reading a market to directing the visuals — build content around a deep understanding of the brand; a level of coordination even engineering teams rarely attempt.

Architecture

It starts from a website URL: it sees how Google and AI view the site, plans a month of strategy, and turns any idea into a real, on-brand asset in one click — from SEO articles to Instagram posts — delivered right where the user works (web and Telegram).

Operational Impact

A one-person brand can publish like it has a content team, going from a website URL to a month of scheduled, on-brand content in a single session — and marketing spend becomes metered and governable instead of a black box.

Metrics

A full month of content, planned ahead · three formats — posts, stories and reels — alongside SEO articles · multi-channel presence with fully consistent delivery on web and Telegram.

Key Lesson

The value isn't generating a post — it's owning the whole chain, from understanding a brand to shipping a coherent month of it.

  • See how Google and AI view your site — and get seen right where it counts
  • A full month of content from a single session — from SEO articles to Instagram posts
  • Every piece comes from your brand's own identity, with flawless Persian
  • Any idea becomes a real, publish-ready asset in one click
  • The more you use it, the sharper it gets and the closer to what your audience loves
  • With you everywhere: web and Telegram, delivered exactly the same

Begin

Your problem could be the next case.

Let's start with a strategic session: name the bottleneck and choose the right architecture path.