Open-source engineering practice · Bengaluru, with global delivery

One Ecosystem.Every Function.Zero Licensing.— Enterprise systems engineering, ERPNext implementation, and integration practice · Bengaluru, India · global delivery

We design, deliver and operate enterprise-grade open-source platforms for ERP, commerce, marketing and automation — engineered to your operating model, delivered on a predictable timeline.Source, data and infrastructure sovereignty is non-negotiable. No licence cliff, no vendor lock-in, no per-seat economics.

Book a discovery briefing
WhatsApp us

No-obligation briefing · Source and data sovereignty from day one · Zero vendor lock-in

Trusted by operators shipping to customers in 6 countries

  • 3M
  • Kinara Capital
  • STEK
  • Nasiol
  • MDT Partners
  • Polemarch
  • Futura Sinks
  • Iadda
  • JustSigns
  • P91
  • 3M
  • Kinara Capital
  • STEK
  • Nasiol
  • MDT Partners
  • Polemarch
  • Futura Sinks
  • Iadda
  • JustSigns
  • P91

Proof · real engagements

See all engagements
Headline metric
9 plants · 1 operating systemA multi-plant Indian manufacturer — manufacturing, distribution, retail, after-sales, and statutory workflows on ERPNext, integrated with banking, GST and customs.
Engagement quote

Quote block reserved — never fabricate attribution. A real quote lands here when client permission clears.

Stack shipped

Built on

  • ERPNext
  • Holisto IEP
  • Banking
  • GST & customs
Mon·Industrial manufacturer·Week 6 of 11 (fixed-scope)·Manufacturing module cutover rehearsal/Tue·Regulated financial-services platform·Week 9 of 14 (T&M)·Settlement integration with depository/Wed·Premium D2C operator·Week 3 of 9 (fixed-scope)·Stock visibility rollout to the last 3 SKUs/Thu·Multi-location service chain·Week 2 of 7 (fixed-scope)·Per-outlet calendar wiring + reminder flows/Fri·Discovery briefing · manufacturer·Day 1 of 5·Scope, timeline, TCO for a 3-plant engagement/Sat·Managed services · retailer·Ongoing·Quarterly release train · payments + reporting/Mon·Industrial manufacturer·Week 6 of 11 (fixed-scope)·Manufacturing module cutover rehearsal/Tue·Regulated financial-services platform·Week 9 of 14 (T&M)·Settlement integration with depository/Wed·Premium D2C operator·Week 3 of 9 (fixed-scope)·Stock visibility rollout to the last 3 SKUs/Thu·Multi-location service chain·Week 2 of 7 (fixed-scope)·Per-outlet calendar wiring + reminder flows/Fri·Discovery briefing · manufacturer·Day 1 of 5·Scope, timeline, TCO for a 3-plant engagement/Sat·Managed services · retailer·Ongoing·Quarterly release train · payments + reporting/
See all 22 active engagements →
Start here

Which capabilitydo you want to engage?

Six doors into the practice. Each one goes straight to the engagement shape, the delivery model, and the procurement conversation.

None of these quite fit? Answer two questions and we’ll point you at the right page. No form.

02What we do

Five engagements.One operating system.

We are an enterprise systems engineering practice. We design, implement, integrate, and operate the software infrastructure that complex organisations run on — across ERP, CRM, finance, financial technology, logistics, government, and data — on platforms and infrastructure the client owns.

  • Advisory

    Architecture reviews, operating-model design, vendor evaluations, and governance-gate design for regulated, multi-entity operators — sized to the engagement, not a one-size-fits-none retainer.

    Engage advisory

  • Implementation

    Greenfield deployments and complex multi-entity rollouts on ERPNext, Frappe and Medusa — structured into named phases, governed at every gate, with a principal consultant on the engagement from kickoff to go-live.

    Implementation practice

  • Migration

    Off SAP, Oracle, NetSuite, Odoo, Tally and Zoho — with master-data fidelity, full audit trail, and no business-day disruption. Polemarch-grade tooling for the financial-data half of the cutover.

    Migration practice

  • Integration

    Cross-system workflows on Holisto IEP — our own Go / GraphQL / NATS JetStream integration plane. ERP, CRM, banking, government APIs, logistics, field systems and partner systems, connected as one data layer with full audit.

    Integration practice

  • Managed services

    Production operation, upgrades, observability and patching — under response-time SLAs, with a named team, defined change windows, and a clear escalation path. Operated as a service, not handed back as a problem.

    Managed services

Unsure which engagement fits? Answer two questions and we’ll point at the right entry point. No form.

Recent work · last 12 months

Before / after —six engagements, six operating systems,one practice.

Each snapshot is a real engagement from the last year. Numbers belong to the client; timelines and stack choices are ours. Named customers (Polemarch, Splendx, Fixcent, Rosemount International Schools, Mandifi) appear with consent. The industrial-manufacturer archetype is described by engagement shape; the underlying engagement is real and the basis is available on a discovery briefing.

Rosemount International Schools · multi-school group

Rosemount — multi-school operations, one operating system.

10 weeks · fixed-scope · per-campus cutover

Before

  • Schools run on Tally for accounts, spreadsheets for admissions, paper files for student records
  • Parent communication over WhatsApp groups; no single view of fee status, attendance, transport
  • Statutory reporting (CBSE / state) assembled by hand at the end of each term

What we shipped

  • ERPNext (Education domain) for admissions, fee lifecycle, attendance, transport, and accounts — one instance per campus, one consolidated group view
  • Polyg.in WhatsApp for parent communication bound to the student record
  • Custom dashboards for principals and the group CFO; statutory reports generated from the same data

After

  • Fee lifecycle — admission to receipt to reconciliation — one workflow per campus
  • Parent communication traceable against the student record, with consent and opt-out honoured
  • Statutory reporting cycle cut from weeks to days

Multi-campus · fee lifecycle · statutory reporting

Read the full story

Splendx · B2B commerce · multi-warehouse operator

Splendx — multi-warehouse B2B commerce, integrated end-to-end.

12 weeks · T&M → fixed-scope · phased cutover

Before

  • B2B orders taken over email, phone, and a basic WooCommerce storefront; no dealer pricing tier
  • Inventory reconciled monthly across 4 warehouses; stockouts common, overstock routine
  • Credit limits and dealer-specific pricing held in spreadsheets, out of sync with finance

What we shipped

  • Medusa B2B storefront with dealer pricing, credit limits, and approval workflows
  • ERPNext (sales, inventory, accounts) bound to the storefront through Holisto IEP — one data layer, no CSV handoffs
  • Polyg.in WhatsApp for order confirmations, dispatch updates, and dealer engagement

After

  • 4 warehouses reporting live stock to the storefront, every minute
  • Dealer-tier pricing and credit limits enforced at order entry, not at month-end
  • Order-to-dispatch SLA visible to the dealer for the first time

4 warehouses · dealer pricing live · ERP-bound

Read the full story

Industrial manufacturer · 9 plants, multi-entity

A 9-plant manufacturer off SAP B1, onto one operating system.

11 weeks · fixed-scope · phased rollout

Before

  • SAP B1 running books + inventory; ~₹48L/yr in per-user licences across 9 plants
  • Every customisation a 4–6 week change request through the SAP partner
  • BI stitched from three monthly CSV exports in Excel; statutory filings a manual exercise
  • No real-time view of plant-to-plant stock or inter-entity transfers

What we shipped

  • ERPNext (manufacturing, stock, accounts) + Frappe Insights for BI, single multi-company instance
  • Holisto IEP integrating banking, GST, e-invoicing, e-way bill, and customs into the same ledger
  • Frappe Helpdesk for internal ops tickets under the same SSO and role model as ERP

After

  • Per-user licence spend: ~₹48L/yr → ₹0
  • Month-end close: 12 days → 4 days across 9 plants
  • Customisation turnaround: 6 weeks → 3–5 days, in-house
  • Plant-to-plant stock visibility: offline → live

9 plants · 1 operating system · 0 licence cliff

Read the full story

Polemarch · pre-IPO & unlisted financial platform

Polemarch — ~15 Cr/month, SEBI-ready from day one.

Continuous · owned platform · managed operation

Before

  • Pre-Polemarch: static WordPress site, manual PDF brochures per share, prices updated by email
  • Trades reconciled on spreadsheets; no CDSL/NSDL settlement integration — handled over phone
  • No KYC / AML / CFT controls at the order layer; investor onboarding a manual queue

What we shipped

  • Holisto IEP as the integration plane — banking verification, PAN/Aadhaar, MCA, depository, settlement
  • Custom Frappe backend for KYC, order workflow, settlement, compliance audit trail
  • Polemarch web + investor app on Medusa B2B + Frappe, with daily-refreshed pricing across 100+ instruments

After

  • Asset classes live: unlisted shares, bonds, AIF, REIT
  • Order-to-settlement: days → same-day for in-stock scrips
  • Compliance audit pack auto-generated; quarterly review cut ~80%
  • Identity, banking, and corporate verification enforced before any order can settle

~15 Cr monthly volume · 4 asset classes · 100+ instruments

Read the full story

Mandifi · agricultural market intelligence

Mandifi — near-real-time agri pricing, at dealer-network scale.

Continuous · owned platform · managed operation

Before

  • Dealers relied on phone calls, WhatsApp forwards, and the previous day's mandi rates to set prices
  • No consolidated view across locations; pricing decisions made on the most recent signal available, not the most accurate
  • Data ops were manual — someone aggregating mandi rates into a sheet every morning

What we shipped

  • Mandifi ingestion layer (Go) collecting pricing from multiple mandi and dealer sources on a scheduled cadence
  • Holisto IEP normalising, validating, deduplicating, and location-pricing the stream
  • Dealer-facing interface (web + mobile) with location-specific pricing, refreshed daily or more frequently

After

  • Dealer pricing decisions made on consolidated, deduplicated data — not the most recent WhatsApp forward
  • Daily refresh cadence across the network, with location-level deltas visible to the dealer
  • Mandifi operated as a managed platform — ingestion health, source coverage, and dealer activity monitored continuously

Daily refresh · location-priced · dealer-facing

Read the full story

Fixcent · aftermarket service & parts

Fixcent — field service, parts, and warranty, integrated.

9 weeks · fixed-scope · per-region cutover

Before

  • Field service operations run on a CRM + a separate field app; parts and warranty tracked in spreadsheets
  • Service-to-stock-to-invoice loop stitched together manually; warranty claims settled weekly, not at the point of service
  • No consolidated view of recurring failures, parts burn rate, or service revenue by region

What we shipped

  • ERPNext (stock, accounts) + a custom field-service app on Holisto IEP, bound to the same ledger
  • Service event → parts consumption → invoice → warranty claim in one workflow, with audit trail
  • Dashboards for service revenue, parts burn rate, and recurring-failure patterns by region

After

  • Service-to-invoice cycle: days → same-day, with warranty adjudicated at the point of service
  • Parts burn rate and recurring-failure patterns visible to operations for the first time
  • Customer service history bound to a single record — no more spreadsheet joins

Field service · parts · warranty · one ledger

Read the full story

Every engagement above shipped under one of three engagement models — fixed scope, time & materials, or managed services — and into a named-phase delivery plan. The procurement conversation we have on the first call is the procurement conversation we have at go-live.

Request a 30-min discovery briefing
Numbers our clients can audit

Scale without surprises — every claim traceable.

Each metric is from a live customer, not a marketing deck.
059
Products we implement
One permission model · one data layer
00
Per-user licence fees
Open-source core, no seat pricing
0–10 wk6–10 wk
Typical go-live
Scoped implementation, kickoff to production
0%100%
Yours to keep
Source, data and infrastructure you own
Side by side

Why teams switch from SAP and Odoo.

Same capabilities. None of the licensing math.

Per-user licensing

MITH.TECH

₹0 / owned stack

SAP B1

₹15,000–25,000 / user / yr

Odoo Ent.

₹2,500–4,000 / user / mo

Time to go-live

MITH.TECH

Named-phase delivery, predictable timeline

SAP B1

6–9 months

Odoo Ent.

3–6 months

GST / e-invoicing

MITH.TECH

Native, day 1

SAP B1

Add-on / consultant

Odoo Ent.

Module to enable

Source code access

MITH.TECH

Full ownership

SAP B1

Closed

Odoo Ent.

Community only

Integration plane

MITH.TECH

Holisto IEP (Go / GraphQL / NATS)

SAP B1

Proprietary middleware

Odoo Ent.

Module-bound connectors

Customisation depth

MITH.TECH

Unlimited, governed

SAP B1

Limited / costly

Odoo Ent.

Module-bound

Data sovereignty

MITH.TECH

Owned from day 1

SAP B1

Vendor-controlled

Odoo Ent.

Vendor-controlled

Engagement model

MITH.TECH

Fixed scope · T&M · managed services

SAP B1

Partner-led, partner-dependent

Odoo Ent.

Partner or self-implement

Run the numbers yourself

What you’d save with an owned stack.

Slide the inputs to match your team. The chart re-renders live, the savings counter animates, and the model is conservative on purpose.

Live calculator

Tune your inputs

Current SaaS spend / month₹1.80 L
Team size45 people
Time horizon3 years

One-time impl

₹15.85 L

Hosting / month

₹15k

On SaaS

₹74.93 L

3-yr cumulative

On Mithtech

₹21.28 L

3-yr cumulative

You save

₹53.65 L

≈ 72% off baseline

Cumulative cost over time

SaaSMithtech
₹0₹37.46 L₹74.93 LY1Y2Y3

Model: 10% annual SaaS inflation · 0.7× one-yr SaaS impl · 8% monthly hosting.

Build my plan

Want the real ranges rather than a model? See what it costs — published bands, no form.

05One system

Everything connects to one core.

Storefront, WhatsApp, POS, field sales, shipping, GST, dashboards — explore the map. Every piece reads and writes the same ledger.

Inside the Core — how one order runs the whole business

Nobody types the same thing twice. Each document is built from the one before it.

Book a Free Demo →
Explore the full ecosystem — commerce and marketing maps too
  • Polemarch — integration supported by MITH.TECHPolemarch
  • Polyg.in — integration supported by MITH.TECHPolyg.in
  • Qu6 — integration supported by MITH.TECHQu6
  • Holisto IEP — integration supported by MITH.TECHHolisto IEP
  • Mandifi — integration supported by MITH.TECHMandifi
  • ERPNext — integration supported by MITH.TECHERPNext
  • Frappe CRM — integration supported by MITH.TECHFrappe CRM
  • Frappe Insights — integration supported by MITH.TECHFrappe Insights
  • Frappe Books — integration supported by MITH.TECHFrappe Books
  • Frappe Helpdesk — integration supported by MITH.TECHFrappe Helpdesk
  • Medusa.js — integration supported by MITH.TECHMedusa.js
  • n8n — integration supported by MITH.TECHn8n
  • Metabase — integration supported by MITH.TECHMetabase
  • Smartflo — integration supported by MITH.TECHSmartflo
  • + banking · government · logistics APIs →
06Regulated industries, mission-critical environments

We operate wherefailure is not an option.

Production deployments across seven regulated sectors, governed for compliance, scale, and audit. Each engagement is led by a practice lead with sector depth, and delivered through one of three named engagement models.
All sectors and the engagements behind them
07Platforms we ship ourselves

Two platforms,engineered to the same standard.

Most practices implement other people's software. These are the two we built, run, and keep improving — proof that the architecture is real, not theoretical, and that we operate what we recommend. Holisto IEP, Polemarch, and Mandifi join the homepage in the next phase, alongside the product pages that surface them.

Three more own platforms — Holisto IEP (integration plane), Polemarch (pre-IPO / unlisted financial platform), Mandifi (agricultural market intelligence) — surface on the homepage in the next phase, alongside the product pages that describe them. See all practice platforms.

08From the practice

Engineering notes,from the people shipping it.

A curated read from the practice's 209-post corpus — the guides that move the engagement, not the ones that move the funnel.

  • Comparisons

    ERPNext vs SAP Business One in India: a 2026 buyer's guide

    A 3-year TCO comparison, the features that map, the features that don't, and the 2027 maintenance cliff that changes the math.

    Read the guideMigration practice →

  • Cost & Hosting

    ERPNext implementation cost in India: published bands, 2026

    What implementation, hosting, and data migration actually cost for a 50–200 person operator — and the four numbers that move the quote.

    Read the guideRun the stack planner →

  • Migrations

    Tally to ERPNext: a clean cut-over, end to end

    The data mapping, the opening-balance reconciliation, the cutover plan, and the traps that stall go-lives — drawn from the practice's published engagements.

    Read the guideMigration practice →

  • Integration

    n8n vs Zapier vs Make in India: a 2026 comparison

    When a self-hosted integration practice pays for itself, and when it doesn't — with the cost and governance math behind the answer.

    Read the guideIntegration practice →

Not seeing the engagement you are scoping? Two questions, the right entry point.

All 209 engineering notes
Last-mile questions

Answers to what CFOs actually ask.

  • Every MithTech engagement is structured into named phases (Discovery → Architecture → Build → Integration → Hardening → Go-live → Managed operation), with a deliverable, a governance gate, and a named owner at each gate. For multi-entity operators we run a single consolidated instance with company-level data separation — the same operating model, the same role and approval framework, with per-entity books, stock, and statutory configurations. A principal consultant is on the engagement from kickoff to go-live.

Request a 30-min discovery briefing

A working session with a
principal consultant.

30 minutes with a Mithtech principal consultant. We pressure-test the architecture, surface the highest-cost gaps in your current operating model, and outline the engagement shape that fits your governance and procurement posture. You leave with a written brief — yours to share with the board or take to a different implementer.

  • An architecture pressure-test

    The three highest-cost gaps in your current operating model, ranked.

  • An engagement model recommendation

    Fixed-scope, T&M, or managed services — matched to your procurement posture.

  • A written brief

    Yours to share with the board, your CFO, or a different implementer.

Request the 30-min discovery briefingEmail the practice lead

  • 30-min working session

    Principal consultant, not a sales script.

  • No obligation

    You keep the written brief even if you do not move forward.

  • Sovereignty, day one

    Source, data and infrastructure belong to you. Always.

Prefer direct contact?+91 90087 70738manoj@mith.tech
or review the platform catalogue first →