Skip to main content
Amey Joshi

01 / Unresolved

Business

Make the journey clear and shippable.

Compliance

Keep every decision traceable.

Engineering

Define what the architecture must carry.

Operations

Design the exception, not only the happy path.

Business Analyst · Banking & Fintech

Amey JoshiComplexity in. Clarity out.

I turn business intent, regulatory constraint and technical reality into one system teams can ship.

02 / Translation

One requirement. Five changes of state.

Intent

What the business is actually trying to change.

03 / Rails

The customer sees a result. The system sees every leg.

  1. 01

    Agent network

    Agent cash-in

    The instruction enters the rail.

  2. 02

    Payment rail

    IMPS / NPCI switching

    The instruction is routed toward the beneficiary bank.

  3. 03

    Beneficiary bank

    Beneficiary credit

    The receiving account is credited or returns a result.

  4. 04

    Operations and ledger

    Reconciliation

    The final state is matched across every leg.

If one leg fails, which state becomes the shared truth?

04 / Cutover

Cutover: parallel work. One release window.

Release window open — five of five ready

  1. 01

    Business

    Scope and operational readiness

  2. 02

    Engineering

    Build and integration readiness

  3. 03

    QA

    Validation evidence and defect decisions

  4. 04

    Infrastructure

    Environment and execution readiness

  5. 05

    Vendors

    External dependencies and coordinated handoffs

05 / Evidence register

The decision trail is the portfolio.

Premise, constraint, contribution and evidence—published only when the facts and disclosure boundary are clear.

Publication boundary / Active

No borrowed certainty.

Engagement dossiers enter this register only after scope, contribution and public facts are verified. Until then, the domain map and work register state exactly what is known.

06 / Before the bank

The work had a name later.

Curiosity became software, a company and a second beginning before it became Business Analysis.

  1. 01

    The 2000s · Kodoli

    Curiosity with a keyboard.

    Games came first. Then the machines running them. Weekends meant LAN cables, Counter-Strike and Dota—and a question that stayed: how does all of this actually work?

  2. 02

    Bharati Vidyapeeth · BCA

    We wanted a company.

    A final-year Office Automation System became something the college actually deployed. Real people depended on software Amey and his co-founder had built.

  3. 03

    2019–2024 · Kolhapur

    Build first. Learn what the work demands.

    Zenox Technologies began in a rented apartment. With no clients in year one, the team kept making—then word of mouth turned experiments into sustained delivery work.

  4. 04

    2020–2021 · Two red signals

    The doors closed. The work did not.

    COVID erased projects overnight. RB Esports then opened from a belief in gaming, survived a second lockdown and reopened with a broader hardware business.

  5. 05

    Late 2023 · The interchange

    A career change that named the work already happening.

    Across projects, the recurring role was asking why, structuring scattered ideas and standing between a business problem and its technical answer. Business Analysis gave that pattern a name.

  6. 06

    2024 onward · Mumbai

    Startup speed. Enterprise responsibility.

    Banking added compliance, audit, security, operations and regulators to every delivery decision. The aim now is to keep the instinct to build while working at greater scale.

Read the complete human route

07 / Open line

Bring me the complicated version.

The one with competing constraints, real operational consequences and more than one team holding part of the truth.