[chundicus]

I led a hackathon team in an in-person 24 hour hackathon, so it's not exactly the same but here's my advice:

- Getting people excited means giving a good elevator pitch and following up with any specifics you've mapped out. Tell them what you're trying to solve, why you're solving it, and how. Engaging with feedback/criticism of the plan will help get interested people on board. Make sure you try to match people's interests to the work to be done. I.e. assigning a backend-oriented person to do frontend work is a great way to kill motivation (unless of course they've requested it).

- For remote: make sure you have clear lines of communication and a clear delineation of work. Be available at a moment's notice to answer any questions.

-- a Slack channel (or something similar) for your team for ad hoc, asynchronous communication is a good idea

-- daily standups over video/voice would be a good idea. Make sure to take longer conversations offline as to keep everyone productive.

- As far as structuring the week that's harder to answer. Map out the work to be done, break it up by person, and then giving a loose timeline with some wiggle room. Something like a Gantt chart could help here, but there are a number of ways you could organize this.