73 case studies · 7 areas
The work behind the projects
Explore how business needs became software: the problem, implementation decisions and evidence available for each project. Start with the area closest to your challenge.
What to look for in each case study
Each page explains the business problem, delivered scope and engineering decisions. Results reflect the evidence recorded in that write-up; delivery stages and measurement limits vary by project.
Experience and responsibilitiesCommerce platforms and applications
Storefronts, supplier integrations and operational applications.
Javaherian commerce platform
Led development of the WooCommerce watch and jewellery store, combining custom modules, product discovery, CRM workflows and management reporting. The case study explains the platform responsibilities and improvements to storefront performance and daily sales operations.
Live-store development
Read case study →Watch marketplace architecture
Designed marketplace workflows for seller intake, operator review, certification, reservations and custody. The case study documents implementation of the seller route; the public GitHub showcase presents architecture and state boundaries without claiming a complete marketplace launch.
Architecture and seller-route implementation
Read case study →Jeweltimeco retail operations PWA
Built and supported an installable web app for catalogue browsing, assisted ordering and staff workflows. It reads product and media information from WooCommerce while keeping customer, order and inventory operations in its own application data model.
Operational web app with ongoing support
Read case study →Reservation and deposit foundation
Developed a reservation foundation with configurable capacity and time rules, payment-confirmation handling and a recorded status history. Repeated payment callbacks are handled consistently. The documented scope reaches deposit and reservation; delivery and settlement belong to later stages.
Implemented reservation foundation
Read case study →Supplier-connected API sales workflow
Designed a sales workflow for supplier-held inventory that separates the displayed price from the price confirmed when an order is committed. Supplier confirmation and margin checks belong to the order path, with exceptions routed for review.
Workflow documented in the case study
Read case study →Student planning and adviser workspace
Developed an adviser workspace around student profiles, study plans and progress records. Plan revision history makes changes visible between reviews, while progress is tracked against the study plan rather than reconstructed from calendar appointments.
Application workflow documented
Read case study →Jeweltimeco item scanning and invoice entry
Implemented phone-camera scanning that resolves a physical item’s unique code to its product and checks reservation state before invoice entry. Browser scanning, a fallback library and manual entry support the workflow; item tracing shows stock, reservation and invoice status.
Implemented scanning and item trace
Read case study →Fatahi Gold price-board PWA
Built a mobile-first Persian web app for gold prices and ordering. Prices are calculated on the server with configured markup and fees, and each response distinguishes live data from a fallback. Separate pricing and order endpoints keep their failure paths independent.
Price-board application documented
Read case study →Brand catalogue sites and dealer workflows
Built four brand catalogue sites that read shared WooCommerce product data, with separate order storage, reseller approval and dealer price monitoring. The case study records two sites live, one awaiting DNS and one on staging at its reporting date; stock reconciliation remains manual.
Mixed rollout stages in the published report
Read case study →AI assistants and research
Diagnostics, reviewed product content and strategy research.
WooCommerce diagnostic assistant
A standalone diagnostic service that reads a store’s configuration through the WordPress REST API and explains findings in a browser interface or API. Access uses an owner-revocable application password, with connection and permission errors reported separately from diagnostic findings.
Implemented standalone service documented in the case study
Read case study →AI product content with human review
A WooCommerce workflow for drafting product titles, attributes, descriptions and SEO metadata. Publication requires human approval; separate permissions, spending limits and duplicate-job controls make generation and review manageable for the store team.
Implemented plugin with a documented review and approval workflow
Read case study →Trading strategy research and evaluation
A research system that generates candidate trading rules, explains their reasoning and evaluates them in a separate stage. High-risk decisions go to human review; outputs remain research hypotheses rather than investment recommendations.
Research workflow; no trading-performance claim
Read case study →Telegram and messaging workflows
Team tasks, customer communication and management reporting.
Team task routing and approvals
Routes work to the next responsible role and requests approval where a decision is needed. It keeps the existing task board as the source of status, alerts management at decision points and reports routing failures for follow-up.
Implemented workflow described in the case study
Read case study →Customer messaging hub for Bale and channel integrations
Connects WooCommerce and CRM contacts to Bale bot and Safir messaging workflows. Campaign queues, message templates, stored opt-outs and support requests share customer records; separate provider modules keep OTP and campaign delivery apart.
Bale implementation documented; architecture supports channel extensions
Read case study →English Boss: scheduled practice in Telegram
Delivers short English exercises, reminders and AI feedback inside Telegram. Learners can follow progress and practice streaks, with separate general-English and IELTS routines. Scheduling, learner records and model integration are kept in separate service layers.
Implemented learning workflow; retention outcomes not measured
Read case study →Management bot and unified daily report
Combines live order and finance cards with one nightly management report and an installable dashboard. The dashboard shows the last available figures with an offline warning; the case study records a monthly-total comparison across the dashboard, finance card and commission page.
Delivered management system with a documented reconciliation check
Read case study →Automation and data integration
Repeatable reporting, system connections and operational pipelines.
n8n operations routing and reporting
Routes CRM and commerce events to responsible team members or approval queues. Scheduled workflows collect and normalize operational data into daily and weekly summaries with next actions; customer-facing actions pass human review.
Implemented workflows with documented approval and error paths
Read case study →Search Console data extraction for SEO review
Extracts query, page and performance data into a stable format for repeated comparisons. Separating collection from analysis lets teams revisit historical search data and compare periods without rebuilding manual exports.
Implemented extractor; this portfolio’s search results are not measured here
Read case study →Clarity behavior data for UX prioritization
Aggregates behavior signals by page and aligns the output with search and commerce reporting. Teams can rank pages for review and compare signals after a change; session recordings remain necessary to investigate the cause.
Implemented page-level analysis pipeline
Read case study →Scheduled operational reports in Google Sheets
Collects and normalizes SEO, product and operations data into a consistent spreadsheet structure on schedule. Existing formulas and team views can use successive runs; reporting reads remain separate from changes to store data.
Implemented scheduled reporting workflow
Read case study →Repeatable WooCommerce order analysis
Normalizes order exports, including Persian numerals, Jalali dates and varying gateway names. Repeatable analysis covers product mix, payment channels and order-status patterns, with files the operations team can review directly.
Implemented analysis over exported order data
Read case study →WordPress diagnostics through REST API
Assesses a WordPress installation through an owner-revocable application password, without installing a diagnostic plugin on the target. A browser interface and API share the same core, while connection and permission failures stay separate from findings.
Implemented diagnostic service documented in the case study
Read case study →Digikala inventory reconciliation from Excel
Reads an inventory workbook, verifies marketplace matches and writes a status workbook for the operations team. Persistent lookup caching and incremental progress records let interrupted runs resume; rendered pages use a browser when needed.
Implemented reconciliation pipeline with resumable runs
Read case study →MT5 strategy rules and risk-sizing research
Combines price-action rules, volatility-based exits and higher-timeframe confirmation with position sizing. The case study describes rule design and evaluation scope; it does not establish live returns or protection from trading losses.
Strategy-engine research; no verified return claim
Read case study →Attendance and office reporting automation
Collects attendance and operational inputs, normalizes their formats and produces reports for management. Logged runs make reported figures traceable to the processing step that produced them.
Implemented data workflow described in the case study
Read case study →WireGuard connection monitoring and recovery
Checks whether traffic crosses the tunnel from the macOS client, rather than relying on interface status alone. Failed checks trigger session recovery and a failure log for investigating recurring sleep, network-change or connection problems.
Implemented client-side watchdog
Read case study →Product image sourcing and processing workflow
Finds candidate product photos, routes them through a workstation and Photoshop review step, then attaches approved output to empty image slots. Existing images are preserved; unavailable workstation processing and failed items remain visible for review.
Live pipeline; source documents end-to-end verification on one product
Read case study →CRM-to-Android call and alert bridge
Connects customer-card dialing to the shop handset through an expiring command queue. Call records and customer-card lookup link phone activity to CRM; order and cart alerts use the same delivery path with their own expiry.
Simulated-client checks and real-handset commissioning documented
Read case study →WordPress and WooCommerce engineering
Catalog browsing, performance, checkout and administration.
A2 catalog filters with contextual options
AJAX filters use available category attributes and price ranges derived from catalog data. Versioned caching and a server-rendered fallback keep browsing available when client-side filtering fails.
Case study reports archive p95 from about 5.2s to 1.7s
Read case study →Stable archive pagination and infinite scroll
Moves infinite-scroll code into a cacheable asset, stops at the actual final page and uses deterministic ordering to avoid duplicate products across paginated results.
Implemented archive navigation fixes
Read case study →Guest-page microcache with commerce exclusions
Caches product and shop HTML for guest requests with expiry, invalidation and bounded rebuilds. Cart, checkout, account, payment and logged-in requests bypass this cache; administrators can purge and rebuild it.
Case study reports product TTFB from about 2.3s to 0.9s
Read case study →Route-specific frontend asset cleanup
Removes unnecessary CSS and JavaScript from selected archive, content and home routes. Separate boundaries preserve cart, checkout, administration and dynamic commerce dependencies.
Implemented scoped cleanup; no new payload benchmark
Read case study →Product and category structured-data safeguards
Repairs JSON-LD and supplies fallback Product and Offer data when upstream output is incomplete. Reference, brand and shipping normalization align the structured output with available product information.
Implemented metadata modules; search outcomes not established
Read case study →Checkout recovery and payment-message controls
Restores useful scroll position after payment or validation states and keeps restricted-product explanations visible. The documented admin safe-mode change preserves live payment calls without replaying historical gateway operations.
Implemented checkout and payment-boundary fixes
Read case study →REST request controls and selective caching
Short-circuits specified anonymous template queries and caches an explicit set of REST responses. Integration exemptions and cache-status headers make the affected routes and cache behavior inspectable.
Case study reports affected-route p95 from 2.8s to 0.9s
Read case study →Product snapshot API for external integrations
Serves normalized product documents from a prepared snapshot for Searchwiz and the SnappPay product feed. Scheduled full and delta refreshes, admin controls and rate limits separate external reads from expensive live catalog queries.
Case study reports products API p95 from about 1.9s to 0.42s
Read case study →Partner-scoped access firewall
Restricts requests from the configured partner addresses: catalog reads and the required REST namespace remain available, while cart, checkout, account and administration routes are denied. Requests from other addresses are outside this module’s scope.
Implemented partner-specific rules with a documented disable control
Read case study →Attribute-based similar-watch recommendations
Builds product signatures from watch attributes, scores bounded candidate sets and caches results. Background signing and selective rescoring avoid repeating the full recommendation workload on each product-page request.
Case study reports render time from 1.9s to 0.42s
Read case study →Bounded WooCommerce background processing
Consolidates queue controls with limited batch size, concurrency and runtime. Server-cron execution and cleanup of obsolete tasks separate background processing from interactive administration requests.
Case study records pending actions falling from about 38,000 to 4,900
Read case study →Controlled transient cleanup
Checks selected transient families against separate thresholds and removes expired entries in bounded batches. Cleanup skips catalog imports to avoid competing with the import workload.
Case study records rows from about 1.3M to 180K; bootstrap timing unmeasured
Read case study →Transient autoload prevention
Checks daily for transient rows incorrectly marked for automatic loading and removes that flag. Optional monitoring reports a large autoload population without treating every option as safe to delete.
Implemented preventive control; no new memory benchmark
Read case study →WooCommerce side cart
Opens a drawer after an actual add-to-cart event and refreshes it from WooCommerce cart fragments. Customers can review or remove items without leaving the current page; the drawer does not maintain a separate cart state.
Live interaction documented; conversion impact not isolated
Read case study →Product FAQs from available attributes
Generates buying questions and answers from populated product attributes. Questions without supporting product data are omitted, and the block mounts into the available product-page accordion or fallback location.
Live module documented; coverage depends on usable attributes
Read case study →Brand discovery hubs with daily catalog snapshots
Shows brand grids with search, letter and price filters. Daily snapshots refresh price ranges and product counts, while cached page structure and administrator rebuild controls support ongoing maintenance.
Live hubs documented; traffic gains not measured
Read case study →Order corrections with snapshot and undo
Lets authorized staff replace items, add shipping or correct line totals inside the order screen. A pre-change snapshot, undo and readable history support review; off-gateway receipts stay separate, and order status and payment gateway are preserved.
Live administrative module with documented write checks
Read case study →Company-stock availability batch control
Changes availability for a defined company-stock set through an admin workflow with preview, pre-change backup and rollback. Persisted batch state allows interrupted work to resume.
Implemented reversible inventory utility
Read case study →Restricted staff access for price updates
Allows price-field changes through quick edit while restricting broader product editing. Save-path checks enforce the boundary beyond the visible interface; access remains assignable and revocable as a WordPress role.
Implemented role and save-path restrictions
Read case study →Clear installment restrictions for SnappPay
Keeps the payment information and add-to-cart control visible on excluded brands while disabling unavailable installment controls. Unusable installment amounts are hidden, and an unclipped tooltip explains the restriction on the product page.
Implemented product-page restriction messaging
Read case study →Mobile header and navigation alignment
Combines a translucent header, sticky bottom navigation and matching footer. Stable content offsets and safe-area spacing keep navigation clear of device controls and avoid late repositioning during page load.
Implemented mobile layout module
Read case study →Cart recovery and pending-order expiry
Schedules recovery workflows through Action Scheduler and handles pending-order expiry through a guarded sweep. Separate recovery triggers and return-path coupon handling support unfinished carts and orders.
Live workflow documented; recovered revenue not isolated
Read case study →Request diagnostics with slow-query attribution
Records slow requests with query callers, page context and related errors. Tiered capture, per-entry limits and log rotation bound the diagnostic output so recurring delays can be traced to their source.
Production logger documented; no new overhead benchmark
Read case study →Outbound HTTP controls for admin responsiveness
Targets traced outbound and loopback delays with a destination blocklist and bounded timeouts. A companion asset monitor and request-level bypass support inspection and controlled troubleshooting.
Implemented HTTP controls; clean before/after average unavailable
Read case study →Order operations fields and filtered Excel export
Adds operational columns and a modal editor with Persian shipping dates and managed stock locations. Filtered XLSX exports and user-attributed order notes keep the order screen and accounting handoff aligned across legacy and HPOS views.
Implemented order tooling for legacy and HPOS screens
Read case study →Restock waitlist with queued notifications
Tracks product subscriptions by phone or email, binds demand to CRM and queues notifications when stock returns. Stored subscription status prevents repeat handling, while customer-specific button state is loaded separately from cached page HTML.
Production system documented; live SMS path verified in the source
Read case study →Transactional SMS monitoring and pattern status
Consolidates transactional messaging and records observable gateway results. The management view separates proven sends, SDK sends outside the HTTP log, unwired templates and unapproved patterns instead of treating all registrations as working delivery.
Source documents 55 patterns; no delivery-rate claim
Read case study →CRM and sales operations
Customer records, counter sales, loyalty and service workflows.
A2 CRM for customer records and sales follow-up
Connects operator inboxes, assigned follow-ups and in-person orders to a shared customer profile. Role-aware access, reporting, audit records and exports give sales staff and managers a common view of the work and its owner.
Implemented modular WordPress CRM framework
Read case study →Sales operations and team activity dashboard
Brings sales outcomes, team activity and accumulated work into one management view. Data comes from existing operational systems, with attention points presented alongside the figures needed to investigate them.
Implemented management view; no quantified sales-uplift claim
Read case study →Traceable wallet and loyalty ledger
Records money movements as append-only entries in exact integer Rial, with separate cash, promotional and refund credit buckets. Corrections reverse named entries; reward points follow explicit earning, cancellation and expiry rules so balances can be explained from their history.
Implemented ledger with mutation checks documented in the case study
Read case study →Mobile CRM desk and customer hub
Lets staff record counter orders and assigned follow-ups while viewing customer and order history. The same WordPress system includes a customer hub for orders, loyalty, wallet and profile data, plus management reporting drawn from operator records.
In daily use and ongoing maintenance, according to the case study
Read case study →Validated spreadsheet imports for price and stock
Processes CSV batches from inventory spreadsheets with brand and reference matching before changes are applied. Price, stock and warranty attributes share the import workflow, with mismatch reporting and timeout handling for long runs.
Implemented WooCommerce import workflow; not a universal marketplace connector
Read case study →Stock-aware fast-shipping messages
Shows fast-shipping information at purchase decision points only when actual availability supports it. If availability is uncertain, the message is omitted instead of presenting an unsupported delivery promise.
Implemented availability-based messaging; conversion effect not measured
Read case study →Repair intake, quote approval and hand-over
Connects technician intake, customer-panel quote approval, payments and PIN-confirmed hand-over. Payment keys and replay checks limit duplicate processing; quoted and line-item totals remain separate, with a warning when they differ.
Operational repair desk with documented payment and hand-over checks
Read case study →Counter-sales import and shared commission reporting
Imports accounting exports into branch-aware CRM customer records, reports ambiguous item matches and protects against duplicate imports. The admin report, owner dashboard and Telegram finance card share one commission calculation; source data and reconciliation limits remain visible.
Cross-interface agreement documented; one owner-calculation discrepancy remains under review in the source
Read case study →Business websites
Product presentation, service information and enquiry paths.
Hooman Gold: WooCommerce storefront support
Frontend layout and WooCommerce configuration work for a gold storefront, with scoped speed, security and presentation improvements. Small custom features support the shopping experience and routine maintenance.
Delivery scope documented in the linked case study
Read case study →Golden Gate Group: corporate website in Canada
Presents services in the language of prospective clients, with credibility information and accessible contact routes. Responsive pages support both a quick business assessment and content updates by the client team.
Corporate website delivery documented in the case study
Read case study →Freshca: service-led website in Canada
Organizes the business offering into responsive service pages with clear enquiry steps. The content structure lets the client team add or update information without rebuilding the site.
Website delivery documented; no measured enquiry uplift
Read case study →Yasi Gallery: gallery and ecommerce website
A gallery-first WordPress presentation for the US market, with space for artwork imagery and an ecommerce structure suited to considered purchases. The owner can add or change pieces through ordinary content editing.
Gallery and storefront implementation documented
Read case study →Yellow Willow: service website in Austria
Makes the service offering and local business information easy to review, with booking or contact routes available through the visit. The presentation is structured for routine updates by the business team.
Service website delivery documented in the case study
Read case study →Ohlala Barbershop: services and appointment flow
A responsive barbershop website with consistent local information, clear service descriptions and an appointment-oriented navigation path. The documented scope is the website structure and user journey, not a measured local-search ranking.
Implemented service and appointment-oriented website
Read case study →Divazheh / Koala Beauty: beauty storefront
A WooCommerce catalog organized around useful categories and visible product differences such as shade and size. Mobile purchase flow and maintainable content structure support browsing and routine catalog expansion.
WooCommerce storefront implementation documented
Read case study →Lampco: industrial products and services website
Organizes an industrial product and service range for both browsing and direct lookup. The corporate page structure lets the business add offerings while keeping navigation and information hierarchy consistent.
Industrial website delivery documented in the case study
Read case study →Saboksaran: construction services and project website
Structures service and project records so new work fits the existing organization. Clear service pages and an extendable content model let the business maintain its portfolio as projects accumulate.
Business website implementation documented
Read case study →Meta Media: agency positioning and portfolio website
Explains what the agency offers, who it serves and how engagement works. The content supports quick assessment and deeper project review, with a structure the agency can update as its work changes.
Agency website delivery described in the case study
Read case study →