Open for new projects

Q4 2026 · ID · GMT+7

Software built around how your business works.

CRM, customer portals, order systems, booking, online stores, and internal tools. We build them around your needs instead of forcing your business into a template.

Talk to us See a system example

— WHAT WE AIM FOR

Understand the problem,
then build the solution.

Think first. Then build.

— ASK NALR

Want to know how we work?

Try a few questions below. This is still a demo with pre-written answers, not a live AI response.

Demo · answers are pre-written.

liveAsk Nalr

How much does a custom CRM cost?

retrieved · pricing.md · case-studies.json

Talk for 30 minutes See services

Sources: pricing.md · case-studies.json

— TRY ASKING

01— SERVICES

What we can build

We build custom software from proven building blocks, then adapt them to your business process. You only build what you actually need.

— 01from 1–3 weeks

Custom business tools

CRM, customer portals, order systems, booking, scheduling, and field-service tools. The workflow follows how your team actually works.

CRM & pipeline
Customer portal
Booking & scheduling
Dashboards

Talk about this

— 02from 3–8 weeks

Industry-specific platforms

Systems built around a specific type of business, such as multi-outlet F&B, professional services, or B2B distribution.

Multi-branch
Role-based access
Audit trail
Custom integrations

Talk about this

— 03from 2–6 weeks

E-commerce & marketplaces

Online stores and marketplaces with payments, inventory, and orders connected to your operations.

Local payments
Inventory
Orders & transactions
Mobile

Talk about this

— 04from 1 week

Company & product sites

A simple way to start working together: fast, polished company or product sites built with search in mind.

Next.js + Tailwind
SEO
Optional CMS
Cloudflare

Talk about this

02— HOW WE WORK

Start with the problem, not the code

You know what we are working on, what is done, and what comes next. During the build, we regularly show you the work.

Discovery

An initial call to understand the problem, goal, constraints, and what a successful result looks like.

TIME: 30 min – 1 hour
DELIVERABLE: Shared understanding

Proposal

We write down what will be built, in what order, when it will be delivered, and what it will cost.

TIME: 2–3 days
DELIVERABLE: Written proposal

Build

The work moves in small steps. You get regular demos and updates through the channel that works best for you.

TIME: 1 week – 6 months
DELIVERABLE: Working software

Handover

We hand over the documentation, provide training when needed, and stay available during the agreed support period.

TIME: 1 week
DELIVERABLE: Docs · training · support

03— STACK

The technologies we use

Web and mobile clients connect to a Laravel API. The API handles business logic, data, integrations, and AI features when needed.

01 / CLIENT3 nodes

Web

Apps for admins and customers

Next.jsReactTypeScriptTailwind

Cross-platform mobile

One codebase for iOS & Android

React NativeExpoFlutter

Native mobile

For apps that need deeper device access

KotlinSwift

02 / APPLICATION2 nodes

API

Business logic · realtime · authentication

LaravelRESTWebSockets

Integrations

Payments · WhatsApp · email

MidtransXenditWhatsApp APIEmail

03 / DATA + INTELLIGENCE2 nodes

Database

Where the main data lives

PostgreSQLJSONBFull-text

AI

Models chosen for the job and the data

OpenRouterClaudeOllama

CLIENT → APPLICATION → DATA + INTELLIGENCE

— RUNS ONCloudflare · VPS · Optional on-premise

04— EXAMPLE

ERP for an engineering company

An example of a multi-module system we build: projects, purchasing, vendors, and HR in one system, with an AI assistant that can answer questions from company data. Client and product names are anonymized.

ROLE: Sole engineer, from architecture to handover
TIMELINE: 2025 — ongoing
SCALE: 10+ modules · multi-tenant ready
INDUSTRY: Engineering services (anonymized)

— DASHBOARD VIEWProject management · example

— ERP Dashboard

internal.erp / projects

Operations / Project Management

Projects, approvals, and operational risk

MAY 2026

Active+8

Overdue+2

On-time-1.4

92%

Project movement

task moving: invoice reminder → review

BACKLOG14

Vendor portal

KPI rollup

RFQ compare

ACTIVE42

Refinery dashboard

HSE inspection

Invoice reminder

REVIEW7

Compliance audit

Purchase approval

Timesheet sync

Invoice reminderdropped

DONE18

Payroll export

Vendor master

CRM quotation

KPI trend

last 8 weeks

CodeNameStatusSourceScore

PRJ-142Refinery dashboardActiveRK68%

PRJ-143HSE inspection appOverdueDA32%

PRJ-148Vendor portal v2ActiveSK84%

PRJ-157Compliance auditDoneSP100%

PRJ-158KPI rollupReviewMK92%

AI suggestion

3 vendor invoices in PUR are overdue and tied to active projects. Draft reminders to PT Sumber Engineering and 2 other vendors?

Sources: invoices · purchase · vendors.profile

05— WHY NALR

Software that fits the business, not just the presentation.

You do not have to go through layers of people. You talk directly to the engineer building your software.

The work does not simply stop when the software ships. There is documentation, handover, and an agreed support period.

We write the code and use AI where it helps. It can speed up parts of the work, but technical decisions are still reviewed by us.

We do not compete on being the cheapest. The point is software that makes sense for your needs and the risks your business carries.

06— MANIFESTO

Think first. Then build.

Nalr Dev started after I went through burnout.

There was a period when a lot of things felt out of control. What helped was not a new technology or a good-sounding motivation. It was stopping, looking at the problem clearly, and making one decision at a time.

That way of thinking became part of how I build software.

Many software projects do not struggle because the technology is not advanced enough. The problems often start earlier: unclear requirements, moving scope, optimistic estimates, or code being written before everyone agrees on what actually needs solving.

That is why we start by understanding the problem. Then we define the scope, choose the technology, and write the code. We use AI where it helps, while decisions that need context and judgment stay with people.

The goal is simple: finish the software sooner without cutting the things that matter.

It does not need to sound impressive. It needs to work and be useful.

07— CONTACT

Have a project in mind?

Tell me briefly what you need. I usually reply within one business day. Small projects are welcome too.

— Send an email

hi@nalr.dev