Welcome to Saeid Shamsaei's portfolio.
SAEID SHAMSAEI.
Portrait of Saeid Shamsaei

SAEID SHAMSAEI

I make complex digital systems feel considered, useful and human.

THE PERSON BEHIND THE WORK

ARCHITECTURE. PRODUCT. PEOPLE.

I'm Saeid Shamsaei, a software solutions architect and technical product lead. I turn complex ideas into software systems — connecting business needs, architecture and delivery.

Five years of independent work across SaaS, e-commerce and specialist platforms. I focus on useful products, clear technical decisions and thoughtful execution.

BORN18 AUG 2001
EXPERIENCE5 YEARS
EDUCATIONB.E. COMPUTER ENGINEERINGBabol Noshirvani University of Technology
SaaS Architecture · Product Leadership · AI-assisted Delivery

I BUILD DIGITAL
THINGS THAT MATTER.

I design useful digital products — thoughtful experiences built on dependable engineering.

COMPLEX IDEAS.
CLEAR EXPERIENCES.

A clear problem, a considered interface and the systems underneath it. Every decision serves a purpose.

ARCHITECTURE.
PRODUCT.
PEOPLE.

From the first line of code to the full product experience, I build for people and for what comes next.

Behind the work.

01 / GARTAL01 / 03
01 / THE PROBLEM

A client inquiry is not a product platform.

The studio needs service-specific pages and a reliable way to receive project briefs. The separate product platform needs shared contracts without forcing independent applications into a single runtime.

  • Client task: choose a service and send a brief
  • Engineering task: avoid duplicating product contracts
01 / GARTAL02 / 03
02 / IMPLEMENTATION

Next.js intake. Versioned product contracts.

GARTAL-SITE uses Next.js service routes and a validated lead API with PostgreSQL and Drizzle. Gartal-Platform separately defines contracts for administration, servers, commerce and industry packs.

  • Zod validation on project requests
  • Separate admin, server and storefront boundaries
01 / GARTAL03 / 03
03 / WHAT IS VERIFIED

Source exists. Launch results need proof.

The repositories contain service routes, inquiry handling and industry-pack descriptors. A production launch, paying customers or completed cross-product integration cannot be concluded from source files alone.

  • Evidence: GARTAL-SITE and Gartal-Platform repositories
  • Status: implementation documented; deployment not certified
02 / AI Development Factory01 / 03
01 / THE PROBLEM

A GitHub commit does not update a Windows checkout.

Managing many repositories creates two different states: the remote revision and what the owner’s machine actually has. Uncommitted local files also need protection during synchronization.

  • Check remote and installed revisions separately
  • Never overwrite local edits to make a dashboard look green
02 / AI Development Factory02 / 03
02 / IMPLEMENTATION

One Windows Worker. Guarded Git synchronization.

The local Worker monitors active repositories, distinguishes pull and push needs, and uses fast-forward operations when safe. A loopback dashboard reports sync status; dirty or diverged checkouts require review.

  • GitHub remains source of truth
  • One local Worker; explicit Git state and lifecycle
02 / AI Development Factory03 / 03
03 / WHAT IS VERIFIED

Report NOT_TESTED when no test ran.

Guardian evidence is tied to Git metadata and can identify unverified work. Under current owner policy, the Worker does not automatically run CI, builds, tests or previews; a pushed commit is not a release.

  • Evidence: AI-Development-Factory and Guardian contract
  • Manual acceptance remains separate from repository sync
03 / DigiRezhim01 / 03
01 / THE PROBLEM

Patient records and nutrition rules need one reviewable workflow.

Physicians need to handle registration, patient context and diet planning in connected steps. Clinical nutrition workflows also depend on scientific rules that must be reviewed rather than hidden inside UI defaults.

  • Physician identity and patient context
  • Clinical rule exceptions require expert review
03 / DigiRezhim02 / 03
02 / IMPLEMENTATION

Four services, with distinct clinical responsibilities.

DigiRezhim separates public web, doctor and admin views, and API services. Next.js and NestJS use PostgreSQL, Prisma and Redis to connect access control, patient records and nutrition workflow entry points.

  • Separate admin and clinical access surfaces
  • Structured persistence for physician workflows
03 / DigiRezhim03 / 03
03 / WHAT IS VERIFIED

Clinical acceptance is not a code-only decision.

Repository documentation covers doctor dashboards and Excel-to-UI rule migration. Medical accuracy, unresolved source-data exceptions and production compliance still need physician and operational verification.

  • Evidence: DigiRezhim repository and doctor dashboard
  • No unsupported clinical efficacy or certification claims
04 / Petiwoo01 / 03
01 / THE PROBLEM

A pet catalog must reflect species and real stock.

Pet buyers browse by animal, category and product suitability. Storefront navigation must also show relevant prices and availability instead of treating every product as the same generic listing.

  • Species and category-driven discovery
  • Availability matters before checkout
04 / Petiwoo02 / 03
02 / IMPLEMENTATION

Catalog APIs connect product pages to the cart.

The Next.js storefront provides search, product details, categories, basket and checkout routes. Commerce APIs supply catalog data, while Zustand manages local basket state and quantity calculations.

  • Product and brand data come from APIs
  • Cart quantities and totals are computed in state
04 / Petiwoo03 / 03
03 / WHAT IS VERIFIED

Checkout code is not evidence of completed sales.

Source files confirm catalog pages, cart state and order-request pathways. Real payment processing, fulfilled orders and sales performance must be tested against deployed services, not inferred from a route.

  • Evidence: Core-Petshop-Store and platform contracts
  • No fabricated revenue, customers or conversion rates

Let's build something that matters.