01 · 2026 - In development
Workinance
A SaaS POS and inventory platform for small and medium retail businesses, built from scratch as my own product.
Founder
Architecture, backend, frontend, and infrastructure
Founder / Lead Full-Stack Developer
The problem
Enterprise ERP software is built for companies with a finance team and an IT department. A small or medium retail business needs the same core idea, one system for sales, stock, and staff, without the weight of modules built for manufacturing plants and multi-company groups. I started this as repair-shop tracking software, then had to decide, mid-build, which parts of a textbook ERP module list a small retailer actually needs, and cut the rest instead of building toward a checklist.
Decisions that mattered
The database is one DynamoDB table, partition key id only, no sort key, no joins. Every relationship is an application-level pointer the service layer resolves by hand, and tenant scoping is a composite key (product:::businessId) so one GSI can list one entity type for one business.
I weighed the build against a full enterprise-ERP taxonomy, module by module, and wrote down what a small retailer genuinely needs against what's out of scope: manufacturing, fleet, formal e-signatures. That document is what keeps the product from growing toward a feature checklist instead of its actual users.
The frontend is three apps in one Turborepo instead of one do-everything app: a Vite and React admin app for owners, a separate Vite and React dashboard app for staff and point of sale, and a statically exported Next.js landing site. All three share one package of UI components, Zod-validated form inputs, and an IndexedDB session layer.
Login is two-tier: owners sign in by email, staff sign in with a business code plus username and password. Both issue short-lived access tokens with revocable refresh tokens across up to five devices, kept in IndexedDB on the client.
The desktop POS is a thin Electron shell that points at the deployed web app's URL instead of a second UI to build and maintain.
The API bundles with esbuild into a single Lambda function, with dependencies shipped in a separate Lambda Layer rather than inside the function zip, the same pattern I use for my own portfolio's MCP server.
Outcome
Still in development, not yet deployed. Auth, inventory, and the point-of-sale core are built and tested against a live DynamoDB table; a production AWS deployment is the next milestone, not done yet. By my own assessment, basic invoicing and a ledger are what would turn this from POS-plus-inventory software into an actual ERP, and that's the phase after deployment.
- NestJS
- TypeScript
- DynamoDB (single-table design)
- AWS Lambda
- API Gateway
- AWS CDK
- Amazon SES
- S3
- Passport.js
- JWT
- @incloodsolutions/node-toolkit
- React
- Vite
- React Router
- Next.js
- Tailwind CSS
- Zustand
- React Hook Form
- Zod
- IndexedDB (localforage)
- Turborepo
- Electron
- Vitest
