Hi Sagar,

Already you have covered the core requirements like licensing, environment setup, security and etc. You can ask additional things a developer need from the client to start work with like 

• Project Scope & Requirements –  To understand the use case, key features, and expected workflows. 
• Existing System Details – Developer can ask If any legacy systems, existing OutSystems modules, or dependencies to consider.
• Test Data & User Accounts – Developer need some sample data and test user credentials for different roles. 
• Error Handling & Logging – Developer can ask logging strategy, monitoring tools, and error-handling approach. Compliance & Audit Requirements – Security policies, GDPR/HIPAA guidelines, and audit trails.
• Performance Expectations – Expected user load, scalability requirements, and performance benchmarks.
• CI/CD & Deployment – DevOps pipeline, release process, and approval workflows.

Hope its helps.

Thanks,

Sriyamini. J

I agree with Sriyamini on the rules for a large team. If you are working alone, this should be even simpler.

They are handling the license and creating the accounts and network connections, as well as a list of other connections and credentials you may need.

Then they need to provide you the specifications and probably some key users for interaction/testing/validation.

The rest is the guidelines on how you are supposed to work and expected deliverables.

If you are working time and materials, they may be more relaxed on those details and see as you go. If you have a deadline or are paid by the full product, you need to define all this at start to avoid problems.