When Not to Build Blockchain Into a Business App

A chain is a product when several parties must share a record none of them can quietly edit. A CRM, a shop, and a staff app almost never need that. Adding “blockchain” to the deck does not make the spreadsheet a protocol.

CodeLoop Studio in Sarajevo builds operational software: custom CRM, web apps, mobile products. cijene.me compares prices. That is a database and a UI, not a public ledger. We will say no the same way we say when not WordPress.

When a ledger is the job

Multi-party settlement, a record regulators will audit across companies, an asset that must move without a single operator — those briefs can justify a chain, and they are rare in the work we take. We are not a web3 studio. We will not pretend a token is a business model.

Business process software in BiH is still Excel and WhatsApp for a lot of firms — business software in BiH. Replacing that with Postgres is the honest step. Replacing it with a consensus algorithm is usually theatre.

What we freeze

• Who must not be able to edit history. If the answer is “only our admin,” you want backups and roles, not a chain.

• Cost of being wrong. Gas, keys, and irreversible mistakes are product risk. We will write that down before anyone draws a wallet screen.

• Login is not a chain. Sessions are app authentication.

• No invented on-chain metrics. We will not publish TVL, token holders, or a client we do not have.

What we will build instead

A shop that checks out — ecommerce checkout. An MVP someone outside Slack can touch — MVP first version. Custom software with a named owner — custom software development.

Send the parties who cannot trust a single admin

If you cannot name them, you do not need a chain. If you can, we will still tell you whether we are the studio. Reply in 24 hours — online estimate or contact.