The cost of a smart contract depends on the behavior that needs to be implemented, the complexity of permissions, integrations, and the desired level of validation. A simple issuance function does not require the same effort as a system with multiple roles, redemption rules, and external dependencies.
The network chosen also affects the project, but it should not be treated as the only factor. Development tools, test environments, monitoring, documentation, key management, and operational support can be just as important as transaction costs.
A responsible estimate separates discovery, architecture, development, testing, review, deployment, and follow-up. When the scope has not yet been defined, the first investment may be a technical assessment to reduce uncertainty before preparing a budget for the full implementation.
There is no universal price or automatic relationship between cost and security. The budget needs to document assumptions, limits, deliverables, dependencies, and what will be outside the scope so that comparisons are possible.