I suspect what you are wanting to do would be best handled with standard Dialog Workflow "waits", but to summarize some of your options:
You can use the Pause Execution component for very short delays, e.g. less than a minute. This component does not stop execution of the web request, and is vulnerable to timeouts. The example given in the help is, "You may wish to pause the execution of an email system for a certain amount of time in order to give your SMTP server time to catch up with the demand. You may use this component to pause execution of your process for a number of milliseconds." I'm pretty sure this component is available in any project type.
Or, you could use Pause Execution Workflow component for longer-wait times. This component is only available in Workflow-type projects (you won't see it in a WebForms project, for example). This component will put the process into Exchange persistence, and then the Workflow monitoring process will retrieve it when the specified interval is up. The interval is defined in minutes. Because it is managed by the monitoring process, you can’t guarantee the exact interval. For example, if the monitoring process checks every minute, then it could get retrieved in 1 to 60 seconds. This component is powerful because you can dynamically or statically set how long the pause will be, or simply when to continue the process. For your specific example, you could dynamically set the ContinueDateTime pause method to "continue" the process the day after the stakeholder meeting (which is presumably a date that you will already have stored in a variable). There are many components in the Date Handling category where you could take your original date/time and, say, add one day or one hour to it.
You may find it easier, though, to just use the built-in capabilities of the Dialog Workflow component to handle what you are trying to do. Dialog Workflow components will basically "wait" for somebody to come back into the process and continue it, e.g. someone needs to come back in and approve a request. I believe this is similar to what you are trying to accomplish. Your first Dialog Workflow component could be the Request for Change form. The second Dialog Workflow brings the PM to a form where he/she determines if it's a project or not. Once that is determined, you send out the V-Cal meeting requests. Then your third Dialog Workflow could send out an email to the PM with a ResponsePageLink that takes him/her back to a form, and on that form, he/she can click "OK" on a form that states that the meeting occurred (and maybe adds some comments or something), and then the fourth Dialog Workflow can handle the approval requests of the stakeholders. This is a pretty common example of using the capabiliities of a Workflow project type to handle long-running, multi-step, stop-and-start processes.
If you need specific assistance with how to use Dialog Workflow components, etc. just write back.