Blockchain
Smart contracts, tokenization, Web3 applications and digital-asset infrastructure, integrated with the rest of the stack.
We take blockchain work when there is a concrete reason: settlement, shared records, an existing on-chain market, or a product that already depends on those rails. The job is still engineering.
Architecture, security reviews, integration with existing ledgers and how the thing will be operated. It is one capability among others, not the identity of the company.
If the same outcome can be achieved with an ordinary backend and a database, we will say so. On-chain systems are not a default recommendation.
When this is the right work
There is a settlement, shared-record or existing on-chain constraint. Not when blockchain is being used as a synonym for new.