Are your sure its because of SQL Server and not application design or data model?

The timeout error could have been caused due to variety or reasons and not just SQL Server being busy

Some things to look at

• IIS Logs and Event viewer on the server where the application is hosted.
• Sql Server Logs to track down the error.Errors logs can be viewed  in SQL Server management studio, SQL Server Agent  last node "Error Logs"
• Run SQL profiler on your SQL/Storeprocedure to see which step is causing the timeout.
• Check the number of records in the table and the indexes on the table from where the data is being requested. 
• Check all connections in the code whether they are being disposed correctly.

Hope this helps