Hossein SafaverdiArchitect & Founder
CVMessage me

Open — taking on 1–2 engagements

Software Architect & Startup Builder

Hossein Safaverdi

I spent six years building the payment and platform systems other companies run on. Now I am building my own — and leading the people who build them with me.

Architect, founder and technical lead. Companies in the US and Europe bring me in when money moves through their product and the architecture has to be right the first time. Between engagements, my own team and I are building three products of our own.

Start a conversation on TelegramRead the one-page CVLinkedIn
  • Tehran, Iran — working remote across US & EU time zones
  • .NET · Python · payment infrastructure
  • English & Persian
Shipping production systems
6 yrs
Own ventures in build
3+
Engineers I lead across projects
Several
Clients and collaborators
US · EU

Where I am going

From writing the systems to owning them.

I started where most engineers start — inside other people's products. Six years of that put me in the rooms where the expensive decisions get made: a payment gateway that cannot drop a transaction, a core-banking service that has to satisfy an auditor, an ERP that five departments depend on before lunch.

What I learned there is that the architecture is the business. The companies that move fast are the ones whose systems let them; the ones that stall are almost never stalled by a missing feature.

So I stopped selling hours and started building. Today most of my income comes from a small number of independent engagements I choose deliberately, and the rest of my time goes into three products of my own with a small engineering team behind them. The direction is not a secret: I intend to own the companies I build.

  1. 2018

    Getting started

    Teaching myself to build, taking on whatever work would have me. Two years of shipping small things badly, then less badly.

  2. 2020

    Engineer

    APIs, warehouse systems, access control. Learning what production actually costs.

  3. 2022

    Senior engineer

    Leading an ERP platform across five departments — the first time the design decisions were mine to make.

  4. 2024

    Architect

    Payment gateways and core banking as lead architect — setting the boundaries and standards other engineers build against.

  5. Now

    Owner

    Three products of my own, a small team, and a short list of clients I partner with rather than work for.

Ventures — in build

Three products, none of them launched yet.

I am founder and architect on all three. They are deliberately described here without names or screens — they are in private build, and the parts that matter are the shape of the problem and the size of the market, not the logo.

Serious enquiries about any of the three: message me and I will walk you through it directly.

Venture 01

Accounting and ERP for the businesses that outgrew the spreadsheet

A full accounting and operations platform — ledgers, documents, receivables and the reporting a real business runs on — built as a clean-architecture service with a customer app, an operator console and a public site generated from one API contract. I led ERP at enterprise scale for someone else first; this is the same rigour aimed at the companies that were never offered it.

Why it can work: accounting software is bought once and kept for a decade, and the mid-market underneath the enterprise vendors is the largest and least-served part of it.

Role
Founder · architect · product owner
Stage
Private build, pre-launch
Venture 02

Audience operations for teams who live inside messaging

A multi-tenant SaaS for organisations whose audience lives in messaging rather than in feeds: workspace-isolated data, subscription plans and billing, channel and bot administration, and an operator console behind all of it. Tenant isolation is enforced in the data layer, not hoped for in the UI.

Why it can work: the messaging-first market has real budgets and almost no serious tooling, and every workspace added is recurring revenue.

Role
Founder · architect · product owner
Stage
Private build, pre-launch
Venture 03

An AI assistant that has to prove every claim it makes

A professional-services assistant that answers questions over a curated body of source material and cites it — with a verifier that resolves every citation against the corpus and strips the ones it cannot, so an invented reference never reaches the reader. Around it: document OCR, drafting, deterministic calculators, metered usage, and a marketplace that hands the case to a real professional the moment it stops being a question.

Why it can work: verifiability is the only defensible position in this category, and the marketplace monetises intent at the exact moment it appears.

Role
Founder · architect · product owner
Stage
Private build, pre-launch

Selected work — client engagements

Four systems I was trusted with, and what came out of them.

  1. Payments · USA

    One payment layer, indifferent to the processor behind it

    Designed a provider-agnostic payment platform over Stripe and NMI — SetupIntents, vaulting and tokenization, webhook-driven state — so the business can change processor without changing its product. Transactional flows on Celery and Redis, metrics and strict typing throughout.

    Django / DRFPostgreSQLCelery · RedisStripe · NMIProvider abstraction

  2. FinTech · Iran

    A payment gateway and a core-banking platform, as lead architect

    Owned the architecture for secure, fault-tolerant transaction processing across multiple providers, and set the microservice boundaries and technical standards a team of engineers built against — under PCI-DSS-aware constraints, on systems where an outage is a news story.

    MicroservicesDistributed systemsHigh availabilityPCI-DSS aware

  3. Platform · Europe

    A .NET 10 service estate, delivered end to end

    Built and shipped the whole surface for a European client: a webhook-driven messaging bot service, an embedded web client over REST and OpenAPI, internal admin APIs and crypto-gateway integrations — containerized, with CI/CD from the first commit.

    ASP.NET Core · .NET 10EF CoreDocker ComposeCI/CD

  4. ERP · Iran

    Five departments on one platform

    Led an ERP covering call centre, trade, accounting, procurement and sales for a commodity trading business — then spent the following year making it faster and safer under real-time transaction volume, and rewriting the internal workflows it had inherited.

    Domain modellingHigh-volume dataProcess designTeam lead

How I work with clients

Three ways in. All of them start with a conversation.

I take on a small number of engagements at a time, because the work I am good at is the kind you cannot do at arm's length. If your product moves money, holds regulated data, or has quietly become harder to change every month, that is my territory.

What every engagement includes

  • A written architecture your team can argue with, not a slide deck
  • Decisions explained in terms of cost, risk and speed
  • Code, tests, CI and observability in the same delivery
  • Direct access to me — no account manager in the middle

  • Architecture review

    1–2 weeks · fixed fee

    I read the code, talk to the team, and hand back a plain-language assessment: what will break first, what is costing you velocity, and the three changes worth making before you hire anyone. Often the cheapest month a founder spends.

  • Build and lead

    3–6 months · retainer

    I design the system and build the hard parts myself — payment flows, provider integrations, the data model everything else rests on — and lead your engineers, or mine, through the rest of it. You end with a running product and a team that understands it.

  • Technical partner

    Ongoing · monthly

    The fractional-CTO arrangement, without the theatre: I own the technical direction, sit in the decisions that have a price tag, hire and review the engineers, and keep the roadmap and the architecture pointing the same way.

Leadership & team

A small team, and the standards they build to.

I lead a small team of engineers across my own ventures and client projects. Small on purpose: I would rather have a handful of people who own their work end to end than a dozen waiting for tickets.

My job in that room is to make the expensive decisions early, write them down, and then get out of the way — and to be the person who says no when a shortcut will cost us a rewrite.

  1. Decisions are written, not remembered

    Every non-obvious choice gets a paragraph explaining why. It is how a small team moves like a much larger one.

  2. Everyone owns something whole

    A service, a surface, a domain — with the authority that comes with it, and the review that keeps it honest.

  3. I still write the hard parts

    Payment flows, data models, anything with money or compliance in it. Leading is not an excuse to stop being an engineer.

Track record

Six years, on record.

Payments, banking, ERP and platform work — for employers, then for clients, now alongside my own companies.

Open the one-page CV

  1. 2025 — now

    Independent

    Founder, Software Architect & Technical Lead

    Own ventures & selected client engagements

    • Founded and architect three products of my own, leading a small engineering team across them.
    • Independent engagements are now the majority of my work — architecture, payment systems and delivery leadership.

  2. 2025 — now

    LeadFi

    Backend Engineer — Remote, USA

    Payments

    • Built a provider-agnostic payment layer over Stripe and NMI — SetupIntents, vault and tokenization, webhooks — on Django / DRF, JWT and PostgreSQL.
    • Implemented transactional payment flows on Celery and Redis, with Prometheus metrics and strict typing throughout.

  3. 2025 — 2026

    European client

    Backend Engineer — Remote, Europe

    Platform & integrations

    • Designed and delivered services on ASP.NET Core (.NET 10), EF Core, PostgreSQL and Redis, deployed via Docker Compose and CI/CD.
    • Built a webhook-driven messaging bot service, an embedded web client over REST / OpenAPI, internal admin APIs and crypto-gateway integrations.

  4. 2025 — 2026

    Hami System Sharif

    Senior Backend Developer — Lead Architect

    Payment gateway & core banking

    • Led the architecture and development of payment-gateway systems — secure, highly available, fault-tolerant transaction processing.
    • Acted as senior architect on core-banking projects, defining microservice boundaries and the technical standards the team built to.
    • Designed distributed payment services across multiple providers under PCI-DSS-aware constraints.

  5. 2022 — 2025

    AhanOnline

    Senior Backend Developer

    ERP & trade platform

    • Led an ERP platform spanning call centre, trade, accounting, procurement and sales.
    • Hardened security and performance across real-time transactions and high-volume data, and rewrote the internal workflows around them.

  6. 2020 — 2022

    AhanOnline

    Backend Developer

    Warehouse & inventory systems

    • Built a warehouse management system in Nest.js and TypeScript, with REST APIs for inventory and order management.
    • Implemented role-based access control and security practices across the stack.

Capabilities

What I bring to the table.

Architecture

Distributed systemsMicroservice boundariesEvent-driven designCQRS · MediatRClean ArchitectureDomain & data modelling

Payments & FinTech

Gateway architectureStripe · NMITokenization & vaultingWebhook reliabilityPCI-DSS aware designCore banking

Build & run

ASP.NET Core · .NET 10C# · Python · TypeScriptDjango / DRFPostgreSQL · SQL ServerRedis · CeleryDocker · CI/CDObservability

Leading & owning

Technical leadershipHiring & reviewProduct ownershipRoadmap & scopeClient & stakeholder workB.Sc. Business Management

Contact

Tell me what you are building.

Telegram is the fastest way to reach me — I answer there myself, usually the same day. A paragraph about the product and where it hurts is enough to start.

@HosseinSafaverdisafaverdi.hossein@gmail.com
Based in
Tehran, Iran
Works with
US & EU time zones
Engagements
Review · Build & lead · Partner
Elsewhere
LinkedInCV
© 2026 Hossein Safaverdi — Software Architect & Startup Buildersafaverdi.ir · Tehran, Iran