Skip to content
DM Techworks

Software house · Bandung

Operational systems that follow the way your business works

DM Techworks designs and builds ERP, admin dashboards, POS, CRM, websites, and AI workflows around how your team works, and stays on to support you once the system is running.

Built personally by Eduardus Alvito Kristiadi, founder

SiHedon order calendar showing the daily delivery schedule, sample data
SiHedon vault table listing note counts per denomination, sample data
SiHedon · order calendar & vault · sample data

Our clients

  • SiHedon · Tangerang
  • Brave Florist · Samarinda & Balikpapan
  • The Booster Gift · Tangerang
  • SIS · Semarang
  • Notarich · Kudus

Services

Five services, built around how your team works

Operational & internal systems

Orders, production, stock, and finance in one system

Work that used to be spread across chats and spreadsheets comes together, with role-based access: owner, admin, finance, production, courier.

  • ERP
  • Admin dashboard
  • POS
  • CRM
  • Custom systems
The Booster Gift corporate order workspace, sample data
The Booster Gift · corporate order management · sample data

Websites & e-commerce

Websites connected to your orders and catalogue

Company profiles, landing pages, customer websites with a catalogue, and e-commerce whose data connects to your operational system.

  • Company profile
  • Landing page
  • Website & catalogue
  • E-commerce
SiHedon online store home page with product catalogue, sample data
SiHedon · online store · sample data

AI systems & workflows

AI workflows for repetitive work

Incoming messages, documents, and forms can be read and sorted by AI, then checked by your team before they are recorded in the system.

  • AI systems
  • AI workflows
  1. 01Input arrives: messages, documents, or forms
  2. 02AI classifies or extracts the content
  3. 03Your team checks the result
  4. 04The result is recorded in the system or sent as a notification

Integrations & existing systems

Connecting new systems with the ones already running

Payments, WhatsApp or email notifications, and report exports are connected to your system. Existing systems are assessed before they are developed further.

  • Payments
  • Notifications
  • Report exports
  • Existing systems

Support & maintenance

Support once the system is in use

Bug fixes, hosting setup, data backups, and further development, with a scope agreed in the proposal.

  • Support & bug fixes
  • Hosting
  • Backups
  • Further development

Case studies

Five systems we built for client businesses

How we work

See the shape of the system first, then decide

  1. 01

    Tell us what you need

    Over WhatsApp or a short brief: the process you want to sort out, who uses it, and the systems already in place.

  2. 02

    Flow demo or discovery

    For websites and simple systems, we show you a flow demo. Complex systems start with a discovery session.

  3. 03

    Built in stages

    Written scope and estimate, staged payments, and progress you can check and test at every stage.

  4. 04

    Go-live & support

    Team training, documentation, and a support period as agreed in the proposal once the system is in use.

Eduardus Alvito Kristiadi, founder of DM Techworks, smiling in a navy blazer and white shirt

About

You talk directly to the person who builds the system

I'm Eduardus Alvito Kristiadi, founder of DM Techworks in Bandung. I design, code, and support every system myself, from the first conversation until your team is using it.

Get to know DM Techworks

Blog

Notes from our projects

All articles

FAQ

Before you start

How much does a system cost?

We prepare an estimate once the needs and scope have been discussed, because every system differs in modules and users. The written proposal covers scope, timeline, and staged payments.

Can I see an example or a demo first?

Yes. For websites and simple systems, we prepare a clickable draft of the flow with sample data. For complex systems, we show a similar existing system and start with a discovery session. A demo does not include real integrations, your actual data, or repeated revisions before an agreement.

Who owns the source code once the project is finished?

The source code belongs to the client once the project is paid in full.

Can you continue an existing system?

Yes. We first assess the running system in a discovery session, then agree on which parts to continue, integrate, or rebuild.

Tell us about the process you want to sort out

Your business context, the process that causes trouble, and the systems you already use. We take it from there and see if we are a good fit.

Chat on WhatsAppSend a brief