Foreign Business App
The full import-operation lifecycle for Argentine businesses, from cost quote to delivery.
Screenshots
The Problem
Argentine importers ran their entire operation in Excel, import-cost calculations with Argentina's layered tax and duty structure (FCA + freight + insurance → CIF, customs duties, non-customs taxes, country tax, commission, and a dozen miscellaneous fees), supplier and product catalogs, per-operation collaborator fees, and payment tracking. One spreadsheet per operation, shared over email, no single source of truth. Errors compounded and nothing was auditable.
The Solution
A web app that centralizes the full import lifecycle, from initial cost quote to the goods arriving in Argentina. Single- and multi-product cost calculators that encode Argentine tax/duty rules via country + product-type preset rules; a step-by-step import wizard with live truck/container fill (weight and volume); supplier, product-variant, and client management; a reduced client portal with data isolation; collaborator assignments with auto-generated payments; and QuestPDF/Excel report generation for suppliers, clients, and customs.
Technical Decisions
As a solo developer working in .NET, Blazor Server let me ship a fully interactive web app without splitting focus across a separate JavaScript frontend stack, framework, and toolchain, one language, one codebase, one person maintaining it. MudBlazor provides a consistent Material UI out of the box.
Importers need detailed cost reports for clients and customs documentation. QuestPDF gives fully programmatic PDF generation in .NET, no Word templates, no manual formatting, no LibreOffice dependency. ClosedXML covers the Excel exports.
Latest .NET for performance and long-term support. PostgreSQL (hosted on Neon) for relational data, imports, suppliers, costs, collaborators, and payments all have clear relationships modeled as a DDD aggregate schema with foreign keys, split across a public data schema and a separate identity schema.
A four-role model (Admin > User > Colaborador > Client) drives both permissions and per-client data isolation, the same app renders a different menu and dataset per role, so external clients see only their own imports and orders.
Outcome
Actively developed and deployed on Render/Neon, replacing the client's Excel-based workflow. Cost calculation and report generation dropped from hours of manual spreadsheet work to a few clicks, with every operation now auditable in one system.
Early access
ImIn is still in development. If you want to be among the first users, leave your email and I'll reach out when it's ready.