ERP & business systems
Production, inventory, payroll, purchasing and costing in one system, built to your operation rather than configured around someone else's.
You stop running the business from memory and spreadsheets.
SOFTWARE ENGINEERING · BANGLADESH
We build the softwarewe run our ownfactories on.
Tech Maniac is the software arm of an operating manufacturing and fashion group. We've built and run production ERP, double-entry accounting and eCommerce systems for our own companies — and now for others.
SYSTEMS REGISTERLIVE
- LIVE · 7+ MONTHS
SHANTOTEX ERP
Textile & weaving operations
- LIVE
VIOR HUB
ERP · double-entry · order sync
- SOFT LAUNCH
TOP LABEL
Menswear commerce · chat order desk
- LIVE · PRE-LAUNCH
VIOR STOREFRONT
Headless commerce · COD checkout
19 SYSTEMS TOTAL · SELF-MANAGED INFRASTRUCTURE
MONEY STORED AS INTEGER PAISATRIAL BALANCE VERIFIED ON EVERY RESTOREBUSINESS DATES STRICTLY ASIA/DHAKAORDER SYNC EVERY 30 SECONDS — SELF-HEALINGNO FLOATING POINT IN THE MONEY PATHBOOKS ARE APPEND-ONLY — CORRECTIONS POST AS REVERSALSBALANCE INVARIANT ENFORCED BY A DATABASE CONSTRAINT19 PRODUCTION SYSTEMS · SELF-MANAGED INFRASTRUCTUREMONEY STORED AS INTEGER PAISATRIAL BALANCE VERIFIED ON EVERY RESTOREBUSINESS DATES STRICTLY ASIA/DHAKAORDER SYNC EVERY 30 SECONDS — SELF-HEALINGNO FLOATING POINT IN THE MONEY PATHBOOKS ARE APPEND-ONLY — CORRECTIONS POST AS REVERSALSBALANCE INVARIANT ENFORCED BY A DATABASE CONSTRAINT19 PRODUCTION SYSTEMS · SELF-MANAGED INFRASTRUCTURE
0
Production systems running
0+
Months a live ERP has closed real books
221 ms4 ms
Server response time
15390
Requests per second
WHY THIS IS DIFFERENT
Most agencies have built an ERP. We have to live in ours.
Our accounting engine closes our own books. Our storefronts sell our own garments. Our factory system tracks our own weaving, our own payroll, our own loans. When something is wrong, it is wrong for us first — and we pay for it before any client ever does.
That changes how the software gets built. Money is stored as integers, never floats. Books are append-only, so a correction is a reversal entry rather than a quiet edit. Balance rules are enforced by the database itself, so no application bug can write a journal that doesn't balance. These aren't preferences. They're what you conclude after your own trial balance refuses to balance at eleven at night.
We build for manufacturers, retailers and distributors — mostly in textiles and fashion, because that is the industry we operate in and the one whose problems we already understand.
WHERE THIS USUALLY STARTS
Nobody wakes up wanting an ERP.
They want one of these to stop happening.
“I can't tell what a job actually cost me.”
Job costing that pulls real material, labour and wastage from the floor, rather than a margin someone estimated afterwards.
“The stock number is never right.”
One stock truth, moved by the same events that move the money — so the count and the books cannot disagree.
“Month-end takes two weeks.”
Books that post as the business runs. The month-end position becomes a query rather than a reconstruction.
“My store and my accounts tell different stories.”
Orders become journal entries automatically. Nobody retypes anything, so there is nothing to reconcile later.
“Everything depends on one person's spreadsheet.”
Roles, approvals and an audit trail, so the process survives the person who invented it leaving.
“We bought software and nobody uses it.”
Built around how your staff actually work — including, where it helps, entering data by speaking Bangla rather than typing English.
WHAT WE BUILD
Four things, built properly, rather than everything built once.
Every engagement is scoped to the business. We don't sell a package and then bend your operation to fit it.
Accounting & financial software
Real double-entry books that post themselves from the documents your staff already handle — bills, payments, production runs.
Nobody has to understand debits and credits to keep correct books.
eCommerce
Storefronts built for how this market actually buys — Cash on Delivery, phone numbers instead of email, local couriers.
You sell online without fighting software built for somewhere else.
Business process automation
The approvals, handoffs and records that currently live in notebooks, WhatsApp and one person's head.
The process survives the person who invented it.
A trial balance that refuses to balance teaches you more than any specification.
Every rule we follow about money, time and audit trails came out of a system we had to fix ourselves, at our own cost.
SELECTED WORK
Three systems, all in production.
Every figure was taken from the running system or its database, not estimated.
01Own venture
VIOR
FASHION RETAIL · COMMERCE + ERP
A storefront and the double-entry ERP behind it, built as two deliberately separate systems.
- Server response time
- 221 ms → 4 ms
- Requests per second
- 15 → 390
VendureNestJSNext.jsPostgreSQL
READ THE CASE STUDYBRAND.VIOR.COM.BD02Group company
ShAntoTex
TEXTILE MANUFACTURING · ERP
Job costing, weaver loans, payroll and books — closing a real company's accounts for over seven months.
- Continuous production use
- 7+ months
- Stock entries recorded
- 3,897
FlaskPostgreSQLRedisGoogle Gemini
READ THE CASE STUDYBOOK.SHANTOTEXTILE.COM03Client engagement
TOP LABEL
MENSWEAR RETAIL · COMMERCE
A commerce platform built for Cash on Delivery and phone-as-identity, operated from a chat app.
- Order and email lifecycle
- COD-first
- Order desk runs from Telegram
- Chat-operated
VendureNext.jsPostgreSQLTelegram API
READ THE CASE STUDYTOPLABEL.BDALSO IN THE ESTATE
Nineteen production systems, on infrastructure we run ourselves.
A sample of the rest, described by what they do rather than who they belong to.
Textile ERP with biometric attendance
HR, payroll and loan schedules, with attendance ingested directly from factory devices.
Double-entry accounting platforms
Chart of accounts, journals, trial balance and full financial statements.
Fabric technical data sheets
Department-owned sections with a submit, approve and lock workflow, and an audit trail.
Sample request tracking
AI-assisted PDF import with a rule-based fallback when the model is unavailable.
Buyer visit management
Visit scheduling and tracking, integrated with Microsoft 365 calendars.
Operational dashboards
Projections against realisations, with scheduled automated data collection.
Internal product catalog
Multi-role approval workflow with QR label printing for the warehouse floor.
Discount request and approval
Structured approvals with role-based routing, installable as a mobile app.
Storefront with server-side tracking
A second commerce platform, with conversion events sent server-side rather than from the browser.
WHO WE BUILD FOR
We go narrow, on purpose.
A generalist can learn your industry on your budget. We already work in ours.
Textile & garment manufacturing
DeepestSix systems deep. Weaving job costing, fabric data sheets, sample tracking, compliance, biometric attendance, payroll.
Fashion retail & eCommerce
Three storefronts across two platforms, built for Cash on Delivery and the way this market actually buys.
Distribution & wholesale
Supplier dues, purchase-to-payment, stock movement and moving-average costing.
Manufacturing SMEs
The patterns transfer — production, inventory, payroll and books are the same problems in a different shape.
WHAT WE BUILD WITH
The stack we actually run in production. Nothing on this list is aspirational.
BACKEND
PythonFlaskFastAPINestJSTypeScriptNode.js
FRONTEND
Next.jsReactAstroTailwind CSS
DATA
PostgreSQLRedisValkeyTypeORMSQLAlchemy
COMMERCE
VendureMedusa
INFRASTRUCTURE
DockernginxsystemdCloudflare
AI
Google GeminiLLM integration
HOW WE WORK
Three stages, and we stay after the last one.
01
We learn the actual process
Not a requirements document — the real thing, including the workarounds and the spreadsheet nobody mentions. Most failed systems fail because they were built from how the process was described rather than how it runs.
02
We build the part that hurts most first
Something real and in use early, rather than everything at once eighteen months later. You see whether it fits your business while there is still time to change it.
03
We run it
Deployment, backups, monitoring and the changes that follow. The same people who built it are the ones who answer when something is wrong — which is the arrangement that keeps software honest.
GET IN TOUCH
Tell us what you're running today.
Spreadsheets, an existing system, or nothing yet — the answer changes what we'd recommend. Tell us where you are and we'll tell you what we'd actually do, before anyone talks about a quote.
Not live yet
This form is built but not connected — it needs an inbox to deliver to. Submission is disabled until then, so nothing is quietly lost.