Read the client's real business need, then configure a working cloud solution: service model, deployment model, and characteristics.
Each client states a real business need in their own words. You are the architect: pick the service model (IaaS, PaaS, or SaaS), the deployment model (Public, Private, Hybrid, or Community), and every characteristic (rapid elasticity, high availability, metered usage, file synchronization, shared resources, VDI) the solution actually needs. Click Deploy Configuration to see what happens. A wrong service or deployment model has a real consequence: wasted infrastructure, a compliance failure, or a missing capability. Picking a characteristic the client does not need wastes their budget; leaving out one they do need creates a gap. Fix the configuration and redeploy until it is right, then move to the next client.