About
Our StoryOur JourneyTeamOur Approach
Services
Operations ManagementAI OperationalisationDecision IntelligenceIT Security & Assurance
Logica
Ecosystem OverviewLogica ERPLogica SpatiaLogica FlowLogica Visi
PortfolioInsightsApproachContact
TAN Digital · Enterprise transformation

Delivering Digital Advantage Where It Matters.

We design, build, and run the systems behind operational work — replacing brittle integrations, manual handoffs, and legacy stacks with software shaped to how your teams actually deliver.

ISO 27001
aligned engagements
OWASP-aligned
secure SDLC
National-scale
telco deployments
100+ cases
across 4 sectors
100+
Application cases delivered
2,500+
Active daily users
2019
Founded
4
Logica services
A glimpse · est. 2019

Beyond a vendor. A long-term digitalisation solution partner.

Most enterprise software pain is not a missing feature — it is the gap between systems and how the work actually moves. Aging stacks, manual handoffs, and dashboards no one trusts share the same root cause.

We close that gap by building systems around the operational reality, not the other way around. The work is mostly unglamorous: simplifying data flows, removing manual steps, and embedding the metrics that matter where decisions actually get made.

Our Journey

Progression of our capabilities and engagements

From the establishment of IT practices to industry-vertical AI implementations — a five-year arc of compounding expertise.

2021

Foundation

Provisioned website information services and custom web-based application developments.

2022

Modular ERP

Established modular ERP frameworks and business process validation for client demands.

2023

Spatial Insight

Implementation of spatial analysis using data to derive insights and tangible directives.

2024

Core Practices

Developed core practices for application delivery and software management services.

2025

AI & Diversification

Engaged with multiple sectors and added diverse propositions across AI & data capabilities.

How we engage

Off-the-shelf rarely fits how the work actually runs

Generic solutions tend to push the work to fit the software. Real systems get built the other way — shaped to how operations actually run, and not tied to any single vendor product.

What usually happens

Product-driven approach

  • Operations get reshaped to fit what the software allows
  • Workarounds pile up and quietly become new inefficiencies
  • Projects scoped to a written spec, not the real workflow
  • Features map to the vendor backlog, not to your business reality
  • Adoption stalls once the launch is over
What we do instead

A digitalisation solution partner

  • Systems built to grow with operations as they mature
  • Designed alongside your team — not handed over a wall
  • Active follow-through after go-live, not just a project sign-off
  • Specialised, proven, and portable across business contexts
  • Vendor-agnostic — anchored to outcomes, not product lock-in
Clients · Government & Industry

Trusted across Indonesia's most consequential sectors

From national telecommunications oversight to integrated mining operations and energy distribution.

KOMDIGI
Telkomsel
Mitratel
Telkomsat
PLN
ANTAM
Petrosea
What partners say

The work, in their words.

Three lines from the people on the other side of an engagement. Edited for length, not voice.

They didn't show up with a deck. They sat with our operations team for a week, then came back with a proof of concept that ran on real data. That's the difference.
Programme Lead Telecommunications · National infrastructure
What we got wasn't a system — it was a delivery practice. The AI pipeline still ships improvements every sprint, two years after the original engagement closed.
Head of Engineering Field operations · Telco towers
Most vendors translate compliance into binders. TAN translated it into a PR checklist that every engineer reads. That's the part that changed the culture.
CISO Application governance · State-owned enterprise

Real attributions available on request — anonymised by default per client preference.

Frequently asked

The things prospective clients usually ask before they engage.

Not everything — if your question isn't covered here, drop us a message and we usually reply the same day.

How does an engagement typically start?

Always with a 30-minute baseline conversation — no deck, no obligation. We use it to map the real situation: where existing systems hold up, where they break, and where intervention makes sense. If deeper work feels right after that, we move into a paid discovery.

How is working with you different from a traditional IT vendor?

Vendors ship a spec; we work alongside your team. The systems we build are shaped to how operations actually run — not the other way around — and we stay involved after go-live so adoption actually happens.

Do we have to adopt the entire Logica stack?

No. Each Logica track is modular and stands on its own — pick the one that fits the immediate problem, add others later without re-architecting. Most engagements start with one.

What does engagement and pricing look like?

It depends on scope. For discovery and fixed-duration builds we use a fixed fee. For longer-running team-based work we use a monthly retainer with a co-located team. After the baseline conversation we send a proposal that makes the trade-offs explicit — not a document you have to reverse-engineer.

Which sectors do you typically work in?

Telecommunications, energy, government, mining, and industrial services come up most often, but the approach isn't sector-bound — the underlying patterns (fragmented systems, manual handoffs, dashboards no one trusts) show up everywhere.

Who actually does the work — co-located or remote?

Engagement teams blend engineering, consulting, and domain expertise on a hybrid model — co-located when it matters (discovery, deployment, rollout), remote when it doesn't. We don't use tier-2 offshore or pass-through staffing.

What languages do you work in?

Bahasa Indonesia and English, depending on the client team's preference. Documentation, team communication, and workshops can run in either — or bilingually when it helps.

What happens after the system goes live?

We stay — at whatever cadence you need. Hand-over usually includes runbooks, a knowledge-transfer block, and a few weeks of monitoring. Beyond that, many clients pick up a retainer for ongoing evolution, because the way operations work keeps changing.

How we work

Locally-rooted engagements. End-to-end delivery. High-impact outcomes.

We work alongside your team — not from outside it — from baseline through whatever comes after.

Start a conversation See our approach