Safety-first, Indonesia-native clinical AI for frontline healthcare. Meet NadiDesa →
AKSES Framework

The AKSES Scorecard

Five questions to test whether your AI product actually includes people.

The AKSES Framework is the inclusion stack Nelly Sutjiadi wishes every AI company would build before it writes a single line of code.

Humans remain in authority. AI remains in service.

Explore the Framework
The five constraints

AKSES means access. The question is: who does this truly serve first?

The framework evaluates inclusion as architecture: user assumption, participation cost, moment of support, measurable outcome, and human authority.

A

Anchor on the hardest user

Define the most constrained user first. Build or evaluate from that person's reality, not from the median user.

K

Keep cost out of participation

Cost is not only price. It includes bandwidth, hardware, confidence, time, literacy, trust, and fear of mistakes.

S

Serve at the moment of need

Support should appear inside the real workflow, in the user's language, at the exact moment a decision or action must be taken.

E

Engineer concrete outcomes

Inclusion must connect to a measurable outcome: income, safer care, clearer decisions, stronger livelihood, better learning, faster access, or real opportunity.

S

Safeguard human authority, with AI in service

AI should help people serve more people with greater consistency, context, and care. Human judgment, accountability, approval, and care must remain visible where they matter most.

The AKSES Scorecard is not a marketing worksheet. It is a design mirror.