My Own Venture — Founding Engineer & Sole Developer

Novira
Persian-Language Coaching, for Iranians Scattered Across the World

Novira is a coaching ecosystem, not a booking app: coaches in several countries, and one digital product that carries the entire client journey — from the first message through sessions and the follow-up afterwards — with an intelligence layer at its core rather than bolted on as decoration.

Fully Persian, Fully RTL Many Time Zones Privacy as a Design Constraint
View Product Strategic Session

The Problem

Coaching for the Iranian diaspora is a scattered business: the coach in one country, the client in another, and a journey that dissolves into messaging apps and disconnected calendars. The problem was never to build "a booking tool". It was to make the whole client journey — from the moment someone first arrives to the follow-up after a session — one coherent Persian experience, and to lift the coordination burden off the people doing the actual work.

Three Constraints That Shaped Everything

None of them were choices; all three came out of the domain itself.

Persian and RTL, from the ground up

The product is entirely Persian and its users live across several time zones. Right-to-left is not a cosmetic setting here — it reaches down into the design system and into how each session's time is shown to each person.

Privacy, not as a feature

This is mental-health data. That makes privacy a design constraint applied before any other decision rather than an item on a feature list — and it rules out some of the easier paths from the start.

One person, a full product

A single engineer against a domain that usually asks for a team. Velocity had to stay high without spending quality to buy it — and the non-technical team had to run its own work without an engineer in the middle.

The Approach

The answer to "one person, a full product" was not to work more hours; it was to change the unit of work. Documentation became the source of truth and gets written before the code. Every working day ships one defined unit with an explicit definition of done. Nothing merges without clearing the quality gates and a multi-layer review. Building with AI agents supplied the speed — and those same gates are what kept the speed from turning into debt.

How It Gets Built

Five operating rules that shape every working day.

1

Docs as the source of truth

The decision is written before the code. The code implements the document, not the other way around.

2

A daily unit of delivery

Each working day ships one defined piece with an explicit definition of done — never "nearly ready".

3

Mandatory gates

Lint, typecheck and tests against a coverage threshold, all in CI and all blocking. No exceptions, not for one line.

4

Multi-layer adversarial review

Every change passes several independent lenses, then a sceptical pass whose job is to find fault rather than to approve.

5

Agent-assisted, but governed

AI supplies the rate of production; the gates and the reviews decide how much of that output survives.

What Makes It Different

  • Designed Persian and right-to-left from day one, not translated into it later
  • Privacy treated as a design constraint, ahead of every product decision
  • The intelligence layer sits at the core of the product, not at its edges
  • Quality judged by measurable gates, not by the builder's own sense of it
  • A dedicated brand and design system, RTL-first by construction
  • Infrastructure and deployment are part of the product, not a separate stage

Impact

A live productIn real use by coaches and their clients, with online payment enabled.
Continuous deliveryMonths of daily shipping, with quality measured by gates instead of gut feel.
An independent teamThe non-technical team runs its day-to-day work without an engineer in the middle.

Lessons

Writing it down first isn't slower

Deciding on paper before coding doesn't cost time; it moves the thinking from the middle of the work to the front of it. What actually costs time is rewriting something that was never decided in the first place.

A gate with exceptions is not a gate

The first time you accept "just this once", the gate quietly becomes a suggestion. The hard part of quality is holding the rule on the day you are in a hurry.

AI speed relocates the quality problem

Building fast with AI is easy; knowing what got built is the hard part. The answer wasn't to slow down — it was several independent review lenses, each looking for something different.

My Role

  • Founding engineer and sole developer — from the product decision to the last line of code
  • The brand and a dedicated RTL-first design system, plus the whole architecture and implementation
  • Infrastructure and deployment: containers, reverse proxy and TLS, email and monitoring
  • Designing the build process itself — the quality gates and multi-layer review that govern the speed
Key Lesson

One day a security report declared an area closed that was, in practice, open on the live environment. The rule since then: no security claim is accepted without proof against the real environment. A green test is not evidence — only a sign that you haven't looked somewhere yet.

View Novira Live View Other Case Studies