Experience

A career path that started with code and grew into system design.

This page summarizes projects that grew out of real business needs: from a simple form or manual process to systems that connect sales, inventory, finance, production, support, and management.

What has been built over the years

Much of my experience was shaped in environments where software was not a side tool. It was part of daily work for sales, finance, warehouse, production, support, and management teams. That is why design has to consider code, process, data, and the people using the system every day.

2008 Professional start with ASP.NET and IT work
1500+ Builds across a manufacturing company software set
70+ Companies in Pooya Payvand product experience
Daily Continuous releases during active development cycles
2021 CEO of Pooya Payvand
Manufacturing company

From manual workflows to integrated sales and finance

At the company where I began with website and IT work, inventory, accounting, sales, dispatch, invoicing, and factory coordination gradually became connected. Proforma, stock, production, dispatch, and accounting were no longer repeated manually.

Pooya Payvand

From module programming to financial product design

At Pooya Payvand I started with receivables/payables and sales development, then moved into design, redesign, optimization, and broader financial business system development. Since 2021, that path has continued with the CEO role.

Custom projects

Systems shaped by real client needs

School registration, a construction contractor web app, retail/POS, gate pass, overtime, training, taxpayer reporting, SMS, commercial books, production, and costing all began with problems that needed careful analysis and custom design.

1405

A personal project in preparation

Since Ordibehesht 1405, I have been working on an independent project that is not ready for public introduction yet. If the path goes as planned, the first introduction will happen on this website in the second half of 1405.

Role path

From implementation to design, management, and decision-making

Job titles matter to me when they lead to deeper understanding. Experience in IT, sales, programming, system design, and product management helps me see software beyond code.

2008 to 2020

IT specialist, IT manager, and sales manager at a manufacturing company

Alongside software development, I was close to real business operations. Sales management from 2018 to 2020 gave me a closer view of orders, inventory, representatives, customers, and factory coordination.

2010 to 2015

Programmer and development specialist at Pooya Payvand

I started with smaller development tasks, then implemented receivables/payables, sales, purchasing, and parts of production while working with the senior analysis and design team.

2015 to 2021

Senior system design and development specialist

Gradually I became the main programmer and senior designer, working on new features, legacy redesign, optimization, and stable evolution of financial business systems.

Since 2021

CEO and system designer at Pooya Payvand

I have served as CEO since 2021, while staying close to product design and development, because strong software decisions need both technical and operational understanding.

Project details and experience

This is not just a linear resume. Behind each item was an operational problem that had to become a usable workflow through analysis, design, development, testing, and follow-through.

2008

Website redesign and early internal software projects

In 2008, I was hired to redesign a company website with ASP.NET while also handling IT work. That path soon led to smaller internal software projects and eventually a custom inventory system.

  • Professional start with ASP.NET, web design, and IT support
  • Moved into real internal business needs, not only website appearance
  • Started building a custom inventory system from daily company operations
ASP.NETITInventoryCustom Software
2009 to 2020

Integrating sales, inventory, accounting, and factory workflows

At the same company, accounting and then sales systems were built. A workflow based on faxes, handwritten dispatches, physical papers, and several days of delay became a software flow connecting proforma, factory notification, dispatch, invoice, and accounting output.

  • Turned a multi-day manual process into a traceable flow between sales office, factory, warehouse, and finance
  • Connected inventory and BOM to sales decisions for availability and production timing
  • Expanded the sales system to 15 warehouses and representatives in different cities with central data aggregation
  • More than 1500 builds across accounting, inventory, sales, and after-sales software
SalesInventoryAccountingBOMSQL Server
After-sales

Spare parts, warranty, and detailed inventory movement control

For after-sales service and spare parts sales, a barcode-based system was designed so every incoming and outgoing part could be connected to customer, project, purchase date, warranty status, and repair or replacement flow.

  • Tracked hundreds of thousands of part movements with barcodes
  • Made small and high-volume parts easier to control
  • Reduced waste, human error, and uncertainty around real inventory
After-salesBarcodeWarrantyInventory Control
Since 2010

Parallel start at Pooya Payvand

I joined Pooya Payvand in 2010. I began with smaller development tasks, then around 2011 fully programmed receivables/payables and later sales, based on the senior analysis and design work of the team at that time.

  • Implemented receivables/payables, sales, and later purchasing
  • Built deep familiarity with integrated financial business systems and module relationships
  • Gradually moved from programming into feature design, debugging, redesign, and system analysis
Pooya PayvandReceivablesPayablesSalesPurchasing
2017 to 2026

School registration system and related financial workflows

Around 2017, the school registration system was designed and built. Over the years it was redesigned multiple times and can now receive data through APIs, handle registration, record payment, issue invoice and warehouse dispatch, and remain aligned with financial workflows.

  • Initial design and full development of the registration system
  • Continuous redesign toward a broader and more integrated workflow
  • Connected registration, payment, sales, inventory, and external data through APIs
RegistrationAPIRetailFinancial Workflow
2020

Web development, multi-currency, and multilingual systems

In the second half of 2020, I carried a web project for a construction contractor from analysis to design and development, using Ionic and Angular on the frontend and a C# handler backend. Around the same period, Pooya Payvand accounting became multi-currency and the financial systems became multilingual.

  • Analyzed, designed, and developed a full web project over about six to seven months
  • Added multi-currency accounting and multilingual financial systems
  • Improved product readiness for more diverse client needs
IonicAngularC#Multi-currencyMultilingual
Since 2021

Retail/POS and continuous financial product development

Around 2021/2022, retail/POS capabilities were added and continued evolving with the rest of the modules. Barcode scanner, card reader, receipt printer, finance, and inventory workflows all had to fit inside the main product.

  • Developed retail/POS capabilities alongside financial business systems
  • Coordinated retail devices with finance and inventory processes
  • Continued product growth through regular releases and real client needs
RetailPOSBarcode ReaderFinancial Systems
2023 to 2025

Factory operational subsystems and legal requirements

For a manufacturing company, multiple operational and legal subsystems were developed: gate pass, goods entry/exit, overtime requests, training, taxpayer reporting, SMS, and commercial books.

  • Gate pass for raw materials, finished goods, repair parts, and vehicle information
  • Overtime request system connected to attendance data to compare approval and actual presence
  • Training system connected to personnel, positions, courses, attendance, scores, and certificates
  • Added taxpayer reporting, SMS, and commercial books subsystems to the product
Gate PassOvertimeTrainingTaxpayer SystemSMS
Since 2023

Production and costing systems

In 2023, a base production and costing system was written to create production plans and calculate formula-based costs. Since 2024, a custom production system has also been developed with new analysis by the team and my programming work, and is now moving toward client delivery.

  • Designed a general production system with production plans and formula-based costing
  • Developed a custom production system for a factory's specific needs
  • Placed areas such as laboratory and calibration inside a coherent production flow
ProductionCostingFormulaCalibrationLaboratory
In progress

Web-enabling Pooya Payvand integrated financial business systems

One of my most important current tasks is preparing the web path for Pooya Payvand financial business systems: preserving the existing core, backend, and database while building an interface that can connect the product to a React frontend.

  • Preserving existing software investment instead of rushing into a rewrite
  • Designing the connection path between the current core and a React frontend
  • Moving step by step from Windows systems toward a web experience
ReactWeb EnablementLegacy CoreEnterprise Systems
Since Ordibehesht 1405

Personal economic project in development

Based on years of experience with financial business systems, process, data, and product work, I started an independent personal project in Ordibehesht 1405. Details are not public yet, but the goal is to introduce a test version through this website in the second half of 1405.

  • Focused on product design and real user experience
  • Preparing for public introduction after a presentable version is ready
  • Showing the ability to carry an independent project from zero to release
Personal ProjectComing SoonProduct Design1405

Working style

Follow-through, calm, and clear problem understanding

In professional work, I care that the client feels the problem has been heard and that the path will not be abandoned. I try to work patiently, clearly, and persistently, instead of rushing in ways that create future cost.

  • Before implementation, the problem and workflow must be understood well.
  • A system should work for today and not run out of room tomorrow.
  • Support and follow-through are part of quality, not an extra task.
  • Less noise, more focus, and reliable delivery.