The Adoption of Artificial Intelligence of SMEs in Davao del Norte: A Multiple Case Study in the Modern Business Landscape

Allocation at minting

The anchored record

Canonical JSON (keys sorted, no spaces, UTF-8). Its SHA-256 is the hash on chain.

{"abstract":"This study explored the adoption of Artificial Intelligence (AI) among Small and Medium-sized Enterprises (SMEs) in Davao Del Norte, Philippines. Using a qualitative multiple-case study design, it investigated the experiences, challenges, and coping strategies of five SMEs across diverse sectors: Financial Services, BPO, Transportation, Healthcare, and Construction. Data were collected through in-depth interviews with owners and managers, and analyzed through thematic and cross-case analysis. Findings indicated that SMEs primarily adopt AI to enhance operational efficiency, reduce errors, and improve customer service. They predominantly used readily available, low-cost tools such as generative AI, social media chatbots, and basic automation systems. However, significant barriers to adoption include high costs, a pronounced skills gap, data security concerns, and initial employee resistance. In response, SMEs developed adaptive strategies such as starting with small-scale pilots, relying on self-directed learning via online tutorials, and providing incremental staff training. Ultimately, successful AI adoption for SMEs depends less on advanced technology and more on a pragmatic approach with strong leadership support, focusing on solving immediate problems to ensure long-term viability.","abstract_source":"original","authors":["Philip Brobio","Mary Jane Amoguis"],"date":"2025-12-26","doi":"10.70838/pemj.510208","id":6985,"issue":2,"journal":{"issn":"2822-4353","name":"Psychology and Education: A Multidisciplinary Journal"},"pdf_sha256":"bf3915556c113155f1a87f0d2f0fcb889b18524d411a59171dc8a870fb9ce08e","schema":"scimatic-article/1","title":"The Adoption of Artificial Intelligence of SMEs in Davao del Norte: A Multiple Case Study in the Modern Business Landscape","volume":51}

Check it yourself

1. The record, from the token's own metadata:

printf '%s' "$(curl -s https://scimatic.org/nft/articles/6985.json | jq -r .canonical_record)" | sha256sum

2. The hash stored on chain (contentHash(6985)):

curl -s https://rpc.scimatic.net -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"eth_call","params":[{"to":"0x0E596B4bb924937aA35D9b342A90347ed6F05eF8","data":"0xf3e0c2900000000000000000000000000000000000000000000000000000000000001b49"},"latest"]}'

The two must be equal (the second with a 0x in front).