Inspiration
A new opportunity can sound exciting while taking its hours from something you already care about. I built GiveWay for the pause before saying yes: when a 12-hour commitment arrives in a full week, what would you give up?
What it does
GiveWay starts with a 168-hour week of named blocks. Add a commitment and choose where every hour comes from, including Free Time. Saving stays blocked until the trade balances exactly. Fixed and protected blocks cannot fund a proposal.
Compare two ways to make room. In the synthetic sample week, Plan A can fund a 12-hour hackathon with four hours from Free Time and eight from a Side project. Plan B starts as an editable copy: take all 12 hours from Study instead. Both plans use the same original week.
Choose B, and a Before → Tradeoffs → After receipt shows Study moving from 28 to 16 hours, Free Time staying at four, and the week still totaling 168 hours. The chosen plan is saved in the browser. You can revisit, edit, or undo it. You can also create your own baseline without an account.
How I built it
I used an AI coding agent with the Devpost Learn Skill Pack to develop a scope, PRD, and specification. These documents made the central rule explicit: every added hour needs a named source.
The app uses HTML, CSS, and JavaScript with no third-party runtime dependencies. Its calculations run deterministically in the browser, with no LLM calls. Half-hour units keep the arithmetic exact; localStorage holds the baseline and one active decision. Editing recalculates from the original baseline, so changes do not stack.
What I learned
A balanced total becomes useful when the person can see which commitments changed. The receipt keeps that cost visible after the decision, while the comparison leaves the priorities with the person choosing.
What's next
I would add a history of decisions and optional calendar import to help people build their baseline, while keeping each tradeoff an explicit choice.
Log in or sign up for Devpost to join the conversation.